I still run into this issue when one of my company's clients requires developing on Windows. Doesn't take many subfolders before node_modules just starts breaking.
There are lots of reasons I hate developing on windows and that's certainly one of them.
I use that all the time but never knew it had a specific name.
Because if you're looking for a subfolder you're not looking for a file, and vice versa? It doesn't matter much in sparse directories, but it annoys me having to scroll through a ton of files to find the folder I want in directories with both.
I too like a lot of things about Mac, but finder could be improved, for sure.
(I have gotten used to a lot of its features and hate Windows' defaults too, so there's that. I don't think an ideal exists, unless it's in Linux somewhere and I just need to dual boot the desktop and get it over with)
No,I'll just disable the cron job before it executes and forget about it.
So do I, but I don't think I need to worry too much about confusing them with 2090.
The vibe I've been getting lately looking at Steam's push for Steam OS compatibility is that it might actually be worth trying a dual boot again next time I can bestir myself to mess with it. I've got W11 but managed to disable auto updates so I haven't received all the AI crap, but also means my OS is increasingly behind on security updates, which I'm not pleased about.
I don't care about the latest and greatest either, generally, so maybe even more worth it...although most of my new game purchases are indie titles and most of those only release for windows. So we'll see. I already have a strong preference for Mac support so I can play stuff on my laptop too.
Not arguing with your choice (props actually, I respect the switch) but it is possible to get a legit grey market key for w11 Pro for a lot less. I think I got mine for $20-30 in early 2024?
Edit: I should have noticed I was in the Linux group before I posted that, I thought I was still in the gaming one I guess! Not advocating windows to anyone, it's a terrible OS. But some people might need it for some things so I figured I'd share information that might help someone save a bit of money if they did. (Yes, there are other ways around that.)
Writing the tests first also ensures that the test actually fails when you expect it to. I've seen test suites that were silently failing for years because they were (presumably) written after the fact and people just assumed that they tested what they said they did. Went in for some other clean up, stared at the test for 10 minutes wondering "how did this ever pass", and then came to realize that test assertions in Jest inside a forEach apparently don't run in the context of the test and failures won't make the test fail. Changing the forEach to a for...of made it all fail immediately.
Neither Javascript nor Typescript require semicolon, it is entirely a stylistic choice except in very rare circumstances that do not come up in normal code.
Given how fast crud accumulates and how much it impacts use, I don't think that would be usable, and probably wouldn't have been for some years.
How would you propose to organize it then?