skysight-inc/HackerNews huggingface dataset:
The last time I considered this:

- Most grid/cluster-based video rendering systems assume trust. Shared filesystems, central nodes that allocate work, users submit jobs to the central node. This trust allows for lower overhead, as each unit of work only needs to be processed once. (By comparison, with blockchains, you need to wait for n copies of the work to be done and compare them to verify that a bad actor hasn't submitted garbage; these are "confirmations".)

- One key property of cryptocurrencies is resilience in the face of bad actors. In particular, you want each node to independently be able to come to consensus without trusting a central node. (Otherwise, you would just devise a scheme that trusts a central node, such as a Bank.) So if you want to replace Proof of Work or Proof of Stake with a "useful" task, you have to devise a scheme that retains the property of "consensus without trust", while also providing "useful" work (that is, correct video rendering results, in a reasonable response time). I'd look up "51% attack", as well as the documents describing the design of scrypt (https://www.tarsnap.com/scrypt.html) and other password hashing functions to get a sense of the attack modes you have to design for.

- Assuming you come up with a good scheme, you then need to convince the rest of the world to adopt it. (Note that some actors have hardware that is optimized for the task defined by Bitcoin. Also, if your user base is too small, then it's trivial to 51% attack by just buying more computers than you.)

I don't think it's impossible; I just don't think it's cost-effective (versus just buying and building a grid/cluster with trusted nodes).
Which is exactly why governments regulate “open and free” markets.
Being in a union that protects your rights as a worker is more like insurance (which the majority indeed mandates the minority to get) than religion.
Short form content is eating journalism
MVC is understood to be the primary partition of an application's architecture. It does not obviate the need for further code organization, which is done in all parts, Model, View and Controller. When the author says "controllers are nice self-contained bit of...[what I don't know?]", and they use that as the justification to throw away the paradigm in favor of another with Model-View-Operations+Events they show they don't understand this. Worse the proposed paradigm does not then collect all the controller code in one place, so the overall lifecycle of the application would be harder to piece together from Operations+Events modules without an overarching Controller to govern the two of them.
Causes of Irregular Menstrual Cycle
Yes you can be part of a union and create your own loan out company.

https://www.wrapbook.com/how-to-set-up-a-loan-out-company/
> We're well paid but besides that, I'd be hard-pressed to think of a way we could collectively be treated with any more contempt than we already are.

Relative to other wage workers yes, but nowhere close to the ratios between wage and housing last seen 30 years ago. There are opportunities to negotiate for that sort of compensation again.

As long as annual compensation doesn't let you own a house outright in 5 years in the same area as your place of work, then there is more work to do.

Comparing yourself to other trades is not relevant. Wage growth in one not-so-rare trade will benefit many more trades and people.

Most of us would not be where we are today if we limited our aspirations to what other people do.
And there is a huge need for better open source tooling in both fields!
This incident is fantastic. I worked at Zipcar on the firmware deployed in the cars, and these kinds of issues are _hard_ to get right, though this failure looks to be spectacularly naive. I had to deal with cars parked in garages underground, as well as off the grid (and moved between countries, and with dead batteries, etc).

There is an inescapable tension between default-permit (the customer _must_ be able to get in the car and drive it) and default-deny (it should be impossible to steal a car) that results in all kinds of trade-offs with UX implications. These are, at their core, sociological problems that the technology can guide but not solve.
No doubt about it. Can't even imagine how hard it can be;
I believe I am using the Snap version on Solus and haven't had any issues.
Tech: Time viewing. See: The Light of Other Days [Arthur C. Clarke, Stephen Baxter]

Horizon: Never. Why? Wormholes don't do that.

Tech: Near infinite storage for nearly free. I'm pretty sure that in my lifetime most everyday people will no longer delete files or care how big something is.

Horizon: 10 years tops. Why? Moores law for data storage.

Tech: FTL

Horizon: 50-100 years. Why? I have a sneaking suspicion that there's some radical new theories about space and time just around the corner.

Tech: Androids

Horizon: 20 years. Why? Almost all the pieces are already here.

Tech: Artificial human wombs

Horizon: 15-50 years. Why? Kinda already here, just needs moral/political support
Financial risk isn't prized in some moral sense. It's just an instrumentally valuable service. If a factory costs $100m to build, someone has to put $100m at risk to build it; no matter how much the workers self-organize they won't be able to build the factory if they don't have the $100m.
We are headed twords the most common job [0] in each state being automated in 10-20 years. Then we [USA at least] will have a much larger unemployment problem till deal with, as the truckers are >=90% men[1].

So then we have a bunch of middle age men who formerly had decent jobs seeing those jobs go away. The economy in much of the country will have to adapt, and that is where UBI or some type of socialism will need to take over.

If you think the disenfranchisement that led to the election of Donald Trump was bad, imagine when the remainder of these jobs vanish..

[0] https://www.thejobnetwork.com/trucking-is-the-most-common-am...
[1] https://www.census.gov/library/stories/2019/06/america-keeps...
As far as I understand, WebThings Gateway is sort of like Home Assistant.

Why would I use WebThings when Home Assistant already has a much bigger community?
"Facebook doesn't control it."

Unfortunately it's controlled by the Mark Zuckerberg of Russia who still has access to his data brokers. None of the companies with access to our private data seem problematic at first. Google was a gift from the heavens with it's insane 1000MB gmail accounts back in 2003, now it's a private intelligence agency. Facebook was about free fun and connectivity, now it's a private intelligence agency. But Telegram's going to be different and money comes from magic and ICOs even after it reaches critical mass.

Aral Balkan explains this better than I ever could https://www.youtube.com/watch?v=jh8supIUj6c#t=35m02

Also, the security model of Telegram is exactly the same as Facebook Messenger: A bunch of promises about respecting your privacy, coupled with opt-in end-to-end-encryption that doesn't work cross-device, and the use of which reveals the intention to hide messages from server (which is extremely valuable metadata: these messages I want to hide from service provider and governments!)
While not the grandparent post, I can add some of my own experiences with unions:

Once, when workers in Chicago supported a general strike in support of an eight-hour workday, police shot and killed a number of workers. [1]. Someone threw dynamite into a crowd. A lot of people died, but we got that eight hour workday.

Another time, workers protested for higher wages, but the company owners hired private security and killed a hundred workers. The army was called in, and private planes hired by the company dropped bombs on the workers [2].

And who can forget the time the richest man on Earth hired private security as strikebreakers after a collective bargaining agreement failed? [3]? Interestingly, these workers were already part of a union, but the owner unilaterally withdrew recognition of the union. A few people died (private security...), and the collective bargaining agreement ultimately failed.

I suggest you make yourself aware of the trials unions have been through over the past two hundred years. Capital will always repress labor by any means necessary, and parroting the lines given to you by capital is implicit support. This makes you a de facto class traitor. United Bootlickers isn't a union, and even if they were, the benefits wouldn't be that great.

[1] https://en.wikipedia.org/wiki/Haymarket_affair
[2] https://en.wikipedia.org/wiki/Battle_of_Blair_Mountain
[3] https://en.wikipedia.org/wiki/Homestead_strike
> Disclosure: I also work on Google Cloud

Wow, half of the comments so far start with this disclosure! Tons of Google people lurking on HN :)
How did Japan allow the virus to spread to hundreds of people aboard the Diamond Princess? If the Chinese ran that operation they would get raked over the coals for it.
Absolutely pathetic for both sides. If you don't like your white collar tech job, go somewhere else. It's not factory work where you're paid way less to do the same thing wherever you go. You make yourselves and your company look weak in doing this.

