If git didn't have this setting, then after checking out a bash file with LFs in it, there are many Windows editors that would not be able to edit that file properly. That's a limitation of those editors & nobody should be using those pieces of software to edit bash files. This is a problem that is entirely out of scope for a VCS & not something Git should ever have tried to solve.
In fact, having git solve this disincentives Windows editors from solving it correctly.
You will have the same problem if you build a Linux container image using scripts that were checked out on the windows host machine. What's even more devious is that some editors (at least VS Code) will automatically save .sh files with LF line endings on Windows, so the problem doesn't appear for the original author, only someone who clones the repo later. I spent probably half a day troubleshooting this a while back. IMO it's not the fault of any one tool, it's just a thing that most people will never think about until it bites them.
TL;DR - if your repo will contain bash scripts, use .gitattributes to make sure they have LF line endings.
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.
I know this isn't quite what you mean, but when you first hit the page, the list is in a random order, but it's then stable across reloads.
I considered the 'vs' approach, but 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.
How do you feel about something like this: The user goes through the long list, picking what they understand and don't dislike, then the 'vs' system is there for helping determine the order of those items. Then the user gets the ranking which they can tweak.
> 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
That's a great question, and it's a core design goal for Nanowakeword.
The short answer is: it should be very easy.
Since Nanowakeword is designed to be a full framework, the plan is for it to have an inference API that is largely compatible with how openWakeWord works. My understanding of the HA pipeline is that it's a Python-based system.
In theory, the steps would be:
1. `pip uninstall openwakeword` and `pip install nanowakeword`.
2. In the relevant Home Assistant Python script, change the import from `from openwakeword import ...` to something like `from nanowakeword import Model`.
3. Instantiate the model with the path to your custom `.onnx` file.
The Nanowakeword `Model` class is designed to handle the necessary audio preprocessing (feature extraction) internally, so you shouldn't need to worry about manually replicating it. The `.onnx` models are already compatible.
While I haven't tested the Home Assistant integration myself yet, building a seamless replacement path is a top priority. Your question is a great confirmation that this is what users want. If you run into any issues trying this, please open an issue on the GitHub repo, and I'll be happy to help you debug it.
`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)
Opera, up until 2000, was trialware that nagged users to pay. At that time, they were one of the first browsers to support tabs. In 2000 they put ads for non-paying users, and from 2005 they removed ads and survived entirely on Google money. Then in 2013 they became yet another Chrome-based browser.
Obviously, that was quite some time ago at this point. Perhaps paid web browsers' time has come again?
Opera corporation had most of income from embedded devices. Presto engine (and something they had before) could run on low end CPU without MMU and floating point math, with a few megabytes of memory! Browser wss just a side gig for them.
> 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.
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...