Nice one, funny internet user.

Funny how instead of fixing the issue of 'doesn't work on clients PC', we pretend the non-ideal bypass is an actual solution.

@@Robluex But deploying containers is a significantly preferable solution over trying to produce an installer that will account for multiple poorly configured customer server setups. It saves a lot of money. The greatest argument though, is that when you need to be able to rapidly increase the bandwidth in line with rising CCUs, having a containerised deployment means you can pretty much instantly bring online more capacity. It also lets you rapidly deploy hotfixes or updates, being able to know with comfort that some external dependency wont scew you.

@@charactername263 my point was that we never bothered fixing the architectural issue of computers. Having that fixed would save everyone time and money in the long run. Containerization is a short-time bypass. It’s not a better solution, as instead of native, you have to run containers, but it saved everyone resources to try and fix the “must be your pc” problem.

⁠@@Robluexthat is because the “it works on my machine” problem is not always caused by an architectural issue. Having a different, let’s say, JDK version installed on a developer machine can lead to subtle different outputs in a program that works with timestamps.

Haha, love this!

Agree)

This is so true

It's strangely really accurate

I was literally just thinking that. I’m obsessed

straight out of portal 2

Yeah for real, had the same thought.

@@untitled6087 we love exploded diagrams

"pulled the hardest banana"

a hard banana you say

A brief and no bs comment for somebody who wants a quick "review" of the video before committing to watching it; thanks.

Thank you!

Yes! And the animation does an amazing job conveying the ideas in great detail. The author is clearly a genius.

that was very nice of you to comment like that 🙂

this sounds like an insult

Thanks for the additions although not all this is correct. It's explained well below, by others.

It's because of the number 4 I quit developing using containers. Now I use many wsl2 terminals to install different Java runtimes. And inside them I code and run projects locally. Just after finishing a project locally and when I want to deploy it to my cloud dev environment I build the image. And after tested in dev env I build the production image and deploy it to the production env. Where I work we also use this workflow and for me it's the most optimal. Sometimes when I want to use a DB locally I run them using container and I use the docker host network, so they work as if in my localhost network

For number 4, you could be using the -v volume mapping feature of docker that maps a part of the host file system to a part of the container filesystem so your compiled changes can reflect immediately within the running container - no rebuild necessary, just restarting the java process (for example) is enough, or if you have hot-reload of class files enabled then you're good to go.

@@thom1218 it is also possible to change any other file within the running container, the changes persistent until you delete the container. I do this to test different configurations before including the changes to the final build of the image.

6. compatibility is not really for free because your host kernel still needs to support the features you need 7. false sense of security: mounts, the host kernel and the X server and bad defaults (like running everything as root inside your container) will remain or become vulnerable

let the container runtime handle the compatibility instead of you handle it by urself

​@@setiakiYou don't understand the problem. If the host's kernel does not support it, you can't do anything. Containers have a (mostly) hidden dependency on the kernel version.

this is extremely true now that i've started experimenting with waydroid on arch linux and learning quite a lot about kernel differences 😭🙏

the hubris of mankind will know no bounds

Because you can install/run on docker

Sometimes packages don't work as expected in different environment, i just ran into this problem today. I wasted 3 hours to setup project locally in windows when i tried to do same in my friend's mac it ran without issue. In my windows it wasn't downloading some npm packages

​@@tilakadroja Mac has been integrating a lot of linux tools lately.

@@mythbunkers4716 mac has always been basically a sibling of linux considering it's based on openbsd.

​@@mythbunkers4716 mac is very similar to linux anyway

if you like bloat, you like bloat.

Haha thank you! Glad you like the style :)

It's like you're reading from documents, but more concisely.

@@coderized Now that sweet ASMR praises has come and pass, let me criticize you on the sound: _you really should edit your wet sloppy sounds out, like many others._

@@ultimaxkom8728 🤤

another channel that fits the description is NoBoilerplate, love both channels

VSCode is not an IDE?! o.o

@@pawekoaczynski4505 Yeah I feel you, but it's still a relatively new feature so I'm hoping it'll mature with time. WSL definitely did! Thanks for the addition, it's great for people to be aware of these current pitfalls!

