1,704 karma · joined August 12, 2015
https://www.grammarly.com/blog/engineering/running-lisp-in-p...
SBCL does a fine job in detecting type mismatches within the frame of ANSI Common Lisp, not Haskell. While I would agree that a strict type system eases long term maintenance of large systems, for "explorative computing", proof-of-concepts, RAD or similar that tends to get in the way. And if such proof-of-concept looks promising, then there is no shame in rewriting it in a language more suitable for scale and maintenance.
Uh, what were they doing before? No, seriously, given that every laptop ever and most legacy free desktops, not to speak of the 1U servers you find in data centers use a single PCB, what makes a SBC a SBC?
I've seen Raspberry Pi and the like being referred to as 'open frame computers', which I thought describes them more fittingly.
$ tar -cxf /mnt/c/Temp/home-backup.tgz -C $HOME"
That's not going to bring much joy.The actual abstract reads: "Recent record-hot years have caused a discussion whether global warming has accelerated, but previous analysis found that acceleration has not yet reached a 95% confidence level given the natural temperature variability. Here we account for the influence of three main natural variability factors: El Niño, volcanism, and solar variation. The resulting adjusted data show that after 2015, global temperature rose significantly faster than in any previous 10-year period since 1945."
You'd want to use a spectrum analyzer to verify that other frequencies are present only at very low levels. TinySA might be the cheapest option or an used Digilent Analog Discovery.
But the compiler is bound by the ABI, isn't it? (at least for externally visible entrance points / calls to sub routines external to the current compilation unit)
Both interesting projects, but other than the words 'boot sector', 'C' and 'compiler', I don't see a similarity.
Ah, good times ;-)
The modest speed (~50MBps at my place) was then ok-ish, but the (variable!) latency of a couple of ms was annoying (it tended to break pacemaker/corosync cluster communication). And every once in a blue moon they stopped working altogether and needed to be un-plugged.
Worst, for someone interested in analogue electronics, they emit (of course) a huge amount of electrical noise into the power lines.
I use it semi-regularly for quite a number of years and (consequently) various versions of Wine to run (a near current version of) LTspice. That works perfectly as far as I can tell, but it is my understanding that the maintainer of LTspice puts in some effort to assure compatibility with the then current version of Wine.
Perhaps we must not rely on it and find a way to make sure that it cannot fail, but I like to point out that this are two different problems and it seems to me that the current crop of so called AIs are pretty good at distilling excerpts. Perhaps that's the easier problem to solve?