I guess if your joy is outputting a lot of stuff. It’s really satisfying to actually learn things and we know llms disrupt the learning process.

What ever happened to challenging oracle’s trademark over “JavaScript”? It sounded like deno was putting up a good fight for a case of trademark abandonment.

Yeah it’s all by design. I hate this framing around anything critical where we’re expected you tie ourselves into knots to protect the status quo. “What if we made it instructive” that will still cause problems and like that would ever happen in the first place.

A really sad ending for deno. Spent a lot of time trying to get my team at work to consider deno instead of nodejs. The writing’s been on the wall for a while but now it’s officially over. Also I guess this means bun won?

Can you really know your enemy if your enemy doesn’t have an actual agenda besides maximizing user retention?

This plus a few “petah”s and you’re set

Connecting on a community like this (with at least the intent) of having actual human responses is a good first step. For the sorts of questions about what to do in life keep exploring why you’ve had bad human interactions and see how you could lower the chance of that happening. For the coding try accepting that very likely you’ll make mistakes or do things in a non optimal way for the first pass. Think of writing code like writing a rough draft don’t worry about big o etc. Focus on building an understanding and mentally model rather than producing an output (read: source code). AI gives you output and brain chooses lazy way to reach the goal.

Think of non AI code production like a woodworker that can read a piece of wood knows where the knots and the unexpected grain direction c changes are and uses that understanding to make something. Maybe what they set out to build wasn’t actually feasible. Compare to an ai it’s more like a factory it will make cuts right on knots etc. All is focus on output with the inputs at any cost.

Software raid 0 with btrfs will make the two drives one but I have no idea how that works if you are still going to have separate encryption keys and params for the second physical drive. If they have the same encryption it should be possible to have the device mapper write to the software raid.

Rip dia

lowers barriers to adoption of the language and its ecosystem

Two things: this is phrased as if each change by another developer ruins your theory of the codebase. This is an oversimplification. Changes to the core engine of the codebase can change the theory of the product but many changes are cross cutting concerns. This is why new developers on large codebases are commonly assigned integration work. You develop a theory with a real lower stakes output.

Second the llm thing. Putting aside hallucinations you could get a start of a theory from an llm but you’ve conditioned yourself to be reliant on the llm. To put things in similar terms of tech job stuff like this article does: prior to llms most teams had at least one SME on the whole codebase. They’d get bombarded with questions and if you had any politeness you wouldn’t bother them with every single question about the code or product as a whole. Occasionally you would need to but there was a natural social forcing function to figure stuff out on your own. Llms are the complete opposite: they tell you “good question” “good insight” etc. brains like short cuts so now there is no forcing function.

Like many other social media sites it’s partially network effects.