skysight-inc/HackerNews huggingface dataset:
This in part has to do with how versions are specified and the standard way that this is done allows minor and point releases to be trusted.

https://stackoverflow.com/a/22345808 - and especially the comment.

You will find a lot of `^1.2.3` in version specifications which means everything from `1.2.3` up to (but not including) `2.0.0` is allowed.

Specifying `1.0.1 - 1.0.3` is allowed too and would meet the desired functionality - but that isn't the culture of JavaScript developers.

The version range is allowed in other dependency management systems (e.g. Maven - https://www.mojohaus.org/versions-maven-plugin/examples/reso... ) but rarely do I see it used - most often its pinned to a specific known good version.
Switching to a four-day workweek (2021)
I’d say their name the way they wanted to, because I’m not an asshole. But I don’t think that’s as much of a contradiction as you think it is. It’s a great example of how language evolves.
My understanding is that private relay only (for now) relays plain HTTP content from apps, and HTTP+HTTPS content from Safari.

This means it likely shouldn't (currently) affect zero rating for apps, though it would affect header enrichment for first-party web based services. A native app shouldn't be affected, and given most services run on HTTPS, they won't be able to add headers to those requests anyway.

The impact of losing visibility of plain HTTP is likely minimal given how much is HTTPS now. The impact of losing visibility of sites visited and DNS queries may impact on carrier 'value add' services like internet filter, malware protection, etc.

Also it would be harder to link location based services in for web-based content, as they can't correlate the browsing session with the phone user.

If Apple was to expand this to cover HTTPS traffic via apps, that would break a lot more. Carriers are desperately clinging to ways not to become dumb pipes, so it doesn't surprise me to see them resist these moves.
>fame and applause
>Maybe they are rightfully so, since they paid with social capital

I'm sorry, but I think you're exaggerating a lot here about the worth of "fame" in something as niche as writing open source software. It's like when people try to pay artists with "exposure" -- flashy, but worthless in every imaginable way.

Case in point: The creator of Homebrew who famously failed to get a job at Google despite having all "street cred" imaginable.
Checking in your dependencies with https://github.com/JamieMason/shrinkpack can help insulate you from these problems until you're ready to face them. I created this before left-pad and thankfully meant that we were unaffected.

A lot of developers, understandably, baulk at checking in dependencies, but there is a concrete benefit in being able to continue uninterrupted during outages.
But resources are not limitless.
What should I wear for snow, or ice and how do I know if I would encounter those conditions?

Before covid, when I commuted, I used to cycle in 11 miles each way every day. Except when the temperature dropped below 5c. Not because I didn't have warm clothes, but because once I hit some ice under a bridge travelling at ~20mph and came off. It took a long time for the wound on my knee to heel from that.
the PR adds effect handlers (`stdlib/effectHandlers.ml`). Does that mean work will begin to start replacing Async+Lwt with a native alternative?
Kaggle Datasets
I don't think Trump believes in conspiracies, generally speaking. I think he simply finds them useful for manipulating large groups of people. I could certainly be mistaken.
Physically separated bike lanes are even worse. You can't get out of them easily if you come across a lot of debris. And they are harder to street clean, so debris accumulates more.
> This is incorrect. DMARC requires nothing but an email address to send reporting to.

This is also incorrect. Reporting (rua/ruf) are optional.

> if you don't have a policy of "REJECT" set on your domains, DMARC isn't doing you a whole lot of good.

With "quarantine" failing emails will go to spam, which is plenty good enough in most cases.
Seems like a step in the right direction here. 125k for 7% is still extremely steep in todays market.
I wouldn't describe the fees as "extremely prohibitive"...

https://ycharts.com/indicators/bitcoin_average_transaction_f...

"Bitcoin Average Transaction Fee measures the average fee in USD when a Bitcoin transaction is processed by a miner and confirmed. Average Bitcoin transaction fees can spike during periods of congestion on the network, as they did during the 2017 Crypto boom where they reached nearly 60 USD.

Bitcoin Average Transaction Fee is at a current level of 1.560, down from 1.798 yesterday and down from 15.45 one year ago. This is a change of -13.20% from yesterday and -89.90% from one year ago."
Basically, applications should use a lock file for dependencies based on known tested good versions of dependencies.

How is it that people aren't doing that today? For the sake of security and stability, lock files should be used.
I've interviewed well over 100 people for DL/ML positions. This may be a good roadmap to what some people ask, but it's a terrible guide to what you should ask. It's like a collection of class exam questions.

Just as in programming, the world is full of people who can recite facts but don't understand them. There is no point in asking what an L1 norm is and asking for its equation. Or say, giving someone the C++ code that corresponds to computing the norm of a vector and asking them "what does this do". Or even worse, showing them some picture of some cross-validation scheme and asking them to name it. Yes, your candidates should be able to do this, but positive answers to these kinds of questions are nearly useless. These are the kinds of questions you get answers to by Googling.

It's far more critical to know what your candidate can do, practically. Create a hypothetical dataset from your domain where the answer is that they need to use an L1 norm. Do they realize this? Do they even realize that the distance metric matters? Are they proposing reasonable distance metrics? Do they understand what goes wrong with different distance metrics? etc. Or problems where they need to use a network but say, padding matters a lot. Or where the particulars of cross validation matter a lot.

This also gives you depth. "name this cross validation scheme" gives you a binary answer "yes, they can do it, or no they can't" And you're done. If you have a hypothetical dataset, you can keep prodding. "Ok, but how about if I unbalance the data" or "what if we now need to fine tune" or "what if the payoffs for precision and recall change in our domain", "what if my budget is limited", etc. It also lets you transition smoothly to other kinds of questions. And to discover areas of deeper expertise than you expected. For example, even for the cross validation questions, if you ask that binary question, you might never discover that a candidate knows about how to use generalized cross validation, which might actually be very useful for your problem.

The uninformative tedious mess that we see in programming interviews? This is the equivalent for ML/DL interviews!
I no longer write Ruby professionally but in my last 18-24 months of Ruby work I leaned heavily on some of Jeremy's excellent work with roda, sequel, and others (forme, erubi, rack-unreloader, etc.). Top notch work, truly. I had no idea that he had written a book, thanks for pointing that out, and I'll definitely be picking a copy up.
> No law compels Bob to provide people with new copies once the work enters public domain

The problem is not what the law requires Bob to do. The problem is what the law prohibits you from doing.

> Once it does, Bob can't stop you from distributing a version you created by buying a print copy and scanning it or taking screenshots of his DRM version and running them through OCR

"The law against breaking DRM isn't wrong but only because it is actually useless."

> Since Bob's DRM is likely used for other works not in the public domain, it's going to be hard to distinguish your breaking it for this PD work from the fact that you've broken it for lots of other in-copyright things.

That's the problem. The tools don't discriminate, so banning them goes too far and prohibits more than it is reasonable to.
Current day job company is big enough to have it’s own “software factory” abroad.

It’s horrible.
Some good guys but mostly Indian freshers that get burned in 1-2 years.

Time zone difference sucks.

Zero understanding of the product.

To get the proper end result you have to specify the work chunks on such a deep level that you are faster doing it yourself in the first place.
You make some great points. My points were for crypto in general, so do you think a crypto will come that is truly decentralized and can be mined more easily?
So the current arrangement of service workers being paid slave wages and given disgusting conditions is working fine?
> Starbucks, Google, Amazon, these companies will spend millions to fight unions. This is prima facie evidence to me that unions benefit workers.

Technically, that does not follow. What can be inferred is that companies believe that unions will cost the company money, but this does not necessarily mean that the employees will get any of that money. One could imagine a theoretical evil union which takes all the extracted profit from the company and gives it to themselves, and not to the employees.
Are you not scared for gusts of wind that will send the panels through your windows? The Netherlands has some rough storms.
The whole point of studying excess deaths is to figure out covid's contribution over and above the usual number of deaths due to these pretty common conditions (like high blood pressure.)
"They ignore stop signs and traffic lights, trying to pass as a pedestrian whenever it is convenient, and have been responsible for many pedestrian related injuries"

No doubt, there are ruthless cyclists as well. Still, are you aware of the difference in numbers and quality of "car driver killed cyclist" vs. "cyclist hurt pedestrian"?
Yup

And if there was any doubt, this action by Google — in and of itself — should convince everyone (outside of Google management) that unions would be a good thing.
I'm sorry but there's a social contract. It's implicit, the moment you participate in a society the expectations from you and obligations towards you begin.

Even if someone asks you the directions to the gas station, you are expected not to deceive them and give them the best instructions to you your ability and they are expected to show some appreciation for helping out the society. You will face backslash if you don't help a fellow human or deceive them despite the fact that you are not receiving direct payment for your act.

Imagine you put a sign that says "The mall is in this way" and the sign is not entirely correct. It was a free sign, no one contracted you to put that sign but if it happens that your sign wastes someones time you will receive negative feedback and probably requests to correct your sign.
> Editing implementation for single lines of text do not work well at all for entire text files. Operations become incredibly slow, which is why we invented things like rope data structures and buffered views.

memmove() is about 100 gigabytes a second on my computer. That's 100 megabytes every single msec. My screen refreshes at about 100hz. None of my source code files are even 1 megabyte let alone 100 megabytes, so at least on my computer, for all of the files I edit, there isn't a single operation that a "rope" or a "buffered view" could offer over the naive because I could literally just rewrite the entire file in C 100 times every keystroke, and I think for many operations it is obvious how to do better.

For this reason and others I think it's absolutely plausible for a beginner to self-teach themselves how to write a good text editor and even improve on things, and I would never want to discourage someone from a discovery they have both the interest and the time for.
I do not see any data about India
> I have a boss, don't get overtime, can't work for other clients, signed a non-compete, etc.

When you are a contractor you don't really have a boss. You have clients, you need to start getting yourself in this mindset, even though the end result ends up being more or less the same.

So again, no boss, but you have a representative from the company that you have a contract with that is your liason and the person that is giving you the work. You need to keep them happy like a boss, but they are not your boss.

You don't get overtime from the company because you are not an employee of theirs, you are employee of your own contracting business. It is up to you whether you pay yourself overtime or not.

Whether there is money available for this or not in the contract depends on how you negotiated the contract.

Regarding not being able to work for other clients, this is just not true. You are your own business and you can take on all of the clients you please. The documents you signed are meaningless and do not hold any water. Of course if you do take on work for other clients, you do not need to let your current customer know unless it will materially impact them in some way.

> I work on a team where everyone else is an employee and I don't seem to be treated differently.

This is normal for contractors. You work alongside regular employees and everyone is focused on the same goal. The only issue is that you need to not think of yourself like an employee. You work for yourself and you create the rules around how you operate your business.

I think what you need to do more than anything else is to talk with other contractors about how they deal with clients.

Get better information about how long they take contracts for, how many contracts they take at once, how they negotiate prices with prospective employers and what formulas they use to factor in external costs, ask them how they budget the money for their operations, how far they plan ahead, ask them how they do their own healthcare.

You need to take your business to the next level, and currently you seem to be allowing a customer to drag you around by the shoestrings to do whatever you want.

It's time to start setting some better rules around how you operate, instead of just going with the flow.

I believe getting this advice from other people who are currently do this is probably the best way to start.
The real long-term solution is for projects not to have hundreds of weird dependencies.

If dependencies are pinned until developers update them, you have massive security holes, because developers can't be trusted.

If you take the latest dependencies on every update, you have massive functional exposures (and security holes), because different developers can't be trusted.

If you have "community review", you create a new class of thankless work that nobody will want to do... except power-tripping control freaks who want to gatekeep over whatever their personal obsessions may be.

If users have to pick the versions, nothing will ever work, because users can't be trusted (and wouldn't want to do it anyway).
Thanks for the links!

