I don't want to stop you from providing your opinion, and looking back, I shouldn't have questioned it the way I did. I didn't consider, after my own experience switching from the time of CVS and then SVN to git, with…
Well, then I'm sorry. Your issue seems not so much that tools have shortcomings, but rather, that you seem to focus on these shortcomings so much that everything looks like crap. Maybe not in general, but at least in…
I don't think jujutsu is proprietary. Source is freely available, and it uses Apache License 2.0. While you're right about the disadvantages of git, pretending that it became ubiquitous because it "became a…
There's -i for interactive, lets you add, patch and reset (unstage).
I agree that requirements need to be kept in check to avoid over engineering. However, I think it's hard to decide for other people far away what their requirements ought to be. So I don't agree that you can call mrb's…
Of course you can call things over engineered, but seem to want to include questioning the requirements, specifically also those of the example we're talking about. Once you start that, you also need to stop somewhere.…
Where would you draw the line for a sufficiently simple implementation of sufficiently simple requirements? A door knocker? A door?
Gotta keep up with pitch inflation! https://en.wikipedia.org/wiki/Concert_pitch
With pleasure. There was a boy A very strange, enchanted boy They say he wandered very far Very far, over land and sea A little shy and sad of eye But very wise was he. And then one day A magic day he passed my way And…
Love the pedantry here. I'm currently at: no op code does anything, it's all fancy effects in the hardware that can be described in arbitrary detail, which somehow allows me to cause these letters to appear on your…
I agree. What I meant to say is that the Wikipedia article tells you upfront where it is going. In TFA, you need to push many little paragraph cards across the screen before you get an idea what you are going to learn.
But Wikipedia tells you in the first paragraph what it's all about. A "Pareto front represents the set of solutions where no solution outperforms any other solution in the set at every objective, and every solution not…
Thanks a lot for the link! I appreciate your work to make this topic accessible in an interactive format. Somehow, in this case, it's too much for me. I think the ratio of information to interactivity is too low. It's…
Is there a version I can just read as text without having to push every paragraph out of the way with my fingers across an unevenly colored background that shines through? I get that this form of presentation may be…
There is clearly LLM-prose involved, but it's pretty well done. Here's one example: "The reallocations were real, but they were never the bottleneck." LLMs love this pattern. Whether one put it into this text, or the…
That's a good point. They're not selling progress, they are claiming to enable progress by selling you (tokens in -> tokens out), making it your responsibility to connect the two. Filling that gap is part of your…
Easy for you to say, but who says they're looking for a way out? It's often easier to find a reason to stay where you are, and easiest to not even need one.
Well, first, we don't have enough context to judge what the "load-bearing seam" was used for in this case ("The key structural point first: the only load-bearing seam is [...]"), so we don't know if it was meant in the…
It's a clunky metaphor, and it's used clumsily: not for the sake of its clunkiness, but by mixing two decent individual parts in an attempt to have them reinforce each other, but ending up with something weaker. It…
As of recently, there is a strong correlation between use of em-dashes and a verbose, bloated style of writing that uses many words to not quite get to multiple repeated points. Not well written, in other words. The…
Nothing wrong with browsers using resources to do useful work. I'm just not a fan of bloat that eats resources because they're assumed to always be available. That's what this thread is about, I thought.
Waste the cycles, everyone has too many cycles, is it even waste if the cycles would just go unused, GPUs are expensive, they better do their bit, who's got no GPU, go play somewhere else without your GPU, pal. It's all…
(I replied to the sister comment to yours, because it was there first, but it's essentially a reply to you, as well.)
I understand the apprehension, and I agree that rules should be as clear as possible and not be applied inconsistently. Hoewever, I take exception to the suggestion that the mere existence of a rule means that it will…
I don't think that the rule should regularly be broken. That's not what they say, and it's not what they mean. The strongest interpretation is: err on the side of not acting surprised at people's questions, because it…
I don't want to stop you from providing your opinion, and looking back, I shouldn't have questioned it the way I did. I didn't consider, after my own experience switching from the time of CVS and then SVN to git, with…
Well, then I'm sorry. Your issue seems not so much that tools have shortcomings, but rather, that you seem to focus on these shortcomings so much that everything looks like crap. Maybe not in general, but at least in…
I don't think jujutsu is proprietary. Source is freely available, and it uses Apache License 2.0. While you're right about the disadvantages of git, pretending that it became ubiquitous because it "became a…
There's -i for interactive, lets you add, patch and reset (unstage).
I agree that requirements need to be kept in check to avoid over engineering. However, I think it's hard to decide for other people far away what their requirements ought to be. So I don't agree that you can call mrb's…
Of course you can call things over engineered, but seem to want to include questioning the requirements, specifically also those of the example we're talking about. Once you start that, you also need to stop somewhere.…
Where would you draw the line for a sufficiently simple implementation of sufficiently simple requirements? A door knocker? A door?
Gotta keep up with pitch inflation! https://en.wikipedia.org/wiki/Concert_pitch
With pleasure. There was a boy A very strange, enchanted boy They say he wandered very far Very far, over land and sea A little shy and sad of eye But very wise was he. And then one day A magic day he passed my way And…
Love the pedantry here. I'm currently at: no op code does anything, it's all fancy effects in the hardware that can be described in arbitrary detail, which somehow allows me to cause these letters to appear on your…
I agree. What I meant to say is that the Wikipedia article tells you upfront where it is going. In TFA, you need to push many little paragraph cards across the screen before you get an idea what you are going to learn.
But Wikipedia tells you in the first paragraph what it's all about. A "Pareto front represents the set of solutions where no solution outperforms any other solution in the set at every objective, and every solution not…
Thanks a lot for the link! I appreciate your work to make this topic accessible in an interactive format. Somehow, in this case, it's too much for me. I think the ratio of information to interactivity is too low. It's…
Is there a version I can just read as text without having to push every paragraph out of the way with my fingers across an unevenly colored background that shines through? I get that this form of presentation may be…
There is clearly LLM-prose involved, but it's pretty well done. Here's one example: "The reallocations were real, but they were never the bottleneck." LLMs love this pattern. Whether one put it into this text, or the…
That's a good point. They're not selling progress, they are claiming to enable progress by selling you (tokens in -> tokens out), making it your responsibility to connect the two. Filling that gap is part of your…
Easy for you to say, but who says they're looking for a way out? It's often easier to find a reason to stay where you are, and easiest to not even need one.
Well, first, we don't have enough context to judge what the "load-bearing seam" was used for in this case ("The key structural point first: the only load-bearing seam is [...]"), so we don't know if it was meant in the…
It's a clunky metaphor, and it's used clumsily: not for the sake of its clunkiness, but by mixing two decent individual parts in an attempt to have them reinforce each other, but ending up with something weaker. It…
As of recently, there is a strong correlation between use of em-dashes and a verbose, bloated style of writing that uses many words to not quite get to multiple repeated points. Not well written, in other words. The…
Nothing wrong with browsers using resources to do useful work. I'm just not a fan of bloat that eats resources because they're assumed to always be available. That's what this thread is about, I thought.
Waste the cycles, everyone has too many cycles, is it even waste if the cycles would just go unused, GPUs are expensive, they better do their bit, who's got no GPU, go play somewhere else without your GPU, pal. It's all…
(I replied to the sister comment to yours, because it was there first, but it's essentially a reply to you, as well.)
I understand the apprehension, and I agree that rules should be as clear as possible and not be applied inconsistently. Hoewever, I take exception to the suggestion that the mere existence of a rule means that it will…
I don't think that the rule should regularly be broken. That's not what they say, and it's not what they mean. The strongest interpretation is: err on the side of not acting surprised at people's questions, because it…