Do you not want to be able to develop while being offline?

With AI dependence, unless you are a holdout, offline development isn't really a thing anymore. Perhaps to do some code reviews, but actually producing new code?

That is sad.

Somewhat, it's a tradeoff we are making willingly

I haven't made that tradeoff. I still code myself without agents from time to time.

Nothing changed. You can still code the old way. All those 100x productivity gains are probably closer to 10% productivity gains after you account for all the added debugging and steering.

I am retired, and don't need to - I have a couple of beelink's (just need my home wireless running) and a couple of VPS if I really want to do things away from home, which I don't

I cannot remember the last time I wanted internet access but could not find it. Cell coverage is pretty good and reliable these days.

also - I do not like developing on my personal machine. I got into this habit a long time ago - I would always use a remote Linux box, and now with LLM's I ride them bareback (or maybe they ride me). If I trash a machine (which has not happened yet), I just rebuild it or find another box.

You totally can, I got Linux+VSCode+Docker running on my new Chromebook in less than 15 minutes, without doing any funny stuff.

But for optimal DX it can still be preferable to VSCode tunnel into your big powerful dev box that has everything configured just right.

No reason that you can't. ChromeOS has supported Linux containers for over a decade.

You can use Google services on a Macbook and have installed apps.

Not for $300, you don't.

I take more risks with my Chromebooks than I do with a MacBook, such as mountain-biking with it or leaning it in a car when visiting sketchy neighborhoods. Chromebooks offer a good-enough on-the-go, full-Unix experience, with an all-day battery. Sure, M-series Macs have higher performance and >20h batteries, but those nice-to-haves re well in excess of what most users need, most of the time.

I think Google is alluding to the fact that they'll continue Chromebooks but they aren't promising anything right now, or even clarifying much outside of the specific reveals.

They've won the netbook market and they'll have existing contracts and education market to always account for. With messaging that the ChromeOS experience will change and may have some things removed to refocus it I think the assumption is that it continues within it's specific use currently.

I don't get how life is simpler.

We are way out of context window, occupied by OS chores.

Life was simpler when we were dumber, but now, no. Stop lying.

I feel like we are of a similar age. This is great advice. My small company is growing and i'm thinking this is the path so I don't need an IT helpdesk.

Do you still use vi or were you meaning vi(*) and actually use something else? I've been on vim for a while but happy to go back to vi

actually both. vim for "real" work, but also vi when I am moving though different machines that have minimal tooling (production or production support machines, which may not have vim installed). I have been retired for some time, so I am programming for fun, and have recently gotten into it a lot more with Codex/Claude. Before I retired I also used more visual editors with debuggers since we were on Macs in addition to vi/m. I have found that I don't need those fancy editors with the LLM's as I am just editing markup/config files and browsing code.

While I think Chromebooks are great, I would consider that if your company grows, not everyone is comfortable with vi/m, and a Mac does give you some nice options for higher end dev systems.

I'd love to read more about your setup. I'm doing about half of what you have.

It is very simple:

I have multiple Chromebooks and an extra monitor, and use Google for files, email, photos. I can grab my cheap Chromebook and throw it into my backpack, don't bother with a case. I have learned to live without using installed apps.

I have a couple of beelink boxes at home that I stash in the corner of a room, connected to my home wireless. I use Crostini to remote into these boxes to do any development. I treat these boxes the same way I treat my Chromebook - disposable. I have scripts that will reconstitute my dev environment from GitHub and my backups.

If I trash a chromebook, I grab or buy a new one. I can do pretty much anything (except dev work) from my phone if needed. If I trash a dev server, I use another one. I also have some virtual machines at Hetzner. I keep my backups there, as well as any apps I want public.

My only concern is my Google dependence. That is the trade-off for being 100% cloud based and treating my devices as disposable.

you can do the same with mac os and also have a great user experience; perhaps not the cheap replacement but doesn't feel right optimizing for replacement given that my devices last around 5 years anyway

The first party integration is the difference. You won't have your files and photos instantly there when you login and you'll still have to download and setup those apps.

Yes, you will.

MacOS has idrive and iphoto with all your files in the cloud.

If I walk over to your mac and log in with my appleid, I have all my stuff instantaneously.

I work across a bunch of machines (all macos) and all my stuff syncs across them pretty seamlessly.

Costs way more than chromebooks, though.