herrkanin

Presumably it is for the 99.999% who didn't spend $12k on a Trinnov.

I have an M2 Macbook Air that i sometimes boot into Asahi to play Steam games that doesn't work natively on mac. It works unreasonably well given that there is something like five different translation layers to make it work!

Is this 'best word' with us in the room right now?

Without any evidence to back it up, my hope is that your criticism in a decade will be the equivalent to "Everybody having a mainframe at home? Do we want to waste a whole room in each and every house just for that?".

I was very much in the Tailwind camp, and simultaneously loved it for its local reasoning and disliked it for how its long class names messed up my components. It has always felt like a bolted-on hack to me but I couldn't argue with the benefits.

Turns out, CSS Modules comes with the same benefits while feeling much more like a natural extension to the web platform. The only thing I thoroughly miss is functions and directives, which hopefully will land in browsers through the mixins proposal in not too long of a time.

The thing that makes it work really well is to make sure it has all the tooling to verify its hypotheses. If you allow it to run the full lifecycle in loops you will be surprised how well it works.

ATProto is closer to how RSS works than ActivityPub. In the same way talking about "RSS instances" makes little sense, the same goes for "ATProto instances".

> How is that better than the Zig codebase you started with?

In contrast with the Zig codebase, you now have clear well-scoped unsafe boundaries you can iteratively fix one by one. This was not the case before.

Running lid closed with external display has been officially supported since forever so I wouldn't worry about it too much.

The public contract previously discussed in RFCs and conference talks hasn't changed. Coding language is just an implementation detail.

Because majority of the audience spend large parts of their day on GitHub and it keeps going down.

Don't underestimate the significance of code being runnable in a browser environment.

Not good for fans. And happy fans are good for artist. So not good for artist.

Your argument is just as applicable on human code reviewers. Obviously having others review the code will catch issues you would never have thought of. This includes agents as well.

It really isn't - a ui framework should be able to properly handle backend latency and provide a great experience while waiting for a backend response with no flicker while not locking the entire ui. It's just way harder to set up good benchmarks for this.

I'm so sick of these performance benchmarks. I understand it's easy to spin them up to show that one framework is faster than another, but in general all these frameworks are fast enough for 99.9% of use cases.

Where frameworks lack today, in my opinion, are in providing the right tools further optimize the UX of interacting with web sites. It's a constant struggle of loading spinners and flicker and loss of scroll positions.

The only framework I see that actually tries to resolve these very hard problems is React, through their work on new asynchronous primitives like startTransition. Yes, they are currently hard to understand how to properly use, but I so wish the discourse would be around how to best resolve these actual UX issues than who can create 50M divs the fastest.

The difficulty to deploy Next.js is greatly exaggerated in my opinion. It's mostly if you care about some of the more advanced features, like image optimization and hosting static assets on a different origin it can become difficult, but these are features no Next.js alternative generally provide anyway.

I might be blindsided by using npm exclusively for years by this point, but what would be a better way to support iteratively migrating from v3 to v4 without having to do it all in one large batch?

Same reason as why it's harder to solve a sudoku than it is to verify its correctness.

I think arrogance has always been part of their culture – partners have _always_ hated working with Apple. Personally I believe it's the shifting dynamics of no longer being the underdog that slowly has eaten away at their core values.

As a web dev, it’s been fun listening to Accidental Tech Podcast where Siracusa has been talking (or ranting) about the ins and outs of developing modern mac apps in Swift and SwiftUI.

It’s not a symbolic link - it copies on modification. No need to worry!

I've been for many years a happily paying customer of iStat Menus [1], from which this seem to be the heavily inspired of.

[1] https://bjango.com/mac/istatmenus/

so by increasing the cost of patient care, they can take out more profits.

He still is

I think I was 8 or 9 when I started building my first website as well, and it looked remarkably similar to this. :) I think the only difference really is that all guides used uppercase for html tags back then. Happy that went out of style.