skysight-inc/HackerNews huggingface dataset:
Many dysfunctional and repressive kleptocracies fail in the exact same way as SK and Japan, ie, massive corruption and power concentration.

There are not many countries in the world that are so dysfunctional as far as democracy that the same party can stay in power for 50 years, nor that literally no single president has managed not to resign. If SK and Japan were in Africa, the Middle East, or South America and had economic outcomes commensurate with the region but on the higher end, we would call them dysfunctional and repressive kelptocracies.

Like come on, if you saw a country in Africa where the same party was in power for a lifetime and the conviction rates exceed 99%, where judges would rather resign than declare someone not guilty, and where a an extremist political faction infiltrated the educational bureaucracy and textbook publishers to prevent historical event from being taught, you would call it a dysfunctional and repressive kleptocracy. The only reason that's not extended to Japan and SK is by comparison with China and because they are our allies.
My credit union's app was very frustrating for depositing checks. Many reviews online said so, but apparently were ignored. So for a while I would go to an indoor ATM when I got a paper check which is not that often.

Then I had an idea - I got a piece of black construction paper for a background and it was much happier taking pictures of checks on that.
Yeah, all these are useful to prune the bonsai. It matters more when the project is big or has lots of branches, of course, but they have benefits even for a single developer.
Hah... I was bored and decided to just press the update button on all of my dependencies. I spend 2 hours changing things pointlessly and then deleted the branch and read why any of these updates were necessary. React Router - "wow, we have an amazing new v6"... *reads the "why upgrade"... "it has hooks now", ok they are already in the version I am using (5.2). "it has some changes to how you specify routes and you will have to rewrite them all. Just wait for automated rewriter". I couldn't really see any advantage to them at all but supposedly "something in the future!". ok delete that one. Material UI - we changed everything.... here is 10 page long how to upgrade guide. Also no date picker in core anymore. ok delete.... delete delete. I will not upgrade this project again. Lesson learnt.
Replying up here instead of way down in the branches.

I don't think disabling of overcommit implies that physical pages are mapped immediately. If caches are instantly droppable, you can use a page that's allocated but unused for cache, and drop the cache page (and zero it) when the allocated page is written to.

You'd still have all of your caches until you have memory pressure with actual data written (but of course, with overcommit, you'd drop caches then too), but if you attempt to allocate more than you have (including through fork attempts as discussed elsewhere), you get a system call failure rather than an OOM kill.
Dupe: https://news.ycombinator.com/item?id=29106398
See, you can't "believe in climate change" and be against the cleanest, most abundant energy source we have: nuclear. It's just not a logically consistent position, a litmus test to determine if one's environmental advocacy is real or merely performative.

That is why China has announced they're building 150 new nuclear reactors in the next 15 years. The US will _inevitably_ have to follow suit to remain competitive.
*Lying For Money
Cryptodunks for Cryptopunks
You would buy a few solar panels for your house at a few thousand dollars a pop, but would you buy a 50MW fusion reactor for your house, at the prices they'd be selling at? If not, there's clearly a continuum between you and the person they'll end up selling to first.

They are rightly taking every opportunity to clarify to investors who their potential market would be.

It has to be someone without vested interests in coal supply contracts and therefore the delayed success of your product, with a huge amount of money to throw at energy security, at a large enough scale for it to be worth a big start up cost. You also need someone to go first, because fusion is scary. This is non obvious. It is an essential part of their pitch, and no amount of cringe from people who know what electricity is is worth omitting it.
My bank doesn't allow overdrafts beyond $10 or so, no fees except a few percent in penalty rate if I keep it negative for a while.

There are some edge cases where one might overdraft more (delayed transactions IIRC), but again no fees.
> Apple is not neutral: they will happily monitor items that sell well on their store, release a shoddy half-baked internal version, bump it right to the top of the store, and eat all my revenue.

http://www.paulgraham.com/road.html

https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...

> If you want to write desktop software now you do it on Microsoft’s terms, calling their APIs and working around their buggy OS.

> And if you manage to write something that takes off, you may find that you were merely doing market research for Microsoft.

History repeats.
What matters is the relevance of the packages in the main repositories, not the quantity. While the quantity will affect some people, it will primarily affect those who use obscure packages.

As for the fudge factor, it would be difficult to even agree upon criteria. For example: should python or rust libraries be included, given they have their own package managers?
For what it's worth, I didn't think it was rude. And I do think it was a substantive aspect of his response. It's a valid perspective even if I personally think it's somewhat orthogonal and incomplete.
Love it. Know your requirements. (Well, love it from a very specific angle...)
Why does it need to take decades to build something we already know how to do, assuming we're actually facing a dire climate catastrophe? Is it the case that we can't technically build nuclear plants in a few years time? Because I very much doubt that.
Not called yes but everybody ive know has sent goodbye text message or snapchat.
Price is not defined by costs. You adjust prices for maximum profit, as in the k of (h,k) of a quadratic equation.

