Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
stouset
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
241.
▲
by
stouset
5mo ago
Of all the things I was imagining it might be, this was down at the bottom. Personally I’m a huge fan of this approach. If you aren’t, it’s literally just a one-liner (that is trivially made into an alias) to advance a branch name to the mo
242.
▲
by
stouset
5mo ago
The conflict markers are a first-class citizen in the repo. jj tells you when a commit has a conflict, and you can go edit it at your leisure. It also does prevent you from doing some things with branches in a conflicted state, like pushing
243.
▲
by
stouset
5mo ago
It’s really not. I start a new branch and begin work. When I’m ready to start organizing that work into a consistent narrative (or when bits are “finished”), I split it out into independent commits. As I keep making fixes and tweaks, I cont
244.
▲
by
stouset
5mo ago
Now compare that by how many died from the disease itself. Now consider that these risks are well-known, well-publicized, well-studied, and well-accepted and nobody is getting arrested for talking about them. Now consider that these risks a
245.
▲
by
stouset
5mo ago
This seems like a lot more effort than the (to me) more natural jj workflow of maintaining the idealized series of commits plus a working commit on top. As you make tweaks and fixes you just squash the relevant parts into the already-clean
246.
▲
by
stouset
5mo ago
You can literally jump into a commit and edit its contents directly, and everything is auto-rebased on top. There are no modal “sorry rebase failed, best of luck” gotchas. There are no “oops I put the wrong thing in the wrong part of the re
247.
▲
by
stouset
5mo ago
I’ll be honest, as a long-time jj user, I actually haven’t the foggiest what you’re talking about with branches being laborious to keep up to date. Can you elaborate?
248.
▲
by
stouset
5mo ago
Yes, that is the case for almost every repo I’ve ever used jj for. It is a complete non-issue. There is virtually zero friction.
249.
▲
by
stouset
5mo ago
I’m going to have to politely request that you stop this immediately.
250.
▲
by
stouset
5mo ago
Indeed the brainwashing is still alive and well. It’s been five years since multiple COVID-19 vaccines have been widely available and administered worldwide, and just about the worst common side effects have been a small risk of mild, self-
251.
▲
by
stouset
5mo ago
I would imagine it’s hard to be reminded of things that didn’t actually occur.
252.
▲
by
stouset
5mo ago
This stupidity is not going to simply be waited out. It is becoming even further entrenched.
253.
▲
by
stouset
5mo ago
The engine that failed on the Southwest flight was a CFM International CFM56, which has also been used on multiple Airbus planes including the A320. The engine itself as well as the containment mechanism that’s supposed to prevent this kind
254.
▲
by
stouset
5mo ago
I was better off not knowing that this morning. Might be worth prefixing that tidbit of info with “trigger warning: the unrelenting passage of time”.
255.
▲
by
stouset
5mo ago
While I think Apple is a prime candidate to do something like this financially, I’ve never had the impression that they ever want to get involved in something “just” for vertical efficiency. There’s always a long-term vision where they can
256.
▲
by
stouset
5mo ago
You certainly don’t need 20 diagrams to understand why you’d want to use jj. This author happened to think it would be useful. Apparently pictures of data structures are crimes. Meanwhile, that article is inarguably the thing that made git
257.
▲
by
stouset
5mo ago
This flatly isn’t true. Each individual PR gets tested and merged the same way they would if you’d authored them one by one in the first place. The combination is merged in your tree well in advance of a PR ever being made. When the ances
258.
▲
by
stouset
5mo ago
That isn’t even about black magic wizardry. That tutorial covers adding files, committing, switching branches, and merging: in other words, the absolute basics. It was, and maybe still is, one of the best beginner resources on how to mak
259.
▲
by
stouset
5mo ago
Are we talking about the same git where—notoriously—one of the best ways to become proficient was to read Git From the Inside Out[1] replete with over 20 diagrams showing how various commands perform tree manipulations? [1] https:/&#x
260.
▲
by
stouset
5mo ago
Very often when writing a new feature, I have to fix a bug in another subsystem (and write tests for it), add a small capability to another subsystem, fix documentation elsewhere, and so on. Those could be separate commits in one PR, and
261.
▲
by
stouset
5mo ago
Safe Rust does. Unsafe Rust allows you to tell the compiler “hold my beer”. It’s a concession to the reality that the normal restrictions of Rust disallow some semantically valid programs that you might otherwise want to write. The safeguar
262.
▲
by
stouset
5mo ago
Of course people are going to generally prefer the thing they’ve already been using and are comfortable with, especially if they are forced to use something else entirely. On the flip side, I run a Windows gaming laptop alongside my Mac. It
263.
▲
by
stouset
5mo ago
This has serious “your dad and I are for the jobs the comet will provide” energy. Sometimes, the outcome of a scenario will be unambiguously tragic for humanity. The collapse of the AMOC would be one such event.
264.
▲
by
stouset
5mo ago
What, exactly, do you expect scientists researching these things to do? Bury their findings?
265.
▲
by
stouset
5mo ago
How exactly will waiting a year or two make this effort appear “characterized by impatience and grumpy annoyance”, as opposed to the people right now who are loudly bemoaning an engineer trying something out as an experiment?
266.
▲
by
stouset
5mo ago
Having read the comments from the actual engineer doing this rewrite, the only petulance I have seen is from those reacting so strongly to it.
267.
▲
by
stouset
5mo ago
The point was that returning a 404 for unexpected query strings doesn’t just happen to okay per the specs, but that there is significant historical precedent for doing so based on application design that was common in the past.
268.
▲
by
stouset
5mo ago
You’ve already managed to completely ignore multiple people who’ve tried their best to clear up your colossal and frankly easily avoidable misunderstanding of this situation. So by all means, don’t let me stop you from crashing out over an
269.
▲
by
stouset
5mo ago
You missed the joke.
270.
▲
by
stouset
5mo ago
Sorry, yes, I should have made that clearer. Burners should as a whole be better about [the fact that they] just dump their trash in Reno on the way out. It’s an enormous problem, and completely indefensible particularly given the number of
More ›