"if you use VSC" as if 99% of all developers ever aren't using vsc bruhhhh

@@8jjiyu654 It is, why? 🤔

@@coderized I am not an experienced programmer. I had heard that VSCode isn't an IDE. How's it otherwise for you? O.o

Thank you :)

Thank you Sufi - glad you liked it! 😊

@@coderized seriously, one cannot overstate how absolutely refreshing it is to be able to watch an informative youtube video with out constant annoying epileptic-tier cuts, over-hyped voices, and distracting background music. thank you.

@@pigsweat7763 Super accurate!

such an amazing vid

Just subscribed.

That doesn't surprise me at all, cloud VM solutions generally seem to be the current happy middle ground between agility, customisability and ease of use It wouldn't surprise me if containers quickly mature in the not so distant future to overtake this though, more sensible defaults alone would make the process less arduous in my opinion

I am strongly of this opinion as well. I understand containers, I use them all the time, but in my opinion their use case is quite narrow. They solve a very specific problem, and they are NOT a panacea. In a desktop environment, they cause far more problems than they solve and I'm pretty fatigued by all the different solutions for containerized desktop applications that claim to finally be the one that gets it right. They all suck, and I intend to happily continue using my package manager and dynamically linked libraries.

Coincidence? Or conspiracy? 🤔😆

@@coderized Touching a banana. ;)

Thank you for the comments Tabs - was really motivating to read this morning! I appreciate the feedback a lot :)

You likely did learn about hypervisors and operating systems fundamentals, though. These are all prerequisites to actually knowing how a container works and what it really is.

​@@nomathic7672 if it's just that then yeah

Thanks Patryk! 💜

It’s for people that don’t know how to take snapshots of their OS and don’t know what multi process applications are. You can run 65,535 Web servers per nic.

kzfaq.info/get/bejne/qM6XqqyZp5ucgHU.html

Be sure to watch a few more videos about this subject though. What is said in this video it’s not the entire or the only truth.

Thanks, no other experience but a compliment that you think so!

Thanks! 😊

Thanks Geralt!

Thanks! Yeah my goal is to spread awareness and provide a little understanding rather than teach it specifically. I can recommend Techworld with Nana for learning the details :)

Yeah in hindsight, maybe it was too much of an oversimiplification with that part

I see. So that's why with containers it sometimes matters what host OS I'm using? Because the container will have a different kernel at its disposal and a different set of executables to use and yadda yadda

@@JohnDoe-ng6ec the host OS will almost always be Linux, as the Linux kernel is what is really providing the process separation that your containers are utilizing. If your host OS is Windows or MacOS, the container software will almost always be launching a (hidden) Linux virtual machine where your containers run. Now Microsoft has created their own thing that allows you to run Windows executables natively as a "container" too, but I haven't played with them. 99% of the time when someone is talking about containers, there is a Linux host OS (kernel) involved. Also, the container image has metadata that indicates that platform architecture (ex: amd64, arm64, etc) because the executables are natively compiled for your processor type -- so when you "pull" a container image from a container registry, the client software (ex: docker) will ask the registry for the image that best matches your processor type. Containers best feature, in my opinion, is that they are nice prepackaged bundles (container images) that have all the dependencies baked in: so you aren't fiddling with the host OS and dealing with installing dependant libraries on the host.

@@beepbop6697Couldn’t that dependency issue be solved most the time by static linking? People in the industry often complain about statically linked executables having large file sizes but an equivalent docker image will probably take up even more disk space.

Actually, LXD/LXC containers are 'system containers' that run a full Os and you can manage them pretty much as if they were a physical machinie. Docker and Podman are 'Application Containers', meaning they usually package a single app.

This is pretty far down in the comments so I didn't realize you beat me to it lol.

Well for one, that’s not a fair test because you’re giving one machine two kernels to run. Guess what’s even faster than containers multiple processes which again all share the same kernel, but without the overhead. take snapshots of your production machines and I don’t see what containers are really simplified other than making it impossible to fix things quickly quickly

Because the software is so poorly written that it can only run on a system that can instantly throw out a crash and start over without losing work 😬

