skysight-inc/HackerNews huggingface dataset:
Not to get all technical, but the "Cube Rule of Food" would classify this project as "pdftoast", not "pdfsandwich":

https://cuberule.com/
If you always rebase, aren't you hiding even more of the history than if you have unlabeled branches?

I have to admit I've never understood the point of keeping the history linear.
Unlike other fusion reactors, Helion doesn’t produce neutrons which could be used to make Plutonium. D + T fusion, on the other hand, makes more neutrons than fission does making it an alternative path to proliferation.
^ This. Also, It's the Wall Street Journal, so consider the source, its own by Rupert Murdoch, whose media companies, until very recently were climate change deniers, so from a rather crude sort of climate denialism, they will likely move to supporting technical "climate fixes" spruiked by the fossil fuel industries. This is a more subtle way of sabotaging real climate action.
I really liked Perforce changelists, so in theory I should like the staging area, but I kind of don't :)

I use it nowadays, but I think it's too limited to provide value like Perforce changelists does.

I'd like to have one changelist for random local dev changes, like setting debug flags or turning off optimizations. Stuff I have no plan on checking in.

Then I'd like to group my edits into maybe one to three possible future commits.

The staging area doesn't allow this, I need to keep doing "git add -p" and carefully sidestep all the debugging stuff, plus that I can only work on one commit at a time.

So could have been useful, but not so useful in it's current state IMO.
GIT - the stupid content tracker

"git" can mean anything, depending on your mood.

- random three-letter combination that is pronounceable, and not
actually used by any common UNIX command. The fact that it is a
mispronunciation of "get" may or may not be relevant.
- stupid. contemptible and despicable. simple. Take your pick from the
dictionary of slang.
- "global information tracker": you're in a good mood, and it actually
works for you. Angels sing, and a light suddenly fills the room.
- "goddamn idiotic truckload of sh*t": when it breaks

This is a stupid (but extremely fast) directory content manager. It
doesn't do a whole lot, but what it _does_ do is track directory
contents efficiently.

- README, Linus Torvalds, Git source code, April 7th 2005
> You now have no way to indicate if your changes are breaking.

You now have no way to indicate that you know your changes are breaking.
I do not see this proposed that would cleanup a part of the npm repository, Google,MS, Firefox could work and find what are most popular packages and then make a list what should be put in the browser or in node, or maybe a blessed optional extended standard library.

For example if we detect that 1 million packages depend on leftpad then add leftpad int eh standard library, if 500K packages depend on isValidUrl,isValidEmail then put this int eh standard library. I am sure Google devs could over engineer this to make it optional and include only what you need.
I understand that this is too much of a reach back.. but there must be some consideration of the fact that a decentralized weak america over threw the globes strongest power. That power thought that Indians(asia) were just English. That australians, canadians, the western colonies were were just English. Eventually there was a realization that these political differences demanded the allowance for self determination. It seems, in order to keep a strong central Oneness, we must enfore coercive, destructive powers to enforce one region over another. The comment I am responding to seems imply a similar extreme; that Floridians are perfectly reconcilable under the name American as is an Oregonite, who are sepperated by 1,556 miles away! Or even that generational Virginians have much politically and culturally in common with generational Massachusettsans. I don't know what is best, truly, but I hope the united states does not become one large California, or Texas, or any ideology that presupposes the people of a specific region. I'll hop off my soap box. :-)
An observation I have seen shared in the context of progressive or terminal conditions is that one can experience mourning before a death.

