Untitled attachment

Notices where this attachment appears

1. Terminal Autism (terminalautism@social.076.moe)'s status on Sunday, 08-Jan-2023 02:17:07 JST Terminal Autism

   in reply to
   Yes, I thought about Icecat, but it's not really all that fair to blame that on them, it's still just Firefox. They just forked it and made it meet the FSF's standards, so none of the bloat comes from them.
   
   The GCC vs tcc thing is because tcc is made to be as simple as it can be, while GCC is made to be an highly optimizing compiler. The more you optimize, the slower it is to compile, by necessity. Of course, there is a balance there, and optimizations are less necessary the less bloated the software is. I think Terry's approach for HolyC was actually more in line with tcc's, and look at his OS. It boots in an instant even though it compiles like, half of it, right as it boots, and it doesn't need all of GCC's optimizations because the software is simple, so in a compiled language, it will be fast pretty much no matter what.
   
   Also, if I called Emacs a development environment, it was a mistake, I meant to say computing environment. Anyway, Emacs is really in just the right position to make you ask "what even is an operating system anyway?", just like Lisp in general does, and also Forth. Languages like that are so powerful, and you can run them on bare metal, and if you do... are they an operating system now? PilOS ( https://picolisp.com/wiki/?PilOS ) is basically just PicoLisp running on bare metal, and it has OS in the name. What if you put that in a ROM chip, would it still be an OS? If a computer has a BASIC ROM chip, and BASIC is the interface between you and the hardware, is that an OS?