skysight-inc/HackerNews huggingface dataset:
This is a bit of a strawman. It absolutely is your responsibility, but that doesn't mean you can't outsource it.
I think there’s a time though when an open source project becomes so dominant in its field, that alternatives become few or untenable. In these cases were all at the mercy of the market for having consolidated on a set of choices. The mindshare around the project gives maintainers a tremendous amount of power over others.

Many mainstream projects fit into this. It’s not feasible from a business perspective to get to fork Linux or MySQL. There’s alternatives, but if they don’t work not everyone can spend startup funding to build a NoSQL database.

In these cases committers have a tremendous amount of power and often get disconnected from practitioners.
Would you hire yourself?
Sure, but this fails if they don't want to spend that 10 seconds, which they totally are allowed to. Since there are hundreds of packages in your dep tree and it takes only one attacker for all your bitcoins to be stolen, your scheme is not enough.
That's cypherpunks.
> it seems to prefer blocks to lambdas

What does this mean?
Data is oil, wheat and pork belly
Servo uses spidermonkey
For those asking about context, or what brought this on, I imagine it wasn't any single complaint or event.

I witnessed one such event recently, and I feel pretty confident in saying that person was just having a bad day. Or bad moment, whatever.
i dont see why this is new or a huge shock. its really as obvious as apple pie contains apples, however once a superstar makes a pronouncement and others agree it is very difficult for anyone to accept that the paradigm is a grainy one that requires focus.
spermatozoa are loaded with moby quantities of mitochondria and some do make it into the oocytic cytoplasm in a functional state. thus there is a paternal contribution to the genetic component of zygogenesis.
the new part has not yet been explored, and that would be what level of silencing occurs due to maternal cytoplasmic factors interacting with the paternal Mitochondriome.
Isn't that what Mozilla created Rust for in the first place?
More choices are almost always preferable over a long enough time frame.
That's the cypherpunks. Cyberpunks are 'high tech low lifes'.
Elm is a very locked down ecosystem, heavily influenced by a single lead developer (Evan Czaplicki) with a very small team of assistants. Development is slow, and focused heavily on what Evan thinks is best; features he doesn't use or doesn't think are working out can (and have) been removed. If he doesn't think a bug is critical, it will be ignored. If Evan decides that the way a chunk of the Elm ecosystem works isn't really in line with his vision, then he'll rewrite it. If that's a breaking change, so be it. If maybe Elm goes a release or two with an important feature not working because Evan is halfway through rethinking something, then sure, that's a thing that happens. The Elm dev team is small, their resources are limited, and they're focused on moving the project forward.

Some people see this and go "okay, I'm fine with this, I like Evan's vision and I want to see where this is going"; many of them use Elm in production and accept the occasional bumps in the road.

Others are interested, and happy to watch from afar, but are waiting for Elm to hit some form of 1.0 release or otherwise announce that it's ready to be used in production before making the jump. (I'm in this camp; Elm is clearly not suitable for me today, and that's fine!)

And some take the entire thing as a personal affront. Entitlement is an issue across all of open source, but Elm has some characteristics that makes it especially prone to driving a certain type of user wild. How dare Evan change Elm internals in a way that breaks the way they were using Elm?
William Walker: Ultimate Yankee Imperialist
Depends on:

https://en.m.wikipedia.org/wiki/Nettle_(cryptographic_librar...

Which is written in C and asm.
It gets women in the Olympics. We can either keep gendered sports and tell people of ambiguous gender where they aren't allowed to compete, or we can have an Olympics that is 99% male(ish) by birth or hormone adjustment. I don't think women are going to like that. Sure, there are a few sports where there is some parity, but not many, at least among the elite.
It’s an average. It’s also 20 lines of tested and debugged code per day. Once you factor those things in, it becomes a lot more reasonable as an average.
Makes you wonder if we are at Peak Open Source
These languages are horrible, filled with parenthesis and not fun. I had to learn these in school, like many other people, and I stayed away from FP languages for a long time because of that (like most people).

Try to learn Erlang or Ocaml, it's fun.
Do you really think cat is as simple as left-pad?

https://github.com/freebsd/freebsd/blob/master/bin/cat/cat.c

Also, cat is kind of an important primitive for building a functional system that uses files as one of its core abstractions. It makes total sense that it would (a) exist and (b) be well maintained by an authoritative and reliable source.

