armchair_expert

First of all, this is an immediate rendering library which is a very inefficient way of rendering the UI for any application that is not a videogame. You are rendering the UI 60 times a second, regardless of whether something changed or not. Most UI frameworks only update when something changes.

Secondly, there are things in GUI frameworks that most people don't think about, such as accessibility. Windows has a builtin accessibility API where apps can declare the objects being shown on the screen, so that screen readers can interact with the application. I'm pretty sure this guys framework doesn't have that.

You can try going into proxy settings and setting to "none" instead of autodetect. Also, the dns server used by the browser could be different (and slower).

I blame Microsoft for this. They release a completely new UI framework every 5 years, completely abandoning the old ones. The design is outdated and boring. The XAML based UI frameworks look terrible if you use the default settings, and force you to customize. It's great that it's easy to create custom UIs, but terrible for consistency between apps.

On the Apple side, things look a lot better. They were able to keep most apps using the native UI.

An iPhone is just a tiny pocket computer. There is no technical reason preventing an iPhone from running shell scripts and emulators. The only reason why it can't do is because Apple controls what apps you are allowed to run on your phone.

Because they put themselves in that position by soldering the ram to the board. This way, people can't buy off the shelf RAM, the only way to upgrade is buying a more expensive mac.

They did the same with the storage. Even on expensive Mac Studios, even though the SSD can be taken out, it's incompatible with off the shelf SSDs. You can't even buy used, you have to go to the Apple store and pay the Apple premium for an SSD, and they reprogram your soldered SSD controller to work with the new drive.