skysight-inc/HackerNews huggingface dataset:
Indeed. Let's start by getting rid of the welfare state and bringing back the greatest incentive to child-bearing... care in old age.

I'm serious. One thing I often see is complaints that the younger generation (typically millenials) are not pulling up their end of the bargain. However, neither are their parents. Typically, one would expect to become a grandparent that cares for their grandchildren. In return, your children take care of you. This is how humans have lived for generations. Yet, today, seniorhood is treated as a second adolescence. Grandparents neglect their grandchildren while parents are forced to do it all, so to speak. It's no wonder they have no time for kids.

Human childbearing is exceptionally hard. It's why human males take part in the child-raising typically (women with committed men have more children on average and shorter spacing between pregnancies). Moreover, it's why natural selection has typically brought about kin groups that care for children. Social security is an affront to this entire arrangement. There's a balance to be struct between guaranteeing no one is destitute and not shifting expectations of the elderly to the point where living purely for themselves is actually considered acceptable.
Backup team of the Cowboys (or any NFL team) would absolutely destroy Brady and a high school team.
Immediately reminded me of a similar term for something slightly different, from about 15 years back - Ambient Intimacy.
https://www.disambiguity.com/ambient-intimacy/
In the end, this is hurting equality.

Clearly, Claudine Gay does not represent academic excellence. She is personifying the 'diversity hire' and providing a true-life example that will set equality back decades.

Harvard can and should do much better.

It's time to do the right thing, fire Claudine Gay and find a worthy replacement.
> India

This is an extremely bad idea.

It's hard to imagine two cultures less compatible. Indians would have a very rough time in Japan -- imagine being effectively ostracized and forever unable to integrate into society (and not only yourself, but also your descendants!) -- and the average Japanese won't last 10 minutes in India without having a nervous breakdown on account of unsanitary conditions, lack of personal space, interpersonal aggression, etc.
I live in a very dense area of the US midwest (still single family homes, but shotgun style houses) and I see a lot more young people and parents! I think it’s the density and walkability. I’m told Japan is really good at both of those things.
Interesting. What are the motivations behind this funding? What is to gain?

As far as i can see there is quite a lot of "quantum safe" encryption so what kind of historical data exists lying around with lots of value?
Two kids 5 and 7. Where are you finding the content? I don't think it aired when I was a kid, and I don't think it's on Disney Plus.
How do you actually quantify sentiment?
I was prioritising for taking less time total, but you’re right, that doesn’t matter if the person gets bored and leaves. I’m tinkering with it now and I think I have a good solution to the problem. I’ll be deploying it soon!
The One Billion Row Challenge
> Demographic collapse in advanced nations is an existential threat to our civilization

Explain why.
You comment shows that you have no practical knowledge of the web ecosystem, and everything you know about it comes from all the blog articles that contributes nothing that's useful in real world use. The reality is that web is fast enough (even with all the tweaks and different approaches of frameworks, libraries etc), and it is the first choice for building a new cross-platform product and for migrating legacy projects. It makes all the business sense as well. Your pedantic arguments are not going to reverse that trend.
I’m curious what your pics for best Frasier episodes are?

Two of mine are when they become illegal caviar dealers and when Niles wants to try weed. The episodes with Lilith tend to also be very good. People love the Valentine’s Day one, but I'm never a fan of that style of episode. I can appreciate the genius in it though
"Superstars are why I don’t try harder and am less engaged. They take all of the interesting ownership and inject themselves into every process and space for communication. I wait for these people to burn out and want to actually be a team member instead of a productivity bully hoarding opportunity for themselves."

Are you sure you've got a "superstar" there?

I think the term ought to be reserved for people who truly do a lot of good work, and not the many varieties of people who manage to make it look like they're doing lots of good work. Which absolutely exist, and need terminology to talk about them, and sharing strategies to deal with them is a good thing to do. But while I'm sure there's a non-zero set of people who are both superstars and very good at giving the appearance of doing a lot of work and being very political about it, I doubt there are many. That's a very particular order off the metaphorical menu of attributes.

I would expect a real superstar to be happy to find that you can carry a meaningful portion of the load. There is always more work to do than can be done. Being able to not do some of it allows them to focus somewhere else.
>but in my opinion there is a tight relationship between population density and the housing market

there are entire towns in Japan with empty houses, the problem is globalization which resulted in jobs being centralized in a handful of cities in developed nations and everything else getting outsourced. Governments embracing and encouraging remote work to help spread people out would be a better solution to housing problems
Spent 5 minutes trying to figure out where field_name is in the second list... I thought it was the same commits rewritten to be more scannable, but they are from a different project.

(I scanned, naturally, the article itself!)

