skysight-inc/HackerNews huggingface dataset:
It’s a tortoise and hare race with genetic and memetic evolution. Recently, the sexual revolution (with contraceptives) has severely depressed population growth. In the long run, the tortoise will win out though. Genetic evolution will select for people resistant to these ideas. Communities with high fertility rates (such as some religious communities) will grow quickly and replace the contraceptive-using public.
> Data never changes, but we have the possibility to create a new version of the data.

Well, it depends on what you mean by data. To avoid ambiguity it is better to talk about data values and data objects which have different properties. This can be formalized as follows [1]:

o data values are modelled via mathematical tuples – tuples are immutable

o data objects are modelled via mathematical functions (one field is a function from this reference to the field value) - functions are supposed to be mutable

(In reality of course we meet quite different situations, for example, struct is mutable and objects can be immutable.)

[1] Concept-oriented model: Modeling and processing data using functions https://www.researchgate.net/publication/337336089_Concept-o...
And you are starting with the assumption that admissions should reward merit rather than produce it. If a public school is not intended to convert potential to merit, I don't know what is. A school is not actually an "-ocracy" of any kind and this is a weird semantic argument.

If one were going to take a fundamentalist view of merit and exclude potential (again, weird choice for a school!) it would be especially important to define what merit it is you think you can measure. Are you sure the test (+ prep system) do that well? Does spending money on a specialized prep that improves your score translate to producing the merit you are talking about? Or are you retroactively defining merit as "the thing you can measure", because measuring is itself the appealing part?
Discovery of Hepatitis C Virus Wins Nobel Prize
Did computer motherboard firmware not have memory test boot programs back then?
Has anyone seen analogous behavior in (adult) tech spaces? Raise your hand if so.
This is excellent advice. The antireflective coating didn’t ever do much for me but I can recommend all other tips 1000 times. Just fine tuning the brightness and level of white of my monitor and turning the orientation of my desk worked miracles.
Yes I thought that when I visited. A vending machine on the streets of a UK city full of beer and cigs wouldn't last 3 minutes.
Here’s the thing....
Was the page actually served from cache for Cloudflare CDN? Cloudflare does not cache html by default and the post does not include the configuration that was used or the response headers.
Aditya Birla Sun Life AMC Uses Artificial Intelligence
I mean nobody knows which parts make the difference, but the market will tell after time. The more regions try to change things the more likely it is going to work somewhere. I think that can be great if the decision makers are held accountable / fired if it does not work. Without proper incentives / skin in the game this is just another way decision makers will (subconsciously) implement some crony-sh*t
For apps that really need security, android porivdes attestation using secure element.

https://developer.android.com/training/safetynet/attestation

https://source.android.com/security/keystore/attestation

So it's not all wild west. But most apps don't need this level of security.
Just found rule 5:

Negative adjectives are formed with "UN"-

Double plus ungood, citizen!
Blood Test for Alzheimer’s in Reach
True. How often that careful measuring occurs would be interesting to know. Except for some people on here on HN I can't think of any personal acquaintances who do it that way.
Generate Random Text from Regex
I don't "enforce" this but I do aim for it, and yes, I do partial squashing throughout my workday.

As I work on a feature branch, I'll check in WIP commits as checkpoints, especially at EOD. I don't expect these to pass the full CI suite.

But as the code starts to shape up, I'll unstage all those WIPs and start to group the changes into logical commits. As work progresses, I'll use `git add --patch` to split new lines of code into those existing logical commits. Sometimes I'll split one up, sometimes I'll group two together; it's still flexible and amorphous at this point.

By the time I'm ready to merge upstream, these commits tend to be neat, focused, and functional, and I do check to make sure they pass the relevant tests (though I don't enforce a full CI build here).

Then a rebase from master, push to CI, and then a no-ff merge commit into master to retain both the low-level commits and the ability to easily revert the whole lot.

