kajman

I used to see so many headlines about how North Korea was a breath away from causing global catastrophe. And then they got theirs. I don't see much now.

I like to keep phones a long time. Before I finally slotted in a sketchy new third party battery, my last android would suddenly shut off at anywhere from 15-30℅ battery remaining because of the voltage drop. I think they deserve a pass for that "scandal".

No parent should have to learn from their child about the abuses computer people have done to mathematical notation.

I'd hate to be their customer right now. Is this the only "corporate-scale" forge besides Github?

There's a lot of cool things happening between Gitea/Forgejo, Tangled, and Radical, but I doubt the latter two have any significant usage beyond OSS hobby projects. I'm not sure if the former two do, either.

"Speed with quality" combined with that says a lot. Sounds to me like it will be the base expectation that their remaining developers slop out features in record time. Any failures will be theirs to "own" personally.

It's the only news I've heard about new-phone-tech that's gotten me remotely excited in a long time. I'm too poor to be buying new devices though so I'll have to let others do the beta testing for a couple years.

I hope there's no web equivalent for a while. I usually hate app lock-in, but any hasty API for this is going to be a DoS or fingerprinting nightmare.

The graphene project seems to choose security over freedom in a few cases. They also recommend using the Google Play store over F-droid IIRC.

Not my preference, but they seem so far ahead of other ROMs right now that I use it still.

I do believe people have built and installed it on other devices without too much trouble, but I don't think that'll ever be supported.

Agreed. The earlier blog post did not explicitly claim this, but I think casual viewers were prompted to believe that the Magic of Mythos (TM) went and found (and fixed??) a bunch of vulnerabilities with minimal human guidance, and even contrasted this with their fuzzing infrastructure and made it sound (to me) like it was casting shade on it.

This new post makes it pretty clear that this was all bolted on-top of their existing fuzzing infrastructure, and really just used to get more and better initial hits that a very skilled team is looking at. I assume Anthropic was giving them a very good deal on inference for the positive PR, but I believe these other reports and suspect Mozilla did not really need them.

I dismissed the earlier non-technical blog post as shameless product boosterism for Anthropic. The linked hacks blog (which is a better source than this article) is a welcome release. It's hard to deny there's something real to this now, I think. Mozilla's internal definition of a "vulnerability" is also probably more widely applied than what many would intuit, but it is good that these issues are being taken seriously and fixed.

Oops, Yes. I got 2/3 of the letters correct, though. I think that might be a better rate of success than their court cases during those years.

Corporations seem to rely on key software that just a few people maintain all the time already, but you're right and the bus factor does not look great. Mise is also currently MITMing my shell, along with presumably many other dev machines, so the threat of compromise is pretty scary.

Anti-trust. They're selling part of the problem (inference via Gemini) and now they're selling a solution. They also dominate web standards by developing the dominant browser. And they control one of two dominant phone platforms that will collaborate to enable this solution.

If this were some smaller company that just did cloud then it'd never even make it to PoC. This can only happen because it's Google Cloud, and they can leverage everything they own all at once. Those not buying into their ecosystem can take a hike.

I don't know what to call this - a "freelancer launch"? It is the best executed one I've seen, though. Maybe even a black-mark on OSS if it does not go well.

> So I left Figma to work on these full time.

The Mise website makes way more sense to me now. I suppose some artistic license is justified when you're at the cutting-edge of the CLI aesthetic and what not.

I wasn't aware, and I even paid for their search for a time.

I still do not understand the market for a proprietary browser aimed at privacy-conscious power-users. There is a non-proprietary option that is many years ahead, along with another proprietary browser marketing to the same niche demographic. Good luck to them.

This would not have ever been announced while Lina Khan was running the FCC.

Such a bizarre boondoggle for a company that otherwise seems to have smart and focused offerings. They may as well announce a Slack or Jira replacement next.

Underwriters already have a solution, but there's a national flood insurance program ensuring taxpayers hold the bag instead.

I hope the only reason people are pretending these markdown suggestions are a "workflow" is fear that a more structured approach will be obsolete by the time it's polished. I can't imagine the pace of innovation with the underlying models will stay like this forever.

I hope to see harnesses that will demand instead of ask. Kill an agent that was asked to be in plan mode but did not play the prescribed planning game. Even if it's not perfect, it'd have to better than the current regime when combined with a human in the loop.

As in, full replacement of developers at Western companies by the "AI"? I would be very surprised.

I do suspect that developing software in California in 10-20 years may be looked at as if one were proposing a sweatshop to sew pants there right now.

I suppose that would just be an interactive CLI. Usually I think of them as one-and-done invocations like sed. It's definitely not an ideal mode as evidenced by the current popularity of vim over ed, but it's better than a program being unusable.

I'm confident the world will need more software developers than ever before, no matter where "AI" goes from here.

I don't think most of those jobs will be in the West, though.

All of the three sectors you've mentioned are not in a good place right now. Probably much less stressful to be an unemployed programmer than trying to make a hobby-scale farm profitable with soaring fuel and fertilizer prices, along with a labor force that is fleeing.

E: Farm automation probably has some juice though, regardless of how close the androids I keep seeing in demos actually are.

Sure is nice as a user. I get better frames in some games than Windows users do!

A lot of the complaints in this thread seem like they're aimed more at recent vibecoded UIs than the concept of a TUI.

Like, okay, they are a big step back with accessibility, but they're flickering garbage because they were vibecoded in a weekend and the TS or Python library they're built on was similarly forced upon this world.

I'm sure there's a proposal for this somewhere, but I've always wondered if it wouldn't be most viable to just have a separate "reader mode" that replaces all the TUI elements with some sort of templated descriptive string of text, something like "Page one. Foo entry. ' bar'"

Seems a lot more viable than trying to get new standard escape codes and outputting those along with visual content that may be flickering erratically. Also probably gets too complex faster than those proposals with more intricate UIs, but IMO it's really hard to defend TUIs for anything but relatively simple programs as an in-between a CLI and a native application.

It's true though. I accidently put a React component in my Postgres schema and all the data was dropped. It really poisoned the whole stack.

Window managers are more flexible than multiplexers, but I also think there's a higher floor of effort juggling multiple separate GUI programs than going between tabs and panes in a terminal emulator.

Multi-monitor terminal juggling also probably loses out to GUIs, though for me it's usually IDE or Browser on one and multiplexer on the other. One big zellij session connected to multiple terminal emulators is probably the best way I could think to handle that.

Fix the issue quickly, or optimize to the point where revenue gained from breaking the law exceeds the fine. Last I read they were holding steady on "passengers want us to pull into bikelanes to drop-off" in California.