Looking back, I wonder what really changed over 25 years for the linux ecosystem. We had lots of distros, there were games built for linux (I remember playing the entire Neverwinter nights on debian) there was wine for StarCraft broodwars, x11+compiz for cool accelerated desktop graphics, proprietary Nvidia drivers were always there. Sure, everything was 32bit but it was good enough for desktop, and amd64 was about to pop.

The other day I tried to install fedora 44 on a friend's computer. He wanted kde so we set that up and whoops, no way to start programs on the discrete video card. I hacked around it by starting xorg, setting an alias and environment variables, but it was a bit embarrassing to see that things have regressed.

I'm not going to downplay it. I've been coding since the 80s and using these models since 2023. 10 minutes after using fable I told my colleague this is a new era. It is the difference between sonnet and opus. I didn't think this was possible.

It was over before this announcement. After a couple of days, even though the model was set to fable, it felt like opus. We are back to sticks and stones.

Sometimes it is ok to sit there in confusion and ask the user to clarify rather than go on an adhd fueled rampage to figure it out without asking.

Yes!

Claude is THAT team member who will go to any length to answer a question…except ask another team member for help.

Best comment in this thread

What do you mean by water fasting? Do you avoid drinking water directly, or do you avoid all food? For example salads are basically sacks of water.

Water fast is when the only intake is water (plus electrolites and vitamines). Basically "eat nothing".

> Basically "eat nothing".

Thanks for this, reading "water fast" and "3 days" gave me a shot of adrenaline. The "water" prefix is just confusing, the word for abstaining from food is just "fast" for those interested.

If this is engagement bait, then well played..

It is a specific type of fasting. Saying only "fasting" can mean a lot of things, saying "water fast" means you only drink water.

https://en.wikipedia.org/wiki/Fasting

Fair enough, thanks for sharing

Water fasting is used to differentiate from dry fasting, where you don't even drink water.

Is this even a thing? Never assumed you'd ever want to dehydrate like this on purpose. Just why?

dry fasts aren't always what they appear. if you have significant glycogen stores in your body as you begin your fast you wont be dehydrated for the first day or two as water is freed. what usually happens is someone who starts glycogen endowed discovers that they aren't thirsty when they start fasting and tout it as dry fasting.

Ok glycogen store was the only possibilty I has in mind. Thanks:)

Religious Jews have a couple of 25 hour complete fasts per year.

Look up how Muslims fast during Ramadan.

What you thought of (not even drinking water) is called a dry fast. It is a thing, but for obvious reasons is much more intense and shorter in duration.

no you only consume water

I also run a Qwen 3.6 moe A4B on old hardware. I set it up with

numactl --membind=1

so it is constrained to one of the memory sticks which speeds up token generation a little.

Learning some schmuck's framework, IDE, language or OS never felt rewarding to me. It was always like playing with broken toys. Hear me out.

There was always some subtle quirk, a bug that irks me once every so often, something I'd never want to unleash upon masses and although these people made their work available through various channels, paid or unpaid, for some reason I felt more of a grudge than gratitude.

And I tried to fix things I did. It was a breathless, thankless exercise of working through someone else's code line by line for decades while hardly being able to lift my head because of actual work I had to do to support my life. And thus a villain was born.

I am so glad it is over. It is all ingested into neural network weights and high-pressure sprayed to the masses through RNG. I am finally free. I don't have to learn your stupid aws commands, your helm configs, your systemd antics, your http api. I don't have to care about your life times, your gc params. I tell the computer and it clinks and clanks and eventually gets the job done like gene rodenberry intended.

To be fair, nowhere on the frontpage does it say it can build libraries that depend on node. It seems like you are just waiting in the bushes to dis AI assisted coding.

And it was so much better/more stable than Borland C++6! Open/close 15-30 files or mistype a path and borland gave you the good old crash. You had to handle that IDE with extreme care. You'd develop a feeling for its quirks and sometimes it would work for hours without crashing.

I loved react in 2013 when it had the life cycle methods. Everything was deterministic, I knew what caused what where and when. Now every framework is a mess and I'm glad I won't have to learn anyone's crap anymore thanks to random code generators.

I lived there idea of hooks when they were introduced.

But they’ve honestly not worked out.

React works have been a lot better if the React team has figured out what useEffect was supposed to be right at the beginning, or at least when they changed what it was supposed to be used for they documented that clearly instead of gaslighting devs into believing nothing has changed.

Also, hooks aren’t a thing. Each hook is its own API and concept. Grouping them under the umbrella term “hooks” gave the wrong impression that it was a single concept, but there’s No conceptual similarity between ushered, useState or useEffect. The only similarity are the restrictions on their use and nomenclature.

In every single project I worked on using Next.js as a kind of full stack framework, eventually I need to do something on the FE as well, and end up debugging a spaghetti of useSomething() until I figure out where to actually implement what I need.