Smaug123

24 ms·

391.
by Smaug123 3y ago
Since when was "there is an alternative C++ compiler" anything to do with "the canonical compiler is in Rust"? The word "lie" here appears to have the sole purpose of aggravating the reader; it certainly has no
392.
by Smaug123 3y ago
The context you appear to be missing is actually the content of the post. It's often the way with articles: they give a title, which is then expanded upon in the main text.
393.
by Smaug123 3y ago
I know everyone always just responds to the title, but do read/listen to this one. I think it's Dwarkesh's best episode ever. Dwarkesh always asks great questions, and Matuschak has this amazing knack of interpreting those qu
394.
by Smaug123 3y ago
You can with Pulumi, for example. I've only used it for provisioning a Digital Ocean droplet before, not for Kubernetes, but it was relatively painless. (Although I do find approximately one new panic in Pulumi every time I upgrade t
395.
by Smaug123 3y ago
Unhygienic string templating of a whitespace-sensitive language is a truly new hell for those who have not experienced it before. Quite an astonishing decision.
396.
by Smaug123 3y ago
I do, thank you! (But it will never be the case that conflicts are modelled in Git, unless one uses notes or something to build a more expressive database on top of it, whereupon I think it's not really reasonable to call the resulting
397.
by Smaug123 3y ago
> Git doesn't have a way to "store a partially resolved conflict" in a way that would remember that it hasn't been resolved. Exactly my point: this is a fundamental limitation of Git for which there is no good workaro
398.
by Smaug123 3y ago
It sort of doesn't! It's just doing exactly the same thing it would do with any other identifier: it's printing its `repr`. Try `repr(exit)`!
399.
by Smaug123 3y ago
Python certainly lets you change things quickly, because it does not let you automatically enforce any invariants; this is why it lets you get into such extraordinary inconsistent states so easily! I personally could never imagine trying to
400.
by Smaug123 3y ago
"Fine" is not "optimal". The mere fact that something does the job does not make it the best possible thing that does the job. The most trivial example of a thing that is wrong with Git and which no amount of getting bet
401.
by Smaug123 3y ago
The canonical example of a merge that is impossible via Git's `recursive` is a base of "AB" (where each character appears on a single line but I've omitted the newlines for brevity), branch 1 is one commit containing &qu
402.
by Smaug123 3y ago
The Nix language is awful. The Nix idea is The Best. When the CLI stabilisation work lands to separate out the store-manipulation plumbing commands from the porcelain Nixlang-related stuff, I have hope that a usable frontend will appear
403.
by Smaug123 3y ago
Jenkins is, like, uniquely awful though. Aside from the sheer staggering number of bugs in its core functionality (I encounter on average maybe one bug per new pipeline I write), it is also configured in almost the worst language I'v
404.
by Smaug123 3y ago
You can still make mana on https://manifold.markets/Mira/will-a-prompt-that-enables-gpt... if you believe LLMs can't solve Sudoku!
405.
by Smaug123 3y ago
Certainly a compelling demonstration that Rust is much more popular than Ada.
406.
by Smaug123 3y ago
That would be Cato, not Cicero.
407.
Proving that Android's, Java's and Python's sorting algorithm is broken (2015)(envisage-project.eu)
3 points by Smaug123 3y ago|1 comments
408.
by Smaug123 3y ago
A team tried to formally verify Timsort's correctness, and failed, discovering that Timsort's implementation was broken for sufficiently large inputs in several common environments.
409.
by Smaug123 3y ago
That, however, is an extremely well-known class of bug. The post is about an extremely obscure (but presumably quite common at the time!) class of bug.
410.
by Smaug123 3y ago
Also in the UK. E.g. a big arrow pointing in the general direction of the site, and a dotted circle around the site itself. The low-tech ways are the best!
411.
by Smaug123 3y ago
They trade off against each other. A language designed for people who can compose primitives, for example, can be used well either by people who have seen all the combinations of primitives before, or by people who can quickly grasp the imp
412.
by Smaug123 3y ago
The USA list is an interesting conflation of what I think are two distinct classes of error: ones which can be made impossible with the right processes followed correctly, and ones which can't. "Wrong site surgery", "ret
413.
by Smaug123 3y ago
Inoffensive. One of the explicit Golang design criteria, as espoused by Rob Pike, was to be usable by "Googlers, fresh out of school, who probably learned some Java/C/C++/Python". The language would presumably look
414.
by Smaug123 3y ago
(Corrective upvote from me. Pretty much any use of reflection dooms you, and reflection is very common.)
415.
by Smaug123 3y ago
Class primary constructors have always been the default thing in F#, and I found it deeply annoying not to have them whenever I had to write C#, for what it's worth!
416.
by Smaug123 3y ago
Personally I use F# for console apps, with ahead-of-time if startup latency is important, yeah. Works fine for me! (Ahead-of-time is much harder with F# though, because .NET idiomatically leans heavily on reflection thanks to C#'s infl
417.
by Smaug123 3y ago
You're thinking of https://github.com/dotnet/sdk/issues/22247
418.
by Smaug123 3y ago
This is the realm of standard recovery planning though, isn't it? Like, your processes should be able to handle this, because it's routine: GitHub goes down at least once per month for long enough for them to declare an incident,
419.
by Smaug123 3y ago
Not really true - Git is distributed, after all. During an outage once I just hosted my copy of a certain Git repo somewhere. You can always push the history back up to the golden copy when GitHub comes back.
420.
by Smaug123 3y ago
Personally I strongly prefer F#'s way, and I always enable it manually in C# by setting `<EnableDefaultCompileItems>` to `false`. It's so much easier to debug e.g. compiler deficiencies/bugs when you can just binary c

More ›