skysight-inc/HackerNews huggingface dataset:
they're playing the long game - making you make the connection and feel smart and smug about yourself. It's all in the game
Which has a freaking DEPENDENCY on is-odd! Seriously?
Interesting observation. I can second your sentiment. For my project, we've recently had a huge push through Google [1]. And I can't remember making substantial changes that would explain this phenomenon.

I don't know why this happened, but I've also heard it from other projects too. But generally, I tend to think that it's always difficult to make out a causation for e.g. hype.

Definitely FB renaming to Meta gave lots of mainstream credibility to an otherwise kinda-fringe space. But I don't know.

- 1: https://plausible.io/rugpullindex.com?period=6mo&source=Goog...
This is what drives me insane about NPM. Libraries are useful, and even package splitting utils like underscore or babel make sense in some scenarios. But it only takes a few packages like these to explode the size of the dependency tree.
I think you may be wrong.

All age groups are equally INFECTIOUS once they have the disease, but are not equally able to BE INFECTED , otherwise people under 55 wouldn't have to wear masks. We wear the mask to protect others right? No matter what our age is.

So why would you reduce the population size to just an age slice?

The same assumption is made when calculating herd immunity. They use the entire populations infectiousness because chance to transmit doesn't change with age but chance to be infected does..

But you DO limit by age group on the infection side because that individuals chance of contracting it from the general population, is based on age/immune system .
Please don't be an asshole on HN, regardless of how wrong or ignorant someone else is (or you feel they are).

HN is a pretty cryptic site. A lot of the time, people have no idea what the rules or conventions are. When community insiders treat non-insiders in a nasty, condescending way, that's poisonous. We don't want that kind of culture here.

In fact we don't want the online callout/shaming culture in general (https://hn.algolia.com/?sort=byDate&type=comment&dateRange=a...). The damage it causes greatly outweighs any benefits.
If I had never heard the phrase "Thirty years war" before reading the blurb, will I be able to appreciate it?
Cloud has nothing to do with outsourcing. We run an OpenStack on-prem cloud all in house. Plenty of major businesses to do. Cloud is a software abstraction to maximize the efficiency of your data center.
This is a result of vaccination. France[1], Taiwan[2] among others are already stopping the distribution of Moderna and Pfizer vaccines. mRNA vaccines actually inject "code" into a cell, much like reverse engineering software.

Unfortunately, small surface hacks can lead to detrimental disaster in overall systems without a full understanding of what that hack affects within said overall system.

We rushed to fight COVID19, and it makes sense. That said, we shouldn't have panicked leaders who aren't able to take a scientific approach.

Now, the news media has been all but completely conquered [3]. The internet is being censored on the guise of misinformation. Freedoms are being lost. It's a tremendous leap that the system of government has made within the past couple years. This is not the result of evil actors, but simply, the system itself has so many forces acting upon it which has led it to become evil itself. Finally, and moreover, as the article implies, the mRNA vaccination experiment is failing, and humanity itself is now at risk.

People talk about 'robot machines' taking over people as in the Matrix movie, but its much more likely 'complex systems of legislation' will rule and dominate people.

Welcome to the Matrix.

[1] https://www.reuters.com/business/healthcare-pharmaceuticals/...

[2] https://www.rt.com/news/540030-taiwan-blocks-vaccines-kids-m...

[3] https://www.youtube.com/watch?v=hWLjYJ4BzvI
NPM fixes private package names leak, serious authorization bug
I love the fact that this small code is still wrong:

var isOdd = require("is-odd");

console.log(isOdd([1])); // TRUE!!
I'll let you explain that to my 90 year old grandma.

(not that a password manager is really any better in this case)
Huh, don't you mean Move fast and break society
Yes. I actually don't mind someone doing this for fun, but to actually defend his actions and claim it's useful contribution is just straight up BS.

I wouldn't want to work with this person.
Why would you even use this?
The worst sites are the ones that truncate my generated password to fit their maximum password length and then don't tell me

Or worse, they truncate your password after you've already used it for years and years.

I had a 30-character password with Bank of America. Somewhere along the line, it changed its password requirements to only allow a maximum of 20 or 25 characters (I forget), which automatically invalidated my password.

The password was stored in my password manager, so I knew I wasn't entering it wrong.

BoA support said I should use the "change password" feature to update my password, but I couldn't because it requires me to enter the old password, which it would not accept. For some reason I can't remember, I couldn't use the "forgot password" feature. Maybe it also didn't work right.

I spent an entire day on the phone getting bounced from person to person before finally someone was able to take a new password over the phone.

Since Bank of America can't figure out how to build a web site login, I no longer trust it with my money. I emptied that savings account and paid off the credit card as quickly as I could. I no longer use BoA.
I've seen this site cripple teams https://sourcemaking.com/design_patterns

"hey we need feature X" (feature X is 2 lines of code).

