I don't know if terminal access is as easy on iPhones, but the utility is there for many work related use-cases. I do think the more square-like form factor of the Pixel to be better for productivity than the rectangular form of the Duo, but the latter is nicer for videos.

And maybe I'm overthinking the cooling issue. It's not like I'm hammering it 24/7. Probably fine to burst high on power draw on use.

Btw, I always love moments like this where library or project owners stumble on their work and chime in on the comments. I really appreciate your work here. It's given me motivation to actually do something with parts that have been sitting on a shelf.

By your phrasing, it sounds like you're implying my understanding is wrong somehow. If so, what am I missing?

I've used it for years to have consistent keybindings for movement across vim windows and tmux panes. Worked much better than trying to do terminals inside vim.

But it's pretty clear that there was a concerted effort to suppress those posts by various actors who did have such intent. I do think it's a failing of the automated system that such suppression can be done at all.

Powerful corporations and nation states have always tried to maintain control over the flow of information. It was never really rules or regulations that kept them in check, but the practicalities of budgets and resourcing constraints. Now that those barriers are crumbling, I think the challenge of moderation will be much harder for all discussion going forward.

An example could be old API endpoints only hit by old versions of a mobile app where users may be slow to update. Or a case where only newer clients/instances support modern features and old ones are stuck on a frozen featureset until they cutover.

But active services with no immediately existant alternative may also be legacy. If your auth is behind a disappointing managed service like AWS Cognito, you may consider your entire auth stack legacy while the replacement is still looming in the roadmap down the line. Maybe you can't justify funding to work on a transition just yet, but you already would avoid building on top of the existing tech stack.

This is not a universally accepted definition. I've owned plenty of services with 95%+ unit test coverage, massive integ test suites, and synthetic canary tests that ran every minute that I would consider legacy. Plenty of AI slop today gets barfed out with 100% test coverage, but much of it is legacy from day 1.

Of course, that's not to say the work done on these platforms was wasted. The divide around io.js was meaningful to getting things moving faster and change the governance structure. Deno and bun both showcased things Node could be doing better and some of that was folded back in.

And in spite of all those past experiences, I still find myself using pnpm over npm today. I'm sure npm will continue to evolve and eventually the critical features of pnpm will just be part of core npm. But the gap today is massive enough that pnpm over npm feels critical. The disk usage and performance wins are life-changing for daily work and CI flows.

Absolutely wild that such a widespread SDK could crash everyone with a serverside change.

Seems like a server-side change.

Comments URL: https://news.ycombinator.com/item?id=49886890

Points: 7

# Comments: 2

When Shopify announced their shift from React Native, this is actually what was on top of mind for me. Week+ delays for critical bugfixes is insane. Being able to patch things with OTA updates is tablestakes at this point.

Sure, Temporal is more mature and battle-tested, but Restate is quite nice and I honestly prefer it in most cases.

EDIT:

I started drafting this reply before seeing someone from the Restate team chimed in.