Live data from Hacker News

Inspecting Web Views in macOS

blog.jim-nielsen.com

131–140 of 147 posts

Re: Inspecting Web Views in macOS

#131
post #125
post #66

Earlier quoted context omitted.

No, it absolutely does not. ImGUI is a completely, totally different model of GUI programming.

Sorry, but they are the same concept. They’re both immediate mode GUI tools that provide a way to declaratively describe the UI in an imperative language.

React is not immediate mode, imgui is not declarative.

Re: Inspecting Web Views in macOS

#132

I think at some point Apple will just have to recognize that the web UI has won. I say that with a heavy heart, I enjoy them as a developer but despise them as a user. But it's really hard to compete. On the browser side, the vendor must only implement the standards as correctly and fast as possible, while the community tries all sorts of crazy paradigms and supports the ones that eventually stick. On the native side…

Flutter would like to talk to you.

Re: Inspecting Web Views in macOS

#133
post #28

GUI development is really fucking broken. I get it, it's hard to compete with a standardized platform with a probably billion man hours poured into it but I'm really hoping that Rust will make it possible to write native and web experiences from one codebase.

How about flutter? It uses native views.

Flutter replaces the entire views with its own rendering engine. That has caused some issues with consistency.

Re: Inspecting Web Views in macOS

#134

I think at some point Apple will just have to recognize that the web UI has won. I say that with a heavy heart, I enjoy them as a developer but despise them as a user. But it's really hard to compete. On the browser side, the vendor must only implement the standards as correctly and fast as possible, while the community tries all sorts of crazy paradigms and supports the ones that eventually stick. On the native side…

Flutter would like to talk to you.

Elaborate please

Re: Inspecting Web Views in macOS

#135
Fascinating. Thanks for sharing! In other news, does anyone know of an up to date catalog or list of all the “defaults” settings, possible values, and what they do? I looked for this several years ago and found nothing, and Apple’s documentation on MacOS was far better back then. As in, it existed. These days ask i can find is incomplete objective c docs that were auto-generated and offer absolutely nothing of value whatsoever (to me). So if anyone knows of some useful docs, please share!

Re: Inspecting Web Views in macOS

#136
post #81

Earlier quoted context omitted.

Hmmmm. I wonder which OS will support in-kernel JIT for JavaScript first. :v (/s ... I hope??)

Why would it need to be in-kernel? What advantage does that serve? For what it’s worth there’s JavaScriptCore (at least for mobile) which is the only way to do JIT on iOS. It’s constantly criticized as being slower than competing JavaScript JITs while Apple counters that it’s an important security barrier.

In kernel eliminates context switching overhead. Theoretically a perfect JIT doesn’t need hardware security.

Also, JSC has been faster on Mac than V8 until a few days ago.

Re: Inspecting Web Views in macOS

#140
Definitely every one of these is sluggish at best on a very modern machine but they are also full of UI annoyances. God I am so tired of little spinners for things that would have displayed instantaneously on ten-year-old hardware with previous UI designs.

I’m also really tired of things that pretend to be single apps but every other thing you click on will jerk you into an entirely DIFFERENT app. Oh, a sidebar: logically, clicking any item on the side should always update the right-hand side, right? Nope: some of the items you click on might update the right-hand side (after displaying a stupid spinner of course); others will hurl you into the App Store app and slide in some un-Mac-like UI to display 3 pieces of information (usually with truncation that can’t be fixed in a view that can’t be resized); still others might just open a web page (one that only works in Safari of course, because to hell with your browser preferences).

Why is any of this crap necessary? It’s perfectly clear that Apple just doesn’t care at all anymore about making nice, smooth, usable experiences. More than that, they don’t seem to even know how their own desktop platform has traditionally behaved. But even if they did want to change how things behave, why are so many things behaving differently? It is a complete mess and they should be embarrassed. No leadership AT ALL on the UI front.

Post reply on HN