Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Programming News

Npm CEO Bryan Bogensberger Exits After Eight Months of Turmoil (techrepublic.com) 26

Posted by msmash from the tussle-continues dept.
intensivevocoder writes: Bryan Bogensberger's exit from npm, inc was quietly announced Friday afternoon in a press release stating that Bogensberger "resigned effective immediately to pursue new opportunities." This marked likely one of the few quiet actions in Bogensberger's tumultuous tenure as CEO of npm, the popular package manager of Node.js. Bogensberger started as CEO on January 9 this year, as part of a move announced by original author and co-founder Isaac Z. Schlueter as part of a plan to commercialize the service. Bogensberger's involvement with the company started in mid-2018, although he was not formally named CEO until 2019 pending the resolution of visa requirements. "Commercializing something like this without ruining it is no small task, and building the team to deliver on npm's promise is a major undertaking. We've sketched out a business plan and strategy for the next year, and will be announcing some other key additions to the team in the coming months," Schlueter wrote in January.
This discussion has been archived. No new comments can be posted.

Npm CEO Bryan Bogensberger Exits After Eight Months of Turmoil More

Npm CEO Bryan Bogensberger Exits After Eight Months of Turmoil

Comments Filter:

  • How does a package manager need a CEO (Score:5, Interesting)

    by sirsnork ( 530512 ) on Friday September 20, 2019 @05:01PM (#59217942)

    Ok, so I might have been out of the loop, but how the hell does a package manager need a CEO. Perhaps equally as baffling, how could they afford to pay someone for that role

    • Well, you're asking the right questions, albeit far too late. NPM is fucking everywhere already. People should really have been wondering about this earlier.

    • I think it's sounds "impressive" ... like when jobless people have "entrepreneur" as title in LinkedIn.

    • "NPM is a public repository of code. Like GitHub. Someone needs to pay for it. Usually that someone is a corporation with a CEO."

    • Comment removed based on user account deletion

      • Because apparently NPM doesn't really fall into the "blessed trinity" and is therefor fucked and can't keep paying for long term development?

        I am perpetually baffled by the supposed "need" to constantly develop an already stable single-purpose utility such as npm. What features are required that are not already part of npm? Aside from any bug fixes that is, of course. A commercial entity could add value to the NPM repository by vetting and certifying NodeJS modules/packages/libraries hosted in the repository.

  • What does node.js need with a CEO? - James T. Kirk

  • And I'm not that picky having worked in a variety of languages: PHP, Matlab, Python, C, C++.

    But the first time I used npm it filled my hard drive because every dependency had a dependency of some other version. It was dependency hell.

    • It's called modularization. The languages you mention don't have great support for it. Node.js does.

      I'm assuming by "dependency hell" you don't mean traditional hell where getting the deps right is a lot of work. I've certainly never experienced that with NPM. I assume you simply mean there's a lot of dependencies. And there are, but unless your filesystem sucks (VirtualBox shared folders, for example, or Windows path length limitations), there's no real downside.

      • So you trust a random library to bring in other dependencies without getting them? Place tell me what you work on, I'd enjoy exploiting a piece of Swiss cheese like that

        • Re: (Score:3)

          by Dino ( 9081 ) *

          So do you use `apt` or do you build your linux images by hand from source? Do you use virtualization or containers or do you hand deliver your servers to the data center and then install a hard drive containing an image with a full stack that you built from sources? Most of us being effective in the IT / DevOps space are using tools to bring in other dependencies because it enables us to make repeatable on demand CI/CD systems. There is such a thing as acceptable risk and there is a reason large enterprise

        • I personally read the code and docs for any library I'm including. If I'm looking for something that does X and I find package A that does X, Y, and Z, nine times out of ten I look and find what package A is using to do X, and I just use that. If package A isn't properly modularized, then I don't use it.

    • Re: (Score:3)

      by Dracos ( 107777 )

      Node is the inevitable result of inexperienced developers building infrastructure for a flawed language by taking a "clean sheet" approach that ignores how the same problems were solved by Perl, Python, Ruby, Lua, and others, to prove that JS can run with the big dogs (it can't) while adhering to "don't repeat yourself" as sacred dogma. NPM is equal parts package manager (for very loose definitions of "package") and a reincarnation of hotscripts.com. It has 30k+ packages because so many of them are absurd

      • Re: (Score:3)

        by Dino ( 9081 ) *

        Javascript (and by extension NodeJS and the entire ecosystem) only gained popularity because of its position as the language of the web.

        > It has 30k+ packages

        There are over a million packages in NPM

        > they're barely curated at all for quality and safety

        They are not curated at all. It's an open registry that anyone can publish to.

        Say what you will about Javascript, NodeJS and NPM-- it is by far the most popular programming language today. The sheer amount of interest in the language have brought forth m

        • Re: (Score:3)

          by murdocj ( 543661 )

          I hate Javascript with the passion of a thousand flaming suns.
          Javascript sucks. Look at how many languages (typescript etc) are built on top of JS, just to turn it into something usable. I'd rather program in C than JS. I've programmed in so many languages I've lost count, and I can't think of any that are worse.

          • Re: (Score:3)

            by Dino ( 9081 ) *

            To each their own I suppose. I've been programming for 30+ years going all the way back to assembly.

            C is great because it runs close to the hardware and it has function pointers. However C also has buffer over-runs, no built-in memory management, no closures. It's great for device drivers and 20 year old embedded systems but to do anything modern enterprise on C you'd be piling a heaping load of libraries on top anyway. You're welcome to your opinion of course but I tired of managing C projects a long time

            • Re: (Score:2)

              by MagicMike ( 7992 )

              Having pretty much the same experience, fellow 4-digit user ;-)

              Seriously, javascript used to be the most ridiculously awful excuse for everything, every time I examined it. Then I studiously ignored it for a long time, and apparently over the last 3-4 years it grew up, and when I checked in on it last year it (esp. w/Typescript in use) is pretty good. I was shocked, and now I'm just productive and employable, so works for me.

              In the end it's just telling computers what to do, if it works for you and your tea

    • It was dependency hell.

      In terms of node.js, this is the biggest understatement since the inception of the abacus.

Slashdot Top Deals

Two can Live as Cheaply as One for Half as Long. -- Howard Kandel

Close