If you can produce a drug for 1$ a dose and you can sell it for 100$ at most without losing customers, you do that.

If your product costs are too high, you don't advertise. You sell the drug to the government as an "orphan drug".
3k Miles from Glasgow, a Town and Its Polar Bears Face the Future
For the same reason why you are allowed to fish with a single fishing rod in some places, but can't just drop a giant net or trawl the whole river: Scale matters, and regulating the tools is often an easier and more effective solution than trying to regulate scale directly.

In particular with data, the processing method makes a qualitative difference, between individual disconnected people each knowing one small snippet of your life, and a megacorp having an overview over whatever you're doing at every moment. By de facto limiting it to "one brain", the panopticon is prevented.

Your rights end where they start impacting other people's rights, and drawing those lines is what we have governments for. Even if you were to use just your memory, if you were tracking what someone is doing in such detail as ad companies do, you'd likely a) not be able to do that to more than a few people b) receive restraining orders for stalking.
> If you have the right to do a thing, you have the right to do it a million times.

Voting is an obvious exception.
Ya i wasnt shit talking the study, i was saying its a bad dataset to use in this case.
Yeah, it sucks. Why must they force their prudishness on the whole world? Such a pain. They force copyright as well via US government and its trade agreements. It's like they won't rest until the entire world becomes America.
Not the parent commenter, but I find Chicago rents cheap relative to the SF Bay Area.
One of the under appreciated legal precedents set a couple years ago was the Ohio V AmEx anti trust case. The case predicated against AmEx’s merchant contract forbidding merchants to steer customers away from using their Amex card. This was a common practice for many years, especially at restaurants since AmEx charged restaurants 6%.

The Supreme Court ruled that amex was able to keep the anti-steering provision in merchant contracts because they defined credit cards as a two sided market, and the harm to customers couldn’t be proven. In essence, the Supreme Court set a precedent that in any 2 sided market, in order for something to be considered anti competitive, a high bar needed to be met: the government must show that both sides of a 2 sided market be harmed in order for something to be anti competitive.

Had the ruling been the other way, almost every industry would have been impacted- Uber, App Stores, Advertising…etc are all 2 sided markets.

In essence, Credit cards have had a huge impact to our lives this century for reasons that are not appreciated enough.
You can build even 100x the amount of solar, but the sun will set anyway.
For the retro/breadboard builder, this is sort of interesting.
Not sure how Dallas fits in there.
This is why I like running LTS distributions where versions are fixed and security patches are backported. Unless you install from 3rd party repos chances are very good that updates will be seamless.
Well, I think it was also meant to be highly distributed as well (many different people all over the place could then come back and bring their changes together)

In order to achieve that, I think you end up with some additional complexity like local vs remote and a complicated graph structure to accommodate people coming "on" and "off" line
> Worse, the Arch wiki (and various subreddits) are almost as bad as the Arch/Ubuntu forums were in 2005. They often lead to a bunch of "shotgun debugging" where users are copy and pasting things they don't understand at all in the hopes that it will fix whatever problem they're encountering for reasons they won't understand.

This drives me absolutely fucking nuts.

> The community in general is full of people who intentionally shoot themselves in the foot and are then proud that they find superglue for the wound on the Arch wiki instead of using a distro with better engineering practices where they never would have had these problems at all.

This. A thousand times, this.

> The mistaken belief that doing any of this somehow "teaches" you meaningful things about Linux as opposed to solving real problems (since 99% of the "problems" Arch users encountered will never be seen on other distros, due to the fact that the maintainers carefully ensure there are limited footguns out of the[m]) is terrible.

Idk. There are definitely some Arch-specific footguns (like the lack of distinction between upgrade and dist-upgrade, so that ordinary pacman updates can do things like uninstall literally all of your kernels (lmfao)). But I don't think the basic approach is necessarily fatally flawed. When I installed Gentoo for the first time as a kid, getting everything working taught me:

