2,117 karma · joined March 13, 2013
I've actually spent a decent amount of time running an excavator, as my Dad owns a construction / road building company. It was a great summer job!
An important note about the pilot hydraulics is that they _provide feedback to the operator_. I would encourage any system that moves these controls on behalf of a remote human operator or AI to add strain gauges or some other way to measure this force feedback so that this data isn't lost.
The handful of "drive by wire" pieces of equipment that my Dad or other skilled operators in my family have ran were universally panned, because the operators are isolated from this feedback and have a harder time telling when the machine is struggling or when their inputs are not sufficiently smooth. In the automotive world, skilled drivers have similar complaints about fully electronic steering or braking systems, as opposed to traditional vacuum or hydraulic boosting approaches where your foot still has a direct hydraulic connection to the brake pads.
My Framework 13 has the Ryzen 5 AI 340 Chip, and I get 5-6 hours of work on a charge. The Macbooks definitely beat this, and their hardware has other benefits (silent if you opt for the Air, bigger/better trackpad, etc) but for me, being able to run Linux is worth the trade-off by far.
I like that on Linux (GNOME) I have all the functionality I need out of the box without having to install a paid app for window snapping (I heard they fixed this recently?) or to make my mouse buttons work. I also find that since I work with containers a lot, developing on Linux removes a lot of friction. I can run docker/containerd natively without having to babysit a VM that likes to eat all my RAM or hang randomly (no docker/rancher desktop layer). Even just having the same coreutils and package managers as I do inside the containers really simplifies things. Our MacOS devs are always struggling with homebrew putting shared libraries weird places that can't be found by the python bindings and this "just works" on Linux.
Up until a year ago where I live, Chevron 94 Octane was ethanol free. I had issues with older carbureted engines after leaving gas in them for ~2 years. With E10 I wouldn't dare go that long as it can be so corrosive.
Yet the roadmap says:
> As Mojo matures through phase 3, we believe Mojo will become increasingly compatible with Python code and deeply familiar to Python users, except more efficient, powerful, coherent, and safe. Mojo may or may not evolve into a full superset of Python, and it's okay if it doesn't.
This is incredibly confusing. If it's _not_ aiming for Python compatibility, why are we talking about Python at all?
Also, is anyone actually considering using an emoji as a file extension?
The same goes for typing.. mypy (written in Python, and contributed to by Guido himself) performed so poorly that they had to invent a bespoke compiler for it (mypyc). The other options written in Rust or node are much more performant.
Another example: the golang port of the Typescript compiler.
I agree with the take it's odd to write a nuget server in node, but the comparison to uv isn't fair. There's concrete reasons to choose a more performant language for the task.
Agree to disagree!
It's not 8-12, and the fans do kick up. The track pad is fine but not as nice as the one on the MacBook. But I prefer to run Linux so the tradeoff is worth it to me.
Battery is good enough (5-6hrs) for me on the AMD model (Ryzen AI 5 340) but definitely not Macbook territory in that regard.
I run Fedora and have coworkers who run Ubuntu and Arch as well without issue.
Within the incus dev environment container though I'm pretty sure I want to keep docker, as I have a lot of tooling that expects it for better or worse (docker compose especially). It also doesn't appear incus integrates buildkit etc. so even if I used it here, I'd still need something else to _build_ OCI images.
Incus is an LXD fork, and focuses on "system" containers. You basically get a full distro, complete with systemd, sshd, etc. etc. so it is easy to replace a VM with one of these.
podman and docker are focused on OCI containers which typically run a single application (think webserver, database, etc).
I actually use them together. My host machine runs both docker and incus. Docker runs my home server utilities (syncthing, vaultwarden, etc) and Incus runs a system container with my development environment in it. I have nested c-groups enabled so that incus container actually runs another copy of docker _within itself_ for all my development needs (redis, postgres, etc).
What's nice about this is that the development environment can easily be backed up, or completely nuked without affecting my host. I use VS Code remote SSH to develop in it.
The host typically uses < 10GB RAM with all this stuff running.. about half what it did when I was using KVM instead of Incus.
Disagree. People vastly overestimate the complexity of hybrids.
The mechanical and electrical components in a Toyota-style planetary gear based hybrid are much simpler than a standard automatic transmission, and demonstrably more reliable than both a conventional automatic and belt-style CVT.
This is a long way of saying, the specific market segment hybrids are a good fit for is the set of all passenger car customers that an EV is _not_ a good fit for. Anyone buying a Corolla, Civic Rav4 or CR-V should be buying the hybrid, and sales seem to be trending that way.
I mostly use VS Code to be honest. I use VSCode for other languages and for a long time it was the only graphical editor to have good remote development (over SSH) support.
Rider has that feature now though and is pretty nice too. I typically jump over to it when I need to profile something as it integrates with dotTrace. If you're coming from full-fat Visual Studio you'll probably prefer Rider.
I don't think we're there yet, but it's reasonable to expect at _some point_ your typical OS model could be 98% of the way to a cutting edge commercial model, and at that point your last sentence probably doesn't hold true.