kragen

11 ms·

121.
by kragen 10mo ago
I don't think they needed improving in order to continue accessing the existing sites that still used them. Also, you may not have noticed this, but you're commenting on a thread that's largely about PETSCII and Videotex. For
122.
by kragen 10mo ago
That's true of Discord, but it's not really true of deploying your own CA certs.
123.
by kragen 10mo ago
Hopefully the people after us will spend some time enjoying the things we have left to them; if they dedicate all their time to creating things that will outlast them , all our efforts will have been wasted.
124.
by kragen 10mo ago
Sixel support unfortunately came to terminals in 01988, as that page explains. I saw it myself in 01992. Sending uncompressed color raster data over a 9600-baud serial link again every time you wanted to look at it was a terrible idea, ma
125.
by kragen 10mo ago
Viznut has made a shitload of amazing things: https://www.pouet.net/user.php?who=2547
126.
by kragen 10mo ago
Seems related to the discussion the other day of Unifont, which is an 8×16/16×16 Unicode bitmap font: https://news.ycombinator.com/item?id=46248859 A great deficiency of Unifont mentioned several times in the other thr
127.
by kragen 10mo ago
Relying on binutils and an assembler is fine. I don't think it really affects the internal complexity of the compiler much, but having textual assembly to look at can be handy for debugging the compiler, so it might reduce the human e
128.
by kragen 10mo ago
As anthk points out at https://news.ycombinator.com/item?id=46272791 , you really only need one opcode for any program...
129.
by kragen 10mo ago
Yes, 11 lines of debugged, delivered source lines of code written per day is within the normal range. The basic COCOMO model used by David A. Wheeler's "SLOCCount" estimates person-months as 2.4 * (KSLOC**1.05), which was ca
130.
by kragen 10mo ago
Depends on your compiler.
131.
by kragen 10mo ago
Dr. Ting did a lot of wonderful expository writing about different Forths, including eForth, but yes, the eForth Model is by Bill Muench.
132.
by kragen 10mo ago
> Does anyone know if Forth suffers measurably in inner loops from have to call words that perform basic operations? Yes, the slowdown is of the order of 8× for DTC, ITC, and bytecode ("token threading"). Eliminating the jum
133.
by kragen 10mo ago
You can see my workflow with Forth in https://asciinema.org/a/621404 , which should help reinforce my point that I'm not an expert. What I mean is that Forth as a programming language is kind of... not great? Li
134.
by kragen 10mo ago
It certainly sounds like a perfectly usable C dialect.
135.
by kragen 10mo ago
Yes, not just public, but also licensed under a license that permits free redistribution, modification, etc. This is awesome!
136.
by kragen 10mo ago
Hmm, do you know when?
137.
by kragen 10mo ago
It can be hard to tell how much extra complexity would be introduced by unimplemented features.
138.
by kragen 10mo ago
Possibly this is why it wasn't mentioned? There are enough differences in that list that I can't imagine any existing C library would compile unchanged.
139.
by kragen 10mo ago
That's a good point, thanks. How complete is it?
140.
by kragen 10mo ago
Coyotos and CapROS are two continuations of EROS.
141.
by kragen 10mo ago
I mean, there isn't exactly a thriving ecosystem of existing software built for CapROS. Right now I don't think anybody even has CapROS itself building. The problem has gotten a lot easier since the EROS days, thanks to Xen, QEMU
142.
by kragen 10mo ago
This is a terminological confusion. The "computers" you're describing gave their name to the universal symbol manipulators we now call "computers" because, historically, the universal symbol manipulators were origi
143.
by kragen 10mo ago
This is a pretty good explanation. I think it maybe undersells the importance of the REPL a bit. (I'm not a Forth expert, but I did write StoneKnifeForth, a self-compiling compiler in a Forth subset, and I've frequently complain
144.
by kragen 10mo ago
She won the Turing Award. That's hardly being forgotten. Is this an interview with her, purportedly made five years after her death? Yes, apparently. At the very end, it says: > This interview transcript is a work of dramatised h
145.
by kragen 10mo ago
It's just you. seL4, CheriBSD, etc., do not fit your description. Neither did KeyKOS itself. You're presumably looking at research prototypes.
146.
by kragen 10mo ago
Seems like Charlie hasn't been merging pull requests in three years: https://github.com/capros-os/capros And the list has been idle since then: https://sourceforge.net/p/capros/mailman&#x
147.
by kragen 10mo ago
There is unsurprisingly an extensive account at https://en.wikipedia.org/wiki/Ford_Pinto#Fuel_system_fires,_...
148.
by kragen 10mo ago
Is Microsoft Windows more like a Ford Pinto with an exploding gas tank, a Lada, or what? I can't think of any car that's ever been sold whose design was optimized to spy on its users and trick them into buying to things and agree
149.
by kragen 10mo ago
https://news.ycombinator.com/item?id=46257598
150.
by kragen 10mo ago
Hmm, I wonder if I was confusing emscripten's asm.js approach with its approach to Wasm. Thank you!

More ›