|
|
|
|
|
|
by j-pb
1022 days ago
|
|
|
Because the compiler is extremely unfinished and buggy. With a codebase this size theres a real chance of having miscompilations in there. What's the points of running a safe language on broken infrastructure, it's garbage in garbage out. And with Zigs recent plans to replace llvm with their own backend I'm not even sure if they won't continue scope creeping into vapourware. |
|
|
You burn those CPUs in. You run them a bunch. Measure them. Measure their efficiency gains. If the gains are real, make a plan for scaling them up. Have fallback plans. The usual stuff. If a company has someone that does this as their job, they're on it.
If Bun affected your source code or development process, I would understand this perspective. Maybe don't use Bun-specific APIs yet, and just stick with the Node compatibility.