skysight-inc/HackerNews huggingface dataset:
Thanks! You can also filter out contributors by language and/or country: https://opensource-heroes.com/contributors. And you can even explore stats for each country: https://opensource-heroes.com/countries. And much more! There is also "Reviews" (like Google or Truspilot, but for open source).
That's part of the challenge of course, but I don't think there's any shortage of places to start. How about making sure every child has meals for school? How about making sure there are only nominal charges to get a post-secondary education like Germany, how about making sure we're drowning in units to rent as opposed to our current chronic starvation and wild-overvaluing of what having an apartment (a proxy for true freedom and individuality) means so everyone who shouldn't live together doesn't have to and indeed has an option short of murder to make that change.

Tell me when to stop hehe
Rebase essentially means "create new commits out of old commits", the original use being to "move" a set of commits from one branch to another (think of the name as meaning, to change the base these commits started from).

There's a few special cases that have their own names, a common one is when you amend a commit - to do that manually you'd make a new commit, then use interactive rebase to squash the two commits together into a new one (or, use the "fixup" command available in that tool, which is a squash that automatically picks the first commit message instead of asking for a new one).

Squash merges will squash a whole branch into a single commit, rebasing it onto the target in the process, and then fast-forward the target to the new commit. It's a tightly controlled use of rebase, and can be thought of a bit like how "for", "foreach", and "while" loops are a tightly controlled use of "goto", an abstraction built on top of a far more flexible tool.
They lost on almost all the claims - critically, any claim that would have allowed them to circumvent app store fees - so it's reasonable to simply say that they lost. The anti-steering provision was the one exception.
My 2 cents :
The only thing I know, I don't think it brings you money, are many projects like Seti At Home : https://setiathome.berkeley.edu/welcome.php
and you can choose among a long list of projects :
https://boinc.berkeley.edu/projects.php
Honestly? The JSON API they announced is the most exciting thing for me so far.
You jest, but flexibility and endurance is important for consumer cables, and except for LAN parties, Ethernet doesn't get moved much (and is much cheaper to replace).
I was just trying pandas native .to_parquet and .to_arrow() without any extra config knobs
It's pinging T-Mobile whether you're allowed to use magenta.
Except the difference was Grove vs Olsen. Both were engineers, both built great hardware, but Grove feared his competitors and his customers' fickleness while Olsen was about beating / carving off business from IBM.

In the early 80s I moved from the MIT/128 ecosystem to the Stanford/101 ecosystem and even to my business-ignorant eyes (I was still in research at the time) and though I didn't understand why for years, it was like night and day.
Sure, but I know many companies that will think it should be the other way round
It makes your git graph instagrammable.
It's not clear from reading this if "Apple developers" are developers who work for Apple, or developers who write software for Apple systems.
It doesn't. Reflog still exists.
Basically equivalent to that. This was about a decade ago.

We had 4 teams, each released on a schedule. Each team had a branch. When a team released, it was merged from master, then each team pulled. The person who did the pull would change, and it was often a rebase.

So my team released, some other team rebased badly. There would be no sign of problems for us until after they released. But since 2 teams generally released at once, and people didn't remember who actually did the merge a few weeks earlier, it was hard to figure out who was actually messing up. (I had suspicions, but no proof.)

I've seen rebase used appropriately since. But that disaster left scar tissue.
Unfollow people that follow him and you won't get this content. My content used to be all over the place as well. After I've done the pruning, now it's various people talking about topics that I care about. Obviously it's not perfect - things leak through, but far better.

Same with Facebook, my feed is now pretty much photos and news from friends and family.
Maybe HN or LinkedIn, lol
I have been utilising GPT to create my own app, and now openAI wants to be the only app that matters. I’m not sure whether I should be excited or not :/
If I were to write a blog post on this I’d make a few do’s and don’ts (why make a blog post when you can blog in HN comments?)

Don’t merge the base branch into a feature branch. Rebase to “update”.

Do use rerere and the curse of fixing the same conflict over and over is (almost) gone.

Don’t rebase (or force push for other reasons) a shared branch. Rule of thumb here is you can probably rewrite history if you work with _one_ coworker in a branch but any more than that and you’re more likely than not to upset someone.

Do rebase -I HEAD~N to reorder/reword/squash into easily reviewable sequences of commits.

Don’t force push after review, until the review is complete. This keeps the history of the review process but you can later merge the fixups with the commits they logically belong in right before merging.

Do use Merge, Squash and “Rebase+FF” as appropriate for merging PR. There is no best solution for every scenario so prescribing “always merge” or “never merge” or similar isn’t helpful. A good rule of thumb though is that IF a branch has merged from the parent branch to update (which I suggested was a “don’t”) then avoid merging it back. A branch that was updated that way is better to e.g squash when merging back.
Sure, but the mindset of the FIRE Zoomer is much different than wealthy people in the past. An easy example would be Fred Trump, whose "winners and losers" mindset was taught to Donald in a way that Donald went to college, started businesses, and maximized his "wins". He taught this mindset to his children and they went to college, even if it was just for networking.

