I honestly don't think this is bad. For anyone who is not a frontend engineer / designer, using tailwind gives good defaults and better LLM support. Frameworks were always about lowering the bar for entry with cost to genuine new design. The alternative is worse than this. I honestly prefer this over a backend engineer using WordPress / static site generators / other no-code platforms.

> MiMo Code is a terminal-based coding agent built by Xiaomi's MiMo team on top of OpenCode and open-sourced under the MIT license.

I think it is great that they built it on top of open code. Open Code harness is good and I want it to grow. Harness is very important and more projects use it, the more it is adopted.

> If Fable had been acting on malicious instructions—a prompt injection attack ... it’s alarming to think quite how far it could go to exfiltrate data or cause other forms of mischief.

Yet another reminder to use Sandbox and Guardrails. Trusting model to be nice is not a good way.

Boring is Better

I'm worried at the general direction of this. More and more companies will gatekeep the model capability even if it is just a few percent increase in capabilities than other models. Lot of companies will start doing this in various degrees.

The line that stuck with me: "Recovery after congestion collapse is an uncommon regime, but it is exactly the regime a congestion controller exists to handle." This generalizes well beyond congestion control.

Most control loops have the same property. The path the system follows 99% of the time gets well-exercised; the path it falls into when things go wrong is the path you actually need to be correct on. There's usually no way to discover the bug until you deliberately drive the system into the bad regime and watch it try to climb out.

My Guess

* Absorb the impact by some margin * Slash base models (which they are already doing) * Efficient software - So, end user experience is not affected. * Direct Price hike always be an option.

#3 may prove difficult besides Safari

Pausing non-foreground apps and compressing/swapping out their memory seems to work well on the iPhone.

You are correct. Though I’m talking more about never-before-solved in-foreground problems such as: Spotlight Search or SwiftUI List views.

I like an AI that can answer questions with all information and context on a particular thread. It should not be visible to others in the thread / post.

You ask, it answers and that's it. It should not take over the feed.

I like the Grok Button at the side of Tweet, I dont like "@grok is this true"

I have used windows 7 since it launched and moved to 10 & 11. I like some design elements of windows 7, but I would absolutely not use it today.

If you think, "I should try this", Any reason why? I'm really curious to know

> Any reason why?

The 2d design of modern interfaces is terrible. Everything looks like a "Label". Scrollbars are terrible. Light gray on dark gray. And, worst of all, they need 3d acceleration to draw a bloody 2d label.

  And, worst of all, they need 3d acceleration to draw a bloody 2d label

Disagree it's worst of all. Why should a specialized piece of hardware not render labels? Even tosters have some GPU cores these days.

why would i want a toaster rendering anything but hot bread?

They do. It is 3d borders that they are strugling with. And borders bigger than 1px are impossible. /s

The "route to a human" part is the bigger gap. Which human? OpenAI isn't licensed as a healthcare provider in any jurisdiction. A real intervention apparatus for 1-3M weekly flagged users is not feasible. I don't think the labs have refused to build it. I think nobody knows what it should look like, and "labs measure what they're pressured to measure" papers over that.