You can’t deny that it correctly predicted the most likely token in this case.
It’s going to depend on where you are, but there’s usually some form of transit here in Sweden in all but the most rural places. Outside of cities, there’s a decent chance you’ll get a car anyway because the transit is not of high enough quality, unfortunate as it may be.
That being said, where I live in Stockholm, transit takes me everywhere I want to go, including longer distances to visit my family that lives far from Stockholm in the form of decently high speed trains. My bicycle is also a great way to get around the city.
I’m very pleased with not having to own a car, it saves me a lot of money and effort, and my transport time is spent more productively - when biking, I get exercise while listening to podcasts, and on transit I can use my phone freely to do whatever I want. It’s also generally a less frustrating way to get around, not having to be stuck in traffic or spend time, effort and money to park. It’s also basically at no loss of time compared to driving for the majority of my trips. All this on top of being a better option from an environmental standpoint. I’m very happy!
I think it might have to do with the broad anti-AI sentiment that seems to be present here at Lemmy.
I don’t disagree, but for obvious reasons, we can’t access Google from a decade ago, since they’ve made it unavailable.
I’m not really describing an ideal state, this is a mere matter of practicality.
I’ve started relying more on AI-powered tools like Perplexity for many of my search use-cases for this very fact - all results basically warrant a pre-filtering to be useful.
It’s a tool like any other, appropriate under some circumstances and inappropriate in others.
Blindly rejecting it without considering whether it’s appropriate in the context is honestly just as bad as choosing it without considering whether it’s appropriate in the context, fwiw.
What’s wrong with multiple returns?
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.
I think trying to go cheap on native apps was always kind of a fool’s errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
If you’re prioritizing cost, you should probably already be building a web application imo. There’s very few cases where I would recommend cheaping out and building a native app, it’s just kind of unsound.
This is not going to be universally true at all big tech-companies. There are places with perfectly reasonable WLB on top of huge salaries and fantastic perks.
These places are usually big enough that you’re going to see extremes on both ends within the same company - some departments with huge deadline pressure cultures, and some with highly relaxed work settings. It can be a bit of a gamble.