esa

But what did you learn? What are we supposed to learn? Did you get any context, like how he actually went to anger management therapy later?

Or is this just guffawing and gawping at an old angry email from a tech celebrity?

This mail is 13 years old, and doesn’t seem relevant for anything? This post seems like a lazy attempt at shit-stirring.

Yeah, JSON is essentially a side effect of having JavaScript already. It makes sense that it shows up a lot of places, especially web. But just like with JS, it’s not really good, just ubiquitous.

I’ve very barely dipped my toes in dbus before, and the option to have something else is on its face attractive (not a fan of XML and the late 90s/early aughties style of oop), but JSON for a system interface?

I mean, Kubernetes shows that yaml can work, but in this day and age I’d expect several options for serialisation, and for the default to be binary, not strings.

String serialisations are primarily for humans IMO, either as readers or writers. As writers we want something with comments (and preferably no “find the missing }” game), so for that most of us would prefer something like TOML if the data is simple enough, and actually Yaml for complexity at the level of Kubernetes—JSON manages to be even more of a PITA at that level.

But machine-to-machine? Protobuf, cap’n’proto, postcard, even CBOR should all be alternatives to examine

Yeah, it’s the kind of thing that in utopia would actually help search engines and users find relevant pages, but under capitalism becomes “hey, listen! look at me my ads!”

Not memory safe, so runs into exactly the same regulatory problems that are driving people away from C in the first place.

It seems to be fun for an individual with a hobby, but I wouldn’t really expect it to get much into professional spaces.

Yeah, I think my sway config is around five years old now. The Wayland experience hasn’t been entirely without warts, but as someone who kind of just uses the desktop to drive a browser and a bunch of terminals, there’s not a whole lot of problems to run into either.

if the process is just “wrong, do it again” without examining any piece of it

that’s the definition of vibe coding. It’s a process where you’re supposed to work as if you don’t know how to code and treat the code as magical mumbo-jumbo.

no, my point is that “vibe coding” is explicitly about not using your head and just going by “vibes”. It’s innately an excuse for shit code, because you’re not supposed to look at the code at all.

If you’re looking at the code and reviewing it, you’re not doing “vibe coding”.

I think you’ve mistaken me for some LLM slop enthusiast. I’m not.

Encourage “vibe coding” and you’ll drown in slop and ignorance.

Yes it is? That’s exactly what it is

IDK, I’ve mainly used the lspconfig plugin and haven’t really had problems in general, but some LSPs seem weaker than others

It turned out to not change much in practice for end users I think. We still want the lspconfig plugin for default settings for the most common LSPs, but setting up without it should be more straightforward. The lspconfig plugin will also be transitioning to the new configuration method.

Yeah, I’ve met some elderly with absolutely no practical sense. One wonders how they manage to tie their shoelaces (they probably don’t). The world must be a lot more mysterious to them than to people who fix most of their own shit.

If ssh has a security issue and you permit root logins then hostiles likely have an easier time getting access to root on the machine than if they only get access to your user account—then they need multiple exploits.

Generally you also want to be root as little as possible. Hence sudo, run0, etc.

I used Ratpoison for well over a decade, and only replaced it with sway once I had a new machine and figured it was time to try Wayland. Apparently that’s some 4-5 years ago already.

DAP stands for Debugger Adapter Protocol or something close to that. My impression is it’s pretty much the debugger variant of the Language Server Protocol (LSP).

Been looking forward to try the new LSP configuration method!

Leaking isn’t really the issue, though I suppose Rust helps with that as well. Its memory sales pitch is more about memory safety, which is not reading or writing the wrong parts of memory. Doing that can have all sorts of effects, where the best you can hope for is a crash, but it often results in arbitrary execution vulnerabilities. Memory _un_safety is pretty rare and most prominent in languages like C, C++ and Zig.

Rust also has more information contained in it, which means resulting programs can actually be faster than C, as the optimizer in the compiler is better informed.

Rust is already in the kernel and Torvalds wants more, faster. He’s being obstructed by C purists, who at this point are the people who should fork the kernel if they see anything but C as heresy.