HN user

zcw100

1,683 karma
Posts0
Comments453
View on HN
No posts found.

People need to stop yelling "Slop!" all the time and saying silly things like "every line of code was reviewed by a human". First, it's ridiculous. There is no possible way to verify that claim, determine what was or wasn't done after reviewing it, and there's no reason to review every single line. It's performative. I have a ton of stuff I haven't bothered contributing. Why? So I can deal with all the hate? When it was "many hands make light work" there was value in sharing the load. Now I've got a backhoe and it's not worth the hassle.

A large number of logically irreconcilable perspectives (in one's own mind) is the precise definition of cognitive dissonance. You also say that I may be building a straw man without even trying to point out where you think I've done that. You've already conceded my argument that there are many competing perspectives and I make no attempt to poke any holes in that so there is no straw man.

I'm done. The cognitive dissonance over AI has jumped the shark. It's not fair that it's everywhere. It's not fair that only a few have it. It's not fair that it uses so much electricity. It's not fair that it's killing my environment. It's not fair there's a datacenter in my back yard. It's not fair there isn't a datacenter in my back yard. It's not fair that it threatens my job. It's not fair that my employer doesn't give me access to AI.

I've always loved the original work and it's nice to see they're still working on it. I've always wondered if there was a way to connect this back to infrastructure rather than images. Something you could run on a cluster and if portions of it failed it would regenerate the system.

Like a bio inspired Kubernettes.....Bionettes.

"no single „this is what this project is” anywhere in the repo description, readme or docs. "

That sounds like he read through the docs to me and make a perfectly valid observation that that the maintainers might find valuable. He didn't criticize them for not doing it he just pointed out that it wasn't there. You then told him to RTFM when you didn't seem to spend much time reading what he had written.

You don't need to write platform-specific code if you use some cross-platform framework. For simple programs it may be enough to use only the standard library of your language of choice.

That's a circular argument and "some" is doing a lot of work there. What cross-platform framework would you be referring to?

It has little value. Compiling a separate binary for each OS isn't that hard, since only a handful of architectures and operating systems are actually in use. Using an abstract cross-platform binary (like WASM) in the other hand adds extra performance costs and other user-side overhead, which isn't strictly necessary.

It my have little value to you but that doesn't mean it has little value to everyone. I don't agree that compiling to multiple architectures is without difficulty and restricting yourself to only popular ones proves the point. What specific "other user-side overhead" would you be referring to? Lots of things aren't strictly necessary, that doesn't imply they're not necessary. Yes, there is a performance cost. Sometimes that cost is worth paying.

This is just like when Paypal got started and was basically operating their own bank. Good luck doing that without getting in trouble. This is selling pharmaceutical drugs over the internet. You're playing chicken with going to jail they just happened to get lucky.

I suspect that we are going to see managers say, "Hey, this request is BS. I'm just going to get ChatGPT to do it" while employees say, "Hey, this response is BS, I'm just going to get ChatGPT to do it" and then we'll just have ChatGPT talking to itself. Eventually someone will notice and fire them both.

"What would you say you do here?" --Office Space

Many technical directions in the past 15 years have been a thinly veiled attempt to actually get paid for doing work.

I'm usually pretty good at explaining new technologies to people but WebAssembly has got to be the most difficult to try and explain. The sheer number of misunderstandings about it is amazing. Luckily the misunderstandings serve my purpose for right now so I'm glad to see all the noise.