10 ms·
I'll opine, happily, that nothing showcases the gap between the OS people and the Web people as well as someone who considers 10 months to be a significant leng
by roenxi 5y ago
I'll opine, happily, that nothing showcases the gap between the OS people and the Web people as well as someone who considers 10 months to be a significant length of time.
There is a happy day coming for the web developers, sometime this decade hopefully, when skills learned as long as 12 months ago will still be up to date.
Did you notice OpenJDK has been upgraded from v11 to v11? That sort of radical change is why I run Debian. They don't break stuff.
- Shish2k 5y agoVery fair point :) All my other dependencies, using 5 year old versions is fine; it’s mostly just PHP that gets an order of magnitude less-painful to work with in each release, so being stuck a few versions behind is extra frustrating...
- slim 5y agoThat's because php decided it needs 6 month release cycles now. You're better off targeting php 7.4 for the next 3 years imho
- jorams 5y agoPHP releases once a year. They've been doing that for almost a decade now.
- CogitoCogito 5y agoIs it that difficult to build and/or install a newer version that better fits your needs? I tend to stick to debian stable, but in the few cases where I need newer software I just build it myself. Using `apt build-dep [package]` and then something along the lines of `configure && make && make install` basically always works. edit: I guess if you work somewhere with a policy of requiring you to use system packages, you're a little screwed, but that seems more of an organizational problem than a debian problem.
- dreyfan 5y agoPHP 8.x is very easy to install on debian by adding deb.sury.org to apt sources. https://deb.sury.org/ https://deb.sury.org/
- Shish2k 5y agoIn this case I’m building software whose primary selling point is “trivial to install on practically any cheap-ass $1/mo shared web host, just unzip and FTP the files to your website folder” - which is the whole reason it’s written in PHP in the first place. (The more I think about it, the more sad I am that it’s 2021 and still no other language has come close to PHP’s low barrier to entry...)
- curryst 5y agoYes. Just as an example, I use VSCode. VSCode no longer works on CentOS 7. It needs a newer glibc, so I'm going to have to recompile a lot of stuff and do some PATH fiddling to get it to work. It's usually not that it's hard to do that for your packages. It's when their dependencies go out of date and I'm looking at having to build a Frankenstein system where I'm running one up to date system on top of a really out of date one, and trying to make the two co-exist in a single OS. It's not insurmountable, but it's enough effort that dealing with occasional Arch breakage becomes easier. Or even something in between like Ubuntu.
- CogitoCogito 5y agoWell I was referring specifically to debian and to PHP. Does VSCode really not compile on debian 10 or 11? I find that a little surprising. But yeah I agree that installing newer dependencies like glibc for VSCode would certainly be a hassle. I can't really speak much to that though since I've never used it.
- int_19h 5y agoVSCode is probably not the best example, because it has official packages for Debian (among many other things): https://code.visualstudio.com/docs/setup/linux https://code.visualstudio.com/docs/setup/linux
- koolba 5y agoOpenJDK is still at 11 because that’s the latest LTS version. Subsequent versions have significantly shorter upstream support lifetimes (IIRC, six months). Until another LTS is released, it’ll continue to be 11.
- smarx007 5y agoNext LTS will be released on Sep 14, exactly in one month.
- vbezhenar 5y agoToo bad, now wait for 2023.
- smarx007 5y agoI think it’s rather Docker, Alpine, JDK 17 and jlink than waiting till 2023 :)
- AndyPa32 5y agoIt means nothing that it will be released in a month. Because new software goes into unstable first, then is promoted to testing and only then to stable. So even if the next LTS release would have been released a month ago, it certainly wouldn't have made it into debian stable.
- throw0101a 5y ago* https://packages.debian.org/bullseye/openjdk-17-jdk https://packages.debian.org/bullseye/openjdk-17-jdk * https://packages.debian.org/search?keywords=openjdk-17 https://packages.debian.org/search?keywords=openjdk-17
- cogman10 5y agoThere's no such thing as "LTS" for the OpenJDK. LTS is strictly a JDK/JRE vendor concept. Oracle's distributions have 11 as an LTS and will have 17 as an LTS. That, however, only matters if you are paying oracle for support.
- 5e92cb50239222b 5y agoYou don't seem to know anything about the "web people" you're criticizing here. PHP skills learned two decades ago are still very relevant today. It's the Java of the web world.
- roenxi 5y agoWhat criticism?
- JasonFruit 5y agoThat's an excellent point: you described a difference, which is in fact real. Any perceived criticism is just that: a perception.
- bonzini 5y agoHmm no, not at all. My first job in 2002-2004 was using PHP4. I barely used classes (and if I did they were just my code, not from the library because I didn't need anything from PEAR) and used the original MySQL client API. Almost nothing of what I used back then would be useful today. PHP4 vs PHP8 is almost more different than Python 2 to Python 3.
- formerly_proven 5y agoI've initially learned PHP4 when PHP3 was still used. Later I learned PHP 5 which iirc was the first version which had classes. I also learned Drupal 6 and then 7. Modern PHP code looks nothing like PHP code back then. Of course, the core syntax is mostly the same, but if you look at a framework like D6 or D7 no one would do anything even remotely like this today. PHP security has completely changed since then as well.
- elipsey 5y agoWhen I was an intern there was this old dude who had an ancient computer with the same Debian on it for like 7 years. He never got excited about new stuff, and just didn't want to break anything. I thought that was kind of funny and un-hip, back then, but now I'm like that. It's like Dad OS. :)
- burntsushi 5y agoI'm a Dad and I use Arch. I can't stand non-rolling release Linux distros. They are constantly getting in my way because they don't track upstream. I have multiple machines running Arch (some over a decade) with no problems. In constrast, doing dist upgrades on Ubuntu has put me into states that I could not figure out how to get out of, and thus had to do a clean install. (Granted, it's been a long time since this has happened, but mostly because I very specifically avoid non-rolling release distros.)
- zozbot234 5y agoUbuntu upgrades are extremely messy compared to Debian. If you want a rolling-like experience, the testing channel of Debian is pretty good for that - though it does get frozen when approaching a stable release.
- burntsushi 5y agoThe dist upgrade is more of an example meant to dispel the myth that non-rolling release distros break less frequently than rolling release. Or at least, an anecdote anyway. Jumping down from the meta level of rolling vs non-rolling, I personally find Archlinux style of packaging much much simpler than Debian's. I've writte numerous PKGBUILD files over the years and it's been dead simple. But my eyes gloss over whenever I look at Debian packages. I'm sure the complexity in Debian is warranted for one reason or another. But it ain't for me.
- e12e 5y agoNote that, Ubuntu had some rough times, and did some odd things (I distinctly remember changing gid of system groups, for example) - but it has gotten a lot better. I don't think I can remember Debian ever having any serious issues on dist upgrade. Well, there was a bit of hairpulling with the change from lilo to grub - but I think that was because I tried it early, before grub became the new standard..). But of course, there are no perfect tradeoffs. I'm inclined to believe GNU guix (or nixos) might be the next best thing(tm) - but I've yet to put that to the test..
- seoaeu 5y agoIn other settings I can add a new feature to one of my dependencies and start using it within days or weeks. You're telling me you prefer having to wait years to get any newly implemented feature?
- notyourday 5y agoOS should not ship your language run time. OS is a giant cargo ship. It does not turn on a dime and it is not piloted by a "lets rewrite it in rust!" crew.
- tomc1985 5y agoSo add a couple of vendor repos and jump the versions queue like everyone else. I do this for all my main dependencies... postgres, ruby, etc
- robertlagrant 5y agoCan you give an example?
- seoaeu 5y agoSure. In the Rust ecosystem, if you submit a pull request to a library it is very common for the maintainer to release a new version soon after. Even patches to the Rust compiler repository are released to stable in a matter of a few months (and the very next day for the nightly channel that many people use) There's always workarounds and so forth, but it is really empowering to be able to have an impact over such a short timespan
- yjftsjthsd-h 5y agoUnironically yes. I would love to be done with the endless version churn and would trade many, though not all, features to get it.
- mwcampbell 5y agoI think the web people have the right idea. If it hurts, do it more often [1], right? I've used Debian for a long time (edit: on servers), but the short (and in some cases getting shorter) release cycles of popular projects like Chromium and Rust have got me wondering if Debian just moves too slow. I'm tempted to try using Fedora as a container base image and see if it's practical to keep up. Edit: I guess Fedora is no worse than Alpine if you actually update to each new major release quickly, since they both release every 6 months. [1]: https://www.martinfowler.com/bliki/FrequencyReducesDifficulty.html https://www.martinfowler.com/bliki/FrequencyReducesDifficult...
- qwertox 5y agoIt is possible that if you build up a routine to always stick to the latest, it will become an automatism. This opens the door to several types of risks. Containers are always an option.
- miohtama 5y agoStatic binaries like Snap, macOS, etc. solve “moving slowly” issue. There should be little need to update the core OS (kernel, initd, /etc stuff) often.
- murgindrag 5y agoNo, the web people have it wrong. It's called: - Failure to do upfront design (yay, misinterpreted agile/MVP/etc) - Reinventing wheels over, and over, and over Newer versions and frameworks tend to be 10% improvement, and 90% unnecessary churn.
- asddubs 5y agoI'd say PHP is still getting a lot of good and important improvements
- murgindrag 5y agoPHP exactly makes my point. PHP was a no-good, terrible, poorly-made, horrific original design for something like powering Facebook. As a result, it needed a lot of good and important improvements. Or to be more specific, it was a great design for what it was intended to be: a pet hobby project to make it easier to make Personal Home Pages, and was never intended to be a programming language. https://en.wikipedia.org/wiki/PHP#Early_history https://en.wikipedia.org/wiki/PHP#Early_history The concept of putting out something this bad, and then refactoring for over a quarter-century to make it almost-usable, is exactly the definition of the webdev way. The result is a ton of churn.
- martinp 5y agoOpenJDK 17 is in Debian 11 as well [0]. A decision was made to include it before its official release since the release is so close (September). An updated package will be available when it's released. From the release notes [1]: Debian bullseye comes with an early access version of OpenJDK 17 (the next expected OpenJDK LTS version after OpenJDK 11), to avoid the rather tedious bootstrap process. The plan is for OpenJDK 17 to receive an update in bullseye to the final upstream release announced for October 2021, followed by security updates on a best effort basis, but users should not expect to see updates for every quarterly upstream security update. [0] https://packages.debian.org/source/testing/openjdk-17 https://packages.debian.org/source/testing/openjdk-17 [1] https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html https://www.debian.org/releases/bullseye/amd64/release-notes...
- eyelidlessness 5y agoI read GP as considering ~4 years total and 2 years out of support a long time.
- TavsiE9s 5y ago> They don't break stuff. Unless they do due to their stance on licenses and remove mp3 support from the lame package.
- AbraKdabra 5y agoThere is a fine line where you need to see which weighs more, using a stable version or using an up-to-date security version, I fully support the latter. PHP 7.4 security support will end in November 2022, will Debian upgrade to 8.0 once this happens?
- asddubs 5y agono, they'll start backporting security fixes. There's still php 5 versions in the wild
- nextaccountic 5y agoBut it doesn't make much sense to run an outdated PHP. I agree with the point of the top level comment, that is to put your dependencies inside docker and completely uncouple from OS dependencies.