I’m not an open source guy - redistribution restrictions (as well as restrictions for corporate and commercial use) are non negotiable for me. You’re welcome to learn from the source code, and anyone is free to fork and make whatever changes they want for personal use.

The license history for this project goes MIT > PolyForm Strict > Forked PolyForm Strict to explicitly allow changes for personal use (named as the “Komorebi” license as changing the text of PolyForm licenses requires removal of the PolyForm trademark).

If anyone is interested in the story behind the initial MIT > PolyForm Strict switch, the tl;dr is that I decided to explicitly restrict redistribution after someone did a rename of the project and started selling it on the Windows Store. A lot has happened since then that has changed my views on open source in general.

non-standard

OSI licenses are not “standard” by any stretch of the imagination, and I personally don’t want to have anything to do with licenses which would permit the use of my software in the mass murder of children.

It’s not exactly a traditional RSS feed, but I run a feed of my highlights on all things related to software development, and I’m an experienced DevOps engineer so a lot of my highlights are coloured by that experience.

If you come across a highlight that is interesting you can click to go and read the whole source article or comment. You can check out a HTML version before you decide if you wanna subscribe to the RSS feed.

The whole point is that you can build a working container image and then ship it to a registry (including private registries) so that your other developers/users/etc don’t have to build them and can just run the existing image.

Agreed, we still do this in the areas where we use Docker at day job.

I think the mileage with this approach can vary depending on the languages in use and the velocity of feature iteration (ie. if the company is still tweaking product-market fit, pivoting to a new vertical, etc.).

I’ve lost count of the number of times where a team decides they need to npm install something with a heavy node-gyp step to build native modules which require yet another obscure system dependency that is not in the base layer. 😅

We all use Linux on our workstations and laptops. That might make it easier.

You are living my dream!

I think this is the key piece; the experience of Docker on Linux (including WSL if it’s not hooking into Docker Desktop on Windows) and on macOS is just so wildly difference when it comes to performance, reliability and stability.

Thanks for sharing this! Added to my weekend inspiration/reading pile. 🙏

Highly recommended viewing if you’d like to learn more about the limits of reproducibility in the Docker ecosystem.

Tutorial != advocation. As I said, no attempt to engage in good faith.

I understood your point, and while there are situations where it can be optional, in a context and scale of hundreds of developers, who mostly don’t have any real docker knowledge, and who work almost exclusively on macOS, let alone enough to set up and maintain alternatives to Docker Desktop, the only practical option becomes to pay the licensing fees to enable the path of least resistance.

Lot’s of (incorrect) assumptions here and generally a very poorly worded post that doesn’t make any attempt to engage in good faith. These are the reasons for what I believe is my very first down-vote of a comment on Lemmy.

NixOS on WSL2 is actually my development environment of choice these days! (With my tiling window manager komorebi, of course! 😀)

I believe this is the Docker Desktop license pricing.

On an individual scale and even some smaller startup scales, things are a little bit different (you qualify for the free tier, everyone you work with is able to debug off-the-beaten-path Docker errors, knowledge about fixes is quick and easy to disseminate, etc.), but the context of this article and the thread on Mastodon that spawned it was a “unicorn” company with an engineering org comprised of hundreds of developers.

Hi!

First I’d like to clarify that I’m not “anti-container/Docker”. 😅

There is a lot of discussion on this article (with my comments!) going on over at Tildes. I don’t wanna copy-paste everything from there, but I’ll share the first main response I gave to someone who had very similar feedback to kick-start some discussion on those points here as well:

Some high level points on the “why”:

• Reproducibility: Docker builds are not reproducible, and especially in a company with more than a handful of developers, it’s nice not to have to worry about a docker build command in the on-boarding docs failing inexplicably (from the POV of the regular joe developer) from one day to the next

• Cost: Docker licenses for most companies now cost $9/user/month (minimum of 5 seats required) - this is very steep for something that doesn’t guarantee reproducibility and has poor performance to boot (see below)

• Performance: Docker performance on macOS (and Windows), especially storage mount performance remains poor; this is even more acutely felt when working with languages like Node where the dependencies are file-count heavy. Sure, you could just issue everyone Linux laptops, but these days hiring is hard enough without shooting yourself in the foot by not providing a recent MBP to new devs by default

I think it’s also worth drawing a line between containers as a local development tool and containers as a deployment artifact, as the above points don’t really apply to the latter.

This bit is awesome, a shoe is lost but nothing can stop the dance. 🎉

If you like swing dance (either as a dancer or an observer), come and join us over in !swingdancing@lemmy.world!

It’s a piece of software which automatically arranges open windows on your desktop according to different algorithms and layouts, and allows you to switch focus them and move them around in the layout by using keyboard shortcuts. One you get in the flow, you very rarely have to use the mouse to move windows around, maximize them, minimize them, resize them etc.

If you’ve ever seen a post on !unixporn@lemmy.ml or similar places, the vast majority of them are using tiling window managers to get that look of clean organized windows on the desktop!

It hurts economically to live here, but even with that and all the social problems, it’s still the best city I’ve ever lived in. 🤷‍♀

Beautiful!

If you’re already familiar with this video, you may feel at home with us in !recovery@lemmy.world! :)

And so it begins again…

This is exactly what I needed for the desktop!

If I can even help one person avoid that same fate, it’s worth it!