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.

Basically guaranteed to be a clear text offender

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

I seriously doubt it. At most this is probably an A/B-test or some content-specific restrictions.

Not necessary, apps can register to open links from specific domains.

The only caveat is that if they don’t also own the domain - like Google owns both youtube.com and the YouTube Android app - you have to manually go to the settings for the app in System Settings and enable them, under ‘Open by default’.

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

I have a lot of charging issues with my Pixel Buds Pro. Other than that they are pretty good headphones, but it does get a bit annoying.

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.

It’s definitely not out of the question that a reboot helps, but an app-level memory leak is highly unlikely to be the culprit.

Apps leaking memory in Android are just going to get automatically get killed by the OOM killer, I don’t think a restart is going to address that particular concern.

At that point, you’re basically just listening to podcasts. Leaning into it might be a good choice, since there’s no visual element that gets lost when listening to podcasts, as compared to YouTube videos.

Yeah, they don’t care that senior talent left because that was the whole point.

Popular might be overselling it a bit there, buddy. It exists and some people eat it.

Now kebab pizza, there’s a popular pizza for you. With good reason, I might add - it’s the god emperor of hangover foods.

A vibe

Sure, but why would this lead to a decrease in power consumption? I’m not sure that follows.

Finally all that power won’t be wasted waiting for a single app download to finish and install.

Wait, what do you mean by this?

I honestly stopped caring a long time ago. I’ve been using bluetooth headphones exclusively since before the jacks started going away, and I’m just not bothered by it.

It would have been nice for them to stick around, but it’s not really a hill I’m willing to die on.

• General purpose LLMs are starting to replace everyday queries I used to posit to Google. Perplexity can be quite good for this.
• Copilot as enhanced autocomplete when writing code. A particularly good use-case is writing tests: with a few test cases already written, a sufficiently good test name will most often generate a well-written test case.
• LLMs for lazy generation of SQL queries can sometimes be quite nice.
• Writing assistance for things I find myself struggling to get written by myself. A writing unblocking tool, if you will.

It’s reducing the effort and time I have to put into some things, and I appreciate that. It’s far from perfect, but it doesn’t have to be perfect to be useful.