skysight-inc/HackerNews huggingface dataset:
Kids aren't born at that age. It takes 9 years. How are the little ones supposed to travel?

At one time, mine were these ages: 8, 6, 4, 2, 2, 0

Doing that on the subway would be nuts.

I actually know somebody who, as a kid, got off the subway at the wrong stop. That really happens. The crowd seems to be leaving, the kid goes, and before the parents can react the subway is moving again.

Activities need not revolve around consumerism. Find a less-densely populated area, and there will be wild space like forests and streams. Backyards can be pretty big too. Consumerism is more of a city thing, since there is no backyard and no forest.
Future-Proof High-Performance Microservice Applications with InMemory Technology
Author of the essay here -- I know they say you shouldn't read the comments, but the discussion on here was so thoughtful I just had to create and account and jump in.

Two thoughts to this convo:

1. One thing it took a few years of living in Europe to learn is that what seems like a logical way to learn or convey information is also -- at least partially -- cultural. I'm an experience first kind of gal -- and I judge theories by how well they explain experience. I also think it's a better way to communicate. But here in Europe the standard way of giving, say, a presentation is to begin with all the theory, definitions, concepts, and only then move on to case studies.

It was when I read Erin Meyer's The Culture Map that the whole thing clicked for me. I think it's worth reading the whole book, but here's a quick summary: https://www.mdttraining.vn/post/on-our-bookshelf-the-cultura...

One of her axes of comparison is "principles first vs applications first." It helped me to realise that my preference for applications first was also due to spending all my formative years in North America, being taught this way, consuming media structured this way, and so on.

2. I actually finally bought Salt Fat Acid Heat this spring, started reading it, and just the chapter on salt has already begun making a difference in my cooking. I do think cooking proves you can do something badly, every day, for an entire lifetime, if you don't either get some better theory or carry out a lot of experimentation and remember what works.

However... the reason I bought the Nosrat book was that I was starting to be inspired by cooking again, and what motivated me in that end was the Ramsay course! It gave me that sense of exploration and play again. So I think it's worth paying attention to what increases motivation, especially with something that can become quite a dull chore.
Isn't that the right answer though?
His job isn't to claim that his client is innocent. His to make the government prove the client's guilt beyond a reasonable doubt.

If we don't require that from the government, the entire justice system breaks down.[1] Because once the government stops being rigorous about its methods for convicting guilty people, it can trivially start convicting innocent people.

[1] Which it largely has, given the ratio of criminal convictions that get plead out, as opposed to being litigated. Plea bargains are a blight upon justice.
Doesn’t that go without saying? It’s AI. It does not have ethics.
Or you could just, like, not watch/read those videos/posts/tweets if you don't like them?

Also, there's a lot more academic fields than the "hard" sciences and vocational stuff.
I don't think Time Machine does, everything I've seen is local to the machine or across your local network.
The problem of deleting stuff from a history of changes is challenging. But I think Darcs, the distributed version control system written in Haskell, does this rather neatly.

Darcs is different from git in that a "commit" (called a "patch" in Darcs lingo) does not depend upon the entire history of what has come before. Rather it has specified dependencies, which Darcs can infer itself – or you can specify if you want more semantic content in the patch structure.

A repository is a collection of patches, which are merged using something called patch algebra. So, if you want to delete a patch, you just issue the command "darcs obliterate" and it will remove the patch, and anything which depends on it. Then working directory is reconstructed by merging together any loose ends using patch algebra.

With careful administration of dependencies, this approach makes deleting specific things very slick.
The new mkl_serv_intel_cpu_true() function seems to have been known since Agner Fog's 2019 update. I am quite surprised that no changes to the feature indicator was needed though.

If you are publishing an application, I still recommend using the intel_dispatch_patch.zip.
It is a truth universally acknowledged, that the more of a system you open up to customization via plugins/extensions/add-ons, the more damage a malicious plugin/extension/add-on can do. So, sorry, suck it up: extensions will be limited and restricted, especially in as security-critical a program as a browser. But note that, say, programmers' text editors suffer from the same issue. How many of you Emacs users download entire distributions of packages for Emacs without even thinking about it? Have you audited them all? If it can be loaded into Emacs, it basically has arbitrary access to the entire session, and anything your uid has permission to access. We've already seen several malicious npm packages... all it takes is one strategic MELPA bomb and Emacs may not be able to recover from the black eye to its already diminished reputation.

Contrast that with Visual Studio Code, which has a restricted, well-defined API extensions may use.

Oh, and the other thing about restricted, well-defined APIs? You're not locked into your present architecture. You can rewrite the entire code base, and all extensions will Just Work provided you reimplement the extension API. Extensions in the Emacs paradigm of having all system internals exposed to them will break the moment those internals change.

