TIL. The wikipedia article with some more detail.
TIL. The wikipedia article with some more detail.
On Android it’s the only reasonable choice so no question there.
On desktop I used Netscape/Phoenix/Firebird/Firefox/Conkeror for many years but switched to Chromium when I had to start over after the XUL-apocalypse. But lately I’ve been maintaining my Firefox setup more or less in parallel with Chromium and this week as it happens I am trying to make the switch back again. Mostly just to wean off the Google stuff. Will see how it goes.
Another (less-critical) motivation is that Chromium takes over 10 hours to build on my machine. Firefox is under 1 and it gets done way faster even if an LLVM or Rust build is involved too.
I’ve give up on the Youtube homepage long time ago. Only the Subscriptions view (with shorts filtered using a userscript) and search results are usable for me.
This sounds similar to SLIME (and its fork SLY) for Common Lisp. These tools use their own protocols rather than LSP in part because they pre-date LSP but also because LSP is not a good match for everything they do. In addition to the usual LSP functionality like symbol lookup, xref and completion they also provide a very good Lisp REPL. It is easy to have the server side (called swank) running as part of an existing service which sounds a lot like what the post describes. For example I’ve used SLIME to connect to my live StumpWM sessions.
And why not phones too if the user prefers it that way. Can we have our user preferences back please?
x86 Macs are not the greatest example of longevity at this point.
When this happens it’s often because a backend component gets rewritten and somebody decides that it’s too much work to re-implement some features for the new backend. It’s much easier to come up with a PR spiel for why removing the features is actually a good thing.