This smells more like a get you hooked and then crank the costs.

Not that I'd be any less skeptical of the first option. We've already seen providers reduce quotas and raise prices.

They tried teaching us this relational algebra (or whatever you call it) in university but most of it went over my head because it was too abstract. Using weird mathematical symbols. But when we started writing actual SQL, all of that made sense to me.

I think it might be easier to see it in action and then go back and understand the fundamentals of how/why it works.

I've ran into this problem many times. I'm quite pleased that the AI can complete the 'last mile' on many of my old projects. I'm finally publishing my packages! Time will tell if they're any good but at least they're buildable, testable, lint-free, documented and installable now.

There's a plethora of 3rd party messaging apps, namely WhatsApp or WeChat -- I haven't felt that messaging has sucked since then BBM days.

We're safe for now, I think.

I run Minikube in Podman for dev. And then I use kustomize to customize dev, staging and prod environments. The environments are 99% the same, they just have different env vars and memory limits.

The cluster isn't that hard to recreate if things go south. Everything is in YAML configs already. And since I'm managed, it's just a few clicks in DigitalOcean to create a new cluster. And actually, I think I can create clusters through their CLI too, so if I did want to automate it, it's already ready to go. So I'd say I'm cattle-ready, but too cheap to pay for more cattle.

I nearly went Docker Compose/Swarm by accident when I was just getting started. I knew I wanted to dockerize my app but then couldn't figure out how to get it into prod. Then I found out people don't actually use Docker Compose for prod it seems and eventually stumbled into Kubernetes. It took a few weeks to wrap my head around, but I'm happy with it now.

Once you have a nice set up, I'd say it's pretty simple to maintain. DevSpace is fantastic for development, and then for deployment I just wrote a little script which builds my images, updates the kustomize with new images and applies the manifests. Pretty simple.

The only piece that's maybe a little dicey is the single load balancer/gateway. If there's a hiccup in that, then everything goes down.

But I've only blown up my cluster once in like 8 years or something, that's not too bad. It was a learning experience :-)

What other kinds of isolation do you want? I can see maybe a separate staging environment if you want to test gnarly things like that ahead of rolling them out to prod. And I guess maybe they can eat eachother's resources if you don't have request limits nor auto-scaling enabled.

But I'm cheap and managing more clusters sounds like a pain. Then I'd have to deal with more kubectl credentials and what not too.

I might have to look more into that... not very keen on Oracle though.

173 looks like ITE

5 in roman numerals is V.

You said it should work, so I did some poking around. Uninstalled it, reinstalled it. Still didn't work. The "About" in app said I was running 1.0.0+stable

Checked my environment paths and saw I had both

    C:\Users\Me\AppData\Local\Programs\Zed
    C:\Users\Me\AppData\Local\Programs\Zed\bin

    Me@DESKTOP-NN7TD9I ~
    $ "C:\Users\Me\AppData\Local\Programs\Zed\Zed.exe" --help
    
    Me@DESKTOP-NN7TD9I ~
    $ "C:\Users\Me\AppData\Local\Programs\Zed\bin\zed.exe" --help
    The Zed CLI binary.
    This CLI is a separate binary that invokes Zed.
    
    ...

Fix is easy then, I just deleted "C:\Users\Me\AppData\Local\Programs\Zed" from my paths.

I don't know if I added that or Zed added that path when installing (maybe from an earlier ver?), but there you have it.