6 ms·
A proposal for an always-releasable Debian
- deleted 14y ago[deleted]
- antihero 14y agoI dislike how "LAMP" is considered a first class citizen, still. Why is "LAMP" preferable to things like nginx, PostgreSQL, Python, Ruby, or other now extremely popular alternatives?
- onli 14y agoThose may be extremely popular alternatives. But they are alternatives to something, and that something is LAMP. LAMP is a standard one can count on being available on linux-distros, and it is a standard which makes it very easy to develop something for the internet on. As much as I like Ruby, I would not dare to assume that Apache+PHP alone isn't way more popular in terms of general use. The one thing though that I count on getting replaced on that stack is MySQL, though the M might stay. If Debian hasn't done that already.
- obviouslygreen 14y agoBut they are alternatives to something, and that something is LAMP. This simply isn't true. Web development is done in many languages, and while the P in there stands for several of them, it's entirely inaccurate to suggest that any or all of them are somehow a default value deployment or development. Web development deployment environments are not the sole purpose of Debian, and the purpose of non-'P' development languages is not to serve as potential but perpetually-sidelined alternatives to this arbitrary default.
- jiggy2011 14y agoPHP is accounts for the majority of lower end web dev and even some % of the high end. Having a LAMP stack that works up and running in one command is great for people who just want to FTP up a bunch of folders and be done with it. People developing on Rails etc are probably developing against some specific version rather than "whatever happens to be in the repo" and are more likely to be either using a specialist environment like heroku or bring their own puppet setup to the party.
- antihero 14y agoAnd this is why sites get hacked so much.
- jiggy2011 14y agoHow so? Other stacks are no strangers to vulnerabilities.
- antihero 14y agoEven still, people are using mysql_, because mainstream PHP culture is one of ignorance.
- hysterix 14y agoAnd why you are sitting around ycombinator trashing php and talking about which stack is superior, I've gotten loads done with it. You can write awful code with php or you can write great code with php or something in-between, it's up to the developer. The fact that you go so out of your way to trash php going to the lengths to question "why lamp is treated as a first class citizen", actually just goes to show your own utter dependency on development environment and existing code base. So if there is crappy code out there, suddenly you become incapable of writing good code? No, so why sit around on sites and trash a programming language that the final product completely depends on the skill level of the person writing it. You touch php and all you write is shit code? Maybe you are just shitty at programming? You don't "have" to use ruby or python to write clean, well thought out code. Please get off your high horse and understand that people get shit done using the lamp stack, and give it a rest. Do you berate any other programmer anytime you see them writing perl as well? You are not superior to anyone because of the technology stack you use. edit: how about you downvoters, actually come up with a coherent response and tell me why I'm wrong instead of treating this site like reddit and downvoting what you don't understand. eddit2: I've noticed you have a nice github repo, which includes https://github.com/radiosilence/Ham https://github.com/radiosilence/Ham All of your code looks clean and very decent, I'm just pointing out that php is obviously a good enough language for you to waste your own time developing in it!
- dietrichepp 14y agoIt's not just for devs, but loads of people just want their Wordpress/Drupal/MediaWiki/Gallery/phpBB/Joomla website to work, or they want to sell shared hosting to customers who want that. The fact that Debian has a "task" for LAMP is really a reflection of how simple the architecture is: you can press a button to install LAMP and then you can install any one of the applications I mentioned on top of it. LAMP is not a "default" by any means, it's just something easy to stick in the package manager, something that a lot of people use. Sure, you can also press a button to install Rails or Django, but those are more self-contained and don't need to be packaged separately as tasks. The reason LAMP is mentioned as important is because a lot of people do use it and do depend on it. In an ideal world, every application would work on Debian. But with finite resources, you make a list of the things you want to test the most.
- antihero 14y agoHonestly I'd settle for an up-to-date version of nginx.
- petsos 14y agoDebian is a distribution for bureaucrats. For installations that are just being maintained. If you are anything close to hacker do yourself a favor and use something else.
- mwcampbell 14y agoHackers also appreciate having a stable, even conservative, foundation on which to build, especially when it's time to put a service in production, scale it to multiple servers, and keep up-to-date with security patches. There is nothing to stop Debian users from using Rails, Django, Node.js, or any of the other alternatives to LAMP. SOme of them are even packaged in Debian.
- fixxer 14y agoI'm running LMDE and I've got all the goodies by default. If there is something else that the package manager doesn't cover, I do this amazing thing... I download the source and make! Crazy, I know.
- StavrosK 14y agoEdessa?
- dangayle 14y agoFirst thing I do whenever I install a fresh Debian copy is swap out stable for testing so I can get Python 2.7, then add the official repos for nginx.
- zokier 14y agoI must wonder why Debian needs to do 10 months of developing/bugfixing software in the first place. I mean most of the software is already supposedly "stable" releases from upstream, is it not? Maybe Debian should focus on working closer to upstream developers so that the software would be more directly usable out-of-the-box.
- mike-cardwell 14y agoTwo headlines I've read in the last 24 hours: "International Space Station Goes Open Source, Dumps Windows XP for Debian" "Google's cloud dumps custom Linux, switches to Debian"
- dbaupp 14y agoBut, for example, the interaction between the pieces of software, as well as, the Debian-maintained software might not be stable.
- e12e 14y agoIt's not so much the individual packages, it's the interaction between them, and dependencies. In this release, we got multiarch, which is quite an overhaul in how cross-compilation works (especially relevant for running 32-bit (often binary only, non-free) software under the amd64 architecture. There are such issues as which version of libxml, libopenssl and even glibc certain packages work with (or especially, do not work with). So, eg nginx upstream might test (mostly) against an upstream release of openssl and some libc, while the apache web server might be more conservative (this is a made up example, tomcat, especially legacy versions such as 6, might be a better example than apache httpd).
- justincormack 14y agoMultiarch took so long to ship that most of the proprietary binaries are now available in 64 bit. It is still marginally useful. The testing issue is a big problem as up streams often have poor tests but that is an upstream issue really. Maybe the best solution is to provide CI frameworks for upstream to use that support current and future Debian versions easily (something like Travis but with more OS versions).
- mwcampbell 14y agoThe concept of reference installations reminds me of Ubuntu main versus universe, or the main RHEL repository versus Fedora's EPEL repo. Makes sense to me. Perhaps Debian should use separate repositories too, so the difference is highly visible when we browse packages.
- e12e 14y agoWell, technically, there is already "contrib". I guess it is a little crazy to have as many packages in "main" as there is. Impressive, yes, but also a little crazy :-)
- e12e 14y agoNow that backports is part of Debian, I think most of the issues with "out of date" packages are much less painful than they used to be. I suppose factoring main into "core" and "non-core", would make maintaining backports easier too - you could then test building a package against a smaller set of core packages and libs. Packages needing newer versions of glibc, automake/autoconf, gcc/clang/ruby/python/perl etc are still tricky though.
- grn 14y agoCurrently contrib is used for packages that have compile-time or runtime dependencies on packages outside of the distribution (e.g. with dependencies in non-free).
- popee 14y agoJust two things. Debian guys should really do something like OpenBSD package flavors. Sometimes you just don't need X,Y or Z support and it's pain to do this kind of stuff with Debian. I'm not sure if that is even possible in such rigid package managemenet system. Other thing would be to allow files/libs as dependencies. Those two things would give people more freedom and flexibility, but they are from start trying really hard to be anal with packages (even given the fact that .deb system is , at the same time, best and worst thing about Debian). So, guess, just forget about it.
- erlangfanatic 14y agoGreat article!