mostlylurks

5 ms·

1.
by mostlylurks 17d ago
Privileging the standard library would be a pretty bad way of fixing the issue. It wouldn't prevent the same issue from affecting non-standard libraries, which are also subject to the same issue. The correct way to avoid this issue wou
2.
by mostlylurks 21d ago
For me, it's like a second sense of vision, which does not get hallucinated into the primary sense of vision and which cannot be confused with actual vision, yet nonetheless feels much like vision, with the exception of "not feeli
3.
by mostlylurks 1mo ago
> Ÿ seems to not be used by any language. Surely those aforementioned non-initial cases would sometimes find themselves in a piece of all-uppercase text? You'd have found such things in print media even before the advent of computer
4.
by mostlylurks 2mo ago
The models themselves are indeed glorified autocomplete in terms of what they actually do (with things like agentic coding harnesses being required as a wrapper around them to make that internal autocomplete something more useful). Many peo
5.
by mostlylurks 1y ago
Not represented directly in memory in its raw form right where the value is placed, but rather stored somewhere else (usually the heap) / in an opaque manner and accessed via an indirection, such as a pointer / reference. Often in
6.
by mostlylurks 2y ago
> We can't do that, however, because Prolog doesn't support unification of functors. We could patch that if we started referring to function application with more elaborate syntax by parsing "sin(exp(x))" as applicati
7.
by mostlylurks 2y ago
> Why is an extra element required, and why is it <font> of all things? I don't know, but perhaps due to the fact that due to the CJK unification in unicode, rendering Chinese or Japanese without explicitly setting a font desi
8.
by mostlylurks 3y ago
The presented trichotomy between no moderation, moderation, and federated moderation is false. Moderation can also be accomplished via a user-level web-of-trust system, where each user can choose who to trust as a moderator, and this trust
9.
by mostlylurks 3y ago
> Techies just love to build and configure things to their liking. I don't, and I don't believe I'm even in the minority in that regard. What you are referencing is a stereotype that may reflect a minority of so called &qu
10.
by mostlylurks 3y ago
Developer-users are real users. A tool (such as a piece of software) is not just a toy just because it's targeted towards users that actually have the skillset to make proper use of it. In fact, quite the opposite; the most useful tool
11.
by mostlylurks 3y ago
You don't, because JSX is not required for react. This isn't even just a theoretical point, but something I've actually done in the past several times; it's very convenient to just try something out by throwing react int
12.
by mostlylurks 3y ago
I don't find it more difficult to use or remember commands for than remembering how to accomplish similar tasks in some GUI (especially if that GUI is emacs). And unlike most GUIs (emacs may be an exception), I can trust that my knowle
13.
by mostlylurks 3y ago
With commit messages, there is a very clear starting point: the commit message for the commit that last touched the line of code you're looking at with git blame, which is my standard solution for finding out the reasoning behind any p
14.
by mostlylurks 3y ago
It's also what I, as a user, want. I don't want some middle-man corporate "platform" (of which there are very few to actually select from to suit your personal tastes) inserting their vision of what UIs should look like
15.
by mostlylurks 3y ago
Non-discreteness does not imply linearity. Seems like a nitpicky point to make, but in fact the difference between linearity and other types of continuous growth can easily be the difference between a non-issue and an unprecedented catastro
16.
by mostlylurks 3y ago
I actually have, but with the caveat that you have to know how to place the dishes in the thing such that they don't block the flow of water. Not a burden once you know how to do it, but might initially take some time to figure it out,
17.
by mostlylurks 3y ago
The most powerful abstractions are typically not free. The rate of performance improvement from improvements in hardware has slowed down and might continue slowing down. Thus, the pressure to learn what happens behind various abstractions m
18.
by mostlylurks 3y ago
> “Web development shouldn’t need a build step” A build step is a huge barrier that makes authoring your own websites require significantly more expretise than it otherwise would. It thus makes web development less accessible, and puts a
19.
by mostlylurks 3y ago
If you're doing proper atomic commits, as most people critiquing squashing probably are, the overhead of making separate PRs for each would be ludicrous. It depends heavily on the situation, but in favorable conditions (greenfield deve
20.
by mostlylurks 3y ago
> How do people with workflows that don't do any squashing do code review? Going through the commits one-by-one or just looking at the entire diff both work just fine in most cases. In the former case, the commit messages (even if s
21.
by mostlylurks 3y ago
> OOP is about building sub programs with their own state and behaviours, yet implementing a common interface so they can still effectively communicate to each other. This doesn't seem like a sufficient definition, as closures are a
22.
by mostlylurks 3y ago
Even polymorphism that is resolved at run-time is not specific to OOP. In fact, it's used quite extensively outside of OOP, including in both functional and procedural programming. Even ignoring the types of dynamic polymorphism presen
23.
by mostlylurks 3y ago
Yes, but the fact that react uses the DOM is because that is what the very restricted platform gives you out of the box, and opting for other options would have several disadvantages that are purely the result of those other options not bei
24.
by mostlylurks 3y ago
There is no need to accommodate for future usage. Most of the issues resulting from abstractions actually come from people treating abstractions as sacred, trying to adapt abstractions used by some piece of code to fit new use cases, when t
25.
by mostlylurks 3y ago
> It leads to over-abstracted, hard-to-change code that runs badly and is much harder to understand, generally speaking. Abstractions, even bad abstractions, are far easier to deal with than unabstracted code. Abstractions are cheap and
26.
by mostlylurks 3y ago
> Bad abstractions are a time sink Yes, but contrary to the general perception, I fend them to be far less of a time sink than duplicated code. It takes almost no time at all to bypass or rework a bad abstraction, but code duplication ne
27.
by mostlylurks 3y ago
With semantic versioning, it's easy to go back and provide a security update (for instance) for an earlier version of a library (which matters if the newer version is API compatible or has different dependencies or a different license
28.
by mostlylurks 3y ago
Preconditions and postconditions seem like the wrong way to go about solving the issue they try to solve. They are essentially a secondary type system that tries to express information not expressed by the primary type system in a way that
29.
by mostlylurks 3y ago
Even if you were to label it as such, how would that prove the original point? Labeling a trait as a medical condition does not make it vanish. If that alleged 3-5% of the population does not share the trait that you claim is universal, the
30.
by mostlylurks 3y ago
No, not everyone likes music [0]. [0]: https://en.wikipedia.org/wiki/Musical_anhedonia

More ›