Or more generally, I thought the point of the article would be that the function / variable names from the first list would be moved to the beginning of sentences. But in the 2nd example they are completely absent, favoring much vaguer / high level descriptions. So we are unable to see the before/after effect for the same list of commits, I think most of the potential impact of the author's intended point is lost.

(Also, the first half extolls the virtues of being able to read quickly, while the second half tells you to use longer sentences for everything for apparently no reason?)
These are all around the country (we went to Fukuoka Citizen’s Disaster Prevention Center for example, during our 2019 trip) & I can highly recommend visiting one of them - it can be very informative and might even save your or someone elses life!
I'd assume this doesn't work too well with shows that aren't episodic in nature. Especially if you binge watch, the line between when one episode ends and the next starts is usually blurred.
I did something similar, in fact, the math may be the same thing and just expressed differently. But when I've had to rank non-transitive things, I use Elo (https://en.wikipedia.org/wiki/Elo_rating_system)

Many years ago when I was a mid-level developer at a dysfunctional company, I was senior enough to be invited to some "strategy" meetings, but junior enough that no one ever listened to me. We (engineering, sales, marketing, etc.) spent nearly an entire summer bickering over what "important" features we were going to schedule next. I finally got fed up, took everything out of the ticketing system and made random parings and had people vote on it. Then just like a chess match, updated their Elo score based on the outcome. Then I had anyone who cared play match-ups for as long as they wanted. We ended up getting a decent ordering of features and finally ended the summer of hell meetings.

I don't know if the order was the correct order, I didn't stay around long enough to see. I was just happy that sales and marketing folks thought that I had some magic math that solved their problem, and I was happy to be back developing and not sitting in useless meetings.

What I like about this is that you don't have to be self consistent, as long as on average you pick the best, it will bubble to the top. And you can mix the results of other voters and see what the "true" winner is. (Of course, to be fair, you have to give each person the same number of match ups, in my case, I just served match-ups to anyone who wanted to sit at the terminal and vote, so someone could have wasted an entire day and overwhelm the system - I didn't care at the time).
I agree. Every single time I a new tool that’s written in Java, I sigh. Just… why? I understand old legacy enterprise stuff, but new things??
> My question at those times is less about "what" and more about "why". Why was this change made?

Isn't the essence of the commit message body to delve into the 'why'?

The ability to swiftly glean the 'what' from the commit subject line aids in identifying the appropriate commit for review. The commit message body can then have a detailed explanation of the reasons behind the change.
Japan has massive amounts of unused land - take the train 45 minutes in any direction from Tokyo to see it.
What I wonder is how you are able to formulate all that, quite eloquently, without thinking with words. It seems that words come into play at some level, and then it’s unclear to me what the qualitative difference is to how I internally experience my thinking.
but so are 32-bit pointers for most applications

The address space of 16 bit pointers is only 64KB so I can understand 32 bit for pointers as well as math use in some cases. But the need to exceed a 4 GB/32bit address space for "embedded" is extremely rare at this time..
I personally prefer conventional commits.

https://www.conventionalcommits.org/en/v1.0.0/

The subject line says what the purpose of the change is (CI/CD, tests, bug fix, new feauture), what component it primarily focuses on, and then a plain text one line summary.

For example:

ci(GitLab): Add rust build directory to cache

This should improve build times by caching most of the compile tree between builds. In testing, I’ve observed builds drop from 2m to 30s when scheduled on a node with a primed cache.

It also forces me to keep my commits focused. If I can’t create a one line summary of what I’ve done, it probably needs to be broken up into multiple commits.
I think merge sort would provide a better experience.

Quicksort can be great for human-comparison sorting if you let the user pick the pivot, and if you have a direct-manipulation interface for dividing a big pile into two smaller ones. Humans are great a scanning large numbers of objects, and can split piles much faster than operating one by one.
I'd say I look at commits ~weekly, especially when trying to understand 'WTF did he do that?' - context of tracing the commits (and offtimes back to individual PR when commit is poorly formatted) is valuable.
That was a Canadian. It was coined by Jordan Peterson in 12 Rules for Life.

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

> Jordan Bernt Peterson (born 12 June 1962) is a Canadian psychologist, author, and media commentator.
It's a testament to how large media interests have totally dominated our copyright system that people are so excited about this completely worthless, 100 year old, antiquated garbage being released into the public domain is considered a big deal. The entire Disney canon would be in the public domain if the duration of copyright hadn't been extended again and again and again and again.

It is 95 (up to 120) years after creation or the death of the author plus 70 years. This is absolutely absurd and serves no public interest. It only serves to benefit huge media companies that have purchased our entire shared heritage's back-catalog and survive largely by leasing it back to us over and over and over.
> Please, don't guess at performance.

I don't.

> My biggest learning about performance is that developers don't know how to measure it.