This is why the rest of the United States thinks tech is full of a bunch of entitled pricks.
The only thing missing is the comment starting with "I'm not anti-union, but..."
IMO with companies, the stakes are not so high that democracies (i.e. unions) need to be implemented right from inception. If a company demonstrates repeated abuse of employees, then sure, retrofit it with a union to keep future abuses in check.

But unions have several significant downsides too, and for companies with a clean record, strong leaders with a vision, good pay and benefits, high morale, etc. I don't see any benefit to encumbering such with a union.
Another thought: Would you say the same if, say, Banksy was doxxed and subsequently quit?
So much this... I tend to do this. There are times where I need a limited subset of a library, and will just pull the two classes I need, add the comment at the top, and adjust the namespace.
Are you familiar with how certificates and CAs work in general? You don't receive a certificate from the CA, they just sign and attest that the one you made is owned by you. The ways CAs go bad is not breaking any crypto but by signing a certificate that you don't own. This vulnerability is well known and LE takes industry-leading steps to mitigate it via the certificate transparency program which is a permanent auditable log of all certificates they sign.
I am a somewhat active SO user and one thing I see other contributors repeating over and over is "stackoverflow is not a code writing service". Usually this comes up in the context of some kid posting their college assignment and asking people to solve it, but I think it should extend further.

Do not copy/paste code from stackoverflow. SO is not a code writing service. It is a problem solving/question answering service. Any code you see in the answers should be takes as reference only. If you don't understand what the code does, re-read the answer, check the documentation, understand and then write your own code. What happened here is such a stupidly trivial bug. If someone only took a second glance at this code it would be blindingly obvious what is going on here. I saw it as soon as I looked at the SO code sample and I don't even write C#. Do people at Docker even do code reviews?

Also, when I write answers in SO, I try (not 100% of the time, but I do try) to make my code generic, so it solves the problem the user is having, but does not include any specifics from the question. I suggest you all do the same.

