💾 Archived View for bbs.geminispace.org › u › norayr › 21838 captured on 2024-12-17 at 15:51:19. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "there was a famous research, and they repeated it once [..."
i recommended go in the other thread because it is easy to compile. and even without google, it's not that hard to write a go compiler - syntax is not big.
as i said the compiler itself builds in 2 minutes.
rust is also not perma for me. as i mentioned in that thread, i cannot build it on my pinebook with 4gb memory and zram enabled, but yes, i can build it on 11th generation intel, and i have to wait i think more than a day for that. don't remember, but certainly a lot.
by my assessment it's not perma at all.
and plain c, without extensions, yes that's perma. we can implement a compiler. just we won't be able to compile linux kernel with iso compliant compiler. (:
Nov 16 · 4 weeks ago
can any modern language like rust, go, nodejs, python etc... that rely on git or some native module infrastructure to be in place be considered permacomputing compatible? I mean with go and in some other cases I guess you could potentially host a local module repo but then you're adding the management and hardware overhead.
What about the vast and varied toolchains depending on which projects/environment s you want perma-available? make (BSD/gnu?), ninja, meson, git, all the shit you need for Android?
I reckon C and Assembly or perhaps something like Forth targeting a CLI environment on limited hardware are probably the best options.
🐙 norayr [OP] · Nov 18 at 11:43:
i just want to say, as always, sorry i have one lp i always play, and that's:
also, c in gcc contains lots of crap, not just iso c.
there was a famous research, and they repeated it once [gemini link] pareto optimal sets for different combinations of objectives [https link] assessing the energy efficiency of programming languages [https link] the paper