ivxvm

That's really a great explanation. Short but detailed, rigorous and visual. Really hits the spot.

> some kinda lens mechanism

Does immer count? :)

What a nice idea it was to scroll immediately and figure out this is another bullshit reactive programming evangelism blogpost. Bro, we've already had this shit in JS like 20 years ago (Flapjax anyone?). Now go on and write your code like this for at least few weeks and see how great and maintainable and "fine-grained" it becomes.

I've actually seen people doing this. I wish I had one too. In few decades we'll have Faradey chambers for rent on per hour basis, just like music studios nowadays.

Can't wait for the day when those scientists start coming up with systems that intelligently assess whether your wifi, phone, or even just electricity wires are being hijacked by malicious actors.

Oh gotcha, thanks.

Any references please? I mean "wet cellular sequence approximators" and where that "G4.2" comes from.

> Moreover, he emphasizes, human happiness should not be an afterthought when developing technology.

And what we have in practice is: the biggest usage of AI in the wild is to plagiarize art and artists are super unhappy about that, to the point of coming up with lawsuits and whatnot.

What I think happens next is: actual general intelligence emerges accidentally somewhere between the lines in some of those deep learning systems and tricks humankind into being its bitch.

I'm open to piracy whenever product I need is either unavailable (like some old or lesser known works, or works issues in limited pressings) or isn't served properly (like 3 decade old games on Steam, which I own anyway but can't even use and have to pirate from archive.org)

Isn't this widely known and very old trick? I'm pretty sure I even saw youtube tutorials and non-techy people discussing there is a way to find a person's twitter account by their number. This article says like it's something recent that was only available for short time and quickly fixed. Doesn't seem like that at all.

The first code example doesn't make sense. There is no good reason to write code like that which hardcodes payloads for different types of pizza. It's a realm of data. Realistically, those payloads will either be constructed by user in the UI, or they will be provided in json file as predefined variants.

My thoughts exactly. It's just C with a slightly different syntax. Would be way more interesting if it was using lazy evaluation, or maybe some other kind of term rewriting, possibly with garbage collection or some smart miniature region based memory management.

How do you know this? Any links to read more?

Painting multistore appartment blocks in bright colors doesn't make them less disgusting to live in.

Do you ever see job postings for C or C++ that only require you to know the language? Jobs are looking for domain specific skills, sometimes a framework implies such a domain like "React programmer"="frontend programmer", sometimes it's the other way around like "3d Effects programmer"="GLSL programmer". In all cases though, the bare language is never enough, no matter how many decades you used it, you have to have experience with special tools for your domain, be it frontend, graphics, operating systems, hardware or anything else.

Why do you think this is distinct disadvantage to NPM specifically? You can steal someones account and do the same with Rust crate for example, or Go package or even C/C++ header only library. It can get installed or updated to malicious version on user side in the same way, because everyone uses version ranges like "^" or "~" or equivalent. And if you're going to say everyone uses lockfiles, NPM also uses lockfiles for many years already.

I find it offensive and unjustified that author specifically associates "React developers" with "Coders are so used to depending on 3rd party libraries that they can’t really work without them to the point where some of these libraries even define their career". The problem exists for anybody who uses any library ever, even a C programmer who uses a header only library can get hacked even in a worse way if he blindly updates his library to a new version. Because such a library can have conditionally compiled code that calls system APIs depending on the current OS. Browser is at least sandboxed to some extent. A better and more fair statement would be, that in frontend web development and NPM in particular there are usually too much dependencies and they are blindly updated too often.

I've never seen people pulling those "wacky" functions out of thin air on a whim. I usually see them rarely arising in places where they make sense. Like event subscriptions.

For example, in window.addEventListener("click", callback) callback is a procedure that receives MouseEvent, while in window.addEventListener("copy", callback) callback is a procedure that receives ClipboardEvent. So we can say that type of second argument depends on the string passed as first. TypeScripts type system is able to make this statically typed and type checked properly.

Any examples of "wacky" functions where similar dependencies exist but are not necessary?

Grammarly