"Ok, I've made 4 layers of abstraction, and 2 interfaces! an extra abstract class!"
If so, the implementation of isEven isn't even right because it assumes anything that isn't an odd number is an even number.
Can't get behind such meaningless hostile logic, I'm not a spammer and I was only sharing something that I wrote myself that I find interesting and worth sharing.

I don't really care what others can do for my blog, it's not a place for me to get popular in primis.
Scott Galloway’s simple formula for success
Thanks, really glad to hear that! If you do ever end up trying the platform, don't hesistate to reach out and ask questions on our github discussions forum.
FWIW, I didn’t read the top comment as saying anything about the TCP format being arbitrary. I could be wrong, but wearing my glasses with benefit-of-the-doubt strongest-plausible-interpretation lenses, here’s what I see above. It’s two separate clauses in the last sentence:

> It's not like there's an intrinsic reason TCP packets are the way they are now

This to me invokes the idea of mathematical intrinsic properties. For example the idea of the number zero didn’t always exist, but to this day we don’t have multiple representations or any alternatives. Something about the number zero feels intrinsic. Addition, multiplication, derivatives and integrals seem like operations that might have different notations, but are unchanging intrinsic concepts. TCP formats don’t seem to share this intrinsicness. It is in that sense that I agree with the top comment; there is nothing intrinsic about the TCP format, it is the result of conscious engineering choices, and today there are reasonable alternatives. In this sense I see your argument as supporting this idea that there’s nothing intrinsic about TCP.

> it's largely an arbitrary choice that we standardized on.

The word “arbitrary” was applied to the choice of standard, not the format. I’m choosing to see a second, different idea in that second clause. I see how and why it implies the format itself is being called arbitrary to you and others, but my defense of the comment is based on interpreting it differently than what you saw.

BTW, the dictionary definition starts with “based on random choice”. If we stop there, it still adequately matches what I was talking about, and it also unfortunately doesn’t add much color either. Then the keyword becomes “random” rather than “arbitrary”, but “random” is also commonly used to mean the reason is unknown or complex.

Total tangent, but being a fan of Monte Carlo methods, I frequently use “arbitrary” to disambiguate from truly “random”. When people are asked to pick random numbers, the results are arbitrary but not random in the mathematical sense. ;)
>> If the reason for the duplicated code is just coincidence,

Totally agree! However, if code is duplicated because there is some is some assumption of functionality that is represented in multiple places then it gets more iffy. I took this article to imply that in each function implementation there were something like similar calls to a library or particular orders of redrawing based on the way the code base worked. That's where it can get dangerous.

It's not as dangerous if there are four very similar functions sitting right next to each other. But if there is a block of code that implements a way of working and another block of code has the same implementation in a place that isn't as easy to find that seems dangerous to me. If you want to make one change to a code base ideally you make the change in one place.
I read this review of one of John Ringo's series some years back and have never been tempted to read anything by him - the review is hilarious, the books sound absolutely fucking awful.

https://hradzka.livejournal.com/194753.html

This review even coined the meme "OH JOHN RINGO NO" lol.
“number" == typeof variable

Works for decimals, too.

Although maybe you meant to include

"1"

In your examples?
I'm curious how you get your password from there and into a form on a website.
Many leagues were stopped for weeks/months due to covid and then resumed. Wondering how this relatively long period of inactivity affected players' health.

Also: some leagues finished their season later than usual and the rest before the consecutive season was lower than usual, i.e.: 3 months of no playing and then suddenly more intensive game schedule than ever.
Doom is becoming the NetBSD of computer games. People managed to port it everywhere
I am not sure if I have understood the question.

I cannot disclose the detailed specifics of my case.
Sell it to a neighbor for cash?
Oh dear - this is also laughable issue, because combating CO2 is depriving trees of their food. Whole Sahara has become greener from climate change and CO2 avaibility - maybe it is worth to grow trees in Sahara. Forests of Sahara - what a great name!
https://twitter.com/YaffaRaz/status/1460311564855218188

Take a look at the author's twitter feed. Without being able to read (hebrew?) they're clearly an antivaxer. This piece doesn't mention covid or vaccines, but its implied.

Reading around it seems like the data is not correct. At a minimum the headline says 100 people died but later on there's nothing, not even their own chart, to support that claim. I would treat this as extremely biased. Flaggin'
There are two sides to web3 as I see it:

On the one side there are people obsessing about ownership and monetization. They want to buy and sell digital things for profit. They want to create pay to win systems where you have to spend money to have tokens to access services.

On the other side you have the altruistic, open access web3 that is focused on decentralization and breaking down walled gardens. For example IPFS is the peer to peer network for hosting and fetching content, resistant to censorship. It is probably the closest thing to old days of web where there was an ethos of open access to data.

