bloppe

Sounds like they did get a mention

There are already a bunch of NGOs that do exactly what you're describing. They are not particularly impactful.

> But no way is it a good idea to let other browser engines onto the OS.

Easy. Just legislate that the only browser allowed on iPhones is Firefox. That way, Chrome can't monopolize the web, and iPhone users get to have a decent browser.

That bookkeeping is a drop in the bucket compared to all the bookkeeping rustc does. In fact, it probably already exists in some form.

When you're compiling a library, anything that's exported is a possible entrypoint for the purpose of dead code elimination. When compiling a binary, the only entrypoint is the `main` function. Apart from that, the dead code elimination algorithm is basically the same.

Rust already does dead code elimination at a couple different levels by default, and generic link-time optimization is always an option on top of that, so I assumed GP was talking about something that was not already the status quo.

Seems like you could either generate the implementation "eagerly" at compile time (possibly with tree shaking to eliminate it automatically if it's not actually referenced anywhere), or you could generate it "lazily" at runtime, which might be useful if you think it's very unlikely but technically possible that the function might ever be called, and you won't know until runtime.

Note that Rust already does dead code elimination at a couple different levels by default, and generic link-time optimization is always an option on top of that, so I assumed you weren't just referring to that.

Lazily emitted from what? You would need information about the type at runtime to derive the implementation, and normally that information is not available at runtime. The debug implementation itself is probably within spitting distance of any other representation that would be sufficient to lazily emit the debug implementation.

Somewhat inconveniencing 1% of people per year seems like a reasonable price to pay for local legislative control.

That said, I've moved across state lines before and didn't find it that inconvenient. I just had to re-register and do a smog check.

Congratulations. You're an edge case.

In my experience there's enough slack in practice for these edge cases. At least in CA, it's very strange for a cop to cite a tourist because their car is not road legal in CA but is road legal in their home state. I've known many people who just get off with warnings, sometimes years after they've actually moved to CA (and just never bothered re-registering their car their, even though that's technically legally required). Ofc YMMV

I think the only point you made which is necessarily TUI-specific is the I/O efficiency / ssh point. Everything else is just a tendency of TUIs vs GUIs, but there's nothing preventing you from making a keyboard-centric GUI with no mouse support and built-in Bash scripting, or whatever scripting.

Vim keybindings, one of the most powerful and widely supported ways of interacting with information, basically impose the "grid of text" nature that define TUIs anyway, so my message prompt has to look like a terminal. The rest of the UI can be whatever, but grid-of-text works well for structured output, especially code blocks, as well.

TUIs compose with tmux. Pi's homepage says "use tmux" twice on it. It fits right into an already-mature ecosystem including a clipboard (powered by Vim visual / line / block mode) and easy integration with shells, editors, and other tools. GUIs generally have to re-invent all those wheels (tabs, splits, sessions, etc.) and it never integrates as well with other tools in a totally cross-platform way.

> The way we like to think about MCP at this point is that it should be much closer to OpenAPI with intelligent tool discovery.

So, exactly like OpenAPI?

I guess it makes sense to just start a project "entirely in x86 assembly" if you never intend to read any of the code (although we should probably still be editing some of the generated Markdown...)

CVEs for runc are much more frequent than CVEs for KVM. The attack surface area is bigger, and containers were never intended as a security boundary, but rather as a resource management tool.

Do you have a source for your assertion that starting businesses is becoming less popular? I thought there was a huge surge since the pandemic / AI.

I think "risk-seeking behavior" is the wrong way to categorize declining trends. It seems more like "dopamine-seeking behavior" to me, and my armchair theory is that it's related to the infinite scroll. Everybody gets so much dopamine from their phones all the time that they don't feel nearly as compelled to go out and flirt with strangers or get blasted on drugs. The iPad kids now in their 20s must have a totally different relationship with dopamine, for better or worse.

I don't think there is any good historical data on dopamine sensitivity vs. "risk-seeking behavior" on a large scale. My hypothesis is that technological / cultural innovations that raise everybody's dopamine baselines (lowering sensitivity) may be able to explain historical shifts in alcohol consumption and related activities.