They might even offer this as an insurance, so you pay a little more but can be sure you stay in budget.

This is a problem in countries where uploading copyrighted and illegal material has strong legal consequences (so I'd not want to share a video before I watched it fully so I can at least can see it doesn't have any obvious illegal content)

So what I do is write SQL commands, but keep all inside a specific file or module of the project. So that I can decide later to refactor it into an ORM.

I think ORMs are great if you write libraries that target more than one database. Or situations, where you have more than one database and need a proper migration part.

If you don't need migration, but in the worst case can start with a fresh, empty database, then write SQL.

But for production system, the no/manual migration might get old quickly. Writing migration code that just adds fields, indexes or tables is easy. But writing code that changes fields or table structures? Not do much.

Still, you don't need an ORM at the beginning of a project, just don't put SQL everywhere.

Also it's understood by ChatGPT (at least version 4). I asked it for "my hovercraft is full of eels" and got "tomo tawa mi li jo e kala mute" which a speaker of Toki Pona confirmed is a good translation. (Roughly: "My moving house has many fish")

Asking ChatGPT to translate it back a month later got "My vehicle contains many fish." which is not bad for a language that relies on context a lot.

Once Duolingo starts a Toki Pona course, I'm in.

Personally I'm going to miss to be able to collect current Disney and Pixar animations on Bluray and they are going to miss my money in the long run.

Disney already stopped releasing the films in 3D format. First in the US (no Frozen 3D there) then in Europe as well. I had to import the last one from Japan for a price of 1 year of Disney +

Compared to collecting Blurays and DVDs, Disney+ is currently cheap and good value. But that's unlikely to stay that way. They will at some point raise prices a lot and/or introduce ads.

Also even now: There's the problem with the picture quality (and internet connectivity) compared to Bluray. You also don't get to import out-of-area versions. Want to watch Pixar's Coco in the Mexican Spanish Dub? Not possible here.

Want to watch a film without "Skip Intro", Age & flicker warning or the complete end credits? Want to easily pause a film to analyse a scene, without some overlay covering the picture?

With Disney's track record on annoying logos and other distractions, I don't trust them to keep their user interface clean or not suddenly force ads and trailers on their paying audience.

Very hard. Of course I can just write everything into a big js file, but if you want to structure things, it's hard. You have to learn all about this NPM and NODE stuff, learn how to refresh and debug things.

And if you make the tiniest mistake, this thing will not crash with proper error messages like python.

For me to be able to write a cool test app I'd need a working date picker and some kind of radio button feature (so that I could ask you to select a date and then display a list of offers on screen to select.)

I checked the docs and it seems there's a radio button, but no date picker yet.

Plus maybe the option to push a pdf result.

(My usecase: I'm a backend dev for a booking api and it would be fun to quickly build a frontend to test the API on my phone)

Is it just the sandbox or is there anything else I'm missing?

I absolutely let Black change code and see the value in Black that it does that so the devs do not have to spend time on manually formatting code.

Black shouldn't break anything (and hasn't broken anything for me in the years I used it) but in the unlikely case it does it, there's still pytests/unittests after that that should catch problems...

Also, everybody was a different definition of convenient and most of the time it means giving up control for it. I'd much rather have control and keep things a bit more complicated.