Earlier quoted context omitted.
Since the LLM craze started I have always assumed it would end up in a place where programming languages are dead and LLMs generate something more low level. Programming languages were always designed as an abstraction to allow humans to more easily instruct a computer than by writing binary or assembly. If humans write natural language and don't check the generated code, there's no reason to take the hit of generati…
If anything LLMs should use something higher level because it compresses the context and makes programming closer to natural language they are trained on. Forcing LLMs to do a shitty job of what a compiler can do deterministically is not a good approach IMO.
Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
701–710 of 754 posts
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#702Earlier quoted context omitted.
LLMs have no conception of time, unless you explicitly feed in timestamps to the context
It doesn't stop LLMs provide "this feature set will require 4 months to finish" (and then finishing it one hour)
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#703Earlier quoted context omitted.
zig is unmanaged memory. But rust also allows memory leaks, and they're not uncommon in large, complex programs. So this rewrite will not necessarily control for that.
What language doesn't allow memory leaks?
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#704Earlier quoted context omitted.
I’ve struggled to get Opus to not write the weirdest possible Rust, ignoring all idioms and so on. Any tips?
Be absolutely ruthless with technical debt. Opus is perfectly capable of producing idiomatic code in any mainstream language you please, but will seize on any opportunity to justify writing basically-python instead because that's "consistent" with the "convention". Deprive it of that excuse.
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#705Earlier quoted context omitted.
> Also their feelings are not hurt by what you or I think, they don’t care. Definitely not true, they tend to care more than most.
They generally care about what powerful/influential people think. I’m not powerful or influential, but I guess maybe the person I was talking to is. If so I apologize for the miscommunication.
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#706Earlier quoted context omitted.
> they are not governed by multibillion dollar companies Every tech you mentioned is absolutely governed by multibillion dollar companies. Something like 75-85% of OSS code is contributed by employees doing their day job. Most Linux and Postgres contributions come from those same employees. HTTP and TCP/IP are managed by standard bodies and industry working groups that, you guessed it, are governed by multibillion do…
The usual model for OSS projects is that initially they are written for free. Then an inner circle forms and exploits the second generation of idealists who write entire large features without ever getting the same rights. Some of the inner circle move to corporations to increase their power and are joined by corporate developers (sometimes their bosses) to take over the project. A lot of corporate OSS development ar…
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#707Earlier quoted context omitted.
I have seen, many times, code that has lots of tests but don't work. Why? Some of the patterns that I saw: * The code is only called from tests but never called in production * Tests are not testing the actual application logic, or the logic that matters. In some cases, the tests have nothing to do with the application code at all, because it does not even run any application code. * Tests repeat the same logic as in…
I think you and I don't share what is a "test". Are you thinking about unit tests? I'm thinking about unit tests, smoke tests, integration tests, e2e tests, functional tests, manual QA tests and probably even "the-product-works-as-expected-as-I-can-see-from-the-amazon-reviews-of-our-clients tests". I agree with your point of view in general, but "having tests" doesn't mean "having great tests". If I rewrite my code a…
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#708Earlier quoted context omitted.
But usually companies are much more careful before even spending that half a million. (And most companies don't have that money sitting around.) They would do small PoCs, do comprehensive benchmarks and evaluations of those PoCs, and decide whether to actually go ahead, and, more importantly, stick to it. Being able to afford half a million doesn't mean you do it on a whim, or just throw all of that away if things do…
> They would do small PoCs, do comprehensive benchmarks and evaluations of those PoCs, and decide whether to actually go ahead Perfect, $1mil in salaries to spare the company $500k in spend :)
Nobody is spending $1mil in salary on this kind of PoCs.
And I guess the word "small" is really difficult to grasp.
Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#709Re: Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
#710Earlier quoted context omitted.
> they are not governed by multibillion dollar companies Every tech you mentioned is absolutely governed by multibillion dollar companies. Something like 75-85% of OSS code is contributed by employees doing their day job. Most Linux and Postgres contributions come from those same employees. HTTP and TCP/IP are managed by standard bodies and industry working groups that, you guessed it, are governed by multibillion do…
The way I understood op is that we don't necessarily have to pay to use linux or postgres (when self hosting, for example). But we have to pay to use claude code... which sucks big time (also, open source models are behind private models)