The "for profit" crowd is trying to create an artificial decentralized monetization system on top of the fundamentally free, decentralized, peer to peer stuff like IPFS. For example if I host something in IPFS then there is nothing stopping folks from accessing it from any peer that has a copy. There is free and open exchange of data. But if I have an NFT then I can claim that I "own" something that is hosted in the distributed, decentralized IPFS. Some people are going so far as to say that they want NFT's to be used to implement a form of DRM on top of the peer to peer decentralized tech that would otherwise be freely exchanging data.

Personally I see web3 as the underlying decentralized tech like IPFS and ENS, but the NFT monetization and speculation side of things is a toxic casino and monetization layer bolted on top and it will probably harm the ecosystem of actual open decentralized tech underneath.
Here the author tries something then gives up. That does not mean clean code is not something to aspire or pursue.

What is described as building trust can be also interpreted as groupthink and colleagues forming pacts of mutual non-criticism (which breeds mediocrity). Which is also the way to build dogmatic cults of personality, and becoming superficial developers that care more about talking about their weekend than their craft.

You do not trust code. Memory and attention are fragile. Everyone makes mistakes. Everyone can have a bad day, be distracted, tired, etc. Building trust sucks. Trust nothing and be able to verify everything.

Your job is to edit code: add, delete, modify code. Each time you check in code it becomes company property. It is not "your" code. Modifying other people's code is completely OK, and expected.

In the end, this article is just wrong. "Give up, tech debt is your friend. Your job is to be best friends forever with your colleagues". All wrong conclusions.
I don't care what you are in favour of. I'm just saying that the outlook of Chechen insurgency in the western world was very positive, and after that (combined with Libya, Iraq and Afghanistan) they've lost any moral stance to complain about any other insurgencies. As one dude, whom I don't even really like, said: "Who are you to f... lecture me?"

The difference between Chechen and Donbass insurgencies is multi-faceted, but the point stands.
You realise that everyone pushing changes to main several times a day is the definition of CI? and it's pretty much impossible to do with code review as a gate for pushing to main. Interesting how CI has become semantically diffused to mean literally the opposite of CI: tooling and processes that delay integration and make it easier to work in isolation.

https://wiki.c2.com/?ContinuousIntegration " The most granular unit of integration should be one step of one refactor. "
It also make coding the backend somewhat easier, as unchecked checkboxes/radio buttons are not included in the POST data. Not sure how much this is an issue with modern frameworks but when I did HTML/Forms work this was a constant surprise to newer developers.
It's not meaningful to talk about IPFS being expensive, it's like saying bittorrent is expensive. Both are just ways for people to seed a file, and other people to retrieve that file from its hash. There's only as much redundancy as there are people who want to seed it. IPFS is in wide usage because of libgen haha. Currently the resolver can take 30ish seconds, and there's a new, fancier resolver that supposedly takes <5 seconds, which is still pretty high compared to what people are used to but it's a work in progress. There's also IPNS which allows for the controller of a keypair to update the content associated with an identifier.

Filecoin is an incentive layer for IPFS that I'm much less bullish on. It's probably what you were thinking of, it's a way to pay money to have someone host or serve something for you on IPFS. It seems pretty underbaked to me but I think it's in the same order of magnitude, cost wise, as AWS.
> IP and TCP were very carefully designed

How did it happen that the byte order of the multi-byte numeric fields in TCP/IP headers is big endian, which is opposite of what most machines use now? Back then, did it look as if big endian would become prevalent?

Today, almost every host attached to an IP network has to byte swap.

The IPv6 people definitely ought to have designed a little more carefully.
Streak (YC W22) is hiring React and TypeScript experts
`is-odd` is made by the same developer. This was created to inflate NPM numbers.
I usually line by line count by hand, you get a good count, and learned the source along the way
You do realize that the managed website hosting of the late 90s/early 00s still exists today, right?

You don't have to stand up your own servers in your favorite cloud provider and become a Cloud DevOps expert. You don't have to manage deployments, dependencies, etc. You can still pay $3/month to get shared hosting on DreamHost, upload your HTML file, and it gets served. No fiddling with nginx, no operating system patching, etc.

Even if you don't want to pay $3/month, I'm sure there are still hosts that will give you a few megabytes of storage and a couple gigabytes of traffic for free.
I mean, I feel like even the most basic execution of Open Banking (aggregated view of your money across all accounts) is a killer use case. People like to know how much money they have.
People are connecting this with COVID and/or its vaccines, but in 2020 we saw a 90% reduction in out-of-competition doping controls. This was followed by statistically significant spikes in athlete performances once competitions had restarted. I would look into that rather than the COVID link.
I would think universal identity management (yikes) would hold back "open banking" given the article's definition of open banking to mean standardized financial data exchange.
I recently bought a foundue set; the hotplate it comes with has a magsafe regular 110VAC wall cord (no DC adaptation) that's magsafe on the device end. I wondered why I had never seen one of these before. Then I realized that that flat device end is actually incredibly dangerous to the touch when plugged into the wall. It's just slightly less dangerous than potentially knocking over a pot of boiling cheese. For regular appliances that aren't going to give you third-degree burns, it'd probably be preferable to just let the device get yanked off the table, than to risk exposure to live current.