What would a FIRE Zoomer teach their children, especially if they invested in crypto early and got lucky? Why work hard if mom and dad "don't" work at all? Why go to college if the point of college is training for a career? How will those children be shown by example how to be a helpful member of society?

I suppose a lot of FIRE people likely intersect with the Child Free crowd where they are achieving financial independence by not having any expensive dependents they need to care for. That does reduce the amount you must spend by quite a lot, but if enough people do it the economy will have issues finding workers at all as more people voluntarily check out of the system and leave no descendants to continue in the future.
Plantations aren't free either. Slaves need to be managed else they will all leave and the owners starve (or worse).

I guess slaves, slave owners, and software engineers are all pretty much the same when you think about it.
You can very easily rewrite your commit message on GitHub when squash merging. Since the organizations I work exclusively use squash merge, I often just update the commit to be more valuable, listing the important changes it contains. (And of course the PR in GitHub will contain the commit history of the branch that was squashed, as well as any discussion.)

IMO, this is a lot simpler and easier to do than rebasing your branch to have a flawless history.
My rule of thumb for commits is that they should be of a size and scope suitable for cherry-picking. So, maybe I'm working on a small feature that entails three changes, and each of those three changes is useful in and of itself and could conceivably be cherry-picked by others. I would create three separate commits, generate a PR with all three, and merge in the work. Sure, I could squash merge and end up with one merge commit encompassing all three changes, but now none of those three changes is cherry-pickable.
There's also a third way called resource groups [1]. We use that to ensure that we only run the newest job if we have multiple deployment jobs waiting for execution. This way even if we have multiple pipelines racing each other, only the last deployment job wins.

[1] https://docs.gitlab.com/ee/ci/resource_groups/index.html
There's a fundamental problem that the first step is you doing all that work. That means there's no way to tell you the work is wasted; you already did it.

I generally think people should do /less/ work when reporting bugs because of this, but you should be careful and clear about what you do put in there.
Did you notice, though, that rebase advocates use very "emotive" terminology when talking about git history? Like it's a subject they care about? Seems awfully touchy feely.
> They show you what you actually committed and don't allow you to do stupid things that might corrupt your repository, which is what matters.

Who cares what you actually committed on a per-commit basis, especially when fixing things that were mistakes in the first commit, and would have been committed as part of the first commit with more planning and/or no innocuous accidents? Who needs to preserve the already arbitrary order of commit commands, and why? I’ve never heard a compelling and real-world reason to need this, nor any popular workflow that this idea establishes or improves.

And what repo corruption are you talking about? I don’t know about you, but one thing people espousing this ‘what actually happened’ philosophy and trying to trash-talk git tend to deliberately overlook is that git commit histories are immutable, and rebase only produces a new commit lineage, with an in-tact backup of the previous lineage surviving anything you do. It’s not possible for the history to be irrecoverably corrupted, unless you’re unfairly including bugs or hardware failures. Recovering from rebase mistakes is simply a matter of learning where the undo knobs are, and ultimately they are pretty easy to use, it’s no more work and no different outcome than learning how to groom the presentation history of Hg or other systems.
Yes. Is OP exaggerating? Or is the board member actually saying such things?
Why would you use FPGA for generating 4k content
As I understand it, the U.S. does not subsidize petroleum marketers, or at least not very much. Oil companies are generally taxed on net income after expenses and depreciation, same as all other businesses.

Plus depletion, which like depreciation reflects the value of an asset going down over time, making the company in question worth less than it would be otherwise, i.e. the book value is going down.
I'm fairly certain you are correct.
100% depends on what specifically the board member said.

If they openly said "kill every Palestinian" then that is a problem.

On the other hand, in the current moment, it is very popular to interpret a wide variety of pro-Israel statements as "advocating genocide".
Or bubble up. Whatever the medium that is implied by this example should be viscous and sticky as shit tho.
Is the number of legal chess positions even or odd?
I found it sometimes frustrating as well. But my experience was that it depended on the engineer/team/screener the Radar went to. Obviously if it was a bug I found, I much preferred to talk to the engineer in person who maintained the code in question.

There were plenty of teams that were very good about jumping on bug reports and getting right back to me. In fact, a decade or so ago at Apple this was more or less the rule.

My sense though is that engineering became overwhelmed with bugs especially as Apple itself became as successful as it has become.

"In the old days" a smaller team would have one of the engineers on the team screen Radars — maybe rotating to a new engineer every week or so. Engineers could quickly mark a bug as a duplicate of another (recognizing a familiar backtrace or symptoms) or might be able to guess at a diagnosis and send it straight to the engineer in charge of the (likely) relevant code.

