-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I myself use Linux (Ubuntu/Arch/NixOS) via Windows WSL2.
I would say that the developer experience on MacOS (with or without Apple Silicon) is "sufficient" for the vast majority of use cases, but there have been some pain points that I describe below as emblematic issues.
If you're developing applications that are intended to run on Linux servers, perhaps MacOS is not the best tool for the job. In that niche, you're likely to be running a different OS, on a different architecture, and perhaps even relying on binary translation (Rosetta 2) to run the same applications as in your target environment. For these sort of "close to the metal" development roles, I recommend aligning your developer stack with your target.
For the vast majority of other development roles, from data engineering to frontend web, I admit to being a little envious of what folks say about their Apple Silicon devices.
Examples of issues I've seen recently with development on MacOS (with or without Apple Silicon). Keep in mind, these are edge cases these days and only listed as examples:
* Major impediments to using the Python gRPC library on Apple Silicon until very recently (https://github.com/grpc/grpc/issues/25082)
* Docker performance was dramatically worse than Linux & Windows until recently, with a recent update improving things for all Mac users, not just Apple Silicon (https://www.docker.com/blog/speed-boost-achievement-unlocked...)
* Performance of virtualized x86-64 applications work against many of the performance benefits of the M1/M2, this is especially prevalent with Docker containers that are built only for x86-64.
* Homebrew is an absolute must, do install script maintainers and colleagues a favor by installing the latest GNU userland (coreutils), as your Mac will come with GNU utilities circa 2007 (the last GPLv2 releases of GNU utilities)
Vagrant has a few advantages compared to Rancher (and Lima[1] which I believe Rancher uses under the hood).
Because of it's popularity, there are so many open source Ruby provisioning scripts you can use as a reference when provisioning your own vms. You can also package up a provisioned vm as what they call a "box" that can be shared with other developers. It also natively integrates with tools like Ansible, Chef, and Puppet which make it a lot easier to manage the provisioning process.
And finally, many of the books and tutorials I've read use Vagrant, so it's much easier to follow along if you have Vagrant installed. For example I was recently reading the book Ansible for Devops by Jeff Geerling, and Vagrant and Virtualbox were used pretty extensively throughout the book.
Also, if you decided to package vms to use in production its pretty easy to integrate with Packer, which is another Hashicorp product.
[1] https://github.com/lima-vm/lima