This can be a very difficult emotional roller coaster if catches a person off guard, and they haven't explicitly recognized that significant emotional losses have already started accruing...
Because Linus created it and Linux community adopted it.
Lies! Aspen has houses at 4 million already. :D
A bit convenient at places that charge extra for credit card and carrying a chequebook is not always convenient. I just load it into Apple Wallet and leave it there.
Wind and solar don't provide unlimited free energy.
Genuinely curious: what would you rename cherry picking, fast forwarding, and rebasing?
That also means that if you used seccomp to restrict mprotect syscall, the child process may never ever write again, which is an unfortunate design choice.
I thought for a moment this would be why SQLite doesn't use Git to store its data structures, which I really wish it did. Still looking for a database that acts as a virtual file system, and automatically orders data into a file tree structure.
I wish it worked that way. I just peeked into how python packages in debian-based distros work. They are most frequently PyPI packages with some debian wrapping, so we're back at the same problem.
"The obvious is they can't do this well..."

You may well be correct! If they're not capable of finding their position without surfacing for whatever reason then the whole nuclear deterrent is likely at stake (the missile's launch position being critical—or it used to be so).
The counter point is, new releases come with new bugs you may now hit and waiting could mean someone else hits them

Besides your points, it also sucks if you hit an old bug that's been fixed yyy versions down the line and you can't get there reasonably

(I tend to agree with many small chunks than a couple huge ones)
> Corporations will never rise to the legitimate use of force.

Jus because that's how things are now doesn't mean it has always been that way or always will be.

The earliest Corporations originally did use force and in fact at times maintained armies and /or navies.
> Moral of the story: don't use debit cards

I use a debit card for groceries and such. However, just to be sure, my paycheck goes to an account with no cards attached. I then transfer small amounts ($100 or so) every now and then to the debit card account.

This limits my exposure to card fraud, and also has the nice side benefit of giving me back some of that "spending feeling" that cash has. If I have to transfer say three days in a row it's noticeable and I can think about what I've spent it on, and maybe slow down a bit if I know I'm running low.
+1 on the Dualit Original. Built like a tank!
> they talk about a lot on the Vergecast (weekly podcast from The Verge) is that the killer app for AR is identifying people in real life for you.
> I think that's probably true for a lot of people which importantly includes journalists.

I am TERRIBLE with faces. Like confuse-my-uncle-with-my-father bad, and i really don't see this feature being great. Like, will i really look for a notification over everyones head telling me there name? Will i have to populate it from my contact book? Will contacts give me their photo?
If you can code or know how to use some demos, you can give a try to Vosk, this is a opensource project with multiple implementations and language models, opensource as well, all of this offline. They have smalls and big models, for mobile apps, iot, asterisk, and much more

https://alphacephei.com/vosk/
I think you're right. And as much as I want to think I'm ruthlessly simple, I do notice this in myself as well.

Everyone will agree with us of course, but suggest something minor like "hey maybe you don't need react" and here come the reservations. To paraphrase Alan Kay, everybody likes simplicity except for the simplicity part.
> I don't think Debian's automatic updates do major release upgrades automatically, do they? Those IIRC do require manual intervention

For major release upgrades, the official upgrade procedure is to follow instructions like these: https://www.debian.org/releases/stable/amd64/release-notes/c...

So yeah, you have a somewhat manual upgrade process once every two years, if you're not on one of the rolling release (‘testing’ or ‘unstable’).

On the other hand, you do get to choose when you make those updates. You don't get caught by surprise with them because you forgot to read the news.

Debian's documentation on Testing and Unstable[1] contains some snippets that may feel familiar to Arch users, including this very relevant bit:

> Consider (especially when using unstable) if you need to disable or remove unattended-upgrades in order to control when package updates take place.

—

https://wiki.debian.org/DebianUnstable#What_are_some_best_pr...
Not true, it's too late for nuclear power.
Additionally it is quite expensive compared to renewables and makes the burden on future generations even bigger.

Anyway, don't shut down any working plant early...
We need everything we have atm
Don't package maintainers for Debian and what not often backport changes without breaking things? I agree that the mental complexity of understanding so many components of software and staying relevant is near impossible, and that is specifically why I try to avoid JavaScript development altogether.
Curious: What git feature does Network mirror then?
You shouldn't skip Ace Combat 7 ;)