I wonder if, in the future, we could have household wall sockets and extension cords with "sense pins" ala USB PD; where the mains-voltage live "rail" isn't energized unless a device hops on the logic-level control rail and negotiates for it. Then we could truly live in a MagSafe-everything world. (Then again, to block that kind of current, they'd probably need to use relays and other non-solid-state parts, so they might not be the most durable things...)
Well, not quite. It has inherent value since fiat is guaranteed to be backed by the full faith and credit of the backing nation. That is, by holding fiat, you trust that the country issuing that fiat doesn't default (and will hence guarantee that value). I don't see a similar parallel with crypto, though I'd love to be corrected.
Or spend 5 minutes and review the anti-vax mess. It spells out it's agenda in the opening paragraphs.

Past that, it isn't a focus on FIFA but globs together tons of posts about anyone who plays sports, eg: school-age leagues.
To be fair, you also get to make a very clear difference in the everyday life of millions, solving actual problems for real people - instead of finding new ways to display despicable ads.
... typeof foo === 'number'
Is it password rules he hates or the UX around the password rules?

I just read the post and if the system response had been "You must have 2 numbers in your password", well then, okay, easy enough to do. An annoyance rather than a hatred.

Not that I think password rules are great. They can, if used poorly, unnecessarily constrain the space of passwords. But they are often required by certain compliance situations.

I love my password manager and think everyone should use one, myself.

Another alternative is the FIDO passwordless technologies that are being rolled out more and more. Though I saw a tweet the other day that said "Biometric identification is a username not a password" that made me think about that.
I once had a bank that used substr(tolower(input_password), 0, 8) as the actual password.
Everything is fine in moderation. Everyone needs time to decompress from a long day in some way or another. If video games are your way to do that, that’s great
I don't think this is necessarily true. If I have one place in my code where I sign unsubscribe tokens for emails and another place where I sign cookies for auth I don't want to implement a HMAC twice. Even if the verification paths are different so the algorithm doesn't actually need to be the same it is still better to use the same code for both so that any bugs, inefficiencies or other problems can be fixed once rather than up to twice.

I think the true decision function lies somewhere in the middle. For relatively simple code that doesn't need to be in sync then yes, duplication is likely the best option. For complex code or code that should stay in sync then extracting the common code is likely best. But there is a huge range of code in the middle where it is a judgement call with no obviously correct answer.
No, the code posted in this thread clearly indicates it will raise an exception in such cases.
The source has no verification for those high numbers. What is has are tons of links to facebook posts and other anecdotes.
Or the site lets your password manager fill the fields, but for some reason their javascript doesn't recognize it and refuses to let you submit because it hasn't verified your password as matching, meeting strength rules, etc. At least in that case deleting and typing just the last character usually fixes it.
I replied to your email but perhaps other users may like to read the explanation, so here it is:

Your account's not banned, but HN's software is killing your posts because it thinks you're running afoul of the rule against using the site primarily for promotion—see https://news.ycombinator.com/newsguidelines.html: "Please don't use HN primarily for promotion. It's ok to submit your own stuff occasionally, but the primary use of the site should be for curiosity." Our software detects that sort of submission history and starts filtering the posts once the percentage of own-posts is too high.

On HN, the idea is for people to submit stories that they ran across and personally found intellectually interesting, not because they have something to promote. It's fine to post your own work, as long as it's interspersed with interesting posts from unrelated sources. But when an account only submits promotionally, it feels like they're not participating as a community member, and HN users notice this and flag the posts.

I don't want to discourage you from submitting your own work! But it's best to build up a track record of interesting submissions from unrelated sources, and to intersperse your own articles with those. The software considers submission histories adaptively, so if you do that, your own-posts will eventually stop getting filtered.

If you dig up interesting things from a variety of places, things people haven't run into before, then you'll be perceived as a community contributor rather than someone trying to market something. Particularly good are stories on out-of-the-way topics that rarely or never get attention. The best submissions are the ones that can't be predicted from any existing sequence (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor...).
I wish some of these large projects would start seriously auditing their dependencies and stop pulling in dependencies that have many dependencies themselves. There is a one-two punch of a culture of "there's a package for that" and npm not requiring flat dependency trees by default. The denial in the node community that npm is uniquely bad is frustrating. I want the community to stop denying and own these issues so things can get better. It's going to take the authors of large packages to start evangelizing the use of fewer, higher quality packages, using flat dependency trees, and re-implementing trivial functions instead of adding another node to trust.