While it's not enough to generate a stable income, faker.js has received over $20k in donations through Open Collective. It's more than most other projects -- but I guess nowhere near what one could get if a big corporation wanted to sponsor the continued development of the project.

https://opencollective.com/fakerjs
lighting network?

https://en.wikipedia.org/wiki/Lightning_Network

or

https://ledgerjournal.org/ojs/index.php/ledger/article/view/...
The problem from my point of view is conflating ongoing healthcare with catastrophic coverage. Outpatient care should absolutely be a free market (prescriptions, lab tests, specialist visits etc.). Catastrophic incidents/diagnoses should be a simple lump sum payout (Cancer, Hear Attack, Stroke, etc.).

Alternative options I've seen being offered for ongoing healthcare is Direct Primary Care where essentially you pay a membership fee to have unlimited access to a primary care physician.

I think the root of the problem is subsidization and the patch work of legislation that gets piled on year after year to "fix" the issue. The entire price function is completely out of wack and as long as the patient is stuck between the provider, insurance carrier, and government debating who has to pay, they will lose.
> Features like donloading content is the main benefit.

Ease of use yes. But ease of ownership is much better with pirated content. I can play pirated music where and how I want. I'm not tied to an ecosystem.

Gabe said it best - piracy is a service problem.
My family worked in the automotive industry for over 60 years now most of them for Mercedes some for Toyota and in the newer generation a lot of them for Tesla. Everyone of them who switched from high profile positions at Merc or Toyota said that Tesla is without a doubt the worst employer especially for lower skilled labor. These are all lower or middle management positions not the poor guys on the assembly lines. Merc and Toyota have benefits for all their employees even the lowest skilled among them. From Tesla the only thing you can expect is an email from Elon to force your subordinates to come in over christmas because paraphrasing here from one of those emails "Without extra time Tesla will be in dire financial struggle." or retaliation because you said no.
The real question is can you do without this job?

