skysight-inc/HackerNews huggingface dataset:
> Unions, in my experience, exist to help keep mediocre, unmotivated employees employed. One has no incentive to excel, as promotions are based on years "served", much like prison.

There is nothing inherent in unions that make them operate like that.
Speaking of nested virtualization, are there any plans to support this on E2, or will we have to use other instance types?
Disclosure: I also work on Google Cloud

That's correct! Once the rollout completes, you will be able to use N2D instances for GKE!
> We do not yet support AMD's nested implementation (we do on Intel).

Any particular reason for that limitation, or just "not implemented yet"? (Not asking for product roadmaps, just wondering if there's a specific technical issue that makes it more difficult to support.)

> As for 224, we've always reserved threads on each host for I/O and so on. Figure 2 from the Snap paper [1] is probably the best public reference.

That's helpful, thank you.
Millions of people across the U.S. benefit from collective bargaining, such as increased wages, health benefits and retirement security, yet one anecdotal off-topic post gets upvoted.
Eh, I want to like signal. I really do. But it does not play nice with Blokada ( though that is an easy fix ). My tech illiterate parent was unable to use it ( when compared to whatsapp ). I am kinda done with whatsapp so I finally broke down and added international plan.

I am annoyed, but I can't really blame my parent.
Elon Musk invested all of his funds. Let's be honest, tons of people believed Tesla and SpaceX was going to fail.

https://venturebeat.com/2010/05/27/elon-musk-personal-financ...
I still get 25K emails / month for free with SendGrid using Azure:

https://docs.microsoft.com/en-us/azure/sendgrid-dotnet-how-t...
> Complaining about the lack of competition when union representation has been decimated, seems like pointless bikeshedding

On the contrary, history shows us clearly that the fact that union membership has declined in the US and the fact that union membership in the US is typically on an exclusive representation basis are deeply linked.

In fact, you can still draw your same argument ("the US Government and industry has spent the last 150 years crushing unions and weakening them") from this fact - it just has little to do with propaganda, as you claimed.

> but "unions bad because of [trivial complaint]" is a distraction.

If you want to have that argument, please find someone who said that and argue with them, instead of responding to my post, which is saying something different altogether.
If the world gets to the point where it really thinks their work is useless, I hope _they_ go on strike.
I've tried explaining this to friends on Telegram - they don't care that the cryptography isn't as good, but that its fast, it works, and Facebook doesn't control it. They don't use Signal because it isn't as polished as Telegram.

Meanwhile I have Matrix-using friends explain to me that Signal is secure but its centralization is a threat by being a single point of failure, but I don't use Matrix because it isn't as polished/consistant as Signal.
Events are how MVC was used before the web world came around. The whole point was your controller listens to model and view events so everything is updated real time as the model changes and the user interacts with the UI. The web is a bastardized version of MVC due to the lack of interactivity and state when compared to a desktop GUI application.

That aside, lots of people in the web world have a sort of "Operation" layer in MVC but call them a "service". Deciding to use events is another architectural decision some people make even in web MVC.

But you can take or leave any piece of this stuff and I feel like you don't need a new acronym for every combination of architectural decisions.
This is a very strangely specific comment.

I am not saying if I agree or disagree, it just seems that you had a rather specific instance.

Unions don't mean anything you said above, all a union does is have a strong-arm against the "company". And gives the company a way of communicating with everyone.

Unions don't make rules like what you experienced, a large amount of unneeded employees with nothing to do convince unions to do that.
Local purchases may not be as green as you think. Only a small percent of carbon footprint from produce is due to transport. A centralized production could be more efficient and less carbon (and land) consuming overall.
I don't see why NPM should be so heavy-handed as to prevent installation of deprecated software. It already shows you a warning.

I think it's a good example of when systems over-act on information they do know (a developer has marked their software as deprecated) in ridiculous contrast to all the information they don't know (99% of developers not even bothering to deprecate their package when they abandon it).
>by replying every 2 or 3 hours, when you're waiting in the elevator, or have some other idle time to fill

Most people don't seem to do that. Most people I know, in fact, check their phones while driving, during lectures, during meals with friends and family, walking the dog (poor things), in the gym, walking down the street... I mean, you see it every day. Those aren't ideal times at which you should be checking your phone. Moreover, idle time can be hugely beneficial to rest our minds, relax, or to quietly reflect on important things about our lives.

>some people simply ignore their notifications until they're ready to deal with them. they don't toggle some setting on their device, they simply choose to ignore the whole device. it varies from person-to-person and you might just not be personally suited to this kind of technology.

If having your smartphone around occupies some of your cognitive capacity [0], imagine trying to "ignore notifications". You are keeping your mind busy with endless conversations kept on the air. I don't think anyone is suited to this kind of devices, because the software they run on has been designed to keep you glued to it [1]. I just don't tolerate it as much as other people, I think.

[0] https://news.utexas.edu/2017/06/26/the-mere-presence-of-your....

[1] Tristan Harris has talked at length about it, among other people.
I did a math-heavy degree, so most of my lecture summaries were all written in LaTeX due to the nature of the content (lots and lots of equations; I published most of my lecture summaries on my homepage). For a few other lectures I used Open Office / Word quite regularly (adding and placing images, and working with tables -- e.g. to picture an array -- was easier for me to accomplish with such a WYSIWYG editor).

Also, a cool thing about LaTeX is that your document source is written in plain text, so you can use git to version your source files.

Funny side note: I was using LaTeX so much during my studies that I wrote a Greasemonkey script to actually extract the LaTeX source behind equations shown on Wikipedia [0]; the equation's LaTeX source is stored in the <img> tag's alt attribute.

[0] https://github.com/giu/wikipedia-tex-source-extractor
When did maintenance mode become deprecated? Why isnt that hyperbole?
Not identical but I am considering got because of nice docs and solid streaming support https://github.com/sindresorhus/got#comparison
> why?

Because this is the now main complaint we receive and because the usages are changing.

But we will do our best so that the people who just use the basic player don’t have much changes for them.
This is what semantic versioning is for, though. Breaking changes to the API that still serve the same function in an app would not unreasonably be a new major version of the same package. No one is obligated to upgrade to the latest major version.

A complete rewrite would be a ship of theseus situation. It's all new code, and the API may be different, but it still exists to serve the same purpose in an app. Why pretend it's a new module when it's really just a retooled version of the same one?

EDIT: Ok, I misunderstood what was going on with the request maintainers; thought they were planning to start up a new package as a rewrite of request. That practice specifically is what I was arguing against here -- it's not good practice to start a new node module with a new name just because you have breaking changes to your API. I do not in any way mean to suggest that someone else should jump in and turn request into something new.
These are all minor variations of the same ideas.
Real title: "Alternative libraries to request". The "deprecating" part is simply the submitter's invention, in order to stir up drama.
I worked at an AI startup that pioneered modeling over inbound leads and Sales outcomes (most of this data is in Salesforce + Marketo/Pardot/Hubspot) and that application was hugely valuable for a few companies with massive inbound volume. Zendesk and New Relic were the poster child success stories, since they didn’t have to massively scale their sales development teams to call on every mom and pop / student exploring a trial. It highlighted the 5-10% of their volume that could actually yield real money very effectively.

Unfortunately, there’s not that many companies with that problem, and the market never materialized to the necessary degree and they sold the existing contracts and pivoted. That said, it was a home run for what it did.

If you find the right problem, AI can create massive value. The hard part is never the learning, it’s finding and framing the right problem.
> Democracy is cool, until we look at companies. Then it's dictatorships as the norm.

Democracy is a horribly inefficient system of government. Its only redeeming quality is that it seems effective at (so far) deterring tyranny and abuse of power.

However, like I said, it's horribly inefficient. Changes that are easy to make under a dictatorship can be extremely hard to make under a democracy. Not exactly a quality you would want for a project or company, especially if you (the founder) have a vision.

IMO, part of the reason Linux and Python were so successful was that they had a "benevolent dictator" with a strong vision. Imagine the gridlock that would occur with Linux development if we had a 2-party system that polarized on controversial issues and got mired at every vote.
Any union in the tech industry is going to resemble professional unions such as Hollywood unions or sports unions much more than the punch-clock unions seen in manufacturing and government.
Likewise. "gcloud beta compute machine-types list" doesn't show them in any zone.
Rotterdam-based companies are hiring techies from abroad
And this is what open and free markets will allow for.
Yea, makes me think of how every news blog reported mp3 as "dead" when the patent expired, when they should have been saying mp3 is now license free.
So if the risk was taken before, why does that entitle the risktaker to seek constant gains on it? If I wrote a program essential for the success of the company, before the success of a company, would it entitle me to a perpetual percentage of the company's profits? The benefits of that program, by current standards, belong to the company perpetually. Why does the risk, taken on behalf of the company, only belong to the person in charge?

By looking at employees, you're also looking at a filtered selection of results (the ones who were able to gain employment). The person who took the initial risk (say, a founder) may often leave the company or sell it. Who in the company has then assumed all of the risk? The person who bought the company?

Even then, we're not living in a just world. What's admirable, or a social justification, for taking a risk in a business that operates in immoral ways, or illegal ways? I'm not saying this applies to Kickstarter, but it certainly applies to a great many other companies.

And when GP said "assuming all the risk", I can't think how that's possibly true. Workers in all professions assume some level of risk every day - either to their safety, career prospects, or continued employment.
It could be an option that is revealed after a warning. "This page wants to use the javascript 'copy' event to place transformed data on the clipboard. If you accept it would place [data shown] on the clipboard, otherwise it would place [raw text] on the clipboard". What do you want to do? copy text? copy data? [ ]remember my choice for this site.

Here, data shown would probably be some info about the data rather than the data itself. It could be a 2mb base64 bitmap...

However, perhaps a better alternative would be to offer both "copy text" and "copy" where the former just copies selected glyphs as plaintext while copy fires the js event allowing the transform.

The important thing to remember is that webpages in 2020 must work like users expect desktop applications to work, and interact with desktop applications (e.g. copy rich content from webpage to desktop must be a default enabled feature or the user will consider the browser broken). For this reason, I don't think it's a viable solution to disable the js event by default (i.e. to hook Ctrl+C to the "copy text" function).
It's something inherent in human nature, unfortunately.
While FEM is (rightfully) very popular, a lot of work on electromagnetism is done using finite-difference time-domain methods (FDTD) instead of finite-element.
What exactly does it give the workers, better ways of dealing with management?
You led me to find a map of US anti-union "right-to-work" states on wikipedia[1]. I previously figured pretty much all of the US is under RTW legislation, but it seems like, outside of the folks in Texas, almost the entire tech industry is in non-RTW states.

[1]: https://en.wikipedia.org/wiki/Right-to-work_law#U.S._states_...
> Everyone I see seems to use axios these days

Axios was somewhat abandoned a year or so ago.

A new collaborator was added in Dec 2019 which apparently is picking it up.

https://github.com/axios/axios/issues/1965

Who knows for how long though...
There are some glaring problems with federal law behind unions.

1. A union is required to represent all employees. They should t have to.

2. Companies will still have the money, and the employees will just have "work".

A better view is worker owned co-ops. That way the manager is the employee. The stresses of union vs company dissipate. Some others do take hold, but are much less so.
Why Design Thinking Works for Data
Look here and with their sister orgs

https://www.usworker.coop/home/

They hold conferences and workshops.

Edit: And if you're looking for a higher level approach:

https://democracycollaborative.org/
>His backup strategy is to direct interview into the same set of overly generic questions where the quest has nothing interesting to say. It's kind of irritating.

Couldn't agree more. I want such people to comment on their fields, not wrestle with some faux-philosophical fluff thrown at them at random. They're not some generic celebrities or CEOs. Their perspective is interesting precisely because they do real work in interesting domains.
That makes sense, thanks for the context! I've been through Canadian immigration processes (I'm from Australia), but have no idea how the UK/EU process works.
> Kickstarter produces enough surplus that the workers can get a better deal than they would otherwise.

