In my city in Norway, at least, there is never a traffic pattern where it's not either:

* a small roundabout with really clear pedestrian right of way marked * a pedestrian path that takes you over or under the road instead of crossing it

It's great!

Depends on the driving culture and familiarity with roundabouts for sure. Moved from the US to a city in Norway with almost exclusively roundabouts, and it's _so much nicer_. Even in the edge cases, I have never once found myself wanting a traffic light.

Simple intersections can have very small roundabouts, and bigger ones you can connect roads from so many weird directions and have traffic flow well that I would never want to return some of the intersections I experienced in the US.

I am an incredibly non-violent person, but have a toddler has really made me work hard to understand the difference in what associations we attach to "violence" as adults.

I try to help him understand this slowly, but a lot of "play" can look violent to my eyes, and I struggle to remember that. A 3 year old just doesn't see it that way yet, and that's fine. But it's hard to remember that in the moment.

Well said. The problem is that vibe coding can paper over bad engineering practices for awhile. And results look good, and when you raise concerns people look at you like you're dumb and trying to slow things down.

But the underlying bad practices _will_ bite the same they would have before AI, you just don't know when.

It's a really frustrating state of the industry to be in.

Models are the worst now that they ever will be. Frontier models do a phenomenal job of employing good engineering practices and code style compared to where they were mere months ago. Unassisted programming is dead. Programming as a human activity will be on a timescale of years (along with a vast swath of other knowledge work).

It's like the casino, crypto gambling, or eating junk food. We're wired for that short-term gains and few of us can escape it. I understand that, just sad that the casino slot machine had to hit our craft.

I went full circle on AI. For an in-editor experience, Zed is top notch. But I've found I actually prefer just to go back to claude code + Zed.

Personal opinions. How is it "top-notch", what does that even mean in practice?

I can tell you why working in Emacs feels empowering - when I'm working with an LLM, my Jira tickets are "transparent" - Emacs knows that any pattern that looks like 'XYZ-124354' is a Jira ticket - I can check the status, description, and other things on the fly. I don't need to switch to any other tool, need no browsing of the ticket. I can quickly convert it to a markdown link with a description (if I need to talk to my colleague about it). Same thing about 'foo/bar#42' pattern - Emacs recognizes it as a bug-reference token - it's an issue or a PR - I can immediately retrieve any info about it in the middle of typing.

I can collapse any large parts of my investigation without affecting my context and I can peek into them without expanding if I don't have to. I can change my freshly typed prompt using a different model, with different parameters, asking it I don't know, fact-check my assumptions or fill the gaps - all that while I'm typing it in my coding AI assistant buffer.

I can search for and pick a Slack thread interactively, without having to even switch to Slack, and tell the LLM to look into it, or simply extract some text or a snippet to paste it verbatim, or with modifications.

I can interactively pick a tab in my browser and insert its url, or grab a text from it. Without ever switching to the browser - it could even be not visible on my screen. I similarly can grab anything from my browser history.

Moreover, I can ask an LLM to change any aspect of my editor on the fly. If there's a use case I stumble on, I'd just slop the shit out of it and watch the agent drive my active Emacs instance, trying different things, popping up windows, taking screenshots and comparing results. I can name countless real, practical, everyday examples where I changed my workflow without missing a beat - some are trivial and some are more complex, and Emacs delivered. Without a hitch or a restart.

Emacs remains the absolute king for text manipulation of all kinds and text in the age of LLMs is simply everything. Nothing can beat Emacs when it comes to text, and oh boy have I tried so many other things.

The "problem" it might solve for me, personally, is having a systems-level language that matches my personal style a bit better than Rust or other more modern systems level languages.

I know they're putting a lot of weight on GPU programming, which is fine and probably solves problems, but this is the part that would motivate me personally.

I'm in the same category, but GPU support is definitely interesting too. The idea of offloading intensive processing to the GPU has its merits.

Once they get an async story figured out I will be much more motivated to dive deeper into Mojo

Don't give him any ideas.

Low value comment, so I apologize, but it's funny to note how many bottleneck articles there are now as a result of AI adoption. Lots of new bottlenecks.

`uv` helps but it's new, and I don't think it has the same mindshare yet on "I just globally want to install this thing that needs an interpreter/runtime", so Python probably just doesn't come first to mind.

I'd put it on this. In my experience Python is fine for scripting your own machine but an obnoxious platform to distribute code on. It's very fragile to version changes, in both directions; I don't know how many things I've seen that only run on 3.10, not 3.9 or 3.11. Its packaging system is global by default which only compounds this because everything needs a specific version but they're all dumped in the same place. And it tends to have a lot of native code as dependencies, leading to all the issues of needing to either have the right build environment or a runtime environment that's already been built for.