You are dipping your toes. Once it all starts be sure to seriously think about how things happen on the ground. Don't let yourself be overworked just because finding something else feels unappealing.

Honestly it sounds like red flags to me. If they need you to determine what tool to use, then they need to be paying you for those choices since it sounds involved. If they cannot move the start date up, they should wait until you start. I think your boss is probably going to hit you with as much overtime as they can out of incompetence (best case scenario).
> If I was an ethical journalist, I would not run a story lambasting others for dark patterns until my own house was in order.

I actually think it is unethical to suppress news like this, but fine, let's grant it for argument's sake.

> And if I wanted to run the story anyway, I would at least mention that my own newspaper is guilty of the same thing for full disclosure.

Fine, let's see what the article says:

> The Times requires people to talk with a representative online or by phone to cancel subscriptions, but the researchers did not study it or other publishing sites.

Okay, the paper being discussed didn't discuss the NYT, but the NYT journo decided to bring it up. We're good then.
"18 U.S.C. § 1030(a)(5)(A) knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer;"
> A developer creates a work, gives it for free(in writing) and receives fame and applause by the terms of the social contract.

There is no "the" social contract. There are many social contracts, and they are not all compatible with one another. The whole point of written, legal contracts is due to a recognition of this fact.

I don't abide by that (or any) social contract when I put something on Github, and nor should I. When I say that I can't guarantee this code won't cause harm (e.g. destroy HW or files on your HD), I mean that. If you want to labor under unspoken, unwritten contracts, be my guest.
What is a SAFE? Any newbie reads? I got the 7% equity part, but some examples could be useful for the code monks amongst us.
> That friend kept asking me to write a converter that would convert a file of TeX to a file of HTML. I kept telling him that such a converter was impossible because TeX was a programming language and HTML was not.