https://www.aroged.com/2021/10/19/bandai-namco-removes-denuv...
It does not
I pretty exclusively play on /tg./ I was most active years ago, sometime around whenever the launch of mini was. Now I just hop on a few times a year when I can sit and burn an entire night and not worry about how little sleep I'll get.
Yes, it was added in response to this comment, as mentioned in one of the replies.
Pelican [1] can translate markdown to html. However, I think read the docs [2] and Sphinx [3] are more suitable for a wiki (but it uses RST). Also, you can use themes [3].

[1] https://docs.getpelican.com/en/latest/

[2] https://readthedocs.org/

[3] https://www.sphinx-doc.org/en/master/
I think nuclear deterrence runs patrols in very deep, very well-mapped areas that are planed well in advance, so are usually fine.

The issue is tactical manoeuvres in the South China Sea, where we don't know the terrain and we don't know where we'll need to go. In that environment all our tools are less effective (because we have less mapping, because sonar is not usable, because we're manoeuvring more so inertial navigation is less effective, because we're moving faster.)
If it were important to us, we could build modular reactors on a massive scale. There are several manufacturers with serious designs. And yes, electricity is "only a part", but it's a big part. A solution needn't be a singular one to make a huge difference. Personally, I think nuclear isn't our best choice. But it is a viable choice and we could make it work.
I don't get that at all. To me the answer is "we want things out of the vcs that we don't get from git nor github/gitlab."

The fundamental difference is: sqlite is a cathedral, git is for bazaars. That's kind of a big deal.
Pretty sure LESS industrial feedback loop generating behavior is the best climate-change solution.

Nuclear power probably seems pretty great to WSJ and capitalist readers who want to own it all, and need the public to be ok with nuclear power again, though.
IMO conflict resolution is almost always harder than redoing the change by hand, especially while looking at the old diff and redoing it towards the new branch. Kind of ironic given how hard diff editors try to help.
> plus that I can only work on one commit at a time.

This is that part of git that bugs me the most! It's totally hostile to the way I prefer to work: one screen session containing all the editors and shells per change that I am concurrently working on. Git simply cannot do it, unless I clone the entire repo for every change, which is not practical for large projects.
I think semver is mostly useful for telling, at a glance, how much of the changelog/migration notes to read

I've noticed (more frequently) npm packages quickly climbing in versions (1-17 in a couple years) but at least it's painfully obvious.
I don't own a vintage Sunbeam Radiant Control toaster, but this video made me want one: https://www.youtube.com/watch?v=1OfxlSG6q5Y
git was a great breakthrough in terms of performance and supporting distributed workflows, but now like many technological breakthroughs there needs to be an interface that exposes completely different abstractions based on the user's workflows rather than the implementation's data structures.

For example, why can't I do something like

git view filename -3 # shows file before last 3 changes _made_to_the_file_ (irrespective of how many commits)

git view filename $date # shows state of file at date

git revert filename $date | number # roll back a specific file to what it looked like at $date or file version

I have the feeling that the developers of git even understand this, but they needed to get git out the door and assumed the community would build the layer atop git to make it more user-friendly. Sadly, attempts to make git user-friendly have so far boiled down to GUIs rather than introducing new concepts. Certainly the current collection of shell scripts that exist as the ui for git definately have a hackish feel to them.
Somebody needs to find a case with a turbo button and hook it up so that the game runs when it's off.
AFAIK Japanese graphic arts can be broadly traced to the Edo period and the proliferation of popular literacy that print created. Much at the core of Edo (1600-1870) can be traced to the western capital of the Tang Dynasty in China, Chang'an (618–907; now Xi'an), jewel of the culturally diverse Silk Road and one of the largest cities on earth at the time. And much of that variation can be traced to a dispersion of Indian linguistics and philosophy.

That's all vague and arguable: but what about the awesome Indonesian Batik shirts? Wikipedia apes supposition that, while attested to the 12th century in Java, it may have been introduced during the 6th or 7th century from India or Sri Lanka.

