Battery swap and back on the road. Obviously moving to this model would require changing conventional thinking. Cars don’t need to be parked, just like an IP address doesn’t need to “rest”. It’s just a pool of resources.
If you're talking about developing a hobby app, I'd recommend using something like react native. The DX on react (not react native necessarily) is unmatched, and easier to pick up than iOS development from the ground up. After that, you can publish the app through Expo, which is an app on the App Store. No $99 fee that way, great DX, deploying is easy and quick, a great middle ground for hobbies.
Alternatively, make a website like you normally would and in Safari you can "Add to Home Screen". You don't even need a domain name, just save the IP to your Home Screen. Native APIs for websites come a long way.
They could simply consume GPT to make their product better. They control a niche that is smaller than the broader capabilities of GPT. It might make it easier for someone to enter their space, but this isn’t a replacement for what they provide. I’ll continue to use the extensions and editor because it provides a better experience overall with streamlining capabilities.
It’s wonderful that someone is pushing their diet to the limit and sharing that with the world. Contrary to the other comments, life isn’t just about eating for every individual on the planet. He can derive pleasure from other sources. It doesn’t necessarily mean he fears death either, he could be maximizing time spent with loved ones. He could be passionate about experimentation.
It's so easy to map to to Wall-E but from my perspective this is in a very different direction. You still have to move to get this to work. This will essentially allow you to walk when you considered Ubering or driving. You'll be less fatigued and less sweaty when you reach your destination.
Happy to see the team moving in this direction. I've used NextAuth extensively and although it has some sharp edges, I feel like those sharp edges aren't unfixable. The documentation has been improving over the past year. I hope that having to adapt to more web frameworks will actually enhance the flexibility of AuthJS and leave few cases to have to shoehorn a solution.
A little, you could imagine this being a framework and passport being a collection of libraries and less of a rigid framework. I've worked with both and found passport/express to allow a lot more freedom than NextJS/NextAuth. But, NextJS/NextAuth was definitely more seamless to put together a simple POC.
It's actually generic "authentication for the web" which is why it comes off as generic. They started off with being authentication for NextJS and it was definitely helpful for a quick auth implementation. Now it's being opened up to any web framework which is kind of a cool evolution.
I've been using this library as well and I find that this isn't completely true. There are a few examples, but you have to pull and stitch from a few places. The documentation has been improving over the course of the last few months.
The older versions of 1Password are BYOH, bring your own hosting. I use it because I don’t want a single source of failure. My information is encrypted and stored in another cloud service. It doesn’t matter if that cloud service is breached. It doesn’t matter if 1Password is breached.