Left pad it is not.
I might even go so far as to say that the contention isn't true. In fact, these days I tend to assume the word "modern" is a developer thought-smell. Unless its user can explain what they mean by modern, it's best to assume it's a set of personal aesthetics informed largely by available fashions/habits in the first half decade of a developer's career (which can be fine, it's just the term modern carries waaay more weight than it should).

( -smell can also be a thought-smell, but that's another discussion.)

I'd guess the author means "modern languages have a reasonably simple concurrency paradigm supported by language or standard library primitives," which would be about the only reason other than the interest in the task itself I can imagine reimplementing PHP in Go. I wouldn't buy that definition myself (and as the parent says, it's less clear whether it's the right fit for PHP) but it's a place to start in addressing the relative merits the project might actually be claiming.
it's a startup. your stock is not liquid.
If the cost to enter the market is very high a monoply can portect itself simply by there being implicit knowldege that a competitor entering the market will result in the monopoly lowering their prices temorairly. With a high cost to enter + high risk of failure + low returns even if the monopoly is broken, a monopoly can protect itself effectively without the help of a state.
PS: if you fork the project, it will have big security warning for dependencies, that is because i have a couple of test dependency files for pip,nodejs,rubygem for testing the crawler job.
> Worse, we frequently experienced a situation where the sync was broken, either due to Github being flaky, or the syncing itself being flaky. In such cases, it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync.

Having worked for some of the big 5 American tech conglomerates, I would say this is the exact reason why they did not support it initially nor fully. The bigger the company, the more risk their is running/depending on someone else's software SLA/scaling/dependencies/security/privacy/laws... You just had a bad experience with Google cloud but you don't really know if it was google's fault or Githubs.

Plus, they have so many software developers, they can build their own version that conforms to their requirements themselves for practically the same costs.
I'm not a member of the Clojure community, and have no idea what context may have driven this but...

...I agree with his point 100%, and it's certainly relevant to other communities.
I do not think it's fair or correct to confine Open Source to that definition the last paragraphy of your comment implies. It may only be a subset of Open source. ASF itself defines what it does as Open Source.

What's described in this rant is basically "Source Available". Open Source means more than that, per ASF, per OSI, and per many who publish software under non copyleft licenses.
When you maintain a piece of code, that only you have written, for a couple of years, and making changes to it is as easy as the first day, then you're a good programmer.

If every change to the code feels like adding another twist to the maze, then you're not a good programmer.
Show HN: React-atom – reagent.cljs atoms for react.js
In his post he stated as follow:

> But kindly don't burn the community down on your way out, with self-serving proclamations

This is him complaining about what the community is doing. The community is free to do what it wants, and he is making some sort of statement as if he owns the community in some way, and therefore can decide what is or is not "burning it down".

Convincing other people to leave the closure community (IE, burning it down) is a perfectly reasonable thing to do if there really are problems with it.

Complaining about what the community is doing, is him making the same mistake that he is complaining about other people doing.
Firefox's js engine is already built with rust
Show HN: Create chatbots for events using Google Calendar
Cloud Source Repositories PM here. I appreciate your feedback and will share it with the team.

>it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync.

We've heard this was a problem for users so we're adding the ability to force a sync and to view the current sync status. These features will be live in the next few weeks.
Allergic inflammatory memory in human respiratory epithelial progenitor cells
F# seems kind of not-friendly to the macOS environment. Looking at https://fsharp.org/use/mac/ it looks like you have to install a ton of things to get started. What about F*?

Now if I can get away from Ocaml's weird syntax, I think this is still a good deal.
Bitcoin plunges again. Now the only currency worse than Bitcoin is Venezuela’s
Thanks, I completely agree. The image has little to do with the caption, and it is very carefully crafted to be subliminally suggestive rather than overtly sexual.

I'm not saying these things should be censored or permanently banned--

--However, I am definitely saying everyone should strive to be better than this.

Zuora should use neutral imagery and win deals based on technical and reputational superiority. If they're winning because of a flashier pitch deck, then my post is lamenting this irrational form of deal-making :(
Devsense commercial VSCode PHP debugger is obfuscated open-source library
The majority of software developers are payed to ship product to a deadline. It should meet the requirements of your customers and be thoroughly tested. There are always trade offs but the biggest impediment to shipping is the procrastinator or the perfectionist.

If you miss deadlines then you are failing at your job.
I was attempting to make the analogy that a system designed to support both untrusted peer to peer payments and exchanges must support the lowest common denominator, the peer to peer untrusted payment which forces huge inefficiency into the system.

Similarly a health care system designed to support people with and without preexisting conditions must be designed to support the lowest common denominator, those without cover, which forces huge inefficiency into the system.

Maybe a poor analogy.

Cash and credit aren’t really analogous to exchange and peer-to-peer as in crypto the former is built on top of the latter. Credit isn’t built on top of cash in the same way, as a trusted intermediary abstracts the two concepts. To some extent they’re both eventually built on top of ACH.
Rich is well compensated mostly because he's a brilliant developer and architect: Clojure is just one point of evidence towards that fact.
I experienced a twist on this. A guy who had very different aesthetic taste wanted me to merge some patches. He got real entitled about it, eventually I banned him. THEN he did the "appeal to Twitter" and made malicious edits to the project page on wikipedia. He made a huge stink and wasted hours of both of our time. It was unreal! I wish I was joking.

I wrote about it, discussing my motivations for open source:

http://charlesleifer.com/blog/your-idea-sucks/
First time Hang Gliding turned into a near death experience
It's not that simple. Open source projects, including Clojure, benefit from the community through bug reports, documentation, free user support, articles, etc.

To make it as simple as you suggest, there should be a code repository and nothing more. I don't think that's the case in the majority of open source projects or even what Clojure desires.

That being said, if you're not contributing back to a project (in any sensible way, not just code) maybe you should tone down your demands. I completely sympathise with author but things are a bit more complex in reality. Ignoring the benefits of these interactions/contributions is not fair to the rest of the community that is contributing. Maybe the author does that feel that's currently enough? I can totally relate.
js.rs itself wasn’t created by Mozilla, it’s also died now.
I’ve been doing a rewrite of it here:
https://github.com/jasonwilliams/boa

Rust was mainly developed alongside Servo which is more the rendering Engine, the JS side of it remained in C (spidermonkey)
I caught that notion they had

> I've shared publish rights with other people before. Of course, If I had realized they had a malicious intent I wouldn't have, but at the time it looked like someone who was actually trying to help me.

Can anyone cite perhaps a handful of examples where this malicious open source usage ultimately bit them?
There are no such things as good programmers. Humans have no idea how to program computers, and anybody who tells you differently is lying.

The most honest person here is https://news.ycombinator.com/item?id=18538092
It's the kind of thing where, if everyone with this problem chipped in $5/month, we could have a central repository of vulnerabilities. So, not absolving yourself of responsibility, but also way more efficient to outsource.
Interestingly, this isn't just isolated to open source. I've heard similar sentiments expressed by artists of popular works, including but not limited to:

- Game developers

- Authors of popular novels that have yet to finish ("GRRM is not your bitch")

- Star Wars
I haven't used Clojure much but what I hear is mostly great. And I love this rant, its always refreshing when people speak their minds.

But.... Rich is pushing things a little too far I believe.

On the front page of the Clojure web site, under the section 'Rationale", his very first 6 words are:

> "Customers and stakeholders have substantial investments [...]"

Those words do not sit well with (from the rant):

> "[..] you are not thereby entitled to anything at all. You are not entitled to contribute. You are not entitled to features. You are not entitled to the attention of others. You are not entitled to having value attached to your complaints. You are not entitled to this explanation."

I get it, Rich is making a point, and its a fair and unarguable one - if he indeed has no loyalty or feeling whatsoever towards said Customers and Stakeholders.

But in the real world, we want our work to be valued by others, and I'll bet that the stewards of Clojure feel just the same and maybe shudder just a little.
They mostly don't matter to users, because most forks fizzle out due to lack of interest, unless there's a really good reason for the fork. If the original maintainers aren't doing something weird like re-licensing under a more restrictive license or closing off development and refusing good patches from the community, it's very unlikely a fork will gain enough traction to end up on the radar of most users.

We've had a few forks of our projects over the years...most often, there's just one initial commit with a few minor changes and some big words about how cool it'll be when the community can steer the ship...and, then nothing, forever. The thing about forking a big project is that it takes a lot of time and effort to make it better, or even significantly different, from the project you're forking. "Do not fork lightly" is good advice, but mostly because it's gonna be a waste of time in most cases.
Users roast coinbase in reviews
https://aip.scitation.org/doi/10.1063/1.860481

This paper published in 92 mentions that the 7-X was being designex at that time. I remember having seen images of the proposed field coil configuration in 91 or 92. So I might have bern off by a few years. But the plans must have bern complete for the project start in 1994.
Avalanche Control in Washington with M60 Tanks
>I think this is the clearest, easiest, correct answer. If you no longer have the time and motivation to maintain a project, and are also not in a position to hand over control to someone you have good reason to trust, the easy, safe answer is to retire it, and have others fork.

To prescribe some preventative advice based on this: it's probably not a good idea if your project gets popular to continue being a solo developer in open source. So plan ahead based on your popularity.

And your project isn't likely to explode in popularity over-night and be a dependency for 1000+ other projects, so you should be able to see this coming.

Of course, this is super-easy to prescribe in hindsight.
...what is this?
Be specific: what exactly would you do in Elm to pwn someone? It would be a much more limited and a much more visible attack.

NPM modules don't even have source code on display. Someone has to download and check the tarball before npm install.

Also, Elm packages are qualified by a github username so there isn't an ecosystem of ownership transfer. No juicy name squatting. People just fork.

Finally, don't forget that my point is "there are a few issues with NPM that make this kind of thing especially easy/lucrative". That's a far cry from "everything else is bullet-proof" but it's tempting to argue with me as if I'm saying that.
Can Bollinger really be argued to be a Tesla competitor? Can they really be argued to be a car company yet? Two products announced, no production or even a price tag to consider.

If I recall correctly the B1 prototype spec doesn’t even have air bags and nor will the shipping cars (assuming any ever ship...), and thanks to some legislative loopholes even avoids basic crash testing in the US. Not being considered anytime soon for my family anyway...
Um, the UP and CP were far from the only lines built with federal subsidies (presumably meaning land grants). The NP, SP, and A&P all received land grants as well. The GN was the big exception.

And the GN wasn't single-handedly responsible for the development of the American Northwest. The NP was there first, for one thing.

The text you quoted seems to be reading history quite selectively.
I'm being naive probably, but I have a hard time believing that this controversy would be so big had it been a case of an abandoned library. Users do whine a bit in the Github Issues for dead projects, but at least they can tell the project's dead and/or broken. In this case, the maintainer, who is a security professional, made the active decision to give ownership to an untrusted party. He shouldn't be held liable in any legal/financial sense, but why wouldn't users be alarmed/unhappy?
> Categorization for restroom usage, locker rooms, etc., given that people still do on average have feelings of modesty such that they don't want to be seen undressed by the opposite sex

So what happens with people who have sex reassignment surgery? If Bob's got a penis now but his birth certificate says "female", Bob has to use the woman's locker room and the woman's restroom if we go by birth certificate and simple genetics.

It is possible in most states to get a birth certificate updated after sex reassignment surgery, but it is not automatic, and may take time and money so there likely will be people who do not bother.

BTW, a large fraction of the population doesn't want to be seen undressed in front of strangers of any sex. If we want to make the most people happy, maybe we should design things so that we have more privacy in bathrooms?
Why are they all >60? (The idea is just to find the closest to 60, right?)
> A competent, experienced developer should produce about 20 lines of code per day, on average, to have any hope for a decent code quality.

That's simply measuring the wrong thing altogether. Lines of code per day produced is simply not a valid metric at all. It's just a bad metric period no matter what number you put on it. You cannot measure the quality of a dev by the lines of code he produces, at all.
Cloud Source Repositories PM here.

>Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose?

Thanks for pointing this out. It's not intentional. I'll make sure it gets fixed.
losing the "momentum" on an abandoned package is a much better choice than having it fall into the wrong hands together with all the people who use it and didn't even know about the change of owner.
> you should feel bad

> start with a little humility

> Recommended reading

Good god. I just remember why I stopped participating in this place.

Please read that book you yourself first before name dropping it.
This is machine learning not AI.
I 100% guarantee you that if he did that, he'd be getting a lot of static about how he should have handed the package over to some contributor.
Hours of deliberate practice is said to be the deciding factor in how good you are. Or at least, we can't be good without it. So yes, counting the hours we spent writing and analyzing code gives us an idea of how good we might be as programmers.
There is nothing wrong with publishing rewritten package with same name under full supervision of original developer. Transferring control generally implies full trust, and Dominic haven't established any trust with new developer. He didn't even ask them for their real name!
In Golang you will typically annotate the error messages with meaningful context as you go up the stack. By comparison, my experience is that often, exceptions only have the stack and one error message, and are missing critical pieces of context. The stack trace will only contain the names of functions, and it will often contain the names of functions that are irrelevant to debugging.

A good error message might look like this:

Could not travel to Alpha Centauri:
warp drive initialization failed:
power coupling 397 is offline:
temperature out of range (temp = 150°C)

A bad stack trace might look like this:

DeviceClient::Connect()
std::promise::something
<anonymous function>
DeviceSet::PowerOnAllDevices()
<anonymous function>
std::etcetera
std::etcetera<some_big_thing, more_params, allocator=std::allocator>
TravelCommand::Engage()
VoiceCommand::RunCommand()

Error: temperature out of range (temp = 150°C)

Stack traces are useful, but they're a poor substitute for good error messages. There's just too much context missing from raw stack traces (which file, which URL, which device) and too much noise (anonymous functions, higher-order functions, etc.) That, and a stack trace often requires reading the source code to interpret properly. That might not be possible or it might be outside the skill set of the person interpreting the error.

Exceptions optimize for the case where the exception bubbles straight up to some handler, but I'd rather not have my errors work that way. It's incredibly common for it to make no sense to bubble an error up without some kind of annotation or additional context.
Please stop claiming authority over a descriptive term of open source. Nobody has authority to define open source.
Android runs on billions of devices and is a fork of Linux. There's two or three commercial forks of MySQL, I think Percona started before Sun bought MySQL, but I can't remember for sure anymore.