HN user

drowsspa

771 karma
Posts0
Comments324
View on HN
No posts found.

Would be nice if people published the prompts, thoughts and responses of the LLMs together with the code, in order to fight against these restrictions... Instead of just publishing the final result and talking vaguely about how they prompted the LLM in a Hacker news comment or Twitter thread

If LLMs are the new compilers those are the actual source code

That's not how it works. Two bodies are in thermal equilibrium if there's no heat transfer between them: that's the zeroth law of thermodynamics. If you're colder than 2.73K in deep space, you will absorb the heat from the Cosmic Microwave Background. If you're hotter, you will irradiate heat away. So it does have a temperature.

I find it amazing how much the mess that building C/C++ code has been for so many decades seems to have influenced the direction technology, the economy and even politics has been going.

Really, what would the world look like if this problem had been properly solved? Would the centralization and monetization of the Internet have followed the same path? Would Windows be so dominant? Would social media have evolved to the current status? Would we have had a chance to fight against the technofeudalism we're headed for?

Stunnel 6 months ago

That's basically the idea behind zero trust, isn't it? The idea being that you can't even knock on the TCP port if you're not authenticated

I guess we'd have to see the graph with the evolution of paying customers: I don't see the number of potential-but-not-yet clients being that high, certainly not one order of magnitude higher. And everyone already knows OpenAI, they don't have the benefit of additional exposure when they go viral: the only benefit seems to be to hype up investors.

And there's something else about the diminishing returns of going viral... AI kind of breaks the usual assumptions in software: that building it is the hard part and that scaling is basically free. In that sense, AI looks more like regular commodities or physical products, in that you can't just Ctrl-C/Ctrl-V: resources are O(N) on the number of users, not O(log N) like regular software.

4. The community seems to have realized that untangling the mess that is building C/C++ stuff is a fool's errand and seems to mostly prefer to reimplement it in Go

Sure, you can't get rid of everything. But you can mitigate a few things, and closing the door is such an easy fix... There's worrying too much, and there's not worrying enough

NodeJS, Ruby, etc also have this problem, as does Go with CGO. So the problem is the binary dependencies with C/C++ code and make, configure, autotools, etc... The whole C/C++ compilation story is such a mess that almost 5 decades ago inventing containers was pretty much the only sane way of tackling it.

Java at least uses binary dependencies very rarely, and they usually have the decency of bundling the compiled dependencies... But it seems Java and Go just saw the writing on the wall and mostly just reimplement everything. I did have problems with the Snappy compression in the Kafka libraries, though, for instance .

People are mostly sympathetic when it's physical issues. Psychological issues are treated as diseases of the soul that you only need God or willpower or whatever to fix. And most fat people are fat because of the incentives in our society, but admitting that also goes against certain political ideologies...