A few teams I worked on were very good about daily "BRB"s (bug review board meetings). With a number of engineers in attendance, again, bugs were quickly dispatched to the right component, assigned to right engineer.

Again though, as Apple grew, I saw bug screeners on many teams more or less automatically flipping Radars back to the Originator if there was not a litany of documentation attached to the Radar. What build of the OS, what hardware, a full sample, system diagnosis.... It was frustrating when it was an obvious bug — maybe even a UI bug — that would take someone all of 30 seconds to repro. I somewhat sympathize though as traffic no doubt began to become a firehose of bug reports.

It seemed backwards to me though to put such a burden on the person who is simply trying to report the bug, trying to help you improve the software. Often in screening Radars the description alone was enough for me to know exactly where in the code the problem was. I didn't mind my time being spent at least scanning the Radar title and description. If it was not clear to me at that point, sure, flip it back for more info. The seeming rise of "auto-reject" is what began to irk me.
Cheap VA (Samsung S32A700), I use mostly as a TV though. I always would get tired quickly previously from 32 inchers, but recently I started liking them more than 27 inch; do not get tired anymore.
Linked article title is Why Software Engineering Will Never Die.
> I've never seen a claim that the 68000 significantly outperformed the 8086...

I think you made a typo and meant 6800. Too late to edit though.

I make this typo too because the 68k was such a significant chip in history.
Is the code shared anywhere? I'm thinking that it could benefit from some input from others that have done a lot of vanilla JavaScript work. That application should be pretty concise and DRY using <template>.
I've been competing in ultra-distance bike races since 2020. In April this year, I decided to take a break from work and see how well I could do if I dedicated one year to training. I chose the Race around the Netherlands in 2024, the race that started it all for me, as my goal race. Training takes up to 30 hours a week, so at time it's like a full time job, but I haven't felt so fulfilled in a long, long time. I definitely recommend it to anybody that has the opportunity.
That post is satire, right? It has to be.
I think this discounts the genuine political opinions that many elected officials in the US government have, especially about the new cold war with China.

It's worth noting that China spends more money lobbying the US government than any other country on earth: https://www.opensecrets.org/fara/countries
> It may also be a sign that OpenAI expects competition in the near future, which would be another good news.

Of course there is competition. OpenAI is using the Andrew Carnegie playbook of aggressively cutting costs so that the competitors have no chance to get up and running. They are cutting off the competition before they can start. I don't see evidence to believe that AI moves into a commodity business anytime soon.
Yea, I thought about it too, but my table is not as deep.
What does Signiant do? And what does Signiant DO?
The actual answer is that arbitrators are liable for their judgements.

If you had your hand cut off by your manager for being 5 minutes late to work and sued your company only to find out it had to be dealt with by binding arbitration, and in the course of discovery you found an email from the CEO and the board telling managers to start cutting off people's hands if they are 5 minutes late to work, and then the binding arbitrator said that the company did no wrong, then they have exposed themselves to a potential lawsuit without the protection of a binding arbitration agreement.

So, just like a fiduciary financial manager, they have a responsibility to act and judge in a way that will stand up to possible external scrutiny.
Steel Industry Advances with Innovative Green Technology in the UK
Norrsken22's debut fund closes at $205M to back growth-stage startups in Africa
Especially as people are deferring starting a family as long as they can, with some just giving up entirely. Lots of countries are struggling with replacement birth rate and our economy is based on endless growth, so something's gotta give.
Headlines so weird, you have to click...

I was thinking to myself, there's no way that someone's acting like it's 1988 again, and we have to embargo this from leaving the country for fear Saddam Hussein will use it to construct a 50 megaflops supercomputer with which to pre-calculate artillery firing solution tables.

Then I clicked, and it really is that dumb. Way to go Congress.
I'm not based in the US, but US companies outsourcing to my location that I worked for did find the concept foreign.

I make a point out of taking the last two weeks of the year off, but I could stretch it to three, because my manager takes this much, so it's not like he would be waiting for me with something anyway.

I'm also planning on taking a whole month off should I become a father of a second child. I took two weeks for the first one and in hindsight it was not enough. A (male) friend of mine took six and the only thing holding me back from doing the same are finances, since as a contractor I have a daily rate.
Does it not provide some protection against a buffer overflow?
At this point perhaps Epic should just bite the bullet and make their own game console like the Steam Deck. I have to imagine many contract manufacturers such as Quanta, Foxconn, etc. would jump at the chance to manufacture a white labelled device for Epic to develop a platform on and brand.

Perhaps they could even make it in a phone form factor like the Nokia N-Gage so they can compete with Apple and Google.

