I think that misses the point entirely. Even if you constructed some system the output of which could not be distinguished from human-produced language but that either (1) clearly operated according to principles other than those that govern human language or (2) operated according to principles that its creators could not adequately explain, it would not be of that much interest to him.
He wants to understand how human language works. If I get him right — and I'm absolutely sure that I don't in important ways — then LLMs are not that interesting because both (1) and (2) above are true of them.
It is tragic that the only robust solution for cross platform apps eats up so much memory and storage but we're getting to the point where it's not that big a deal.
I can remember when the rhetoric against Java apps being "slow" was just as strong as it is against Electron now. And they've always been less native-feeling and clunkier than Electron.
How so? I know there are theoretical arguments and microbenchmarks that Java might be faster than JavaScript, but I've never seen an actual user-facing GUI app in Java that felt smoother to use than good Electron apps.
Correct me if I'm wrong, but isn't the problem with tauri and wails that they are still dependent on the client's native OS webview? I know Tauri uses WRY which essentially takes in your request, finds the webview present in the client and calls a corresponding function. The differences between these webviews are vast and you end up with different UIs or cobbled together adjustments for each OS to split the differences. Fully embedding a browser is extremely storage inefficient but it does guarantee apps look identical regardless of platform.
> The differences between these webviews are vast and you end up with different UIs or cobbled together adjustments for each OS to split the differences.
Like frontend developers do all the time? Why would this be an issue for apps but not on web? Reminds me of the old ”our website works best in Internet Explorer” banners.
The webviews on windows, Linux (gtk) macOS, iOS, Android all support modern CSS and are basically identical. Speaking from experience.
Depends on what you care more about: the package size or that sort of consistency in exactly how things look. For example, when I was using Wails to quickly throw together a UI for managing some other client software, small package sizes were great and since whatever I do inside of a WebView/browser will always be different than the native OS GUI solutions, slight differences were inconsequential. Someone else might have vastly different requirements.
I appreciated this as well. Going in I was expecting a long winded technical report detailing npm compatibility issues or bundle size optimizations but no, they're simply setting up an apache webserver and shipping HTML/CSS.
What? The incumbent is on his way out, and it is the incoming guy that has the opportunity for the win by bringing it back afternoon tomorrow (Jan 20th).
This is eerily similar to the Carter/Regan hostages situation