@@Bobo-ox7fj huh? i think you missed my point. look at the title of the video. it's so misleading, just perfect clickbait example yet noone mentions it, like it's fine. he definitely knew what he was doing. my last comment, i'm not giving this shameless ytber more attention.

Lets learn some media literacy! Why would someone say "don't install locally" then run through common issues like the too common "it works on my machine" ? That's right, because they're implying using docker images to do installation stuff so that you don't have issues when deploying! Look at you, learning so fast

​@@thatguy5233 It's not misleading, it makes sense to a developer, so if you weren't able to connect the dots, then you probably don't need to worry about it in the first place.

Very happy someone noticed that 😄

I'm about to set up a NAS server at my job and I'm getting the impression that the only practical way to do that is on the hardware.

Hooray for FreeBSD jails!

Containers are useful because most software is messy piles of crap today that needs tons of things intertwined to look good. Many things however are still single monoliths

Was scrolling through the comments to find the other Nix users, glad to see others enjoying the best tool for this job 😎

I think one issue I have with over-reliance on containers is that it traps you into a "contain/virtualize everything" mindset instead of properly understanding your dependencies or fixing more serious issues in your architecture. Using containers are not the end of the world but I do think it adds bloat (size, iteration time, etc) if it's not necessary to use it to begin with. Containers is very useful, of course, but it's not a panacea, and sometimes I feel that people who are used to it just default to using it without thinking through the pros/cons.

Nix seems to be much more granular than most containers. Rather than using a standard pre-configured distro running on top of your primary OS, Nix, using much simpler features, gives you exactly the dependencies you asked for, and _only_ the dependencies you asked for. And then it tries to share as much as it can prove is safe between different environments, which it can get away with because it relies more on path variables than a fixed filesystem hierarchy. It's honestly something of a shame that containers and other immutable systems get all the hype, while Nix uses a completely different (arguably better) approach to solve the same problems.

@@angeldude101 Yeah. I think this "just use containers for everything" trend and also newer binary app distribution formats like Flatpak have some of the same traits. They essentially say "we don't want to solve the problem of creating a deterministic system", and so we over-virtualize (I'm using the word "virtualize" in a general sense) and re-duplicate everything and call it a day. It does work, but I'm not sure if it's really the best solution. I guess sometimes, the mediocre solution that works well enough and is easy to deploy tends to win.

@@angeldude101 TOTALLY agree. I think many are put off by the idea of learning a new language (Nix), but then go learn Dockerfile anyway. Nix's approach is easily the best, I 100% agree. Flakes further perfect the concept as well.

Not really, he didn't cover...A LOT...like the UEFI settings you need to run one etc

@@rarespetrusamartean5433shut up

Thank you Tommaso!

Software info in discord

Bro, I almost thought it was a terraria pet reference. Then rememberred that it was added as reference to the companion cube and I was like... "poonter of pointer of"

Yess! Hardly anyone got it, as you said. Maybe most viewers are too young. Tron was always one of my favourite movies growing up.

@@coderized hell yeah man. im a big fan of tron, even though i am pretty young. ranked 1# movie in my book. i loved the new one and the old version

@@undefined4277 You're my new favourite person ;)

There’s nothing faster than running on bare metal. There’s no reason why you need multiple containers sharing a kernel, when instead you can have multiple processes that share the same kernel. … other than that you want to add a layer of emulation in between. You can run 65,535 Webb servers on a single machine with one NIC

😂

@@coderized bro read every single comments and I appreciate that, and I look forward to more future videos.

I hope you find them as useful as I have over the years!

Thanks for watching regardless Alexander! Glad you enjoyed it :)

Yeah different arches definitely need to be considered, nice addition. Maybe I'll make a part 2 someday

Haha, my favourite bit, glad you liked!

in fact, cramming a given nix closure (for curious readers, that's just a fancy term for a store path & the paths it depends on) in a container is significantly closer to the original minimal-environment vision of containers as opposed to the typical start-off-by-pulling-in-ubuntu monstrosity that a given app's official docker image has a good chance of being. not entirely clear on what cursed politics gave us the world in which "distroless" containers are some wacky revolutionary idea rather than the norm but hey lol.

nix gang RISE UP