It baffles me that people actually take these assertions seriously, especially after having used different software that uses voice input, like Siri, Google Assistant, Alexa or whatever. Those things make some serious mistakes even under ideal circumstances, and you want me to believe that they can accurately overhear things in non-ideal circumstances? I highly doubt it.

Regardless, you can use an ad blocker to make this a moot point - I’ve never experienced anything even close to this, because I never get ads.

General purpose: Kebab case

But really, follow the conventions of what you’re working on. For example, I’d use pascal case when working on a Java/Kotlin project, and snake case when working on a Python project.

Not saying there’s any reason to switch, but I believe you can load CSV’s into sqlite.

Datasette would be something that I would try for CSV’s as well, that seems like an interesting piece of technology I haven’t had reason to use yet.

Finally there’s always Jupiter Notebook and any respectable DataFrame-solution.

Not to knock spreadsheet-solutions too much - I certainly see their value and use them frequently - but if I had to do something that warranted writing VBA, I’d probably reach for a tool I could combine with some form of VCS like Git at least.

I don’t know if it matches your desire for easy install of small disk space, but it might make up for it in other arenas - Ruby is my new-found love when making simple scripts. Being able to mostly emulate the shell integration that bash has by just using backticks to call a shell command is the killer feature in my book.

Naturally, but by then it’s no longer milk, it’s tofu.

Basically cheese but made out of soy, afaik.

Oat every day of the week honestly

Out of all the things you can make out of soy, why milk? Tofu exists and it’s grand-master based food. I’ll smash several plates of mapo tofu without hesitation. Soy sauce, edamame, all ridiculously good shit.

I’m sure they make enough money to not care. Being in the part of the company that brings in the dough is generally a pretty good position to be in as well.

While Rust would probably have been a good choice for implementing a new browser, I don’t think Swift deserves the criticism it’s getting in this thread:

• Swift was created by the same person who created Rust, and has many of the same nice traits
• Swift is a modern language that is easy for plenty of developers to pick up; I’d place it in the same family as Rust and Kotlin
• Swift grants access to a large pool of native iOS/Mac developers

Podcasts often dynamically generate ads at the point of download, making the SponsorBlock-approach unviable: since the media is expected to be variable-length you can’t store media positions that map to advertisement segments.

Healthcare is pretty rough, I’d be willing to bet that the grass actually is greener in this case.

Actual unironic gigachad moment

It’s on mobile.

With a bit of know-how, you can make a mobile version that works quite well: https://github.com/blake502/balatro-mobile-maker

Should have say: self-hosting is always superior to cloud hosting.

That statement still comes with a pretty damn big caveat though - you need to have the know-how, the time to invest and the hardware (i.e money) to actually set something like this up.

If all of those are true, then self-hosting can definitely be an attractive option for you.

It’s only true for a vanishingly small fraction of the population, though.

Hence, Bitwarden is a pragmatic solution that will be superior for the vast majority of the population.

Also, local software and database is always superior to cloud.

Now there’s an unfounded blanket statement if I ever saw one.

Bitwarden is probably a more pragmatic choice for most users, given that it’s free and without having to manage the syncing yourself.

Any password manager is better than the alternative, though.

Sweden has a mixed system. Generally you are required to use 20 of your legally mandated minimum of 25 vacation days, and you may save the rest. The days can then be saved for 5 years, after which they must be used or paid out.

It’s not out of the question to have ‘memory leaks’ - apps accumulating more memory by keeping around references to more and more objects - but memory leaks in the stricter sense of not deallocating objects that you no longer have references to is less likely. Regardless, the OOM killer will come for your app, no matter how good you’ve been about managing your memory, as long as someone else wants to have the memory and you’re the one who has been active the least recently.