It might seem like a ton of busywork, but I find that staging atomic commits like this doubles as an excellent line-by-line review of the code I've written. It also forces that review step to happen throughout the process rather than all the way at the end when I've forgotten all that deep context.
Nodemailer postinstall script wastes 2 months of computation time every week
> See Racing Point breaking system affair. It's illegal for sure, but no fine has been issued because they need racing point to be there and fill up the grid.

You mean aside from the €400k fine...? (along with the deduction of 15 points in the constructor's championship)
I sincerely hope to remember this when I'm drunk and need it.
The core task of a lawyer is risk identification and mitigation.

If everything else goes south, the client sues the lawyer — and the best defense is “here’s where I said that might happen.”
Then that's the other half of my point. If you can limit PRs to 300, then merging PRs into a single commit is better. If you can't, then maybe squashing isn't ideal.
Lots of people aren't victims, they choose to remain ignorant after being warned. Often they don't take the warnings seriously and even insult the person who was just trying to help. They absolutely deserve to be blamed for the results of their choices.
You can revert a merge commit by providing which side of the merge is mainline:

git revert -m 1 $sha_of_the_merge_commit

That provides the "revert a commit and remove entire features" use case, assuming the original feature was all encapsulated within the merge (branch) in question. You can get the "readable commit history" with:

git log --no-merges

You can have the best of both worlds. git has had these features for as long as I can remember, but devs have had the "NO MERGES ONLY CLEAN HISTORY" platitude repeated so often they must think git lacks an alternative.
You are correct that most of us have totally lost control. This company gives me hope: https://permission.io
I disagree. What about “Experts do not decide what is and isn’t a programming language, regular people do, so if they say HTML is one, it is”?

I think it is more that there are two terminologies in different fields, just as, in botany, tomatoes and cucumbers are berries, and strawberries aren’t.
I'm still a little confused. In my mind, if I hold one surface still and rub the other surface on it, it's exactly the same as if I reversed their roles -- the surfaces shouldn't know which one is moving and which is stationary. For example, if I was sanding a block of wood, it wouldn't matter if I moved the sand paper on the wood or the wood on the sand paper.

Yet several statements in the article make it clear that my understanding is not correct (e.g. "Next, the Green plate acts as the control and the Red plate is lapped against it," or "Next, the Green and Blue plates are lapped against each other in an alternating manner.")
Nvidia CEO Outlines Vision for ‘Age of AI’ in News-Packed GTC Kitchen Keynote
If this business is so lucrative, why isn't organized crime involved? It seems like a field where they have a number of comparative advantages:

1. Good at negotiating with local businesses.
2. Good at motivating low-paid employees to handle large cash sums without pilfering.
3. They love cash businesses.
4. More tax efficient than people doing 'side hustles'.
5. Good at managing kick-backs to eg. motel staff.

My guess is that the most 'gold mine' locations are already controlled by entrenched players who defend them using a variety of legal and illegal methods - vandalism of competitors' machines, high rents, kickbacks, threats to landlords.

Then all the marginally profitable locations are competed over by amateurs who routinely lose money and get disillusioned.
The preprint Rapid, field-deployable nucleobase detection and identification using FnCas9 [1]:

> Here, we present FnCas9 Editor Linked Uniform Detection Assay (FELUDA)... At the heart of such a detection procedure lies the property of CRISPR proteins to accurately bind to target DNA or RNA, undergo conformational changes leading to cleavage of targets generating a reporter-based signal outcome.

> We then developed a pipeline to adapt FELUDA for an affinity-based fluorescent read-out system, where the amplification step generates biotinylated products which can then be immobilized on magnetic streptavidin beads.

The end-to-end process is similar to PCR and requires specialists to collect samples that are then processed by a lab.

[1] https://www.biorxiv.org/content/10.1101/2020.04.07.028167v2
I think it's more interesting on what happens to any analysis done with this incorrect data. There was a news article last week suggesting that the growth in COVID-19 cases was "levelling off" and I wonder in retrospect would this incorrect data account for such a position.

The article in question: https://www.bbc.co.uk/news/health-54387057
The "DOD of games" is just a "special case" of more generic Data Orientated design/programming.

E.g. ECS is a direct consequence of seperating data from code.

Furthermore for it to work well you normally also want #2, #3 and #4.

Sure you can build a ECS without #2,#3 and #4 but it makes it more complex.

Lastly in a ECS you split up components into many parts each having their own data and you normally want the idea behind #5 to apply to each of the parts.

EDIT: Well ok, weather #2 makes any sense at all depends on the language you use. And using a language where #2 makes no sense can be a as reasonable choice. I only would apply #2 IF it makes sense for you language of choice.
What he likely meant is that losing a low-paid job, i.e. falling back to unemployment insurance (which in Switzerland is 60% of your net salary, 67% if you have kids) in Geneva often meant that someone would be unable to afford basic needs, with drastic consequences, e.g. losing their apartment. Makes sense since they barely get by with the full salary in the first place.
With a high minimum wage this fall to 60% may mean they can get by until they are able to find another job.
There is also fast.io - from Mediafire. What i like there is their dropbox interaction. Basically your dropbox folder becomes website with few clicks.
It might not be a good investment, according to the article:

- Many of the best locations — places with heavy foot traffic, or large worker populations — are already saturated with machines.

- Some owners have to make 100+ calls before landing a decent location. In the end, they often end up paying the owner a commission of 10%-25% of gross sales to drive home the deal.

- And these figures are pre-expenses. The business comes with its share of overhead costs. For starters, ~50% of revenue goes toward the cost of items that go in the machines.

- Most vendors have seen a 10-50% dip in revenue this year due to the stressors of the pandemic.
This article presents a very good argument clean and squashed commits are important, under a click-baity title.

The ability to use git bisect effectively is one of the more important reasons to enforce a clean and readable commit history by squashing and rebasing before merge.

A history where the majority of commits doesn't even compile ("sorry, updated test value was wrong", "oops syntax error", "forgot to update these references in the last commit", "big refactor wasn't complete") is a major headache not only to readers but to anyone using automated tools such as bisect. The author here was lucky the commit history was in a good shape. The size of the offending commit was reasonable too, so any trivial commits had been squashed away here.

My personal issue with this particular commit is the useless commit message. "Extract CreateTokenValidationParameters method". Well, obviously. But why? What was this intended to result in? Why was particular change made and not something else?

A more suitable commit message would have included something along the lines of "JwtSecurityTokenHandler methods belong conceptually with other code that configures JWT parameters. Break them out to CreateTokenValidationParameters because ..", that would have make much more sense and made the change easier to understand for someone else!

After all, this is how the author describes the patch, when taking the time to do so in order to write a blog post. It isn't that hard.
3000 is a steal for a quality prototype you can build on, stop being a miser and pay your friend out.
You could also see this as a form of single point of truth.
> A pod exists but is less common.

It may be less common, but it's where Kubernetes got its term 'pod.' Docker's mascot is a whale, Kubernetes manages groups of related Docker containers … pod!
Well, you know, except for all the people not getting the virus due to reduced transmission.

But yes, when distribution networks are stressed, bigger players will obviously have more pull and smaller businesses will have more trouble getting in what they need and/or delivering their products, at anything beyond a very local scale.
Why the capitalist part?
Where's the Vorlon planet killer?
Definitely not ice. Rub your hand on an icy pond. It's very bumpy.
Education’s Shameful State of the Art
I would say the authentication app is becoming mandatory, not the banking apps.

It is perfectly possible to use the website but authorize with the app. Which I admit does not solve the problem at hand
How to Cope When Everything Feels Bad and Somehow It Keeps Getting Worse
I agree these are the correct questions to ask. This company has very promising white papers that answer many of them: https://permission.io
Also, check out Robin Renzetti, (here he is lapping a surface plate: https://www.youtube.com/watch?v=6nY7uW1uG9s). Lacks the entertainment and dad jokes of ToT, but is an absolute genius. Absolutely amazing attention to detail. Top Lipton has a lot of good videos too, and has written a couple of books.
That form of broken legal system is, as far as I know, peculiar to the USA. In most of the world, businesses aren't allowed to arbitrarily negate laws specifically created to protect their customers just by including some weasel words in the fine print. In fact, here in the UK and at least across much of Europe, businesses are required to actively inform their customers of various rights and other details, and failing to do so can have significant consequences.
A few basic invariants about how your code is structured does a lot more than it being excessively "generic". Writing simple components that actually adhere to the single-responsibility principle (and composing them into more complex logic) doesn't just help out the mysterious future. It makes your existing codebase easier to understand and to validate up front.
How was CloudFlare set up on the workers and CDN side? If it’s not set to cache everything, the origin server will still need to be contacted, and each edge will need to contact the origin when the cache expires (which is defaulted to 4 hours). This feels like it’s configuration related. CF is very fast in my experience, but I haven’t done similar tests so I can’t know for sure.
My first Linux was Slackware 2.0, which I got via the first edition of Linux Unleashed book, and it had a big sticker bragging about being the first Slackware release with elf support.

I shared your Trident woes, having a Trident 9000, couldn't set it beyond 640x480, whereas I was already on 800x600 on Windows 95, on a 14" monitor.
My bank had just notified me that starting Jan 2021, I won't be able to use my bank card without a smartphone app for online purchases inside the EU.

This software arrived just in time.
The World Is Ending. Should I Just Pray?
The New Normal in Cybersecurity Management
> and go for hydrogen fuel

There are almost fewer cars running on hydrogen on the road right now than there are F1 cars on the grid (only half joking), and while many mainstream manufacturers have made prototypes and concept cars even before they did anything pure electric, pretty much all of them have real full-electric products in their lineup, or at leat in the pipeline. There are some hydrogen pilot projects, sure, but I can't go to a dealer right now and order one. So going for hydrogen would be a really bad move, also because its energy density is inferior. The current ICE units in F1 are already at the upper-limit of possible efficiency, so replacing it with a fuel with a lower energy-density will be a step back in performance, with little or no future path to real improvements they don't have right now.

I'm an F1 fan, but I see that it is on a dead-end, one-way street. It'll take a while to reach the end, and as long as there's not a superior technology which can beat it on it's own grounds, it's not going away.

The "only" thing standing in the way of electric race-cars beating them is energy storage, which I expect to be improved at a break-neck speed in the coming years. FE has the advantage that this is the exact same problem affecting road-cars, which is why you see quite a few mainstream brands being attracted to it right now. But the energy density of oil-based fuels will be hard to beat, it will take a while before an FE car can beat an F1 car in every situation. But I'm excited for when this happens, since right now, FE fails to capture my interest for multiple reasons. There is no track-overview, all look pretty much the same to me, there are no iconic locations. Next year they'll finally be using the full Monaco circuit, which is a good start, and currently one of the very few viable F1 tracks for FE, but they have a long way to go.
This is very much like database normalization, in that it has the benefit of making invalid data impossible, but the drawback of often making queries into the data much more cumbersome and usually also inefficient.

As with database normalization, it is a good idea to first do it as much as possible, and then denormalize again until it is fast enough.
> I think people responsible here are still the ones that decided to buy it. They are responsible the market exists. Also not a mystery since those people are mostly evaluated by how many people they put behind bars.

That's letting the people selling (and producing) the snake-oil off the hook, which I'm not willing to do that easily.

If you know what you're making is at best making lemonade out of statistical noise, or at worst actively harming people and society, and it's being marketed as an intelligent system that gets results, well then you bear a big chunk of that moral responsibility.
I totally agree with "data should be creatable without explicitly doing any function calls, variable assignments or similar."

Could you explain what you mean by "Creation must not depend on implicitly captured data"?
Principle #2 always bothers me.

"Model the data part of the entities of your application using generic data structures (mostly maps and arrays)."

and example

function createAuthorData(firstName, lastName, books) {
return {firstName: firstName, lastName: lastName, books: books};
}

For a simple, obvious object like "person" it might work, but for a complicated domain object with many other composed objects this starts to be a pain.

I am not feeling ready to memorize all the field names, I prefer to have an object with documentation for each field.
I squash most feature PRs, but this is into a dev/qa branch initially. This is later merged into the actual release branch where we obviously want to maintain each of the individual commits.

Reason for the feature squash: most of the context of the original commit(s) are meaningful only to the original dev who is free to keep that history locally (or share with others). There are time's it's convenient to structure the commits in a certain way, but this is often most useful at PR review time, and less so after merge.

Granted, you may want to be able to re0review code at a later date, and hence keep that structure, but hopefully this is a rare case, and PRs and not often so huge.
My BIOS is J06 04/04/2019, iLO firmware 2.70 May 07 2019.

Latest B120i driver was released at 30 Apr 2020. I don't think it's retired yet, but they don't support RHEL 8, so I'm forced to stay on RHEL 7.

I can see that iLO firmware is not latest, but it's BIOS who's responsible for fan speed control and I think that I'm running latest BIOS.

That's not really about BIOS versions. When HDD runs under B120i fakeraid mode, server is aware about HDD temperature which is displayed in iLO. As long as this temperature is low, fans stay low. When HDD runs under AHCI mode, server is not aware about HDD temperature anymore, so it uses high fan speed to ensure that cooling is good enough even if drives are hot. That's how I interpret this whole situation.
This. It is a stunningly beautiful city. It is also right by the Mediterranean.
If this thing can run even just the Xcode command-line utilities, it'd be a huge asset for cross-platform projects, build automation, etc. Definitely keeping an eye on this!
Dine is not an emulator?
Summary: the script shows advertisement, and adds a 4 second delay after that.

But the tweet is actually incorrect. setTimeout call does not use any "computation time" (or "cpu time" or "userspace time"). It does waste wall-clock time, but CPU can do other things at that time. As long as your machine has other things to do, nothing is wasted.
I personally really dislike merge commits because it makes the tree really difficult to follow in most visualizations. If I'm trying to follow the main branch only to a certain point the graph is polluted with all the "WIP" side branch commits between head and the commit I end up getting to.

It also defaults to causing the main to have a ton of commits with "Merged from XXXX branch" as the summary lines when that's not nearly descriptive enough to quickly find what type of commit I may be looking for.
If you're referring to Perl 6 versus Perl 5: that problem has been fixed by renaming Perl 6 to Raku (https://raku.org using the #rakulang tag on social media).
> the facility put a moratorium on late fees in April due to the COVID-19 pandemic

They probably hoped for such an occasion for a decade or two.
I'm not sure I'd refer to crows, a murder of or a flock of, in a beginner's textbook on the English language. I don't think crows are commonplace enough in every day conversation to justify their inclusion.

If I was needing to refer to a group of crows in this textbook then I'd refer to them by their proper collective noun, a murder of, because that would be correct.
There is nowhere you can take your money that doesn't force you to accept the same abusive terms of service. They all pay lawyers to write this stuff and they all come up with the same self-serving clauses. Once you've read one of these documents, you've pretty much read them all.

What they say is basically:

> you have no rights

> you promise not to try and exercise any right you think you have

> you will not do anything the company doesn't like

> the company can do anything whether you like it or not

> the company is not responsible for anything ever

> we make no guarantees about anything
$5k in AWS, Airtable and Notion credits
'The days of the salad bar are gone for the foreseeable future'