Not really. It may be short-term better for the workers, but not likely long term as they are effectively constraining the growth of the business relative to what it would be if the union did not exist.
Most people don't think about the fact that "evolution" really is a euphemism for a cold, indifferent, rational genocide performed by nature. When I read phrases like "evolutionary leaps" I can't help but think that yes, with the luxury of retrospective, even the abhorrent acts of the Mongols can be seen as a productive force; but at the other end of it is always countless victims, lives snuffed out by pure chance.

When climate change every so slightly changed the course of our evolution 250 000 years ago, it did so in a world that selected the most competent hunters, survivors, "animals" in the world as it existed. It's curious, and somewhat depressing, to think about what type of "selection" the more than likely catastrophic climate change we will experience in a few generations will have on homo sapiens.

Society, as I see it, is created upon the foundation of knocking natural selection out of the equation. And good riddance; I don't want a world where humans have to fight like predators for the privilege to survive. But this also means we have rigged the game for alternate selection. Considering what the most "fit" future survivors will be, I can't help but wonder what our arbitrary and egocentric selection process will do to the future human -- if it will even be around.

In a sense, we really are space age apes with stone age minds. Whoever survives into the future will be more up to chance and gamble than competence, since our world is so far from meritocratic. At the very least it will be more like a random selection than a fit selection, and worst case we will doom ourselves through our own humanity. But what is the option? IQ tests and fascist elitism? Sometimes it feels like there's no right answer wherever you turn to look.
If the alternatives are better, then devs will choose those solutions and "request" will fade over time. It doesn't have Promise support, so new projects will likely not choose it.