P.S. I know that this rant of mine is rather idealistic. Nobody is going to stop copy/pasting code and these things will keep happening. But writing this was therapeutic.
I misunderstood -- I thought the authors of request were going to keep working on a rewritten version, but were going to start a brand new node module for it.

Strictly speaking, react-router is doing it correctly. It's the same library, just different versions. The normative way in the npm community to handle breaking API changes is to increase the major version, not to completely rename the package.
> Its design shines a light on technical skills that researchers didn't think Neolithic people possessed.

It seems these kinds of discoveries -- people were more advanced at some point in time than previously believed -- happen quite frequently. It makes me realize I have a much too linear view of the development of technology and civilization. There have been many stops and starts and backtracking along the way, of course with plenty of uneven distribution across single points in time as well.
Also Docker 2.2 broke volume binding in a way that's kind of staggering (basic operations like move and delete fail). Ive had to keep everyone on Docker 2.1 because after spending two days on it I just concluded it can't do basic file system operations correctly. I really hope they start testing more thoroughly.
The experience I have had with UK unions is very different from this, and the other descriptions of unions in the US.

I only had a few interactions with them (in a union capacity, the rep was a normal worker as well). These were things like: Getting some new equipment for the break room (kettle and mugs), pushing some new health and safety process (developed alongside the company), and then the yearly meeting, which was along the lines of: "We tried to get X% pay increase, but we ended up only getting X-y% increase. We're organising events for this charity this year. If you want to get involved please get in touch".

I get the feeling that, in general, in Europe unions and companies work together with a co-operative relationship. Whereas in the US there are many that have a more antagonistic relationship, which is just weird to me.
That's a bit snarky.

I've been engineering software for a long time and I've never come across a code base (associated with a successful product) that was debt free.
More power to you. I prefer to use the best tool for the job which in this case are session IDs since they are simpler, have been battle tested, and proven to work for over the last two decades.
Thank You, Ronaldo Lemos
Maybe? But you haven't made a case supporting that's why they went down the tubes.
Unions in Europe are usually optional and are thriving. Unions in USA are usually forced and are not thriving. Don't you think that USA should learn a bit from Europe about this since they are typically far ahead of USA on worker rights issues?
I find that time domain is best for low-Q devices (antennas) while frequency domain for high -Q (filters). Though there are times when one will mesh a structure better than the other. Thin, double curved dielectrics with metal on both sides are the most difficult, especially antennas since you need to mesh out to 1/4 lambda.
Folks should really read this article to get more context on Kickstarter's history with unionization, it is truly bananas and not what you think:

https://slate.com/technology/2019/09/kickstarter-turmoil-uni...

- The first thing that jumped out at me was that the primary spark of conflict was NOT compensation or working conditions.

- The main conflict was around a Kickstarter project "Always Punch Nazis", a project that gathered a few laughs among Kickstarter's largely liberal staff + management. When they faced right-wing political pressure to de-platform this project, since it technically violates their "do not incite violence" ToS, it triggered a ideological schism within the company.

- Unionization seems to be largely about placing this kind of decision in the hands of the employees. This is somewhat consistent with Kickstarter's history of activism.

- However, it's pretty uncharted territory here: Unionization that is not primarily motivated by distribution of wealth, but for the political soul of the company.
A union is simply an agreement between workers and management. Agreements can be modified to prevent such faults when both parties enter in good faith.
Not that I know of.

It was slick because of how high quality the designs, and colors, etc for each slide were. Most importantly, though, it was the best 'story-telling' I've seen in a presentation.
Best practice for TOR:

- Be aware that 3 letter agencies monitor TOR.

- Use HTTPS for everything.

- Dont goto personal stuff that could ID you.

A VPN service could also sniff the traffic and ID you. Work blocks freepn.com, so cant read the article.
good luck to them. I was part of a union and joined the negotiations board. come bargaining time, I was probably the most stressed I have ever been at a company ever. you learn just how little the company actually cares about you and everyone else.
I find the same thing with my local newspaper. I'm sure it costs a lot to have photographers but man if the article says "raging fire"... I want to see some fire.

That's half the draw there / should bring in lots of clicks!

But no...
Ah, I guess it's because I'm on Github Student.
I did some rudimentary testing with AMD vs Intel on AWS recently and found that AMD lacked enough in single threaded perf that it meant they weren’t worth the savings for our workloads (Rails apps).
Depends on how clear the documentation/usage is... and sometimes you accept that you have limited knowledge and understanding. Either way, it helps to understand what you are doing, and when in doubt look it up.
Yeah, I’ve found the purpose built blog generators I’ve played with to be a bit overly complicated for what they do. I’ve found Frozen-Flask to be more straightforward, and it has the advantage of being switchable back to a dynamic site fairly easily. An alternative would be wgetting Wordpress or similar.
Hardly a hot take but a lot of people seem to think that if code isn't actively being worked it, you can't use it, as if there can never be a point where fewer and fewer bugs are reported and fewer and fewer features are requested.