Then Epic would be in a great place to show everyone how to provide an open platform that has no developer fees and no costs for developer tools. They can also allow other app marketplaces to be installed on it directly without the need for side loading.
For anyone like me that was wondering how average screen time on phones compares to average "screen time" watching television in the late 90's:

- 2000: "Almost all 6-17 year olds (99%) watch television in their leisure time, and on average spend *two and half hours almost every day* in front of the screen."

- 2023: "On average, children ages 8-12 in the United States spend 4-6 hours a day watching or using screens, and *teens spend up to 9 hours.*"

I think this screen time increase, and, specifically, the lack of regulation around social media consumption is a crisis. Data on the harms that social media is directly and indirectly accountable for is abundant. The increase in children getting a tablet thrown in front of them is particularly concerning to me.

This might be me (a Millennial) channeling Socrates[^2] about the next generation, but I am increasingly strongly believing that insufficient life skills development and the achievement gap in general will be significantly wider in the coming years because of this, and that wage/class inequalities will increase with it.

[^0]: https://eprints.lse.ac.uk/21172/1/Young_people_New_media.pdf

[^1]: https://www.aacap.org/AACAP/Families_and_Youth/Facts_for_Fam...

[^2]: https://old.reddit.com/r/AskHistorians/comments/a4vnuv/old_g.... Yes, I know it's misattributed to Socrates and is a much more recent quote than oft-believed.
Isn't Tolkien's Atlantis reference Númenor? Like, he didn't change a comma :-P
There are just too many things you have to know about which commits are what and what's going on - especially with a larger team - it's not a good use of time imho to be fixing rebases when they go wrong. Like the big list of dos and don'ts at the end of this should be a red flag.

Better alternative I've found is squash merge - topic/feature branches are squashed as a single commit instead of bringing down each individual commit or creating a merge commit. You're history is cleaner, you're able to revert stuff easily, and it's really hard to mess up since it's just an atomic last step you do in your workflow.
I dont' want to be judgemental about your choices. They are yours to make. But we can't really complain that life is unaffordable based on what sounds a luxury breakfast with a mimosa/champagne. I've never had a mimosa for breakfast in my life! The same breakfast at a highly-rated, non-chain, brunch place in my large US city would cost around $15+tip without the mimosa.

No person is entitled to have others serving them on the cheap; if we want servers and cooks to be well paid, then restaurant food will have to cost a pretty penny.

By the way, you can make the very same breakfast at home for less than $10/person, including the mimosa, and barely $5/person without it.
It seems unlikely everyone in Sacramento forgot about the differences between types of municipalities, at any point in time.
Can we not ruin HN with political stuff and claims like this?
There are a lot of huge announcements here. But in particular, I'm excited by the Assistants API. It abstracts away so many of the routine boilerplate parts of developing applications on the platform.
Do users even use Feedback Assistant? I have yet to hear of anyone in my circle (friends, family, coworkers) submit a Feedback. None of them are developers or us the developer beta of iOS, so I have always surmised that to be why.
The Whisper V3 model was released open source a few minutes ago: https://github.com/openai/whisper/commit/c5d42560760a05584c1...
This is just not true. The experience is typical if you know how to solve your problem in a GCed language and the solution is to solve problems the Rust way, primarily by using handles (and/or arenas) instead of references.
You will wait long for this. MS didn't pay a billion for having others selling it too.

But click yourself an azure account, build an API and just use it.
If lots of people are watching the file sequentially, then sequential order is close to optimal. Consider a Bittorrent-based lifestream. Clients should focus on getting and distributing the chunks that everyone wants.
see http://bittorrent.org/bittorrentecon.pdf section 2.4.2
I can only thank you for the work you've done in creating sudo, I think it's an invaluable tool in the general day to day use for so many people. As someone working on sudo-rs, our goal with creating it never was to invalidate any of the work previously done, and we are very much aware that our implementation will not be bug free, especially not at the start.

For me personally, creating this Rust version allowed me to work on something that I would normally not be able to work on, given how I would not rate my confidence in writing relatively safe C code very high. If nothing else, at least we already found a few bugs in the original sudo because of this work. Despite the 43 years of bugfixing, such a piece of software is unlikely to ever be free of bugs, even if just for the changing surroundings.

Other than that, having some alternatives can never hurt, as long as we keep cooperating and trying to learn from each others work (and from each others mistakes).
It’s your algorithm. I mostly see content where he’s being dunked on or Tesla is the butt of a joke.
> I'm planning on going back and playing the Divinity: Original Sin games that Larian made before it. I hear they're fantastic as well.

They are. I'd play them in order -- the combat mechanics of DOS1 are kind of tough to swallow after the improvements in DOS2.

The DOS1 plot is also a bit thin, and you have to appreciate their brand of humor. But they are both great.
Economist fact-checks Peter Zeihan's China collapse story
Marijuana use linked with increased risk of heart attack, heart failure