Earlier quoted context omitted.
If you'll permit a tangent, there are a lot of drunk pedestrian fatalities. I don't think we talk enough about the risk of drunk walking. Over one third of pedestrians killed in the US each year have been drinking too much to drive. https://www.usatoday.com/story/news/nation/2013/08/05/drunk-...
Not a statistic that's great to pass around but I have read that drunk pedestrian walking is more dangerous than drunk driving (to the driver). Taking an uber is always the move.
CoreJS: State of the project? Looks like dead. Any official fork?
41–50 of 168 posts
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#42Earlier quoted context omitted.
After reading the whole translation linked in the GitHub issue, and being a father of 6 kids who love to make me practice being a judge every day as if I have nothing better to do, I’m convinced the judgment is reasonable. Even in our tiny library parking lot, I very often see people driving unreasonably fast between all the parked cars and the library door, often within a foot of the cars. Even if they are driving w…
Yes, but this wasn't a library parking lot. This was a roadway, at night, and he appears to have been going the speed limit. And the victim was lying down on the roadway in dark clothes. And there was an oncoming car with high beams on according to the court findings. So you think that he should spend 1.5 years in a Russian prison for that? A sentence that may very well ruin him psychologically for the rest of his li…
A good portion of my reasoning comes from my daily dealings with my kids. This case bears many strong resemblances to arguments they come to me with.
Edit to clarify: when my kids come to me with an argument because one was careless and hurt another, the defense is usually that they were acting as reasonably cautious as could be expected. My justification in grounding them (after getting the facts and eyewitness testimony) is that I would have acted more cautiously than they did given the circumstances, and would not have caused the same injury, so that their caution wasn’t really as cautious as should reasonably be expected.
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#43Can NPM not just override "core-js" when performing dependency resolution and point to a maintained fork?
Perhaps a less destructive change that someone with access (Github, NPM, Microsoft, etc.) could make, is to link to the new project from the readme.
Eventually when something breaks, this could be surfaced as an `npm audit` response (Core-js is no longer maintained. Switch to core-js-fork to resolve issue xyz).
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#44I am really curious as to what happens here, remember left-pad controversy? [1][2] This is like round 2. How will npm/github act now? Especially now that it's Microsoft's npm /s [1] https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos/ [2] https://blog.npmjs.org/post/141577284765/kik-left-pad-and-np...
That’s why forking it’s a thing. It’s certainly inconvenient but transferring the access of the original project to another party sets a very bad precedent. Maybe when the maintainer dies, but this guy is very much alive.
It is his work and he chose to give it freely to others through an OSS license. That doesn’t automatically grant anybody access to the original project. If somebody wants and needs to keep updating it then they should just fork it.
The left-pad issue is also different because in that case the original maintainer took it down which broke a bunch of packages that had dependencies on it. This project is still in the registry and it will still work as it is for the foreseeable future.
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#45What a wild ride this has been. Looking at the police report, I do wonder what the punishment would be in other countries. It seems the victims were laying drunk on the ground in dark clothing at top a hill (edit: hill not mentioned in police report, but seems logical given the headlight statement), causing the headlight beams to not illuminate them. On top of that, incoming traffic blinded the driver. This is of cou…
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#46Earlier quoted context omitted.
If you'll permit a tangent, there are a lot of drunk pedestrian fatalities. I don't think we talk enough about the risk of drunk walking. Over one third of pedestrians killed in the US each year have been drinking too much to drive. https://www.usatoday.com/story/news/nation/2013/08/05/drunk-...
Not a statistic that's great to pass around but I have read that drunk pedestrian walking is more dangerous than drunk driving (to the driver). Taking an uber is always the move.
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#47Earlier quoted context omitted.
Now Microsoft's preferred forker. Yikes!
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.
Try that with macOS.
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#48Earlier quoted context omitted.
I haven't read the full coverage, but it does appear it occurred at a pedestrian crossing, and there doesn't appear to be any dispute that it was properly signposted. Most countries require greater care at pedestrian crossings.
Yes, but they were lying flat on the road, intoxicated.
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 seconds of travel time. There’s no downside and only extra caution and safety for all involved.
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#49Earlier quoted context omitted.
Yes, but this wasn't a library parking lot. This was a roadway, at night, and he appears to have been going the speed limit. And the victim was lying down on the roadway in dark clothes. And there was an oncoming car with high beams on according to the court findings. So you think that he should spend 1.5 years in a Russian prison for that? A sentence that may very well ruin him psychologically for the rest of his li…
> So you think that he should spend 1.5 years... hold on... no one ever said anything like that. not a single comment here. let's keep calm. the whole situation still seems unreal to myself...
Re: CoreJS: State of the project? Looks like dead. Any official fork?
#50Earlier quoted context omitted.
I don’t know man. I’m sorry I don’t know the language, looks like Russian? Or something closely related? But based on the parent comment translation, and the translation on the issue page, I’m not sure we should be quick to condemn this person. The court report says he was going 60kph. That’s barley over 35mph, a normal speed limit for city streets. So it appears he was not speeding. If it really was a drunk guy, lit…
I don’t think anyone is accusing the defender of malice. But it is reasonable to expect that people can at least try to drive cautiously. Especially at night, near cross walks. I’ve seen far too many reckless drivers even in suburban streets, almost always young adults or teenagers, on streets that have kids playing at the edge of their yards. They’re testing Murphy’s law. This isn’t a necessary condition of life. Th…
It is. But the underlying point being made by several people appears to be that they believe he _was_ driving cautiously. And that it just so happens that, even doing so, the situation was such that it was still reasonable for him to not be able to avoid the collision.