Restricted, well-defined APIs are system design 101.
> Negotiation is not really an option on the table, the last time one of the other volunteers responded at all we got a ~150Gbps volumetric attack

that's hilarious, have you tried trolling them back like just enjoying their company? start saying pool's closed and things like that
Sure, you could also fork all of GCC as part of your frontend. That's still a massive undertaking compared to a framework that's designed to be used as a library.
Even if it did, all software has bugs...
Is this a joke? Just wanted to check because my own shocking results show that we're urinating all over ourselves and without doubt many droplets reach those on neighboring urinals. I bought a nice pair of wool designer shorts by D.gnak $250 and for whatever reason they have the incredible property of causing water to bead up in a way I've never seen before. While wearing them one day, I went to wash my hands and realized I was covered in 20-30 beads of liquid. Yes after using the urinal. I was horrified, soaped up a paper towel and cleaned it. I thought it was a one off event but soon realized it is IMPOSSIBLE no matter how carefully, softly, and at what angle one fires at the urinal to actually get less than 20 beads of pee on oneself. I tried for months, shocked every time. With any other type of clothing the beads don't form but the same liquid is instead instantly absorbed into the fibers.
I would say exactly the opposite : cliffhangers and cheap thrills are the stuff the Da Vinci Code, Tom Clancy novels and all your best selling page turners are made of.

Literary prize winning fiction has been what you could call post narrative since (at least) the Nouveau Roman.
It just says that "some scenarios present ethical issues". And follows by saying that their business model want's to mitigate those risks as to not experience brand or reputational harm.

I feel like the title is just click bait...
This looks really impressive, and I don't want to take anything away from the quality of the code itself here, but I feel like I have to point out that this repo is a school book example of how commit messages should not look:

- "update" https://github.com/cleardusk/3DDFA_V2/commit/a339c36d795b4d6...

- "some updates" https://github.com/cleardusk/3DDFA_V2/commit/a8cab53dbaa87d1... (license change mixed with code)

This is an easy pattern to fall into when you're the only one in the project, I've been there myself, because you feel like "it doesn't matter, this isn't quite done yet anyway, and noone else will read it".

Well, here's the point:

- "Someone else" may very well be yourself a few months from now. Don't avoid good git practice, you're shooting yourself in the foot.

- Even if noone will read it now, someone may read it way down the line, when that one line you changed caused a really annoying bug. Imagine the feeling when the commit has no information on why the change was made. Commit messages are mandatory for a reason.

- If commit messages are not atomic and mix different files that aren't logically related, understanding what was done will be extremely hard, even for yourself looking back.

There are many guides available online on how to write good commit messages, I won't point out a single one of them as I don't feel one is authoritative over all others.

I'd also like to point out that this is something you need to know if you're ever going to collaborate on software projects, so learning it now is as good as a time as any.
I didn't have space for this in the essay, but the mechanical egg also plays "The Final Countdown" when the eggs are supposed to be hard boiled.

It's honestly not a great way to cook eggs, but don't underestimate the joy of hearing those opening notes in the morning...
Being some form of "intelligence" may mean for some people to have ethics, I suppose.
I don't see how GCC (or copyleft in general) would help here. If they don't do the work cause they don't need it there's nothing to release.
TLDR (kind of)

* Using alpha/beta decay in a diamond structure to generate electricity in the battery

* Utilizing nuclear waste in the process

* They say the battery is safe for civil use (e.g. not limited to military/industrial use)

* About the same price as a LiIon battery for a Tesla (~$9K)

* However, it recharges itself and shall last for decades !

* They want to do a pay as you go sales, but also extract revenue for the utilization of nuclear waste.

* Done with the PoC. Doing a commercial prototype. Outlook is ~2y time to market.

* Targeting the UPS market at big cloud datacenters as a first customer

* They say technology works from nano scale (bots) to cars and industrial applications. However military/industrial could be first large deployments (no need to comply with same regulations)
I'm just a user, but I really wish the web team had waited a bit longer to push it out. Not having any of the UI related about:config options available is really unfortunate.

Stable just feels unfinished in its current state, I'm not sure about Nightly. I prefer my browser to not surprise me with much of anything, so I prefer not to be on the bleeding edge.
I would be fairly surprised if any current AI would have an ethical framework to evaluate its own actions or even any formalized rule system that comes close.

So they warn that decisions by AI should be reviewed, they write "Some AI scenarios present ethical issues". Maybe just to protect themselves they state the obvious.

Looking into the future I could imagine misbehavior to be blamed on AI. Having a handler in such cases might be a good idea, otherwise we might see a lot of cases where people try to shed responsibility.
> Lawyers wouldn't have the reputation they do if all the members of the club had integrity.

Some anecdotes:

- A company I started, hired a big-brand SV legal firm, super expensive. We thought they would be great. But we were so little to them, it was sometimes even hard to get a timely response. In the end we stopped using them, but not before we signed a bunch of documents they reviewed and told us were fine to sign, when in reality those contracts left us fatally exposed (and were in great part responsible for the downfall of the company later).

