News for hackers. Stuff that matters.
Re:The sad state of sysadmin in the age of containers (2015) by jwr on Monday December 09, 2019 @05:53AM (#21741677)
I recently had a similar discussion with people using npm for building a CSS framework library. I tried to explain the concept of getting a pre-downloaded tarball and using "make" (or similar) to produce target artifacts from source files in a deterministic, repeatable and reliable manner, without relying on any third-party servers being available and without pulling in dependencies that might have changed.

It seems the concept was entirely alien to programmers younger than me.

Re:The sad state of sysadmin in the age of containers (2015) by y0y on Monday December 09, 2019 @07:14AM (#21741973)
I know you're taking some flack for making it about age, but I do think there's some merit there. I'm 34. I feel like I'm in the middle in terms of software developer / sysadmin age. Lots of bright minds came before me and there are lots of bright minds out there right now in their early 20s.

A key difference is I can remember a time when network connectivity was flaky. When it was hardly a given. Even when it was available, the download times alone could often constitute a large part of the overall build time.

I think that we have all become complacent with regard to internet connectivity and service availability, but I think the younger you are the more complacent you are likely to be. If github.com goes down entirely, let's be honest - there are a lot of Jenkins builds that are going to be in the red.

Re:The sad state of sysadmin in the age of containers (2015) by phaedrus on Monday December 09, 2019 @09:49AM (#21743075)
I'm 36 and recently was assigned to mentor a new employee in his 20s. We had a moment of miscommunication when I asked him to use git to clone a local repository. He was confused when he couldn't find it on github.com (what I'd sent him was a path to our private network share). I had to explain that, yes you can use the github.com client if you want, but "git" is different from "github". I honestly couldn't tell if he understood the difference.

Now I'm losing sleep worrying if there's any way he can accidentally add a github.com remote to our private repo and push to it. I would be blamed, and I'd have to explain to managers older in turn than me what both git and github are.

Re:The sad state of sysadmin in the age of containers (2015) by chefandy on Monday December 09, 2019 @10:50AM (#21743609)
I've worked with developers that have used git for 10 years who didn't fully realize what all of the 'git reset' options entailed, and I don't blame them. Git is complicated and you could certainly have a perfectly effective workflow with it for your whole career without using most of the features. If you'd only worked in environments in which code was entirely managed in GitHub, you probably wouldn't know that either. Judging someone because they don't possess the same slices of implementation-specific knowledge you do doesn't really make sense. They almost certainly know things that you don't simply because you've never encountered situations in which you had to learn about them, or for that matter, remember them even if you did.
Re:The sad state of sysadmin in the age of containers (2015) by u801e on Monday December 09, 2019 @01:10PM (#21744867)
> I've worked with developers that have used git for 10 years who didn't fully realize what all of the 'git reset' options entailed

While knowing some of them, if you use git reset on a frequent basis is expected, knowing where to find information on the other options is essential. I frequently go back and read through the man pages for various git commands so that I understand what will happen if I use a particular set of options and also to learn new things while reading through them.

So, the proper answer for a developer who doesn't realize what a git command is capable of is to refer to the man page for that particular command.

Re:The sad state of sysadmin in the age of containers (2015) by edoo on Monday December 09, 2019 @06:03PM (#21747635)
Re:The sad state of sysadmin in the age of containers (2015) by u801e on Monday December 09, 2019 @07:27PM (#21748325)
I believe it's more beneficial for developers to learn the underlying model of how git works (blobs, trees, commits, tags, etc) and how various commands deal with those underlying concepts. The Pro Git book git internals chapter is a very good place to start. That, in combination with the man pages for the commands they go over, will greatly enhance one's understanding of how git works.

Relying on cheat sheets to learn how to use git is not much different compared to learning how to use a programming language via Stack Overflow. In other words, you'll never develop a more thorough understanding of how the tool works and how to use it effectively.

Re:The sad state of sysadmin in the age of containers (2015) by chefandy on Wednesday December 11, 2019 @11:29AM (#21764018)
Right. Assuming that they're not competent because they can't recall a slice of domain-specific knowlege from memory is not good.
Re:The sad state of sysadmin in the age of containers (2015) by jeltz on Monday December 09, 2019 @10:38AM (#21743491)
I am the same age as you, but I do not think this is about age, at least not mainly about age. My father who is almost 70 has no issue understanding what git and github are and I have worked with people under 25 who have not had an issues with this distinction either. And there are plenty of open source developers I have met who are pushing 70 who keep up with technology just fine.

Sure, I notice that younger developers do not know some things, like they never experienced the Java EE hype, so they can fall into some traps which are well known among older engineers.

Re:The sad state of sysadmin in the age of containers (2015) by ryandrake on Monday December 09, 2019 @11:45AM (#21744054)
Yea this seems like more of a competence-related problem than age-rated. I never even considered that I might have to ask candidates if they knew the difference between git and github but now I wonder....
Re:The sad state of sysadmin in the age of containers (2015) by saagarjha on Monday December 09, 2019 @04:46PM (#21746965)
> I had to explain that, yes you can use the github.com client if you want, but "git" is different from "github".

To be fair, this is largely the result of a concerted effort by GitHub to muddy the difference. If you didn’t know any better, you might think Google is the internet too.

Re:The sad state of sysadmin in the age of containers (2015) by diehunde on Monday December 09, 2019 @04:56PM (#21747054)
That's funny. That same situation (not understanding that git and github are different things) has happened to me a couple of times but with older engineers.
Re:The sad state of sysadmin in the age of containers (2015) by IAmEveryone on Monday December 09, 2019 @08:19AM (#21742314)
People adapt to the situation they experience. Github (and other repositories) tend to be stable, so they are used. Network speeds have increased, so we use the network and expend less efforts on local caching etc.

There's nothing "complacent" about this: previous generations also relied on infrastructure and didn't plan for prolonged power outages or had backup ham radio network links for when AOL was down.

People using nom install instead of custom makefiles aren't ignorant or stupid, they have found better ways to achieve their needs. And if 10 years on the job don't create the need to learn some skill, there is no reason to invest time into it. And I have complete confidence that people would be able to come with some workable solutions rather quickly if the githubcopalypse ever happens.

There is some cultural component at play among the "luddites" here as well, maybe comparable to preppers? It feels like planning for really exciting emergencies when one's skills that have been derided for so long are suddenly needed and safe the day. In this analogy, I guess Makefiles are the equivalent of very masculine hunting and zombie-defending skills.

Re:The sad state of sysadmin in the age of containers (2015) by tonyarkles on Monday December 09, 2019 @09:24AM (#21742863)
I half agree with you, and am chuckling a little bit about the "very masculine hunting and zombie-defending skills" part, but... I'd like to offer some perspective.

I'm 36 and work on a pretty broad set of consulting projects: some schematic/PCB/mechanical design, firmware, some lower-level desktop/server code, and up and up to web/mobile apps. "Full full stack" if you will.

I live in a "major" Canadian city (although not in the top 15 by population), and I also own two wonderful properties about an hour out of town in a quite rural area. One is a cabin on a lake, and the other is a church from the 1910s. Sometimes I head out to one of these places to do the "Deep Work" thing, distraction-free, and sometimes it's to take time off, but end up getting an emergency call from a client. In either case, my Internet connectivity is limited to tethering, and depending on a few factors, that can either work fantastically well or poorly.

Going from the lowest-level to the highest-level projects, there's a very clearly declining probability of the project being able to build during a low-connectivity event. The embedded stuff pretty much always works just fine (it's a Makefile, or CMake). The C desktop/server stuff? Always works fine (any dependencies were pre-installed). Python/Ruby/Elixir web backend projects usually go OK, although I've occasionally ran into issues where the package manager wants to check for updates. Node front-end builds sometimes start to fall apart, and Android (via Android Studio) often refuse to build at all! (Some kind of weird Maven/Gradle thing that needs to go out and check something, even though the dependencies have all been pre-installed...)

It's extraordinarily frustrating when you can't change a line of code and hit "Build" to test a change locally. Everything's already present on the machine! It worked just fine 5 minutes ago!

To your prepper comment, and the previous comments about infrastructure, there's a significant population of the world that doesn't have 100% reliable infrastructure, even in Canada and the US. The tools we have used to work just fine in that environment, but are getting progressively worse.

Re:The sad state of sysadmin in the age of containers (2015) by Bjartr on Monday December 09, 2019 @12:17PM (#21744344)
> Some kind of weird Maven/Gradle thing that needs to go out and check something, even though the dependencies have all been pre-installed...

It is often possible to tell Maven at least to work in offline mode and not check for dependency updates.

Re:The sad state of sysadmin in the age of containers (2015) by u801e on Monday December 09, 2019 @10:26AM (#21743384)
> There's nothing "complacent" about this: previous generations also relied on infrastructure and didn't plan for prolonged power outages or had backup ham radio network links for when AOL was down.

A lot of the protocols for asynchronous communication allowed for operating in offline mode. So if you didn't have an internet connection, you could still compose and send emails, but the client would only actually connect to the network when were actually connected and send the emails all at once (as well as downloading emails from the POP or IMAP server).

git actually has commands that leverage email for sending an receiving patches, so that code review and development can take place without requiring a connection at all other than to send and receive when needed.

Re:The sad state of sysadmin in the age of containers (2015) by saagarjha on Monday December 09, 2019 @04:48PM (#21746987)
> A key difference is I can remember a time when network connectivity was flaky.

I’m young enough for this to not be something I have experienced, but I don’t have to have to understand that depending on things you don’t have control over can be a bad idea.

Re:The sad state of sysadmin in the age of containers (2015) by ekidd on Monday December 09, 2019 @09:14AM (#21742772)
> without relying on any third-party servers being available and without pulling in dependencies that might have changed.

There are two different issues here:

1. Not pulling in changed dependencies. This is what "lock files" are for: To limit builds to known version of every dependency. npm was terrible about this for a long time. Most other language package managers are better.

2. Not relying on third party servers to be available. Personally, I've mostly worked with Ruby's bundler and Rust's cargo, and in over 10 years, I've lost maybe two days of work because of package server outages. That's less than I've lost due to S3 outages, less than I've lost due to broken backup systems, and less than I've lost due to complex RAID failures. For the clients and employers in question, this was acceptable downtime.

In the rare cases where one day of noticeable build downtime every 5 years is unacceptable, then it's usually possible to just "vendor" the dependencies, usually by running a one-line command.

For many small to midsize businesses (and many growing startups), a small risk of brief outages is an acceptable engineering trade-off.

Re:The sad state of sysadmin in the age of containers (2015) by hn_throwaway_99 on Monday December 09, 2019 @09:41AM (#21743007)
> npm was terrible about this for a long time.

That's putting it lightly. To me "terrible" would mean they just didn't support it, "batshit insane" means they supported lock files but ignored them every time you ran npm install.

My favorite comment from this stackoverflow post: https://stackoverflow.com/questions/45022048/why-does-npm-in...

"Why would you expect something called package lock to lock the packages? Package lock is analogous to how, when you put any key into a door lock, the lock reshapes itself to match whatever key was put in, then opens the door. Now if you'll excuse me, I'm late for a tea party with a rabbit."

Re:The sad state of sysadmin in the age of containers (2015) by hinkley on Monday December 09, 2019 @04:26PM (#21746773)
I think one of the scenes with Humpty Dumpty could be an appropriate allusion as well.
Re:The sad state of sysadmin in the age of containers (2015) by dirkf on Monday December 09, 2019 @10:18AM (#21743313)
At work we also cache all 3rd party dependencies locally. Not because the 3rd party servers might be down but to be sure that one/two/... years from now we can still recreate the same software we delivered at that time to a customer. Our build machines typically didn't even have internet access. If a dependency was not available offline (due to developer error or whatever) we would know quickly.

In certain industry branches this is even mandatory if you want to be seriously considered as a supplier. If a build tool does not support reproducible builds in such a way (both fixing dependency version and getting it from a cache somehow) or makes it difficult then it is considered as a hobby toy that has no place in the workplace.

Even for small businesses I would advocate to take this seriously from the beginning. It's not that hard and will save you headaches later on when suddenly reproducible builds become important.

Re:The sad state of sysadmin in the age of containers (2015) by hartzell on Monday December 09, 2019 @09:02PM (#21748921)
> At work we also cache all 3rd party dependencies locally [...]

Can you say a bit about your platform and tooling? Are you working in a single language or a polyglot world? Is the cacheing at the network level or are your build tools aware of your mirrors?

I work in a space (biotech/pharma/...) that shares these concerns. I've solved the Perl specific version with Pinto (https://metacpan.org/pod/Pinto) and the more generic version with Spack (https://spack.io) [which is neat also because it supports installing multiple versions of applications, doesn't require root, <other things>].

Re:The sad state of sysadmin in the age of containers (2015) by forgottenpass on Monday December 09, 2019 @10:36AM (#21743472)
>I've lost maybe two days of work because of package server outages [...] For the clients and employers in question, this was acceptable downtime.

Even if the downtime is fine, I don't find it goes over too well if framed as "we rely on a 3rd party service, that we have no contract with nor any guarantees of reliability or product longevity."

Re:The sad state of sysadmin in the age of containers (2015) by hinkley on Monday December 09, 2019 @04:24PM (#21746754)
npm has only gotten worse about lockfiles over time, not better. I wonder out loud some times if they know what the word 'lock' means.

If yarn would fix a particular bug that blocks our workflow I'd be burning political capital at work to get us off of npm as fast as humanly possible.

As to proxies, we have something misconfigured with ours, such that occasionally it gets latest of half of the React or Babel ecosystem and latest-1 of the other half, resulting in dependencies that can't be resolved for a few hours when they increment a minor version somewhere.

Re:The sad state of sysadmin in the age of containers (2015) by mixmastamyk on Monday December 09, 2019 @02:31PM (#21745572)
There are other advantages such as build speed. Having local copies is simply faster.
Re:The sad state of sysadmin in the age of containers (2015) by Tade0 on Monday December 09, 2019 @06:24AM (#21741787)
Truth be told the whole front-end ecosystem relies on those servers being available, so in their absence any development everywhere would grind to a halt - as it almost did during the left-pad scandal.

While I agree that this is not exactly the sanest approach, within the ecosystem there's no incentive to work differently.

Also, like someone else mentioned - dependency hell only got worse over time - setting up a new project you're likely to have several versions of the same library in your node_modules.

Re:The sad state of sysadmin in the age of containers (2015) by tomcooks on Monday December 09, 2019 @07:22AM (#21742010)
> Truth be told the whole front-end ecosystem relies on those servers being available, so in their absence any development everywhere would grind to a halt

There's a world out there of LAMP/LEMP stack web developers that wholeheartedly disagree with this perception.

Re:The sad state of sysadmin in the age of containers (2015) by weberc2 on Monday December 09, 2019 @07:50AM (#21742142)
There’s a pretty straightforward solution to this problem which is to run your own NPM server even if it’s only a caching proxy. For some orgs, the uptime provided by the third party servers is sufficient.
Re:The sad state of sysadmin in the age of containers (2015) by doomslice on Monday December 09, 2019 @09:04AM (#21742686)
Having been at 3 companies that did this, I can say with certainty that our caching proxies (artifactory in all of them) were much more likely to go down than the public repos were.
Re:The sad state of sysadmin in the age of containers (2015) by _-o-_ on Monday December 09, 2019 @10:48AM (#21743591)
Yeah, I think I've lost a day in total when our local npm was finicky on several occasions or failed to fetch latest version of a package that we've developed in house, but made publicly available.
Re:The sad state of sysadmin in the age of containers (2015) by llampx on Monday December 09, 2019 @12:16PM (#21744333)
They just don't have to be down at the same time to be useful.
Re:The sad state of sysadmin in the age of containers (2015) by regularfry on Monday December 09, 2019 @09:51AM (#21743092)
Yes, but at least in that case you have the fallback of the public repos.
Re:The sad state of sysadmin in the age of containers (2015) by CathedralBorrow on Monday December 09, 2019 @09:21AM (#21742837)
Maybe it's obvious and straightforward enough that other people have come up with the same idea, tried it and not found it to be worth the effort?
Re:The sad state of sysadmin in the age of containers (2015) by radicalbyte on Monday December 09, 2019 @06:36AM (#21741836)
I like using Artifactory for this, you keep a local copy of all NPM / nuget / etc dependencies hosted next to your build infrastructure.

What shocked me most about NPM is that it used to have absolutely 0 verification built in, yet it was being heavily promoted by very well known, educated and experienced tech celebs. All at a time when it was basically a hobby toy.

Re:The sad state of sysadmin in the age of containers (2015) by etimberg on Monday December 09, 2019 @07:31AM (#21742042)
Last time I tried to use Artifactory for it's caching it barely worked. Would randomly 404 when a package was not in it's cache yet and you'd end up retrying a CI build for a while until everything was there.
Re:The sad state of sysadmin in the age of containers (2015) by anon73044 on Monday December 09, 2019 @09:45AM (#21743038)
At work I'm running ~2000 builds a day across 14 repos, mix of c# and php. We're proxying several hundred NPM, composer and nuget packages on 2 artifactory containers running in high availability. It was a rocky start but about 2 months in everything was pretty stable.

If you're still apposed to artifactory you could try sonatype nexus

Re:The sad state of sysadmin in the age of containers (2015) by jwr on Monday December 09, 2019 @06:13AM (#21741743)
To follow up: I ended up building my own Docker images which contained the build tools (also known as the npm burning dumpster tire fire with extras thrown in), source code and all dependencies. This allows me to get reproducible builds, the modern-day analog of "./configure; make".
Re:The sad state of sysadmin in the age of containers (2015) by mateuszf on Monday December 09, 2019 @06:01AM (#21741695)
It can be done using package managers too, for example using Nix. The problem here is not related to distribution method but rather dependency hell in javascriptland.
Re:The sad state of sysadmin in the age of containers (2015) by weberc2 on Monday December 09, 2019 @07:56AM (#21742180)
I would say the main issue is that Nix is super difficult and requires you to intimately know your entire dependency tree down into Linux particularities. JavaScript makes matters worse, but even packaging a nontrivial Python package pulled directly from Pypi is often difficult.

I want to like Nix, but it is far too pedantic to be practical. And this isn’t even mentioning the usability issues.

Re:The sad state of sysadmin in the age of containers (2015) by glglwty on Monday December 09, 2019 @07:55PM (#21748538)
I think you only need to specify your immediate dependencies in nix?
Re:The sad state of sysadmin in the age of containers (2015) by weberc2 on Monday December 09, 2019 @09:22PM (#21749026)
Someone has to write the package definitions for those dependencies, and the public package repository doesn’t have broad coverage for many popular packages in many languages. This is understandable in that this is a massive effort, but that’s also the point—the effort to manage packages is huge and the extra effort compared to other tools is not a good bargain for many projects, nor is it much of consolation for project maintainers who would otherwise like to use it.
Re:The sad state of sysadmin in the age of containers (2015) by pojntfx on Monday December 09, 2019 @07:45AM (#21742111)
18yo JS/Ruby/Go dev here. `make` is certainly known to us; it's just that platform-specific build systems (`mage` for Go, `rake` for Ruby, `gulp` for JS etc.) are simply more sane to set up per languages than using `make` for all languages and allows for efficient code reuse.
Re:The sad state of sysadmin in the age of containers (2015) by celticmusic on Monday December 09, 2019 @09:05AM (#21742700)
You have make call the platform specific build systems.
Re:The sad state of sysadmin in the age of containers (2015) by Spivak on Monday December 09, 2019 @09:28AM (#21742900)
What's the point in a project that only uses a single build system? You're essentially getting nothing out of make except indirection. Might as well just have a build.sh at the root of the repo.
Re:The sad state of sysadmin in the age of containers (2015) by frenchyatwork on Monday December 09, 2019 @11:34AM (#21743970)
> You're essentially getting nothing out of make except indirection

The thing you're getting is some familiarity, I think (because of the indirection). It's sort of like using a `package.json` for the scripts section, but you get to have comments, and there's less other random stuff in there.

I definitely understand why many would think this is over-kill though. A proper readme is probably just as good/better.

Re:The sad state of sysadmin in the age of containers (2015) by celticmusic on Monday December 09, 2019 @07:01PM (#21748130)
familiarity, documenting the process for building, and last but not least, access to the entire unix toolchain.
Re:The sad state of sysadmin in the age of containers (2015) by pojntfx on Monday December 09, 2019 @09:28AM (#21742901)
I have done so in the past. This leads to a lot of duplication though.
Re:The sad state of sysadmin in the age of containers (2015) by asdasdasdasdwd on Monday December 09, 2019 @11:18AM (#21743830)
I use it mostly so when I come back to the project after months, the Makefile is a reminder of how to build it. Also autocompletion.
Re:The sad state of sysadmin in the age of containers (2015) by maple3142 on Monday December 09, 2019 @11:53AM (#21744137)
Wouldn't it just be like a build.sh? And makefile is not cross platform enough, especially on Windows.
Re:The sad state of sysadmin in the age of containers (2015) by celticmusic on Monday December 09, 2019 @07:07PM (#21748182)
I can't speak to the others, but if you've installed rubygems on Windows, you've installed mingW, and you have access to those tools. This is because rubygems will not build source gems against microsofts toolchain, but against the gcc toolchain ala mingW.

If you prefer using Powershell on Windows, great (or bat if you're a masochist). The point was that being in Ruby doesn't automatically invalidate the use of make as a build tool.

Re:The sad state of sysadmin in the age of containers (2015) by majkinetor on Tuesday December 10, 2019 @09:40AM (#21752824)
Here is how to use tools on Windows via my chocolatey packages without WSL, mingW etc.

    cinst ruby                        # install ruby
    cinst msys2 --params "/NoUpdate"  # install msys2 without 
    system update
    Update-SessionEnvironment         # refresh environment vars
    ridk install 2 3
See notes on https://chocolatey.org/packages/msys2
Re:The sad state of sysadmin in the age of containers (2015) by maple3142 on Monday December 09, 2019 @07:53PM (#21748525)
Yeah, maybe it is true for Ruby development on Windows, but not for others, says Node.js. Developing Node.js on Windows is (comparatively) easy to do so, usually you only need to install `node` and `npm`, then optionally install `yarn` and `windows-build-tools`. None of these steps will give you GNU toolchain, so it won't available until you install it.

That is ehy I prefer OS-agnostic tools such as npm or npm+gulp for more complex build tools.

Re:The sad state of sysadmin in the age of containers (2015) by celticmusic on Tuesday December 10, 2019 @09:14AM (#21752562)
make IS an OS-agnostic tool, it's just not available by default on Windows. But it can absolutely be installed. Or you can bring the mingW/ binaries along with you. Even something as simple as installing git for windows will give you access to a decentish unix environment.

staying inside rake, et al is fine if your software is simple enough to get away with it (by simple I mean self-contained without too many moving parts). But quite often you can't get away with that, and make becomes a good choice.

I would also argue that if you're developing ruby on windows you're doing it wrong. You can do it, but I would personally never target Windows for a ruby app. been there, done that, have the scars to prove it.

I would also add that installing all of that for node doesn't really seem to be simpler than using make, but that's just my old timer sensibilities coming into play.

Re:The sad state of sysadmin in the age of containers (2015) by danmckinney on Monday December 09, 2019 @06:40AM (#21741856)
I don't think it's specific to just younger devs, but there absolutely is an argument for having your own artifact repository that you can control.
Re:The sad state of sysadmin in the age of containers (2015) by maple3142 on Monday December 09, 2019 @06:19AM (#21741769)
I sometimes have problem doing `./configure && make` because dependencies varies across different distro, which have some subtle differences that make it not easy as expected.
Re:The sad state of sysadmin in the age of containers (2015) by regularfry on Monday December 09, 2019 @06:37AM (#21741841)
If you can do `./configure && make`, you can also do a `checkinstall` on debianesque systems, which gives you a package so you don't have to do it again.
Re:The sad state of sysadmin in the age of containers (2015) by pbhjpbhj on Monday December 09, 2019 @07:32AM (#21742049)
checkinstall does rpm/slack too (or did), not sure how debianesque they are.
Re:The sad state of sysadmin in the age of containers (2015) by jwr on Monday December 09, 2019 @06:48AM (#21741882)
True. But at least it doesn't auto-download half the internet (with new and improved vulnerabilities of the day) and dump it all in your "project directory" (whatever that might be, I'm still fuzzy on the exact definition).
Re:The sad state of sysadmin in the age of containers (2015) by tjoff on Monday December 09, 2019 @06:27AM (#21741800)
But it is consistent, which is very important.
Re:The sad state of sysadmin in the age of containers (2015) by Gravityloss on Monday December 09, 2019 @05:56AM (#21741685)
It can be sold as a new invention in a few years.
Re:The sad state of sysadmin in the age of containers (2015) by mr__y on Monday December 09, 2019 @08:10AM (#21742241)
>building a CSS framework library

I think that might have been the root cause of the problem.

Re:The sad state of sysadmin in the age of containers (2015) by JustSomeNobody on Monday December 09, 2019 @06:56AM (#21741908)
I don’t think it’s age so much as it’s “well, that’s just what everyone does now”.

If you want to work in this industry you have to follow the herd; for better or worse.

I certainly don’t agree with it, but people have bills to pay.

Re:The sad state of sysadmin in the age of containers (2015) by fargle on Monday December 09, 2019 @11:11AM (#21743771)
What if "well, that's just what everyone does" is just wrong? I trimmed the word "now" from the quote because lazy sloppy short-term thinking is nothing new. Good configuration management takes a lot of work and pays great returns, only not in the very short-term. It's not surprising that inexperienced devs will fall into this trap.

And just why do you "Have to follow the herd"? Pretty sure just about everything new and creative (good or bad) was a result of not following the herd. I recommend going where you need to go. If a herd starts following you, that's great. At least they'll be slipping and sliding on the shit you leave behind, not the other way round.

Re:The sad state of sysadmin in the age of containers (2015) by kbr2000 on Monday December 09, 2019 @01:48PM (#21745185)
Managers and C-levels surely have appetite for this. In the end it just degrades mostly to trial-and-error, which I'm sure is no problem because the people have to do the real work get sick of it and get replaced (sometimes voluntarily, sometimes with force), or play the game nice out of fear losing their job (thus feeding the beast).

It's not very surprising since 'products' nowadays are more like 'services' instead, and offer some kind of encapsulation: people are not interested much in how something ticks behind the scenes, and so it can drive down the behind-the-scene quality. They also are conditioned to accept lousy excuses (including none) for outages and breakdowns, because they got sold 'magic', and boy that is magical..

You'll might have to work in obscurity to keep up operations quality, which is in turn a driver for your own demise. Game over.

I'd like to suggest to you the following reading material:

- Bullshit Jobs (David Graeber, 2018)

- The Dilbert Principle (Scott Adams, 2000)

- Future Shock (Alvin Toffler, 1970)

Re:The sad state of sysadmin in the age of containers (2015) by jlgaddis on Monday December 09, 2019 @07:24AM (#21742020)
Your comment reminds me of the "Lemmings walking off a cliff" animated GIF that was popular once animated GIFs became a thing on the web.
Re:The sad state of sysadmin in the age of containers (2015) by asdfman123 on Monday December 09, 2019 @12:52PM (#21744719)
You'll get blank stares and resistance whenever you throw a bunch of jargon at people that they don't understand, though. It makes people feel insecure.

You can't expect new programmers who sound like primarily front-end devs to learn all the hot new stuff and all the old stuff, too.

If you want someone with that kind of knowledge, you need to hire a senior dev with 20 years of experience.

Re:The sad state of sysadmin in the age of containers (2015) by winrid on Monday December 09, 2019 @10:44AM (#21743544)
Easiest thing to do to solve this would be to have something like artifactory or even squid in front of npm and use exact version numbers. Front end devs are going to use NPM. Solve the other problems separately like you would with any other build system.
Re:The sad state of sysadmin in the age of containers (2015) by eckza on Monday December 09, 2019 @10:46AM (#21743568)
Sure. And then when something unexpected happens, you have two problems.
Re:The sad state of sysadmin in the age of containers (2015) by winrid on Tuesday December 10, 2019 @12:53PM (#21754787)
You mean clearing a cache? I don't understand. Using a proxy to protect yourself from missing dependencies/down servers is a bad thing now?
Re:The sad state of sysadmin in the age of containers (2015) by AndyMcConachie on Monday December 09, 2019 @08:01AM (#21742199)
s/younger/less experiened/
Re:The sad state of sysadmin in the age of containers (2015) by colinjfw on Monday December 09, 2019 @09:13AM (#21742762)
Not alien to me, likely younger.
Re:The sad state of sysadmin in the age of containers (2015) by pwagland on Monday December 09, 2019 @06:27AM (#21741798)
Don't turn it into an ageist thing, unless you are particularly old, there will be plenty of older developers that also don't understand this.

It largely comes from understanding _why_ reproducibility is a good thing, and there are _lots_ of open source maintainers that understand this that are likely "younger than you". The vast majority of developers though focus on other things, that SQL injection attacks are still a thing indicate that we as a community have a _long_ way to go on the security front.

Re:The sad state of sysadmin in the age of containers (2015) by was_boring on Monday December 09, 2019 @06:45AM (#21741872)
It is way bigger then security, and hits upon quality of life and reliability.

Without a deterministic build I don't know what I check in actually works across environment, or if the deployment artifact works.

Re:The sad state of sysadmin in the age of containers (2015) by rtpg on Monday December 09, 2019 @07:13AM (#21741966)
checksums are a thing, as well as package mirrors or outright holding onto the file and checking in a binary.

There's loads of ways to know what you are using without needing to strip mtime's from zip files.

Re:The sad state of sysadmin in the age of containers (2015) by zaphar on Monday December 09, 2019 @08:58AM (#21742633)
Checksums, solve a different problem. How does a developer know his code which works on his laptop will work on production. One of, but not the only, conditions for that are that his development artifact builds with the same dependencies as it will build in production. Their are a lot of possible causes for Dev/Prod to differ wildly. One of them are poor build practices.
Re:The sad state of sysadmin in the age of containers (2015) by Tade0 on Monday December 09, 2019 @09:41AM (#21743005)
Without a deterministic build I don't know what I check in actually works across environment, or if the deployment artifact works.

Actually that's mostly a given in JS land.

Many bright minds worked hard for it to be this level of idiot-proof.

Re:The sad state of sysadmin in the age of containers (2015) by mcguire on Monday December 09, 2019 @04:33PM (#21746857)
I recently discovered that in node 10.10 (IIRC), you need oracledb < 4.0.0 whereas on other versions of node like node 10.16, you can use oracledb 4.0.1 (again, IIRC). I discovered this via the message when it blew up on application start, since it's not encoded in the package versions.

I may be a better idiot.

Re:The sad state of sysadmin in the age of containers (2015) by Tade0 on Monday December 09, 2019 @05:19PM (#21747262)
Oh, that.

Weird that it didn't complain during building or installation.

Anyway I had one project where I couldn't use `async` `await`, because apparently this feature requires Babel 7, which in turn requires a version of node fresh enough to support generators.

This tends to happen, but it's rare to discover such an issue only after starting the application.

Re:The sad state of sysadmin in the age of containers (2015) by SkyPuncher on Monday December 09, 2019 @09:40AM (#21742997)
> Without a deterministic build I don't know what I check in actually works across environment, or if the deployment artifact works.

I use to have this concern, but it's really not an issue with modern package managers. Even without a checksum in a lock file (e.g. gem bundler), I haven't actually had a deployment break because of dependencies changes. The biggest issue is being blocked for a couple hours because a package repo went down.

Most of this is solved by using a self-hosted or 3rd party proxy package manager.