lloeki
Joined 16 years ago
Joined 16 years ago
As what an actual, safe, efficient implementation, of course not.
The point is there could have been a "dynamic HTML" alternate timeline where you could have had interactive pages for 90% of use cases without executing full blown generic computation arbitrary code on the client device.
But worse is better won and now we get insane trackers and cryptominers at every turn because the web can't degrade to exist without JS massaging DOMs.
Mostly because people around the mediterranean sea didn't have to care, tides being so small there. Yet the Greek had fairly advanced models of tide schedules.
Pretty sure peoples that were experiencing bigger tides and depended on it e.g for fishing figured out the relationship with the moon pretty quickly, whatever esoteric reason they may have plastered upon it.
Not saying that's exactly what should be done, but an example that there may be another way than full-on generic code execution wrapping XHR.
And before that, PowerMacs and PowerBooks.
Then Nvidia got into a feud over Samsung, Qualcomm, and indirectly Apple via PowerVR making their own GPUs so Apple ragequit and gave them the finger, culminating in refusing to sign third-party Nvidia drivers.
Also it's not e-ink but MIP, and that one being solar can go on basically indefinitely.
But hey if they ever qualify as "smart watch" they're definitely more on the utilitarian side than on the "wrist-sized phone" one.
France has presidential elections coming up next year, and growing civil unrest is happening. Cyber attacks are routine, and several have been officially attributed to Russia.
Anything that can trigger fear can elicit irrational reactions. That has been a known propaganda tool since forever.
> Every society is three meals away from revolution.
So I wouldn't entirely handwave it away.
lima does, not colima (well it does because it's lima under the hood)
Imagine the only scriptability you get for the OS is Automator or Shortcuts, https://github.com/apple/container is at best an API at worst a GUI app and certainly not a CLI, and that's it. macOS is MacOS (pre-X). Or iOS-like. Terminal.app spawns a sandboxed Linux microvm. You never see the host from a shell. Dear colima can't even _exist_.
https://github.com/anomalyco/opencode/tags
If you use Nix it's a flake so super easy to run too.
Seconded that v2 has much better background shell + subagent management: it's now much more eager to appropriately spawn either of them on its own, and does so in a way that is asynchronous, i.e it doesn't block the conversation and you can examine them by pressing down arrow at the prompt box.
gsettings set org.gnome.desktop.interface gtk-key-theme-name 'Emacs'
or GTK: ~/.config/gtk-3.0/settings.ini
~/.config/gtk-4.0/settings.ini
[Settings]
gtk-key-theme-name = Emacs
I have it enabled but it can be very confusing: depending on whether you're in a text field or not, in say a browser, ^W will mean delete word or close tab. And sure enough closing a tab will sometimes but not always focus the URL box of the previous tab.There used to be an obscure internal GTK setting to properly separate control plane from command plane like on (then named) Mac OS X but IIRC it's long gone / hardcoded to only GTK on macOS.
EDIT: Found it, GTK up to 3 had proper <Primary> vs <Control>. In what I would consider to be a fatal regression, GTK 4 just aliases <Control> and <Primary>, leaving the apps to do the work.
[ my public key: https://keybase.io/lloeki; my proof: https://keybase.io/lloeki/sigs/Ge11LJtfT8YAZ7Di4d6s5jlrxG_SPKFtCtZsfl8NO1U ]