- Had a complaint filed against me personally earlier this year. The complaint has some truths twisted to paint a mostly false story, but it also has plenty of lies and omissions. The lawyer(s) that wrote the complaint knew what they were doing, yet no one is ever going to get punished for it.

- Looking for lawyers to defend the case (and in previous experiences), I realized that most lawyers have certain formulas or patterns they follow for specific types of situations that they already know how to address, if you don't fall into those, then they'll either pretty much fail at the job, not do what they actually should do (sometimes even if you ask them directly), or just refuse you as a client. It is very hard to find a lawyer that will actually take the time to really listen to you, understand your story/situation and then work on a personalized strategy/solution.

I think that any lawyer that intentionally mis-represents stuff in their work, or tries to shoehorn their clients into their formulas, or just half-asses their job, are seriously lacking in integrity. And by my experience, this seems to be the case for 50%+ of lawyers. A lot of them will probably do a ton of damage both to their clients and their counterparties, and they will never be held responsible.
When will Artificial Intelligence surpass us? A review of recent progress in AI
> Python -m venv in your project directory. Then source ./bin/activate.

And how do I do that from inside an already running Emacs session? (Or Vscode?)

Needing to "prepare" an environment before you can work with it, prevents you from simply "jumping" into a task from an existing workflow.

Working with .NET, Rust, Node, go, Haskell, etc... I have no such issues.

This "venv"-requirement only applies to Python, and it's really the opposite of ergonomic. I really think it's about time the Python-community starts recognizing this.
Aerosols are basically floating particles with virus, which is not airborne, but still carries the virus a lot further.
Absolutely. I usually email them a cheque with a note of the instances I've spun up.
Alas https://github.com/attic-labs/noms#status :(

> Status
> Nobody is working on this right now. You shouldn't rely on it unless you're willing to take over development yourself.
Mortality rate in older folks is terrible, and needs to be managed, but it can be managed.

Yeah...I keep seeing this handwave from the "I should be able to do whatever I want" crowd. How exactly can it be managed? Basically it's "if you have any possible risk factor, you should lock yourself away so me and my friends aren't inconvenienced by your existence". Ignoring the fact (and the associated abdication of responsibility) that there's no established risk assessment beyond "if you're an oldster, stay home", and it's not clear why the many otherwise low risk are getting sick and dying. They are apparently the cost of partying on weekends.
It appears you're actually both on the same page, you didn't say the opposite.

He's saying the common fiction including best sellers are generally predictable. And literary novels being less so.
Presumably Google are making quite a bit more on that traffic. Apple might just be eyeing those additional profits.
At the same time, when I think "appliance" I think something like a toaster. Push down the lever and the wire gets hot. Dead simple, nothing hidden or artifically withheld from the user. But that's not what modern appliances look like; we're getting ever closer to the future described in "Unauthorized Bread".

As Strong Bad might say, we have too much appliance in our computers, and too much computer in our appliances.
I also have one of these still. They're still pretty common I think. I also think my dog has one that look similar :)
Nice, thanks for the recommendation!

The book is freely available online at https://nlp.stanford.edu/IR-book/information-retrieval-book....
Hmmm... this has me wondering. I've been writing about teaching and learning for a while (my dissertation and book were on the topic in the early Middle Ages). MasterClass has only been around for five years though, and the Wintour course came online last year. It's possible there were review pieces out. I did do a bunch of searching on MasterClass last year, because I was tempted by it but found it a bit pricey and wanted to know if there was any substance to the courses. Most of what I found were very brief reviews though.
I'd argue that the fundamental block is that it's not human, period.
Borges and God
It should be somehow made possible to reverse transactions (like theft) with some sort of distributed consensus.
I think the maintainers thought this is only Debian/Ubuntu problem, but in reality, it affects a lot of other systems. Fedora, Conda distributions seem to have been affected too.
If you read Agner Fog's old "Cripple AMD" thread from 2009, when he actually served as a FTC witness, you will see that his later updates in 2010-11 shows no reduction in behavior of this kind on Intel's side. If Intel were to comply, this would've been a solved problem.

What we are seeing has to be a new deal.
so what's the alternative? build houses right on top of factories? pact stile mass transit with strict worker<>factory allocation?

there's zero chance mass transit can accommodate people's needs, even if you somehow solve the shopping issue with local markets and fixed item prices, the job<>house graph will always look like a fractal set of overlapping stars.

cars is one of the most important social equalizer of this and last century. it allows people from basically all social status to move themselves, their family and their belongings at any time in full autonomy, enabling them to find houses and jobs in the most economical and convenient places.

