You’re limited on UX when it comes to PWAs. For tools where this matters a lot, PWAs are a non-starter.

Iceland runs plenty of these and has a nice culture of frequenting the public bathhouse. It’s one of the few things you can do that is actually affordable there.

They do have the advantage of having essentially infinite clean energy in the form of geothermal heat. As do Japan in many cases, for that matter. I’m sure that has something to do with these institutions having staying power there.

Anyway, I think this idea has merits, but not as an energy saving measure. The reason for this is that in order to maintain good water quality, you have to shower thoroughly before getting into the bath, negating the potential energy benefits of the initiative. We can bring it back for it being nice, though!

Wanting to learn is a good requirement in itself.

Try starting with the language and then see what you can make of it in that case. You may find out that it’s not exactly viable, but then you can always try something else.

Understand what tradeoffs different solutions make, then inform your decision on that. A fairly general principle for example is that the more cross-platform compatible a solution is, the less well-suited it will be for any given platform in terms of looks/behavior/performance. This may or may not matter for what you’re building.

There are inherent qualities to some solutions (for example, a particular library may make for good solutions on a certain platform), and some qualities will be situational (a particular library is good for you because you happen to know the language/patterns/framework/whatever).

I personally like to build things in Kotlin and Jetpack Compose, but that’s because I primarily build mobile apps for Android and I like the reactive UI paradigm that underpins this library along with the language that it’s written in. I would perhaps reconsider if I were building a desktop app (not as well supported), and definitely reconsider if I were building a web app (definitely a poor fit).

So yeah, start with what you’re building and what its requirements are. Then think about what you already know, and finally put those together when evaluating a UI solution.

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.

Testing in prod is a power move honestly. Rock star-level

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.

Kotlin-style async is pretty neat, ngl.

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

Because the pandas are all staring at you.

AI-generated, perhaps?

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.

Jon Schlinkert, I believe. Sindre has a lot of stuff as well, but has a better reputation afaik

While the rest of the world shifted left dudes went ahead and shifted right

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.

A lot of Balatro, lol. I wish it was on mobile, though…

You’re in luck - it’s fully possible to get Balatro to run on mobile: https://github.com/blake502/balatro-mobile-maker

It runs quite well and is a very good fit for playing on mobile. The only downside I know is that it drains your battery like mad.

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.