This was all supposed to be worked out prior to Cloud Next, but it wasn't. Ironically, they mentioned Claude in a few of their presentations at next.

And that was our solution. We are a big GCP customer but our whole team is on Claude now and much happier.

I personally chose C# for this reason, because ASP.NET is mature and (IMO) well designed. But there's also Java/Spring and and lots of other options in different languages depending on your preferences.

Popping open Activity Monitor, when I have a lot open my swapfile regularly hits 6GB and memory pressure is yellow, but I'd have no idea otherwise.

Not to say the rumoured 12GB in the next Neo wouldn't be better, but for the price you can't go wrong.

While I lean on VSCode remote SSH pretty heavily so you could argue I'm using it as more of a thin client, I've ended up using the Neo more than any of my other machines.

My Windows and Fedora machines have 2-4x the RAM but the Neo is just as responsive when juggling 20 Firefox tabs and a few other apps (mostly electron eg. Slack).

At my workplace, we use the .editorconfig and static analysis heavily to push us towards a consistent C# feature-set and style. This plays the same role that pyupgrade would in python, for instance.

It's not MacBook good but it's much better than 3hrs :)

I have a Ryzen 5 AI 340 powered machine and average about 6 hours. I might be able to stretch that to 7 if I dimmed the screen a bunch and only did light web browsing.

This is closer battery life to MacBook Neo, not an Air or Pro under the same workload.

I daily drive VS Code remote SSH and had a (honestly inexplicable) thing for Chromebooks for a while. Before the included Linux environment let me install "real" VS Code, these options worked well for me.

Not all workloads are HTTP.

> gateway .. for millions of customers

That's basically what an AWS ALB is. It's not provisioning bespoke infrastructure when you create it.. it's just a routing rule in their shared infra.

If Amazon wanted, they could easily have shared IP's but the cost of an IPv4 isn't so great that this approach has been warranted yet, clearly.

So all this is doing is adding context for the LLM and some persistence.

I have yet to see a compelling use case for Gemini Enterprise at my company but we're still experimenting with it.

As other commenters have stated, maybe this isn't the best place to ask.

I'm definitely in the "almost all of it" camp. I have Diablo II game saves on my desktop that are carried forward directly from my Windows 98 SE box circa 2002-2003. As well as Linux ISO's I acquired on Kazaa while still on dial-up internet.

Well that's your problem right there. The home labber setups are for experimentation or "hot rodding" purposes and they typically way overbuild their solutions.

What most people need is an old desktop in a corner somewhere (preferably close to your router so you can get to it with an ethernet cable).

It's won't be Grandma proof, but if you're remotely technical you can write a docker compose file that glues together some useful home server utilities that sound interesting to you.

My setup is roughly speaking: Ubuntu LTS, ZFS (with 4 disks in a RAID10 style config), and a docker compose file that runs plex, transmission, syncthing, vaultwarden behind an nginx-proxy[1] container that even automagically renews my Let's Encrypt certs for me (though it's probably even easier if you use a Cloudflare tunnel).

If you're confident all your apps are available on these platforms, the storage part is easier with something like TruNAS or Unraid. If you don't need storage at all you can slim down your hardware a lot and just use a raspberry pi.

IMO, just find an old beater machine and get hacking :)

[1]: https://github.com/nginx-proxy/nginx-proxy

[1]: https://jellyfin.org/downloads/dotnet