Schizoid personality is not a "disorder".

Having your own ideal and philosophy and not sheepishly following corporate and government propaganda (so called "trend") is what every other person should do.

I tried wayland multiple times before, but the lack of xsct equivalent and the awful input delay (compared to X11 window managers without compositor) made my experience very frustrating. Some might say "it's just a one or two frame delay", but for me that makes a night and day difference. Just an additonal frame delay gives me a feeling of driving a 70s American boat car with worn out tires.

Clippy was the Copilot from the late 90s: A pointless annoying gimmick that disrupted everyone's workflow.

The coconut death claim is an exaggerated lie. From the Wikipedia article (https://en.wikipedia.org/wiki/Death_by_coconut):

"In his paper, Barss observed that in Papua New Guinea, where he was based, over a period of four years 2.5% of trauma admissions were for those injured by falling coconuts. None were fatal but he mentioned two anecdotal reports of deaths, one several years before. That figure of two deaths went on to be misquoted as 150 worldwide, based on the assumption that other places would have a similar rate of falling coconut deaths."

Stop referencing Twitter posts. The only thing I see in it is a popup that I should sign up for their platform.

You can use xcancel.com or farside.link's nitter redirect to avoid that, if you're on Android it's easiest to use URLcheck‡ with these chunks added to the pattern checker:

``` "Twitter to Nitter": { "regex": "^https?:\\\/\\\/(www\\.|mobile\\.)?(twitter|x)\\.com\\\/(.)", "replacement": "https:\/\/farside.link\/nitter\/$3", "enabled": "true" }, "Twitter image to Nitter": { "regex": "^https?:\\\/\\\/(pic\\.twitter|pbs\\.twimg)\\.com\\\/(.)", "replacement": "https:\/\/farside.link\/nitter\/pic\/$1", "enabled": "true" }, ``` (I haven't updated my copy of the Twitter image regex for the rename because I haven't seen any X.com image links and upstream seems dead)

‡: https://github.com/TrianguloY/URLCheck

Even more annoying when the twitter post in question is literally just a screenshot. Put it in the blog post.

It still hides your cursor though.

This is not about "lack of humanity", but about violating fundamental UX rules such as hiding your cursor at random times. It's offensive.

You don't have to sacrifice usability while expressing personality.

I barely noticed it. The complaints I've read about it are making a mountain out of a molehill.

You get the said 10 year old chip cheaper, with lower power consumption and smaller physical size, on newer and improved fabrication methods.

Yeeeeaaaah... that's not how that works. Legacy processes are often difficult or impractical to transport between fabs at the same node, much less fabs at different ones.

GP is saying you get the same functional performance as older chips for less size, power, and cost. Nobody makes main processors in 22nm anymore, for instance. That’s basically what was used in production 10 years ago for processors.

Nobody makes old processors (except for legacy support) because Moore's law has been a thing for 50 years. It has always been cheaper to produce chips at scale with the latest tech. This has justified the creation of 10 billion dollar factories, till recently

Now that the law is close to coming to an end, the economics changes. Latest tech provides negligible marginal benefits to the median consumer. So now it is possible to think of commodotizing a single process and making the factories much much cheaper.

>> Nobody makes main processors in 22nm anymore, for instance. That’s basically what was used in production 10 years ago for processors.

Raspberry Pi would beg to differ.

'Main processor' meaning the SoC used in a modern high performance device. Phones, tablets, or computers.

Plenty of lower power or older stuff (RPI included) use older nodes just because that's available. Microcontrollers tend to use higher nodes (22, 40, or 55nm) just because they don't need the super high speed stuff.

Also, the RPI5 uses 16nm, not 22nm. Still not modern, but not unheard of for stuff like SBCs where performance is not particularly important compared to cost.

No, GP is saying 'you get the same chip' but on a different process node.

You don't, pretty much. Exceptions exist, but not when it comes to mixed-signal processes.

People do that too. Fab ports to smaller nodes are something that absolutely happens, especially as older legacy nodes close down. It happens all the time.

I don't think machines should rely on an opaque logic to assume and "correct errors" on user input. It's more accurate to "fail" than handling out an assumed output.

And also:

> they need to supply ones specifically engineered to be uncorrelated with the right figures.

I assume most people will understand this way (including me) when it's said to "input wrong figures".

That Russian word had a useful information. It means "contrast", and that obviously implies "Increase the contrast to reveal the secret message".

It also reads KONTRAST, you don't even need a dictionary or google translate ;)