when's the last time Knuth wrote a check for TAOCP? Is it "dead"?
Rockwell Collins, which became United Technologies, which became Raytheon, who was responsible for the 737 MAX's MCAS software and outsourced it to a low wage country, agrees.
Just because you work in tech doesn't mean you can't get exploited. And just "go somewhere else" isn't possible for everyone.
That sounds amazing... as an admin, I mean. Can you imagine being allowed to have scheduled downtime every day? It does suck a bit for users, although honestly putting it at 3-6AM mitigates a lot of my concerns with that.
Masking the memory of fear: Treating anxiety disorders such as PTSD with opioid
Having family who worked with the UAW as well is IBEW I can tell you that Trade Unions in general are much better at 'holding a standard' and truly keeping their trade-craft respectable.

However the UAW, the most worthless crap joke of a union that makes other unions look bad. Basically just protects people who show up to work drunk or drive forklifts into walls. Forces companies to do insane things to fire people who do nothing but drag down the common output of a factory.

Be careful what you wish for and who you choose to put in control a good union can be a blessing... a bad union can be a millstone around your neck that ends up just being owned and, in the case of the UAW, is just a puppet for whatever company they serve.

I will say that when with Amazon I talked to some of my peers in Germany and I was fascinated with the labor protections that were provided to staff over there vs. the USA. They have some kind of thing, like a "labor council" or something. This group had to be consulted before lots of things could be done. In this case I think that it kept the Amazon buildings across the pond much happier than the ones in the USA. (Obviously this is simply my opinion)

I am on the fence, I was raised in a blue collar union family- even went to a little UAW brainwashing camp as a kid (Black Lake anyone?). My family members in IBEW have shown me that there are some very dedicated unions that do very good things and keep a trade from turning into a free market shitshow where everything becomes lowest bidder. If a union exists to truly protect staff AS WELL AS uphold high standards I think it will survive. When its just US V. Them...gimme` free crap, you are asking to be burned to the ground by competition.
Sure, taking on dependencies introduces pros and cons. But isn't this just the classic HN trope where you fly off the handle on a loosely related rant just because TFA has some sort of triggering buzzword like "NPM"?

Not sure how your rant is related. In fact, that such a popular library is being deprecated contains in itself the realization for unknowing developers a downside of depending on large libraries.

Someone upset by this deprecation that wasn't yet aware might, in the future, seek out a more timeless solution for making http calls like the Node implementation of the browser's native window.fetch(). All without having to read a rant.
Who said anything about linux packages? this is NPM.

I'm a library maintainer, and it doesn't make any sense to me to create totally different packages with different names just to handle a breaking change. This is what semantic versioning exists for.
Some things other than salary to consider: open-space offices, unpaid overtime, increase in managerial oversight (pointless standups etc.), erosion of work time/free time boundary, onerous non-compete/intellectual property clauses in employment contracts. Everybody is constantly bitching about those things but despite the claimed shortage of software engineers they seem to only get worse with time. I don't claim that unions are the solution but these problems don't seem to magically resolve themselves either.
There is also the expectation these days that when your project grows big enough, the unicorns are supposed to step in with funding. Considering MSFT is evaluating and using Rust now, paying a couple maintainers would hardly unreasonable for them, the community dropped the ball here. Mozilla and the Rust community need to step up their fund-raising game, losing product managers left and right is simply terrible for the ecosystem. Just a fortnight ago we lost the lead developer of one of the fastest web frameworks in existence over ideological conflicts. For good or for bad, libraries don't code themselves, every effort needs to be celebrated and applauded.
Is being a native Android _and_ iOS dev a dying art?
It's becoming harder to be productive both in Android and iOS as the respective SDK features and number of devices grow.

How rare is being a platform 'bilingual' developer now ?
Telegram does invest heavily on their UI. It's been hard for me to convince people to move to it, regardless.

I imagine I'd have an even harder time moving people to Signal. While their encryption is better, I've seen complaints of messages not being sent and the sender not being aware until days/weeks later after personal follow up on the receiver. Even if this didn't deter me from using it, I have little to no contacts using it. And for the ones that do have it I have no way of knowing if they uninstalled and I'm sending a message to a black void.

If Signal had the reliability, UI polish, consistent updates, and feature-rich experience of Telegram I'd be putting more effort to convert users toward it rather than the latter. I'm a fan of both apps and companies running them nonetheless and am using Signal as my primary SMS app as it's a step to detach from Google.
If you're maintaining two copies of the same features, then, by definition, you're not exactly following the process described? The process was developed to avoid exactly that
Fantastic work, Harry! This is a great product!
So what happens now? Do the 37 nay voters need to join the union or be fired?