Ask HN: What are your most ambitious projects in 2026?
Both successes and failures.
Both successes and failures.
I'm trying to build a personal social media client to stop the platforms from shoving their feeds down my throat and to consume only the content I care about, so this hits home.
(I just got blocked from LinkedIn for letting an agent set all of the 77 email notification toggles off, which in hindsight was obvious but I wasn't going to do that manually since every toggle has their own separate page, it's a lot of clicks.)
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...
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
Sounds promising to me.
Also the full story here seemed to be
1. Person installs git on Windows with autocrlf enabled, automatically converting all LF to CRLF (very cursed in itself in my opinion).
2. Does their thing with git on the Windows' side (clone, checkout, whatever).
3. Then runs the checked out (and now broken due to autocrlf) code on Linux instead of Windows via WSL.
The biggest footgun here is autocrlf but I don't see how this is whole situation is the problem of any Linux tooling.
But the UX is just terrible (for me) or at least has been every time I've tried to start using it more.
I mean, come on, the most basic use of creating a request goes like this:
1. Sorry, can't let you create a request before you create a collection.
2. Sorry, can't let you create a collection before you make a decision on in which path you will be storing all your collections.
3. Sorry, can't let you create a request before you think of a good name for it.
etc.
Like what the heck? This should be just one click to create a new untitled request then fill in the URL and send.
At first I thought this might be growing pains since it was new but every year I try it and it hasn't improved.
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)
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.
For example Thunderbird is fully funded by donations.[1]
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.
[1] https://blog.thunderbird.net/2023/05/thunderbird-is-thriving...
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.
[1] https://blog.thunderbird.net/2023/05/thunderbird-is-thriving...
- 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.
Firefox has never tried it so we don't know it for sure. I think they should at least provide it as an option.
You can donate directly to Thunderbird development for example https://www.thunderbird.net/donate/
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.
Also I wish GitHub and GitLab had colorMoved.
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.
>Which?
Here's a table https://en.wikipedia.org/wiki/Decimal_separator#Examples_of_...
EDIT: Ah, now that I re-read that, I see the "English-speaking" specifier.
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".
Host machine stays clean.