increasing my donation to FSF. we need more education on why free software and the GPL matters. Everyday is an attack on the computing freedoms that people take for granted.
> Everyday is an attack on the computing freedoms that people take for granted.
Just to be clear, Ariadna Vigo is not attacking computing freedoms; pretty much the opposite. I agree with her position on nearly everything except for her stance about the GNU operating system. This is a technical detail in the grand scheme of things. Just like tabs vs. spaces, for which it is fun to disagree in an over the top way.
We must support the FSF for pragmatic reasons, but we can still acknowledge that the "pure unix" philosophy is a great and beautiful idea. Also, cat-v and suckless are fun websites full of interesting stuff.
Yeah. Fyne picked Go because it is a great language for building a GUI - not because we were Go developers.
Fyne existed before the founders knew any Go :)
Mostly coding window managers and desktop environment in C/C++ is so painful that you can see why it stagnated 20 years ago...
Personally I think both. Yes the X11 APIs are horrible to work with - but decent code can abstract that away so the app APIs are sane. Doing that was easy with Go, but doing the same with C seems to end up passing around `void*` everywhere, so type safety (and a good coding experience) goes out the window.
I personally support Docker Desktop for Mac for an organization of 250-300 engineers.
I have been supporting it for 2 years now. Been through all the Docker Desktop upgrades, performance issues everytthing. I have researched docker performance on macs running k3d + k3s + istio and a bunch of microservices. I have had to jump into the internals of Docker daemon and docker cli and networking to solve how docker networks are provisioned for various proxying issues.
1. Docker dragged their feet with native performance for file syncing. We have to selectively enable it and just so that it doesn't bog the machine down.
2. When running it gets the CPU running at 75-80C, causing the fan to run non-stop at 3000 rpm at least. It is definitely impact by bad macbook pro design, which is terrible at airflow and heat sink activities
3. We were on unstable for a bit to test the new file syncing approach. Docker dropped that in stable and said "deal with it"
4. The paid forced upgrade notification means that I can't peg the Docker Desktop version for the whole org at a certain version.
5. Right after we switch from the unstable to stable, the next minor version is a breaking change.
6. Number 4 would be fine it docker would keep to their guarantee of stable being stable. They do a terrible job of being backwards compatible. The current stable we had was 3.3.1. With the constant minor upgrades, and pushing people, some people went to 3.6.0. (the latest as of yesterday, Aug 30) This broke everything inexplicable with just a VM error where k3d would keep crashing. I downgraded everyone back to 3.3.1 to get teams unblocked while waiting for me to find a fix.
7. Finding a fix usually involves waiting for Docker to prioritize something but at this point I don't trust that Docker know what it is doing.
I am currently pushing for Linux laptops, hosted dev environments and reducing the need to run distributed monoliths. We shall see.
I hope you do get the Linux Laptops through. I just joined s company that made an exception for me to use Linux and I haven't felt more valued ever. I never want to use another OS again.
I think it's unreasonable to expect so much from a company that doesn't make money.
The non-desktop docker product on it's own is crazy good, I think it's reasonable to expect docker desktop to improve once docker actually makes money from it and can afford to hire more engineers to work on it.
