guenthert
Nonsense. Embedded systems, often event driven, improved as did the rest of the computing landscape (perhaps at a tad slower pace). HST has been a major driver on low latency computing in the data center. And then there are of course robotics and military applications ...
Perhaps. I wouldn't argue either way, but dpkg still maintains its "data base" of installed and available packages/files as plain text files rather than using a DB format like sqlite (which one might chose for such today) or Berkeley DB (back when). The performance difference is negligible today on fast hosts with NVMe backed storage, but fairly annoying when using lesser machines with slower storage, e.g. RPi with root fs on a SD card.
Don't let IT hear that unless you work on FOSS.
Not the IMHO more interesting analog tech which lifts signals out of thermal noise.
I recall VICE emulating the Brotkasten on 386 PCs some thirty years ago, later UAE doing it for Amiga. How long til my currently running system (anno 2016) is being emulated?
That did Fry's in, didn't it? People coming in viewing, touching hardware in store and then buy it on-line (elsewhere) so that they could save 2.5%. Or worse, buying it in store and returning it two weeks later when they found a better deal or didn't need it anymore.
Most recent status update can be found at https://science.nasa.gov/blogs/roman/
https://forum.pjrc.com/index.php?threads/linux-on-teensy-4-x...
World's first? What about the VIA C3 (or earlier NEC V20)? I'm sure there are more / earlier ones.
You make it sound as if that were a bad thing.
CLISP's maintenance status is mentioned, but I can't help wondering in which way that would be relevant.
Yes, it's an annoyance, not an insurmountable obstacle. If one is bothered by it, there's the hub gear, invented more than 100 years ago.
Now human programmers might find it more difficult to get certain things right than others, but to a LLM only quantity of examples matters, no?
The killer (hah!) feature is arguably its homoiconicity, allowing to modify the language easily within itself ("macros"). This has the obvious advantage that you can add missing features (usually) easily yourself; and exactly that causes headaches for those tasked with maintaining other people's code.
> Nowadays with LLMs writing all the code
Oh, you came all the way from the future and that's what you bring us?
Obsolete standard turns out to be insufficiently strict, news at 11.
Presumably one intends to debug the code, when setting (debug 3). Then it'll be helpful to see the stack, no?
> Another related footgun is deep recursion of other kinds, for example when recursively traversing down lists. For long lists it's easy to exceed the stack size limit. The common idiom is to recur on list elements, but iterate or map to go along a list.
Not going to argue with seasoned lispers here, but IMHO recursive code makes most sense when accessing recursive data structures.
Only those who try to maximize profits while skirting the risk of a revolt care whether global average temperature will be 1.2 or 1.8K above pre-industrial average in ten years. For the rest it's already too warm, the damage is already plainly visible.
We don't need better models to predict future warming; we dragged our feet long enough that we can now look at historic data to see where it's going.
I'm sure some of the more entrepreneurial minds will argue that many of those rules stifle innovation and progress. But also on a personal level, at least to this returning German, some of the rules seem silly at best and at worst cause some underlying sense of oppression. Why, e.g., is there a Meldegesetz/Meldeamt? I survived for 25+ years in California without such.
There are safety/freedom tradeoffs and whether they are worth it, everyone has to decide for themselves (at least Germans are granted the liberty to leave, if they don't like it). Many Germans long for a more adventurous life, but in the end most prefer to visit, rather than emigrate to, foreign shores.