> I worried that there might be a lot of iterations where one or two of the options would be things that the person didn't understand, or didn't care about.
I won't disagree here, it would be tedious.
> picking what they understand and don't dislike, then the 'vs' system is there for helping determine the order of those items
Not an expert on how this will affect the results but since the list is so long, would it be better to show visitors two random-ish features at a time and have them pick the one they care more about? Or at least offer that kind of UI as an option or the default, and the current list for those who want more control.
`git reparent origin/main -n 3` sounds a lot like `git rebase --onto origin/main HEAD~3` and `git move-branch from to` sounds like `git branch -f from to`.
I love backup branches as much as anyone but I'd also recommend getting used to `git reflog` or perhaps `git log --all --oneline --graph --reflog` if you're worried about losing commits.
There is one* footgun in git that you can't just reflog your way out of and it's stashes because they piggyback off of the reflog, so dropping stashes will also remove them from the reflog. In those cases you can still visualize them with `git fsck --connectivity-only | grep 'dangling commit' | awk '{print $3}' | xargs git log --oneline --graph --all --reflog`.
*(as long as you've committed your changes, if not then there are way more)
> First of all, your donations to Mozilla don't go to funding the browser.
This is exactly my point. They should establish direct Firefox donations. I agree that it won't change anything overnight, but they need to start somewhere.
Of course Thunderbird's budget is in a different magnitude than Firefox but I'd guess the amount of users is also in a different magnitude.
As far as I know there has never been an attempt to fund Firefox by donations. You can _only_ donate to Mozilla, which does not go to Firefox development.
People keep saying it wouldn't work but it has also never been attempted so we do not know for sure.
- uBlock Origin with "Disable JavaScript" checked in the settings. Only enable for specific sites.
- Temporary Containers with "Automatic Mode" checked in the settings. Also MMB and Ctrl + LMB always open links in new temporary container. This provides full session isolation for all tabs. There are permanent named containers for logged-in services like email that are only used for email. Outbound links from email for example open in a new temporary container.
All browsing by default happens in a clean isolated session with JS disabled unless explicitly allowed.
I also have Behind The Overlay Revival for when I'm too lazy to zap elements with uBO.
But you can not donate directly to Firefox development, only to Mozilla, which I'm sure most are less enthusiastic about than supporting Firefox development.
If this was any other language than JS I would agree but my personal experience with JS is the opposite.
In my experience almost everything in the JS world is already async. User interactions are async, requests are async, almost all NodeJS APIs are async. To me having to add more async in JS is a tiny barrier compared to what I'm facing in other languages that feel more synchronous to me.
Since there is already so much async I also feel like debugging, profiling and error handling are all pleasantly solved problems in JS.
Offloading to workers is also async so while there are many valid benefits to be gained, avoiding async does not seem like one of them to me.
I do not run Docker in production at all but I also do not develop any serious projects outside of Docker.
Installed on the host machine are only VSCode, Docker and Git.
You work on a project by cloning it, opening in VSCode and clicking on "Reopen in container".
This will spin up generic services like databases and then the actual app container as a VSCode Remote Container, with all the development tooling inside the container.
Does not matter if tooling changes between projects, any project can be worked on with a single click of "Reopen in container".
Sometimes I have trouble listening without my thoughts drifting elsewhere. I found out that playing a Tetris clone that never increases in speed and never ends is a good way to keep a clear focus on listening. After changing phones recently my perfect Tetris clone stopped working as it was 32bit and the support was dropped. I've been looking for an alternative and finally found one in a 2048 clone with an Undo button. I thank you for that. It has saved me a lot of trouble staying focused!
For just hosting something as long as possible I would highlight two options stolen blatantly from previous threads:
If you can throw enough money at the problem and are in the US, set up a trust to host your content for as long as the funds last.
If not you could bet on The Internet Archive to outlive you (and maybe donate to them).
But I think the bigger issue than hosting is discoverability. How will your great grandchildren find your content even if it was still available?
To cover both issues the best bet is to focus on somehow convincing your offspring on keeping your content and memory alive in what ever way they see fit, enough so that they pass it on. I have no ideas for exact details here, maybe someone else does?
While we're throwing ideas, someone please implement this:
An as simple as possible Android app that lists any discovered Chromecast devices and when you tap on one it attempts to cast your screen to that one.
Why? Because screen casting isn't an AOSP feature. It is really difficult to get it to work on GrapheneOS if it works at all.
But VLC can stream video to Chromecast on AOSP without issues.
So my thought is: Take a look at the VLC Android source. It's mostly a wrapper using the VLC bindings as an API. Look at how it uses VLC to discover Chromecasts[1] and how it uses them as output[2].
Then somehow pipe the createScreenCaptureIntent API into it.
Another option would be https://html-props.dev/
EDIT: For clarity, if it does get updated, the original URL was:
https://old.reddit.com/r/javascript/comments/1pj4ros/props_f...