private cars win over public transit because it's a better product. the only way for public transit to compete is to mandate laws to make cars comparatively a worse product, which is fundamentally anticompetitive - once public transit become monopolistic, once the company owns a tract, they can abuse their position deciding pricing and timetables.

even in traffic, private cars offer a better experience: people are in their own space, under a roof from start to finish, with their preferred temperature and away from both obnoxious or influenced people.

forcing mass transit trough legislation will surely have some short term benefits, but also:

- more class divide between the richs, that will always be able to afford a car, and the poors who won't

- massive gentrification of well connected areas, while the poors get pushed out to where service is of less quality

- dependency of the poors to expensive third party services on any occasion they need to move themselves or their goods across a non serviced destination. rentals is not an option: rentals need a credit card, and guess who don't own one?

- dependency on public transit times. have an unusual work shift or need to visit parents? get prepared to wait in the open under the cold or rain. need to get your child out of school in a down hour because he's suddenly ill? too bad, transit only gives peak service at peak hours.

of course there's situation where mass transit gets convenient, like large cities where a significant percentage of the population shares the same source/destination points, at which point people will use it naturally on their own.

opposing private transit is going to destroy an important achievement of modern society, the car has been a great economical equalizer and still is. market, after all, need customer flexibility not to be captured. pollution is something to be solved with more efficient cars and better technology all around.

it'd be like discovering tomorrow that soap pollutes: some will want to force everyone to smell, some will create a better soap.
Heaven forbid the useds have to wait a little bit for someone else for someone to do something for them! Must be placated, must be pleased, must be coddled at all costs!
Doctors are encouraged to communicate with certainty. Breeds? Selects? For arrogance. Other professions apperciate and display uncertainty. Most scientists speak of confidence intervals.
Danish system is called Sundhedsplatformen, for Capital + Sealand regions. Powered by Epic.

From what I've read it seems that most of the users are very unhappy about it (https://www.dr.dk/nyheder/regionale/sjaelland/ud-af-tre-laeg...) and crucial integrations to outside systems (like Medicine Card) still don't work properly after 4 years (https://www.dr.dk/nyheder/regionale/hovedstadsomraadet/ny-br...)
Firefox is struggling due to the borderline legally liable gross mismanagement of their executive leadership. How are any of these people allowed to be in control of, sadly what was, such an important piece of the open web?

Mind blowing all of them do not resign out of shame and humiliation.
Almost all the water problems are due to agribusiness usage.

If you reduced all consumer usage of water to zero, it would barely make a dent.

California can solve its consumer water problems with a couple of desalinization plants. Farming in the Central Valley, however, would basically need to be shut down to stop draining the aquifers.
Or Heinlein’s “Shipstones.”
Have you compared them to Google counterparts? There's really no comparison.
After parsing the sibling threads, in this case there were only 4 distinct answers:

- Python -m venv + ./bin/activate + pip

- poetry

- pipenv

- pip (without isolation of projects)

You may add varying recommandations on the usage of OS python or a user installed one, but I think the same concern exists with most languages.

The main problem is that Python's mantra is supposed to be "There is only one way to do it". Less than two years ago, I read the official PEP doc about "Managing Application Dependencies", and it was a mess. pipenv was recommended (and still is), but there was a critical bug that ended in fatal errors on my development system.
A major portion of an S-1 is outlining every possible thing you think could possibly go wrong, so that someone can't sue you later for something going wrong you didn't warn them about.

Given that, there's no incentive to calibrate these risks to real world probability (and sincerely, given the dual purpose of such a document, there shouldn't be), there's a lot of pretty wild possibilities included in S-1 filings. Although, just for fun, I just skimmed Uber's and they failed to acknowledge that an airborne illness resulting in a global pandemic could dramatically reduce their bookings and cause serious long term structural harm to their business. Maybe I should sue...
I'm not (yet?) a kernel dev; I haven't ever contributed to any OS project, but I'd like to start with the pinephone.
I'm curious: why using Nitter instead of Twitter for the links? It seems content is replicated from Twitter: https://nitter.net/tsimonite/status/1298711894241366019 / https://twitter.com/tsimonite/status/1298711894241366019
According to this person there is plenty of research saying you should tell them how to do it

https://www.youtube.com/watch?v=g1ib43q3uXQ

I think she makes a good point. We don't hand people a guitar and say "figure it out on your own". Cooking shows don't generally show the final dish and say "if you want to make this yourself figure it out on your own".

You might say computer programming is different but I suspect for most people here you were taught things like sorting algorithms, database queries, lexers and parsing algorithms, etc. You were not made to figure them on your own. Sure maybe you were self motivated and looked up the topics by yourself but likely you mostly learned by looking at existing code and over time figured out how to see what it was doing and how to modify it or apply the same ideas.
"If you have any possible risk factor, you should lock yourself away so me and my friends aren't inconvenienced by your existence" is how quarantines have worked for hundreds of years.