Quekid5

6 ms·

31.
by Quekid5 5mo ago
Wikipedia says it was created in 1974, so something's definitely off with the time line here.
32.
by Quekid5 6mo ago
Try writing an exhaustive spec for anything non-trivial and you might see the problem.
33.
by Quekid5 7mo ago
Analysis Paralysis?
34.
by Quekid5 7mo ago
I think wmf's comment in this thread was absolutely correct and succinct, so I won't repeat, but I think it's worth noting that many (all?) of the Wayland devs were actually Xorg devs. Make of that what you will.
35.
by Quekid5 7mo ago
Ministry of Truth & Love.
36.
by Quekid5 7mo ago
SQLite is public domain while the code released by id/Carmack is GPL. The latter technically doesn't prevent anyone making money off it, but in practice it does (other than nominal fees). That alone is a massive difference.
37.
by Quekid5 7mo ago
Java's Virtual Threads (JVM 21) + the Structured Concurrency primitives (not sure exactly what's available in Java 21+) do this natively. Also, a sibling poster mentioned ZIO/Scala which does the Structured Concurrency thing
38.
by Quekid5 7mo ago
sqrt(2)
39.
by Quekid5 8mo ago
Moist run is the way.
40.
by Quekid5 9mo ago
It's getting better (in a C++ kinda way), certainly, but... It's ultimately still driven my matching "random" identifiers (classes, ids, etc.) across semantic boundaries. Usually, the problem is that the result is most
41.
by Quekid5 9mo ago
I think the Referer header kinda-sorta serves as mitigation for 3rd parties just (maliciously) hot-linking to, say, images on your domain, effectively forcing you to bear the cost of upload bandwidth for those images. (And similar, it'
42.
by Quekid5 10mo ago
(EDIT: I'm sorry, this silly and dumb.) "You want many folds!" We gottem!
43.
by Quekid5 10mo ago
Assert what, exactly? Anyway, the larger point is that a re-entrant general solution is desirable. The sort example might be a bit misguided, because who calls sort-inside-sort[0]? Nobody, realistically, but these types of issues are pr
44.
by Quekid5 10mo ago
The issue is that many optimization opportunities only appear after monomorphization, inlining, de-virtualization, etc. etc. Not that you couldn't do source level analysis as you suggest... it just wouldn't be effective in many
45.
by Quekid5 10mo ago
Imagine a comparison function that needs to call sort() as part of its implementation. You could argue that's probably a bad idea, but it would be a problem for this case. (You could solve that with a manually maintained stack for th
46.
by Quekid5 10mo ago
Yeah, that's true and that's a good convenience even if it's not full inference. In the case of Scala, the parameter types may often be required, but at least the return type can be omitted, so there's that.
47.
by Quekid5 10mo ago
I can't speak for the parent poster, but for global function declarations, yes, absolutely. It's infuriating when a type error can "jump" across global functions just because you weren't clear about what types t
48.
by Quekid5 10mo ago
> I think it's pretty widely agreed that requiring type annotations at the function level is a good thing anyway. Apparently it's considered good practice in Haskell even though Haskell doesn't require it. In Haskell-land:
49.
by Quekid5 10mo ago
Yup, that's basically it. "SAT says no" isn't a very useful error message.
50.
by Quekid5 11mo ago
I think it's been a commonly held opinion in security circles for at least 15+ years that the Robustness principle is generally counterproductive to security. It (almost inevitably) leads to unexpected interactions between different sy
51.
by Quekid5 11mo ago
No, LSPs return the name/metadata of a concrete type. Dependent typing means that the return type of any given function in your (static) program can depend on a runtime value, e.g. user input... In well-defined ways ofc.
52.
by Quekid5 11mo ago
I think the big thing (potentially, for me) is the ability to postpone conflict resolution during a rebase. That can be quite painful in regular old git, but git-mediate helps make that less painful in practice in my particular situation an
53.
by Quekid5 11mo ago
Add "-noindent" to the compiler flags. Done.
54.
by Quekid5 11mo ago
The size of the stdlib has a huge impact on backwards compatibility and how much pain is caused by maintaining said compatibility for the authors of the stdlib . I mean... it's hard enough for just any regular library to do that sen
55.
by Quekid5 11mo ago
Magit[0] is so good that I haven't felt any real need to use jj... yet. I'm sure I'll switch if it gets emacs integration of a similar level to magit, but the one I tried[1] isn't quite there yet. [0] Well, plus git-me
56.
by Quekid5 11mo ago
The Ocaml module system is great, but the module system in Scala isn't the usual Java package thing... it's traits. It's about as powerful as the OCaml module system on any axis I've ever used, but it's easy to miss
57.
by Quekid5 11mo ago
Which led to a really bad standard library with next to no features... but yes, it's very stable. And, hey, if it works for you, that's great... but Batteries Included can also be great for a language.
58.
by Quekid5 11mo ago
Scala 3 didn't "drastically" change syntax -- most of the changes also have automatic rewrites with appropriate compiler switches. The effects story is still pretty experimental, but there's also improvements to 'ef
59.
by Quekid5 11mo ago
> I can't imagine building something like a graphics framework without some subtyping. While React technically uses some OOP, in practice it's a pretty non-OOP way do UI. Same with e.g. ImGUI (C++), Clay (C). I suppose for the
60.
by Quekid5 1y ago
I was thinking something a bit snappier and bit shorter... maybe an Index? Maybe it could be even maintained automatically by the database...

More ›