- how to identify hardware using using common utilities (like `lsusb`, `lspci`, and `lshw`
- how to set up a chroot environment, how to use a chroot to manage or repair another system
- how to install and configure a bootloader, what configuration a bootloader needed
- how to use basic CLI networking tools to get online
- how to manage kernel modules (blacklisting them or adding them to initrd), although admittedly a good distro will *usually* be able to anticipate those needs for you
- how to think about package version constraints and manage packages from different sources
- fundamentals of building and managing software (i.e., what compile-time options are, how to think about dependencies and reverse dependencies)

Probably the first two are the most valuable, and I guess nowadays the Arch installation tools basically hide what is going on in the chroot environment from you (and actually make it tricky to customize, like if you want to add extra mountpoints to it). But I don't think the whole ‘set everything up yourself once’ approach is worthless.
Disabling overcommit on Linux doesn't tend to enable library and utility developers to have used memory responsibly. So it can be hard to run a system with common software.
> The really annoying part is that you can't use shared libraries without doubling the size of function pointers (FD-PIC ABI).

Interesting, thanks. That didn't come up on our system—not only did we not use shared libraries but we also linked the whole system into one binary, kernel and all. Link times were atrocious in combination with identical code folding and big VLIW sentences, but it worked.
I already met someone I’ve been talking to on Zoom for 2 years and he’s just fucking massive. I expected him to just be a normal size guy but he’s like 6 foot 8 and the whole dynamic would have been very different if we had started in person.
I want to know this too
Only by default, you can opt out this behaviour. But I don't see a problem with it, if someone already has my number he doesn't get much more information (beside the fact that I may want to have a "secret" Telegram account. But in that case you can register it with another phone number).
When I am working on assembling multiple commits at once, I make a large number of small commits with commit messages that indicate which commit they're going to end up in, and then do an interactive rebase at the end. The workflow looks something like:

# At the point I realize I have two commits
git add -p
git commit -m 'first'
git commit -am 'second'

# Do some more editing
git add -p; git commit -m 'debug' # commit the debug stuff so that I don't have to keep skipping it
git add -p; git commit -m 'first'
git add -p; git commit -m 'second'
# After repeating the above a few times
git rebase -i origin/master
# Remove the debug commits, move the first/second/etc. commits together, squash the runs of first/second/etc. into one commit each, and then go back and write commit messages for each of them
+1

Not to mention, everyone I know knows at least one person who had a stroke within weeks of getting one of the "vaccines", I know three. Previous to this past year I've known one person in my entire life that had a stroke, and it was my wife's uncle who was in his 90s.
Portland, OR is pretty close.
Agreed.

Title should read "Was" not "Is".

We're out of time. We should have been building out nuclear for decades.
The oldest operational nuclear power plant in the US is Nine Mile Point 1 in New York and Beznau in Switzerland coming online in 1969.

I wonder how much maintenance cost and updating compares to 50 years of a wind mill or solar farm.
That’s the definition of evolution, just applied to human societal organisms.
Yeah if you want any semblance of anything working 'out of the box', arch is just not for you.

There is no default install on arch. There is not even an installer. There's just the command line on a live system and then you create the partitions and put all the files in place automatically.

It's really great that arch exists but it's just not for everyone.
Feynman, in "The Pleasure of Finding Things Out":

> The first way in which science is of value is familiar to everyone. It is that scientific knowledge enables us to do all kinds of things and to make all kinds of things. Of course if we make good things, it is not only to the credit of science; it is also to the credit of the moral choice which led us to good work. Scientific knowledge is an enabling power to do either good or bad — but it does not carry instructions on how to use it. Such power has evident value — even though the power may be negated by what one does.

> I learned a way of expressing this common human problem on a trip to Honolulu. In a Buddhist temple there, the man in charge explained a little bit about the Buddhist religion for tourists, and then ended his talk by telling them he had something to say to them that they would never forget — and I have never forgotten it. It was a proverb of the Buddhist religion: “To every man is given the key to the gates of heaven; the same key opens the gates of hell.”

> What, then, is the value of the key to heaven? It is true that if we lack clear instructions that determine which is the gate to heaven and which the gate to hell, the key may be a dangerous object to use, but it obviously has value. How can we enter heaven without it? The instructions, also, would be of no value without the key. So it is evident that, in spite of the fact that science could produce enormous horror in the world, it is of value because it can produce something.
Your site "you currently cannot scan arbitrary URLs."

So, how can we use the scanner?
Btw, I also hear good things about Pittsburgh.
That may be true. A list of prices might not be copyrightable in your particular jurisdiction. However I was only responding to the raw assertion made without any such qualification.

On the opposite end of the spectrum might be a photographer's website containing a gallery of their sample work. The fact that the gallery is openly published doesn't represent a relinquishing of copyright over those images.
Does Consumer Reports test toasters?
Products don't have requirements, users have requirements :)

The requirements of Linus and the kernel developers are completely different from the requirements of the vast majority of users of Git, who are using it in small teams in a centralized way.

I would argue that the only benefit that this decentralization gives is a local cache, which makes things nice and fast. Most users don't need to be able to create branches easily (code review tools already let you do that, effectively) and it's just given people enough rope to hang themselves (e.g. GitFlow).

IMO the worst aspect of this needless complexity is having to explain to people "you've got 1) the branch central repo, 2) your local copy of that branch, and 3) your local branch". It gets even more complicated when personal forks come into the picture, as there are just so many copies of things to manage or trip over.

Try explaining to a junior developer why "git fetch" takes two arguments ("origin" and "master") while "git rebase" takes just one: "origin/master".
Ah yes, pull requests and adjacent functionality is my favorite part of git.
It's been ages at this point since I used Mercurial (around 2010) and probably these things changed along the way.

- But with mercurial branching where more like forks with different directories. Made me avoid that feature in web development work (that way I didn't have to fiddle with my webserver config every time I would have liked to create a branch)

- I recall having to deal with a bunch of gotchas around mercurial bookmarks (tags), like not being able to delete them, problems with sharing them with others, and things like that.

I was actively exploring different DVCS around that time, coming from a SVN background where I remember spending a lot of time fixing merge conflicts like a sucker. The one I liked, for its theoretical aspects, was darcs (as I was also leaning heavily in the Haskell ecosystem of the time).

Anyway, in short for me git overtook mercurial because it was easy for me to hop around multiple branches, pick off individual commits, and rebase commits (I was still pedantic about how I formatted my commits before a PR, nowadays, not so much).
Git set out to solve the problems the Linux kernel development faced, which is not particularly "Agile" and doesn't do CI/CD.
It's been working for me so far :)
I'm not sure it's so obvious that it does it well. The thing about the tech industry is there's a lot of cargo cult and leader/follower mentality. There are plenty of shops that use git just because every other shop uses git. Chances are, most of them don't need anything nearly as complex as Git and other version management approaches for their project would suffice just as well.

It's sort of how a lot of shops decide they need to incorporate 'AI' into everything, or they need to use microservices and Kubernetes to solve their problem. Some of it is just resume driven development but a lot of it is just observing and following trends.
BS, doctors give the samples to friends and family, and some to patients. Doctors can't know a patient is poor. In private practice, the doctor assumes the patient isn't poor.
So building new nuclear power plants, expanding carbon capture technology, and planting more trees are not real climate action?

What exactly is real climate action? Hoping that renewables and batter technology can scale up to completely decarbonize energy use?
Hi, this is awesome! As a heads up, my partner is on Android and the sharing function does not seem to work. Even so, this app is great. Thank you for sharing.
Lisbon is pretty great. Beautiful, cheap, great weather, good public transit, artsy, increasingly international and the language is fairly accessible.
> > At the end of the day, credit cards are still significant better for customers.

> Yeah, I don't know.

Credit cards are safer for the consumer, by regulation. So that much is just factual.

You can set up automatic payment for your credit cards if you like, no involvement. I don't because I like to review each line item and control when I post the payment, but it's possible.

A debit card is basically an open port into your bank account. A credit card is a firewall which buffers all withdrawal requests for a month (or so) until you approve them (or reject any fraudulent ones).
I am used to US credit cards and moved to Germany a few years ago.

In Germany credit card chargebacks are very cumbersome. I had 3 banks' customer service tell me at first that it isn't possible (like they had no process for it or the agent never did that or is too lazy) and then the next agent said it works but has huge-list-of-drawbacks-fill-9001-forms-and-waste-days effort.
2 massive whoppers in the just the first few sentences.

> Helion is by far the most promising approach to fusion I’ve seen.

> Helion has a clear path to net electricity by 2024
There are a number of credit card issuers in the US offering 1.5% cash back.

Suppose you charge $1000 each month at the rate of about $33 per day, and also pay it off when the bill is due.

In a year, you've gotten 1.5% of $12,000 back which is $180, but you could also look at it as though they are paying you 36% per year to use (on average) $500 of their money.

The latter interpretation makes it seem irresistible to me.
Under the hood, “forks” are really just fancy branches. So realistically that would also be git log
I'd be fine with more nuclear power plants, but if wind/solar plus batteries are cheaper, that's what's going to get built.

Also, renewables don't require a high degree of trust in the human operators to manage risks appropriately. I think that's really the main sticking point with nuclear; reliable reactors can be made, but how do you manage the humans who maintain the plants in a way that's not susceptible to corruption or corner-cutting?

If nuclear can be made to handle more of our energy needs for a reasonable cost, then that's a good thing, and if it can be made cheaper by updating regulations without sacrificing safety, then I think that would be awesome. But I think we should plan for the future under the assumption that most of our energy will come from renewables. That's the lowest-risk plan that doesn't require major regulatory changes or new technology. (Apparently there are also some major lithium iron phosphate patents that are expired or expiring soon, which should open up cheap battery manufacturing to companies outside of China.)
I think the explosion of the internet sort of squashed some of the great distributed feats. Having blazing fast internet connections (at least relative to source code transfer) available all over the world makes decentralization less important (in the normal pull, change, push model)
The author is comparing with github/gitlab as fossil offers both VCS features, like git, but also features a Web interface with issues, wiki and forums, which you can only get with those third party products.