Announcement

Collapse
No announcement yet.

Apache Gets Booted From OpenBSD Base Over Being Too Bloated

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by mark45 View Post
    BSDs are irrelevant, it becomes ever more often that if an app doesn't compile/run on a Unix OS which is neither Linux or Mac/iOS - take a hike. I never cared if my app runs on any BSD, even my Java apps.
    Considering that Solaris is the "home" OS of Java it's curious that you're so narrow minded.

    Comment


    • #12
      Long Overdue

      Originally posted by phoronix View Post
      The Apache web server has been removed from the OpenBSD base operating system over being too bloated and server administrators are now being asked to switch to lighter-weight alternatives...]
      I've been incredibly frustrated by the tendency of distributions/developers to not only consider Apache the default httpd; but to make it a dependency of many packages. I often want to install some package on a VM on an antiquated server or a cloud VM for development, testing, or learning purposes and the reliance on Apache makes this difficult or impossible. I've learned to create "bogus" packages that install Nginx while stating that they provide Apache2; however, this sort of trickery has bitten me on occasion.

      I've also ended up building packages from source to avoid dependency chains including Apache. All this to avoid a server that I have not deployed on the public web since 2002. I'm sure that there are use cases where Apache is the best httpd. However, I strongly suspect that for the **vast** majority of installations, something between dark-httpd and Nginx are **ideal**. By best/ideal I refer to an optimal balance of resource utilization, ease of administration and security.

      I certainly hope that Linux distros from Debian and RedHat to more experimental ones take note and follow along.

      Comment


      • #13
        Originally posted by Cthulhux View Post
        I, for one, would have preferred lighttpd; but I guess the OpenBSD devs had good reasons for their choice.
        I've been using lighttpd for years, but it seems Nginx is more popular. And I hear that Lighttpd's development has kind of stagnated, while Nginx has a lot of active development happening.

        I also used to use thttpd and boa, I'm not really into bloated apache

        Comment


        • #14
          Originally posted by mercutio View Post
          I've been using lighttpd for years, but it seems Nginx is more popular.
          I gladly doubt that's relevant in the BSD world.

          Originally posted by mercutio View Post
          And I hear that Lighttpd's development has kind of stagnated, while Nginx has a lot of active development happening.

          Comment


          • #15
            Originally posted by Cthulhux View Post
            See, that's why no one can take Linsux users serious.
            Linux killed your bsd shit. You have to live with that. It doesn't matter if openbsd or some other bsd chooses to drop something, because it won't affect market share at all.

            Comment


            • #16
              Originally posted by Calinou View Post
              BSDs are not irrelevant in the server area.

              Before saying something is irrelevant, have sources and think twice.
              They're irrelevant. Server market is dominated by Linux and Windows comes next.

              Comment


              • #17
                Originally posted by mercutio View Post
                Considering that Solaris is the "home" OS of Java it's curious that you're so narrow minded.
                It doesn't change a thing. I bet it has even lower market share than bsd. It's a dead cow.

                Comment


                • #18
                  Originally posted by Cthulhux View Post
                  Also, "migrating" from default Apache to default nginx is not much of an effort, right?
                  If you're using php through php-fpm like you should have been since it's introduction a couple of years ago, instead of the php apache module. Then at least the php part you don't have to worry about.

                  The only real problem is with the local site config files apache supports. While they're supported in NGINX afaik, if I remember the support was not as good as the one in apache. And that may be a problem for domain/isp providers.

                  Comment


                  • #19
                    Originally posted by Pawlerson View Post
                    Linux killed your bsd shit. You have to live with that. It doesn't matter if openbsd or some other bsd chooses to drop something, because it won't affect market share at all.
                    A lot of people came from Linux to BSD as they noticed its flaws.
                    Including me.

                    Comment


                    • #20
                      Originally posted by Cthulhux View Post
                      I gladly doubt that's relevant in the BSD world.



                      http://www.lighttpd.net/2014/3/12/1.4.35/
                      if you look at that page 1.4.28 was in 2010.


                      and lighttpd 1.5.0 was being talked about in 2007.

                      All the lighttpd.net domains (blog, trac, www, xcache, upload, …) are now running lighttpd 1.5.0-trunk. It took some debugging to sort out …

                      Comment

                      Working...
                      X