Seems like on balance India's former achievements are being lost to time. I just watched Around India with a Movie Camera[0] (A compilation of early Indian film clips ~1900-1920) last night and boy was it cleaner back then.

[0] magnet:?xt=urn:btih:DPYEDYZ3HMG3FEG2LFFSDLKYSFFFMRTO&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce
so where’s the one that correlates to git log —graph ?
> We really thought we were entering a new era in humanity.

The nuclear power industry has really only existed for a generation. The promise is still there.
btw. i use a nh-dh15 and run the blender test and i only did go to ~65° maybe I was lucky with the silicion tough. but the stock cooler was horrible.
The lawful bases for processing data are listed in Article 6. Subject consent is 6(1)(a) and legitimate interest is 6(1)(f).

Consent is used when processing is not required to provide the service, no other basis applies, the processor still wants the data anyway, and the subject agrees. Legitimate interest applies when data isn't needed to provide the service but is necessary for related business functions (like fraud detection) not covered by another basis.

No basis except 6(1)(a) requires the subject's consent because the rest all cover processing required for the service to work.

https://gdpr-info.eu/art-6-gdpr/

===

Edit: I read "They're not" as "the bases aren't separate." On rereading, it could also be the interests aren't 6(1)(f) legitimate. Which, agreed, they're usually not. I'll leave this up in case it's useful to someone.
I HATE Git. It seems like every other over-complicated, over-engineered solution to problems that should be simple.

I used svn for a long time. New developers got it right away. Git is treacherous waters for 7/10 of the developers I've worked with.

That said, I LOVE GitHub and gitlab. Amazing tools for collaboration. But the Git part doesn't really do it for me. I'm waiting for something better to take its place.
The blackouts are because of fire-risk from transmission lines, and this is largely because PGE paid out bonuses instead of paying for needed repairs to the transmission system.

This group of corrupt execs are the same people entrusted to make safety and maintenance decisions for Diablo Canyon.
git log?
I don't understand the difference between intentionally suppressing researchers, which they are obviously not doing (that would be ghastly) and directing research towards the most profitable drugs, which they are obviously doing (to do otherwise would be bad business).
I am a CTO and I use a system76[1] I would rather my devs used Linux systems, for a long time I did only deploy only Linux ThinkPads, but devs want MacBooks- even more so after M1 launched. A few have turned down offers because we didn't offer macs. Now we basically allow them to choose, but in the recent past not a single one has not chosen Apple .

I don't think it is all just CTOs either, there is lot of aspirational value partly driven by design of the system (light weight/looks) partly because expensive it becomes more exclusive.

Without M1 there was nothing else to go for technically they were not that much better, now atleast post m1 there is value to maybe justify the costs.

TCO for ThinkPads are way cheaper than macs upgrades are possible when it is not on macs or easier you don't need to send it apple service for ages, the in-house IT has no shortage of spare parts . No sensible CTO is going to choose apple over anything else if he had choice .

[1] ThinkPad X1 carbon before that both were much better devices just in terms of build quality than my last mac the 2016 pro .

Having linux just work is worth investing in frame.work or system76 or dell developer edition I rather do actual work than fiddle with drivers .
I would eliminate these tasks from the aspect of the user and provide a more straight forward way to accomplish the same intent. You make a good point though because this is easier said than done with a typical terminal based application.
> They keep time: if blown with cold air on the first of every hour, by the third hour, they’ll retract just before the cold snap.
If you want to avoid bot detection, learn how bot detection work. A lot of commercial "webapp firewalls" and the like actually have minimum requirements before they flag certain traffic as a botnet; stay below those limits and you can keep hammering away. Sometimes those limits are quite high.

In the past we've had the most success defeating bots by just finding stupid tricks to use against them. Identify the traffic, identify anything that is correlated with the botnet traffic, and throw a monkey wrench at it. They're only using one User Agent? Return fake results. 90% of the botnet traffic is coming from one network source (country/region/etc)? Cause "random" network delays and timeouts. They still won't quit? During attacks, redirect to captchas for specific pages. During active attacks this is enough to take them out for days to weeks while they figure it out and work around it.
Most of the previous version control systems you mentioned were much less complex and had an extraordinadily easy mental model to understand in comparison.