So have you measured it and compared it to anything else? Judging by the fact that you think that "JS is fast" has something to do with rendering and layout, my guess is that you haven't.

> The DOM is an in-memory object accessed via a standard API.

This has nothing to do with rendering, layout, and doesn't make it fast (compared to other ways of doing UIs) in the general case.

> string parsing mechanisms, like query selectors, is several times faster than it used to be.

Again. This has literally nothing to do with either layout or rendering.

> To run your own tests see this micro-benchmark test:

I said it: "A few billion dollars of development and hundreds of thousands of man-hours have optimized it beyond any reasonable expectations, but it's still unbelievably slow because of many architectural decisions rooted back in the 90s."

> To run your own tests see this micro-benchmark test: https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc

Oh wow, you can select elements quickly. What does this have to do with the actual performance of things that matter? Or with the rest of your claim about rendering and layout?

It's funny that you claim something about people guessing, and then use and talk about things that are completely irrelevant to your claims.
Oh indeed, but the underlying problem is broadly the same - children are a lot of hassle and expense, and in advanced nations the calculus appears to be that they aren't worth it (to each individual). We must change that calculus, or our civilization will evaporate.
Time for me to snatch musicsort.com or something. ;-)

That would honestly be fun, great call!
Not sure if you are to do any super sensitive work on the tablet or not.

But a home folder encryption rather than full disk might solve the touch input problem.
Young people need take care old people

Old people go

Young people take job

No young people bad

No young people no job
> Other than wildcard certs mentioned by sibling comments, note that this is security by obscurity in pure form. This is insecure!

I prefer defense in depth, and it starts with not having all kinds of stuff publicly visible on Shodan with zero effort required for an attacker.
> They take all of the interesting ownership

How do they get to "take" as an IC.
That's because in the United States, children and people in general are cooped up in these crazy things called 'cars'
Yeah everyone says that and stops there which is absolutely useless. Benchmarks are at least objective ways to measure something. And there are no "correct" benchmarks. Unless you have better metrics or another way to prove things, please stop repeating these meaningless words
Four of the top wrestlers come from the Isegahama sumo stable. The wrestlers of this school often take the battle name of Fuji gentleman in honor of the school master who is former Yokozuna Asahifuji.

https://en.m.wikipedia.org/wiki/Isegahama_stable_(2007)
So what defines the limit,.and what is it?
Imo as long as world overshoot day is not beyond December we definitely are.. there are other knobs and factors one could touch to shift that (e.g. our current living standards), but who wants to cut in there? Everything else is just theory, or waiting for some assumed tech to save us..
Seems like an awfully dangerous game to play imo.
I like the first concept.
The ONNX Runtime is written in C++ and it uses the GPU. And Java is certainly much faster than Python.
Well, yes, but to say that it will last means it cannot fail before then, which obviously cannot be true. Any vehicle can fail right out of the lot, so it's about when they usually fail, or how long they usually last.
I personally look more often at past commits, but I've still never really had a need to scan a list of changes like this. I really don't see the point of the advantage they're claiming, even if it's real.

What I normally do is, while investigating a tricky bug and finding some lines that don't make sense, look through history to see why those lines were introduced (to see if they fix something else), and perhaps when (to see which versions may be affected by a hard-to-reproduce bug). But that typically pinpoint a commit already, and I just need the commit message to explain why it was there.
WASD is still the most popular. These immersive control schemes are highly overated
>I don't know of an interface other than email that doesn't wrap them.

Here are some common examples:

1. GitHub's single commit view word-wraps at monitor width, not at a reasonable line length:

https://github.com/matklad/repros/commit/9351f5c91bd1d80dbcc...

The result is completely unreadable.

2. `git log` in a full-screen terminal wraps at window width, not at a readable length.

3. In VS Code in Magit, lines are not wrapped at all by default. It is possible to enable wrapping, but then they are wrapped at the screen edge, not at a readable line length. I _think_ VS Code actually has a setting to visually wrap at column, but I wasn't able to make that work.

Additionally, if you look at that commit message, you'll see that, to properly soft-wrap it, you'll need a markdown parser to recognize an indented bullet list. VS Code actually wraps that list correctly, but I expect very few other tools to do that.
I have been thinking about showing more than 2 options to help it go faster. On mobile I guess that would be quite difficult, but for people on bigger screens, yes, let them run through episodes as fast as they can.
Dirt cheap? And when combined with all the other services? Which ones do I get?
> the point is that our current social structures seem incompatible with even replacement levels of child birth.

This means our current social structures need to change. We can’t have exponential growth forever. It’s literally not possible on a planet with finite resources.

> And that is before we consider the effects of the second order transition (i.e. going from a growing population to a shrinking population). That in itself wrecks things like pension provision.