According to Massimiliano Gubinelli (please take a look at the following comments thread https://news.ycombinator.com/item?id=27820466, in particular at https://news.ycombinator.com/item?id=27822662), the reason why a converter is impossible is that the _syntax_ of TeX is Turing complete. If one had kept syntax and programming constructs separated, then a converter would have been possible. (I understand the argument only superficially but I trust Gubinelli enough to report this here).

> Future of TeX?

is TeXmacs, worth trying
I've lost countless hours to "works on my machine but not coworkers" which turned out to be issues compiling nokogiri with native extensions. It broke all the time between macOS updates. Vagrant / docker were a godsend to removing that element of uncertainty.
The 'g' is not sounded out loud anyway in Dannebrog, so your interpretation still lives, I can happily report.
It's because having an actual shrinkwrap file in a library introduces a huge number of conflicts. If library A has 20 transitive dependencies, and library B has the same 20 transitive dependencies, deduplication based on ranges can leave you with only 20 transitive dependencies. If both libraries have shrinkwrap files in them, you can end up with 40 transitive dependencies, even if those are nominally compatible with each other. When you consider that even with the current behavior projects end up with thousands of transitives, you're looking at adding literally thousands or 10s of thousands of duplicate dependencies to a project. That's not even considering that some duplicate dependencies will just break things if they show up multiple times in a project (older versions of react, for example).
Fantastic article. As it suggests, the key to fighting back against social-media manipulation (including here BTW) is education. Learn how you're being distracted and guided against your rational will, and you'll be better able to resist that pernicious influence.

Fun anecdote, related to the Google snack-bar example mentioned in OP. When I went to Facebook bootcamp (yes I worked for the evil empire), there was a segment on the cafes. Not cafeterias. Cafes. It's classier, and TBH the quality of the food at those cafes does justify the distinction. Anyway ... they made a big point of how they consciously arrange healthy vs. non-healthy choices at the serving stations to guide employees toward healthier choices. At the time I thought it was cool. Now, all I can think is that they're showing far more consideration for their employees than they ever do for their users. On the site/app we all worked to support, every design decision was made to encourage unhealthy choices for the sake of profit.
And it has been going on for 25 years, the deal being cited as the reason Bill Clinton visited Denmark in the 90’s (we usually never get visits from US presidents)
My understanding is that the point of unions in tech is for people to band together to stand up for those that might be under-represented. It's like the ultimate diversity/inclusion initiative.
I didn't think I worked for Amazon in Customer Support, but apparently I do! Upvoting because signal boosting through social media has become the only channel for receiving human-intelligent customer service from Big Tech. It's not worth thinking about it any deeper, it is what it is.
>I believe the news should have a vendetta against anyone and anything that has outsized influence and control in society.

so, should news have a vendetta against news? because one thing i've seen over the past 6 years is how much influence media has on the population.
I tried to do the same switch and found the results wildly unpredictable. That said, to get there I reverse engineered some demo code that was very hard to follow, and I probably made a mistake. Either way I’m perfectly happy with my HSLuv results so I reverted.
I hate this position. Imagine someone ranting about MKULTRA if the CIA never acknowledged it. Imagine it was just some papers on the internet with no providence. I like to think of it as a matter of diversity of though. We need the "crazy" people to explore the really unlikely bizarre scenarios that MIGHT be true that most mainstream people will never even humor. At the end of the day reality is stranger then fiction.