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.
Just chipping in to say that I've never seen it churn for more than 20 minutes in two years worth of usage. The longest I've ever seen it churn is when I had it give extremely detailed analysis of five fictional novels simultaneously.
I spent a long time playing with the sim. Nice work.
Most of the random data sets that I ran ended up with a two body system, where the third body was flung far into space never to return. However, some of these were misleading. I had one running for 15 minutes at 5x, and the third body did eventually return.
> However, some of these were misleading. I had one running for 15 minutes at 5x, and the third body did eventually return.
That's not misleading. Real three-body orbital systems show this same behavior. Consider that such a system must obey energy conservation, so only a few extreme edge cases lose one of its members permanently (not impossible, just unlikely).
Ironically, because computer simulators are based on numerical DE solvers, they sometimes show outcomes that a real orbital system wouldn't/couldn't.
I'm just saying that, because of energy conservation, an escaping member would need to permanently carry away more than 1/3 of the system energy (for equal-mass satellites). This is possible but unlikely.
Question, can you mathmatically plot a trajectory across time X and energy required to see when it's met and how long it would take given a start position or something? Or is the simulation so complex that you can never project.
Oh never mind I see answers to this elsewhere here, cheers.
I've been using a very similar setup with vim/tmux for about 20 years. I've tried all the new IDEs but still keep coming back. With AI, I thought I was going to have to change until Claude code. Now I'm back in my happy place.