request is very simple and straightforward library that solves a very common issue.

Deprecating it causes a lot of work for every project out there. Either using request directly or indirectly.

I have a lot of respect for the maintainer, and he can choose to do whatever he wants with this module. That's his privilege.

However, the fact that he got "bored" with this solution, doesn't mean he needs to deprecate it. He can just stop working on it, and give ownership to someone else.

If it had a security issue and he is not going to ever update it, then that would deserve the deprecation so people should be warned.
At what point does user experience trump the ability to use the software at all in the first place?

UX designers are often seduced by reductionism because it makes their lives easier and combined with various hand-wavy aesthetical rationalizations, proceed to ignore several immutable aspects of reality:

Developers of an open source project usually have little insight into how their project is actually being used out in the real world. They only know about their use cases and (if they're lucky) that of their co-maintainers and bug reporters.

If at some point in time, an option was added to make some piece of the project do "x" instead of "y", it is overwhelmingly likely that the option _was put there for a very good reason_. Just because you don't know the reason doesn't mean one doesn't exist.

If the project has more than a few dozen users worldwide, then it is extremely likely that for every UI widget, command-line option, or configuration setting, there is a non-trivial subset of users who rely on that thing being there for their workflow. Remove it, and at best you lose those users. But more often you make them angry as well.

When looking at others' code and designs, it is a very human trait to assume that the person who created it didn't know what they were doing and that the way _you_ would do it is better. I get this and I fall into this trap more often than I would like to admit. _But it is almost always wrong_. We often look at the code in a vacuum and don't see the context under which is was written and why it is still there.

I've watched this happen time and time again with various open source projects: Person (or team) creates a successful project, maintenance of the project shifts to a new person or group who decide that the old project was "unmaintainable" and decides to a ground-up rewrite into what they _think_ is going to be a better version of the same thing. When in reality, all they have done is written a new, far less useful version of a somewhat similar thing.

Citation: https://www.joelonsoftware.com/2000/04/06/things-you-should-...
My experience with US unions was similar.

They're just another layer of bureaucracy that is NOT required to respond to you as an individual in any way. I've had lots of poor experience with US unions protecting the lowest denominator at the expense of everyone else. They seem to focus on very specific rules that came up in specific situations applied to everything possible and end up just creating a web that is no different than an employer's web of bureaucracy ... albeit much slower / resistant to change.

I've seen a lot of strange posts about how a union will help with X, Y, Z. They can only help with what they've negotiated, and those rules are restrictions on you as well as the employer. In the US if you've got a fairly simple job that's probabbly OK and a net positive. A nuanced job / people with lots of different skill sets / moving quickly ... those rules can be a nightmare.

Those rules apply to what you can or can't do as much as they apply to what your employer wants to do.

I've heard European unions are notably different, I'm highly skeptical of anyone's ability to emulate that as the help most tech union drives in the US seem to be getting is from traditional US unions.
I don't see anything wrong with MOVE... but why does MVC need to be dead?

It's such a perfect representation of the coder trope of loudly proclaiming that this new thing I found makes everything else obsolete. Eight years later, MVC is still miraculously not dead!
Use Tor? Your privacy may be compromised
> election period

didn't they just complete the election?
Why is an alternative needed? To me it sounds like the library is “done” and has all the features it needs. I wish more code was in that stable state.
Wow this really sad, provided Kickstarter is one of the nicest places to work at and their public benefit corporation was not empty words.

These people ruined a really nice NYC company for everyone around. Anyone running their company who thought of making the workplace a bit different will expect the kind of crowd from this photo to show up and implode it.

One thing is if the conditions were bad, there was insane overtime, the pay was low etc etc., but no, none of that applies to the people on the photo.

This is why we cannot have nice things.
What install limits? I don't really understand what you're talking about, I'm afraid.
> Those who test negative will be allowed to leave between Wednesday and Friday, while those who test positive will be hospitalized. The same measures will apply to crew members. Most of the passengers to be released on Wednesday will be Japanese, with priority being given to the elderly.

How is this enforced? Do they shepherd the infected straight into quarantine after the test, or is it more of a "we trust that you go there now" kind of a situation?

And how is that enforced on those that don't have health insurance - is covid automatically covered?

I wonder (not so much about Japan, where things tend to go down mostly orderly) about other countries with poor healthcare. How is it "managed" in areas where people are already misinformed and/or maybe who rather take the risk (to themselves and others) of sitting it out, because they fear costs or other drawbacks (losing your job etc).