Pension provisioning will suck yes. But it’s not an “existential threat to our civilization, if not our species. As much as climate change.” You are drastically overstating the drawbacks to population decline, as evidenced by your immediate moving of the goalposts when probed.
What Will Happen in 2024
I like a style like:

codebase section: short summary

longer description if necessary

eg:
cocoaui: fix images being incorrectly aligned on high dpi displays

We were calculating the position of the image in logical pixels, but not converting that to actual display pixels for rendering.

I think it's a really nice style that makes commit messages really easy to scan in a short log, and lets you ignore commits easily that don't touch the area you're interested in
Poorer countries tend to get richer over time. And their diaspora prefers to settle in richer countries. If all populations don't level off then over-population becomes an increasing problem.

Easily exploitable resources are also finite. We are consuming non-renewables and haven't even built a renewable pipeline for the renewable sources, like solar panel or wind turbine construction.
Or we could just allow immigration?
What's tremendously useful for us to have in the commit message, is the ticket ID the work is related to in our issue management system, to the point where it is practically mandatory.

I see it as a matter of scoping communications. The issue management system includes a broader set of people than the git repo. You want the commit linked to the issue so that you can see the entire history behind the commit, including the business decisions, the designer making a call, the back and forth with QA etc. That can all be useful a year or two down the road if you want to understand why something was done a certain way.

Now there is some info about the change that perhaps only the devs would ever care about, and probably that can sit in the commit messages. That sort of happens naturally but there's not really a lot of it for us. But that seems to me to be the relevant thing from an organizational perspective, no one writes commit messages except for devs, and almost nobody except the devs reads them.
The mystery of Rails' `lib/` folder
Substack's Dilemma
What do the people posting the fakes, get out of it?
> how they'd justify the 1.5x expense.

Because of lack of benefits, don't have to go through unions to fire ect.

Same reason you pay higher on a short term apartmentlease.
I’m against any style or enforcement of style of commit messages that breaks changelog

I use git log history for changelogs with a little dressing for markdown. I could pull this from Jira but it’s worse. Stories aren’t changes.

So I understand that some folks use git log for history and care about their code style so much as to enforce commit message stylecop, it’s overkill in my world and would only cause you to have to amend your commit or write a new message on squash.
> Yes the population decline is alarming but does slowing growth really matter when you have a strong culture?

Wtf is "strong culture"? I guarantee your answer would be different than Tucker Carlson's because he never intended it to be defined. It's just a fake term he made up because, in the heads of his mindless listeners, it invokes the idea that some cultures are superior, but deliberately with no criteria to define it.
Sorry, but that is unreasonable theory vs practice.. "by my metrics the world could support 150 billion people" but we don't even manage to put 8 altogether at reasonable living standards while we dump the world into a climate catastrophe?
Why assume some tech that doesn't exist or couldn't be deployed at that scale? Even those crop yields are not sustainable long term.
The subject-first style felt grating at first, but comparing the two I found myself reading more per line than I did in the verb-first approach.

Fix skip fix skip fix skip add skip

I knew nothing at the end. The second style had me grasp more, as there were no obvious hooks to skip without knowing what had changed.

But as others have said, commit messages are a cesspool of bikeshedding and ultimately useless, unless every commit is a self-contained chunk of work which it rarely is.

On the side, I enjoyed all of this author's thoughts in the repo. Good find.
> For every child you don't have, your government will import one.

Source? In the US green cards are capped per country of origin.

> Our borders are undefended. Our coffers are open for the pillaging. We don't seem to care.

Which borders are undefended? How are our coffers open to pillaging?
> Why not just force 3D-Secure

And guess what the bank will most likely be doing to mitigate that liability shift. It's heuristics all the way down.
he didn't invent shit, he certainly didn't invent the apple ii, he didn't even invent the blue box he and woz sold! but he did force apple to do the adobe deal to ship the laserwriter even though it meant sinking a large chunk of cash into risky startup equity. i don't think apple's post-apple-2 jobs-driven trajectory in the 01980s (bringing guis, desktop publishing, vector graphics, and laser printers to the masses) can be fairly described as 'it all went to shit' in terms of jobs's goals. from the perspective of user freedom and empowerment, plausibly, and that improved dramatically when they kicked jobs out

next didn't fall to pieces. it birthed the world-wide web, then merged with apple, replacing apple's then ceo, and provided the software stack that currently powers the macintosh line, ipod, iphone, and ipad. i can understand why you would describe next as a failure if it was 01996 and we were having this conversation on compuserve or fidonet, but in retrospect it seems obvious that next was at least the second most important software firm of the 80s and early 90s
For people who don't understand what generative AI is and think it's real, the future is going to be strange and hallucinogenic.
The Friendship Problem