Yes and screen recoders

Well there is mathml but it has poor support in chrome til recently. That is the website native equations formatting.

The arch wiki has the best source https://wiki.archlinux.org/title/Unified_Extensible_Firmware...

Note sbctl is one of the easier tools to do this.

I mean there is a middle ground. LSP is good for coding a project. But I do agree with your point. What I generally do (as nvim user) reduces plugins to the bare minimum and try as much as possible to do progressive enhancement (atleast I try). Maybe as nvim improves LSP, I hope the diff between LSP and native methods are close enough that they both work.

India had a meter gauge to broad gauge but India was always a mix and India did a very slow transition to standardize on broad gauge which kinda smoothen stuff quiet a bit

Thats is xdg-portals and it works. It needs apps to support it though which slows adoption

Do you need a wrapper script for scripts in the PATH or execve? I would usualy chmod+x the script but I am not sure here.

If you want to make it work regardless of where uv is installed, you can use the following shebang line:

  #!/usr/bin/env uv run --script

Discussed here:

> Using uv as your shebang line

— https://news.ycombinator.com/item?id=42855258

Since `env` doesn’t pass multiple arguments by default, the suggested line uses `-S`:

   #!/usr/bin/env -S uv run --script

Not at a laptop to try this right now, but shouldn't this be possible with the shebang? Something along the lines of:

    #!/home/tetha/Tools/uv run

Yes it is, I just converted my work scripts over this afternoon.

    #!/usr/bin/env uv run

Epiphany is a webkit browser for linux and due webkit architecture, gtkwebkit uses alot of gnome components such as libsoup and gstreamer. The biggest flaw is the webrtc support is missing so not online meetings.

I think the distinction is a soft fork or a hard fork. A soft fork is just a patchset over upstream and some people do not call it a fork. Hard fork mean that you are diverging from upstream, you do not longer follow upstream and you are fully separate from the upstream

I think fork implies following upstream. If you don't follow, then it's a divorce, not a fork.

No, "fork" means development has separated paths from original project. Changing some relatively minor parts but otherwise keeping close to upstream would be better called a "spin", especially when most of the changes are just to the default configuration.

It's a shame that GitHub messed up this term by calling any clone of a repository a "fork".

Your definition of fork excludes many notable forks. I never heard someone call a software project a divorce.

Waylands problem is that to use it, you need code generation so the wayland backend kinda hard to design for a header only lib.

I've seen some interesting work in doing Wayland by hand:

https://gaultier.github.io/blog/wayland_from_scratch.html

I'd also look at the work done on minimal wayland projects like [foot](https://codeberg.org/dnkl/foot), which supports wayland well and seems to be written by hand (see: https://codeberg.org/dnkl/foot/src/branch/master/wayland.c)

I just have the Makefile do the code generation, it would be annoying for the user, but they can complain to Wayland if they don't like it.