Git set out to solve a different problem: adapt VCS to an agile, CI/CD world. It does this much better than those previous VCS generations, but its mental model does seem needlessly complex.
renovate bot can do this. set it to wait for x days before accepting a merge, and pin your versions so there's no chance to update by mistake.
I'm sure that working at Strip has been helpful for his credit card knowledge.
I don't have a deposit banking relationship with any brick-and-mortar banks, so for me it's very convenient: I have a way to turn my paper money into electronic money.
The concept only makes sense in the context of APIs. I don't know if that's obvious; I've seen people use semantic versioning with software that didn't have public interfaces.

Even if you go through a deprecation cycle, you're still going to eventually have a build N with feature X, and build N+1 without feature X. That's a breaking change.
"non-major in-person purchases as it's inherently private and anonymous"

Most of the time that's an anti-feature - there is no point of hiding transactions of you buying bread, it could provide you an alibi in case you are accused of a crime, but there is no conceivable way it could be used against you.. (people don't stop to buy bread on the way to the crime scene)
I agree with you on all counts, but it's worth highlighting that the parent did not call the designers dumb, but rather the situation and implementation.

I know it can seem like a distinction without a difference, but I think it's fair to critique work. I think they could have been more articulate and considerate towards the designers, and have some empathy that many people have worked very hard on it, and did their best in the problem/solution space they were working with.

I just think it's important that people stay objective on if the quality of the people themselves is in question. It's not ok if it is, but I don't think it was here.

now people that don't check how malloc() returns being blanketly labled as lazy is an example of it being about people. people don't ignore the possibility of a nullptr return from malloc because they're lazy. They ignore it because it's hard -- even if you do catch it, there's very little that you can actually do. You can't dynamically allocate...so I hope you've got enough stack space to do what you've gotta do. And even then, you have to be able to propagate that there's no memory all the way up the stack as it unwinds...and check every single allocation.

The cpp world is mildly better in that it can throw std::bad_alloc...but if you have something that winds up doing an allocation in a destructor, I imagine that's not a fun time.

Most of the time, there's not really a better thing to do than crash -- and there's not a lot of incentive to put any work into it. It's not something that should be happening on any sort of regular basis.
>steering your 2-tonne cyclist crushing machine

wow
> Then, the scientists turned out the lights and watched
The HUD's quite intriguing, I can't seem to turn it off. It's like a "score" for page responsiveness ;)
I don't even use *the multiple uses of `git checkout`. It may be suboptimal but I think it's easier to quickly recall in my mind-- `git branch name` to create a branch and `git checkout branch` to check out a branch.

`git checkout` for restoring files is dumb though, but as others have mentioned the UX has been improved with `git restore`
You want to remove fast-forward and rebase from a graph based version control system? What would you do instead? Always merge?
I completely agree. Git is a product of its requirements. It's not perfect, but it gets the job done, and obviously it does it pretty well.
If SQLite used Git, they could self-host a more reasonable web view of the repository using GitView or CGIT.

> why it seems Github goes out of its way to hide the typical commit tree navigation

Wild guess: because those kinds of features requires the back end to execute Git implementation code which can invoke some pretty expensive cases. Imagine that across thousands and thousands of repositories being accessed at once.

They want to steer the user toward doing a clone and doing their own in-depth drilling on the copy.

CGIT caches for better performance; but caches require extra storage and some sure-fire expiry mechanism so it doesn't grow and grow. Caching things for internet rando visitors doesn't seem like a good idea.
How you know?
I took an offer elsewhere. Twitter would have been fun as Mudge was invoked with that team.
Some forms of "gossip" (such as slander) are actually harmful, and thus probably should have legal consequences (and usually does).