That thing is unstopable. Incredibly cheap to purchase and use. 100 would buy again.
165 karma · joined January 29, 2020
That thing is unstopable. Incredibly cheap to purchase and use. 100 would buy again.
Of all the languages I would choose for a desktop app, it ranks pretty far down, yet I am clearly in the minority.
But I’m not here to show my age or biases - I am genuinely curious. What am I missing that makes JS/node (or is that a redundancy? Is there any other choice than node for JS local development?) such an attractive choice for local development.
Over say java / swift / rust for static languages or python / closure / julia for dynamic?
Specifically how the “better” crowd spent a lot of time trying to solve PCLSRing while the “worse” crowd just said: meh, throw an error and let the program figure it out.
Previously
To paraphrase: The idea being that a well designed library api gets you 90% of the benefits of a richer language’s features, but without exactly that penalty that Carmac calls out.
If that is not possible, precompute the average count representation length to get an accurate AVG offset per entry. Accurate in aggregate.
But I wonder if I wouldn’t use some prefix representation, like a trie, but that’s cheating I think
* proportional (yes) * sans serif * has the common programming ligatures
The proportional with programming ligatures bit tends to reduce the search space to zero.
Oh and since we are volunteering, I like dank mono which I paid like $30 for.
Here the author has boiled the problem down to its minimal form, and it’s still 10s of lines of code.
It is this weird overlap of over-verbosity a-la c++ and extreme succinctness a-la Perl. You have to spell everything out and every bit of punctuation matters.
I notice in section 6.1 reliability, the word “must” in clock going backwards mitigation is not MUST.
Intentional?
I never used it (darcs) but got the impression that it was easy to get into merge cases that were very hard to resolve.
(To be clear: I am not /claiming/ the above, I am asking whether my recollection is correct)
Deniable cities, so to speak.
These initially seem fine, and it’s only when you repeatedly search the same topic that you notice the stolen content. You can tell the legit site by having bylines, references, and fewer ads.
Google seems to weight them the same, which is near malicious: it has the history to show primacy.
I’m sure unions play a factor, but many others do as well.
Borax Soup Borax Salad Borax Turkey Desserts Borax)
But it is referenced here
https://www.wpr.org/borax-dinner-party-kickstarted-fda
I will go look over metafilter archives, since I imagine that’s where I read this originally.
Thanks for the pointer.
But I'm curious about your case: why not use the old-fashioned solar water panels to create hot water directly?
I was envisioning a clock where the second hand dragged the others every time it passed over. So the minute hand would only move when swept over by the minute hand, for as far as it needed to revolve. Similarly, the hour hand.
I would be nice if the minute hand moved the hour hand, but that would be noticeably inaccurate.
(*) The tolerance clock always displays time that is within some tolerance of true time, but that is all it guarantees. I never worked out formal specs, so either crazy clock or early clock would suffice I think.
neat!
Despite surface similarities, the two projects are very differnt (speed vs energy efficiency, simd vs mimd, lisp(*) vs forth)
But to program them you must keep the same mindset, I think, and both are best seen as macro-FPGAs.
I loved my first job. Every thing about it. But looking back in hindsight, it was a vanity project of the ceo, and was never going to recoup the manpower investment. Requirements and goal posts were ever-shifting. I was too naive to even perceive role status and did little or nothing concrete to forward my career except turn out (quality) code.
I loved it.
I would be frustrated to distraction if I were in that position now.
Discussion there includes Plan 9's Venti filesystem, which I have always admired as throughly well engineered.
Is it better than markdown, as laid out by my browser and the free pluggin, and saved to pdf? Not from those examples.
So we generated our parser to fail if field ORG/1457 (made up) was not numeric max 8 digits. Or missing where mandatory.
Even if we never touched the data in that field.
Turns out that no-one else used the spec that way. No two were the same, so we had to basically implement two layers of parsing. One to put the data in a common parse tree, and the other to per-sending-mainframe interpret the data as how the sender had implemented.
We assumed that the mainframe would never send illformed data, and indeed that-could-never-happen. But they differed in what they thought was well formed.
But that's probably an anachronism, given the age of IRC.
Parent was saying that the Linux model has failed spectacularly to deliver the software they needed.
Possibly there are categories of software illsuited for development by donated time from loosely coordinated volunteers.