Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CoreJS: State of the project? Looks like dead. Any official fork?

github.com

Post reply on HN
Print view View original

81–90 of 168 posts

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#81

Post by tonyedgecombe »

jnbiche wrote: post #65
sdegutis wrote: post #48

Earlier quoted context omitted.

If the google translation wasn’t too faulty, one was still lying down, one was getting up and probably trying to get out of the way. The main impediment to seeing them seems to be the headlights of oncoming cars, possibly while coming over a hill. I always slow down in exactly those circumstances (hill and oncoming headlights) for similar reasons: you just don’t know what’s over the hill, and it’s an extra few second…

There's a medium between being a super careful driver like you and I, and being a grossly negligent driver who drove in such a grossly negligent manner that they deserve over a year in a harsh prison system. I highly recommend driving like you say, and do so myself. The last points on my license were were over 15 years ago. But I don't think someone who was failed to be extremely careful to this level deserves 1.5 ye…

If he didn't slow down enough that he could stop in the distance he could see then he was grossly negligent.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#82

Post by Zardoz84 »

foepys wrote: post #47
battery_cowboy wrote: post #12

Earlier quoted context omitted.

I'd rather hear Microsoft's suggestions on libraries to use than some random Joe Developer. They have/had unethical business practices, but their tech is really good and they have very smart people working for them.

A lot of people are making fun of Microsoft but most of them don't know or appreciate that you can run software compiled in the 90s on the most recent Windows 10 1909 without problems. Microsoft's backwards compatibility is off the charts. Try that with macOS.

Well... Windows 10 have the record of the being the only windows that breaks backwards compatibility sometimes. I saw Visual Basic 5/6 applications stooping to work because Microsoft break something on a update.

Also, good luck trying to run any Windows 16 bit application on a modern Windows 64 bit installation.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#83

Post by ankka »

SaxonRobber wrote: post #66

Jesus npm is a cancerous dumpster fire. Guy must have been a saint to continue maintaining the project in spite of all of entitled "developers" using his package and scolding him for DARING TO ASK FOR A DIME.

And nobody wants to take responsibility and maintain it either, not even now.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#84

Post by tim-- »

Zardoz84 wrote: post #82
foepys wrote: post #47

Earlier quoted context omitted.

A lot of people are making fun of Microsoft but most of them don't know or appreciate that you can run software compiled in the 90s on the most recent Windows 10 1909 without problems. Microsoft's backwards compatibility is off the charts. Try that with macOS.

Well... Windows 10 have the record of the being the only windows that breaks backwards compatibility sometimes. I saw Visual Basic 5/6 applications stooping to work because Microsoft break something on a update. Also, good luck trying to run any Windows 16 bit application on a modern Windows 64 bit installation.

> Also, good luck trying to run any Windows 16 bit application on a modern Windows 64 bit installation.

The officially supported method is to have Windows 10 (32 bit) running in HyperV. There is no 16 bit support in Windows 10 64bit builds.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#86

Post by hombre_fatal »

agildehaus wrote: post #16

Couldn't someone he trusts just ask him for credentials? It may be harder to contact him right now, but not impossible.

Seems really sheepish to bother the guy in jail over this.

Also, publish creds aren't the problem. The problem seems to be that nobody else really wants to maintain it including anyone at Babel, core-js' biggest user afaict.

If nobody steps up, it should just be a reminder of how flimsy open-source can be when there are so many bus-factor-of-one nodes out there that we depend on. It's a pretty big downside of depending on the hobbytime charity of random people, especially when we (or github comment culture) are so hostile when anyone dares to seek a penny.

You could write a library that every fortune 500 company uses to save a cumulative hundreds of thousands of dollars in employee-hours over the library's lifetime, but you're the asshole if you use your library's popularity to seek work or donations. People will come out of the woodwork to scold you.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#87

Post by dredmorbius »

overeater wrote: post #75
_pd19 wrote: post #71

Earlier quoted context omitted.

I wish we were as sympathetic to drug dealers and theft as many on HN want us to be towards a programmer who ran someone over in their motorcycle.

Why? Those people chose to do something bad. The programmer was not doing anything intentionally wrong.

In 2020 hindsight, operating a motor vehicle in conditions and a manner resulting in the death of a human being represents at the least negligence.

Circumstances as described possibly mitigating some aspects of this, but driving (or motorcycle riding) is an inherently and widely known dangerous activity. Situational awareness is a requisite practice.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#88

Post by throw_m239339 »

ankka wrote: post #83
SaxonRobber wrote: post #66

Jesus npm is a cancerous dumpster fire. Guy must have been a saint to continue maintaining the project in spite of all of entitled "developers" using his package and scolding him for DARING TO ASK FOR A DIME.

And nobody wants to take responsibility and maintain it either, not even now.

I'm not surprised at all. I bet there are plenty of multi-billion dollars companies using that project who never contributed a cent to its author yet sent their developers on GitHub to complain about the state of the project.

It happened to a few maintainers I know. These companies save millions in development cost on the back of a few developers in developed countries. This is open source, I get it, but this isn't fair either.

Look at that comment:

> ....yikes. Sounds like a fork needs to happen. And github should really look to provide a 'risk' rating to projects from a maintenance PoV... a project depended on by 4.5m users with 1 maintainer should visualise as a high-risk dependency.

It's not up to GitHub to do that, it's up to the individual or the company to audit a project and its dependencies and be prepared to be able to maintain it themselves. Or pay the only developer to do exactly that.

Another comment (quoted by another guy):

> Babel maintainer here We are probably not going to fork core-js because we don't have enough resources to maintain it.

And people expect a single developer to have the resources to do exactly that? look at babel and the list of sponsors, yet they don't have the resources:

https://github.com/babel/babel

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#89

Post by miguelmota »

The CoreJS author blocked me and many other people on github for simply making a suggestion to tone down the "looking for a good job" npm install logs because it'll invoke other people to try the same thing which would result in unnecessary log pollution. It seemed like strange behavior for someone maintaining a very popular community driven project.

Re: CoreJS: State of the project? Looks like dead. Any official fork?

#90

Post by kbumsik »

SaxonRobber wrote: post #66

Jesus npm is a cancerous dumpster fire. Guy must have been a saint to continue maintaining the project in spite of all of entitled "developers" using his package and scolding him for DARING TO ASK FOR A DIME.

Yeah. There even seems to be trolls blaming him in the issue page.
Post reply on HN