All of these benefit from weight training, but depending on the sport, the programming will be very different.
256 karma · joined April 13, 2022
All of these benefit from weight training, but depending on the sport, the programming will be very different.
Does a number not matter "in practice" even if it's used to compute a more commonly use constant? Very odd framing.
Running is a great example because a dedicated runner, even a hobbyist, can expect to see 3-5% improvement in speed/endurance or whatever every season. But no runner expects to see improvement during a single run. But the same isn't true for activities like golf or language acquisition (my own example).
It isn’t fair to say “since I don’t read the source of the libraries I install that are written by humans, I don’t need to read the output of an llm; it’s a higher level of abstraction” for two reasons:
1. Most Libraries worth using have already been proven by being used in actual projects. If you can see that a project has lots of bug fixes, you know it’s better than raw code. Most bugs don’t show up unless code gets put through its paces.
2. Actual humans have actual problems that they’re willing to solve to a high degree of fidelity. This is essentially saying that humans have both a massive context window and an even more massive ability to prioritize important things that are implicit. LLMs can’t prioritize like humans because they don’t have experiences.
People doing actually interesting stuff can't get funding, so they have to lone-wolf their entire research or just give up and work on stuff that gets paid, people like
- Jonathan Edwards
- Allen Webster
- Brett Victor
All with seriously intriguing ideas that probably have potential, but nobody seems to want to actually dig in to the stuff. Fortunately, there are guys like Stephen Kell who are kind of doing it even in academia, but I think he's limited too towards working on the boring problems that get funding as well.
The nuance here is that LLMs seem to exacerbate depression. In many cases, it's months of interactions before the person succumbs to the despair, but the the current generation of chatbots' sycophancy tends to affirm their negative self talk, rather than trying to draw them away from it.
I think you're missing the point, and I don't think OP is "being critical of companies making practical designs."
Also, I think OP was imagining some kind of tree based topology, not connected graph since he said:
> ...but it would take talking through up to 15 intermediaries to communicate between any two arbitrary cores.
If your question is about the general intricacies in graphics that usually have bugs, then I'd say they have a much better chance at solving those issues than other projects that try to support 3rd party graphics hardware.
I don't think anyone denies the current utility of AI. A big problem of the current OSes is that AI features are clumsily bolted on without proper context. If the entire system is designed from the ground up for AI and the model runs locally, perhaps many of the current issues will be diminished.
What is a screen reader but something that can read the screen? It needs metadata from the GUI, which ought to be available if the system is correctly architected. It needs navigation order, which ought to be something that can be added later with a separate metadata channel (since navigation order should be completely decoupled from the implementation of the GUI).
The other topic of accessibility a la Steve Yegge: the entire system should be approachable to non-experts. That's already in their mission statement.
I think that the systems of the past have trained us to expect a lack of dynamism and configurability. There is some value to supporting existing screen-readers, like ORCA, since power users have scripts and whatnot. But my take is that if you provide a good mechanism that supports the primitive functionality and support generalized extensibility, then new and better systems can emerge organically. I don't use accessibility software, but I can't imagine it's perfect. It's probably ripe for its own reformation as well.
It's not invisible though: those who work with these kinds of engineers easily see how valuable they are.
Is Object Orientation bad? Is AI driven development bad? Not intrinsically, but anytime people are drawn to convenience, there are hidden tradeoffs they're making.
As far as programming goes, I tend to think that the friction created by bad OO practices haven't really led to anything other than "creative" coping mechanisms in those codebases, so perhaps for this analogy, that doesn't really bode well. But anyway...
Spelling bee is the opposite direction, going from pronunciation to spelling; not a fair comparison.
- Emacs packages like Consult, Denote, Helm, Magit, and many others
- Anki
- Recoll
- FSF
- Virtually all community driven linux distros
If you want to make the argument that "I don't know if I can trust the maintainer to actually put my hard earn money to good use in improving the project", then I would say "just be ethical; the laborer deserves his wages".
Not so hot take: FOSS should be treated as shareware was in the 80s and 90s.
In general, anyone can find some reason to criticize even the best things, and if there's one lesson humanity can take from social media it's that negativity and cyber-bullying is contagious. I am completely in favor of YouTube for creating a comment section that I actually enjoy reading; one that enhances the video-watching experience. Not even a single flavenoid of bad taste in my mouth about this.
“I’m gonna return a pizza because I want a pizza”
When of course, what one really wants is a pizza in a box. And the oven objection is also kind of funny. It leads to a “but computers are so fast, why can’t they build me a new oven for each pizza?”
People think they want real-world analogies, which they hope will make code easier to reuse and maintain when what they really want are deep modules with clean interfaces, for which object orientation is not necessary in the least.