skysight-inc/HackerNews huggingface dataset:
I have definitely felt this pain when navigating i to the past to investigate the origin and evolution of changes.
I'm guessing they're referring to conflicting transitive dependencies. Everything works fine when you use version 1 on date A. A couple years down the road, all those depends have matured at different rates and the top level packages all specify different versions of the same transitive packages so you have to try to line them all up.

On the other hand, the longer you wait to update, the worse it gets. Updating more frequently you can suss out packages moving quickly vs slowly vs not at all and address the problem before you're in update paralysis
To be clear, they did “damage” was to our bottom line. Most sites don’t capacity plan for random cliff walls of 2-10x traffic (clearly we should!). We’re scalable enough to handle that traffic after a period, but a) it caused intermittent periods of low availability (costing us money because we didn’t generate income the way we normally do) and b) cost us money from scaling all our services up.

It’s just selfish. If you’re going to take the product of other people’s work in a manner they don’t consent to, at least do it in a way that doesn’t cost them twice over.
> The nuclear power industry has really only existed for a generation.

More than 60 years is, by the usual means of counting generations, at least two and pushing three generations.
I’d answer that if I knew what they did. But I’ve only used git for 3 years now, so still a novice I guess.
I noticed my wifi router had an "update firmware" option. Hmm, I said, that sounds cool. Go to the trouble of looking up the manufacturer's support page for my model, download the file, poke it into the update box, click go.

Now all my IOT devices on the 2.4ghz now fall off the network after ten minutes and have to be manually restarted. I'm sure if I spend the time to look into it I'll find some fascinating difference of opinion regarding a detail of the 802.11b spec between the manufacturer of my very cheap wifi router and the manufacturer of the very very cheap wifi radios in my internet-connected thermometer.

Instead of doing that, I factory reset the router, and spent fifteen minutes restoring various configuration details from memory.
> Seller warrants that to the best of their knowledge, no existing claims or liens exist on the transferred Soul and agrees that any prior commitments that are in their power to dissolve are formally dissolved by the formation and signing of this agreement.

Does this mean that Christians would be bound to being baptized prior to selling their soul?
Something I consider to be a "red flag" in the press releases of any new kind of energy source, power plant, or engine is when they start talking about the potential applications of something fungible like electricity.

E.g.: In the Tech Crunch article linked elsewhere in this discussion there is this quote:

"Helion’s CEO speculates that its first customers may turn out to be data centers"

Do you know what else a 50MW generator could be used for? Anything. Anything that electricity is used for now. Why talk about things we all already know? Why talk about specific applications?

It's like a car company advertising that their new engine could be used to drive to Starbucks to get a coffee.

Once you notice this pattern, you'll see it everywhere in Free Energy / LENR circles...
I've used RCS, SCCS, CVS, Subversion, SourceSafe, ClearCase, AccuRev, Perforce, and probably at least one more I've forgotten. ClearCase was a garbage fire for reasons of performance and stability, but none of them had an internal model that was as much of a hot mess as git's. It's not the OP who has forgotten what things used to be like. Maybe you-now understands git better than you-then understood CVS (for example), but that might have more to do with personal learning curves than with inherent complexity.
>Seriously, I hate scrapers. I hate the people who make scrapers. I hate their lack of ethics. Fuck those guys.

if a scraper is effectively DDoSing you, call it what it is -- a denial of service attack.

i've found from experience that most scraping attempts originate against host-sites that are generally user-hostile; no APIs to use, JS tricks to bother user browsing, or groups that profit from first-mover advantage and thus try to obscure data.

So, if your sites are commonly the victim of scrapers that are harvesting publicly available data i've found that it's more useful to ask myself what alternatives I could provide those that feel the need to scrape.

As for a 'lack of ethics' on how publicly available data is wrangled -- well, i'll just say that I feel that it remains the responsibility of the administrator rather than being something to push the blame onto clients for. There are plenty of technical avenues to pursue before appealing to morals and ethics for help.
A DIY lawn-sized version… but with flames instead of lasers. https://hackaday.com/2021/09/11/dont-sleep-on-the-lawn-there...
> [Reshade] is a generic post-processing injector for games and video software. It exposes an automated way to access both frame color and depth information and a custom shader language called ReShade FX to write effects like ambient occlusion, depth of field, color correction and more which work everywhere.

From https://github.com/crosire/reshade
Founded in 1992:

https://en.wikipedia.org/wiki/Ambrosia_Software
and dangerous for us?
Yes, that’s pretty much what I suspected.
Yes coming from Mercurial I find Git very confusing.
Click 'commits' on any repo and you will see the graph.
Ah, so this is a revamped UI for Joe's tool, I've seen his website before. I think the main reason why his tool didn't get much traction is that it didn't offer any tangible improvements over existing tools. Wally, one of the oldest available tools, set a pretty high standard right from the start. Later came Half-Life Texture Tools, which added sprite-making capabilities, so it became popular as well. And recently, I made WadMaker/SpriteMaker, which enables a much faster workflow by removing several tedious steps (no more exporting files, adjusting palettes, manually managing wad file contents, etc). People are finding it useful so it's slowly getting some traction, but it has also taken several months of working on updates, writing tutorials and helping people out.

The wad and sprite formats have already been documented by others (most notably by Yuraj), and if you're a bit familiar with the HL modding scene then it isn't hard to find source code that deals with these formats, so parsing was actually one of the easier parts. Figuring out how to convert true-color images to 256 colors without too much quality loss was much harder.

If you're interested, here's how I'm making palettes: https://github.com/pwitvoet/wadmaker/blob/master/Shared/Colo... . It starts with creating a color histogram (the 'frequency list'), and then it treats these colors as 3D points within a 256x256x256 'RGB cube'. It calculates the bounding box for these colors and then splits this box along the longest edge. It then takes the box with the most colors and splits it up, and repeats that process until it has created 256 boxes. Ideally, these boxes will all be fairly small, which means that they contain very similar colors. A palette can then be created by taking the average color of each box (weighted by color frequency). When combined with dithering this produces quite reasonable results: https://raw.githubusercontent.com/pwitvoet/wadmaker/master/d... (but clearly there is still room for improvement!)
if you want to allocate physical memory, allocate address space with mmap() (malloc with options) and use mlock() to wire the physical pages to the addresses in your process. mlock() will fail if there's not enough physical ram to satisfy your request.
> Corporations will never rise to the legitimate use of force. If they do, they'll be governments.

Corporations, as creatures of law, are an apparatus of government. And they’ve participate in the legitimate use of force from the very dawn of corporations as a thing.
What I don't understand from these groups is why they don't go after nuclear _after_ coal, natural gas, and oil are gone from the grid. There are arguments against nuclear, but they aren't that great when there are still fossil fuel plants operating.

Also, a pet peeve of mine is when people say "replacing nuclear with zero-carbon sources" (as per the wiki article). That doesn't exist. There's energy sources that have zero operating emissions, but nuclear is one of them. But if we talk about lifetime then there's nothing that fits this criteria. So I don't get why this is in opposition.
My developer environment is all inside docker, which I assume significantly reduces the attack surface.
The interface is very attractive -- high-resolution pictures of the various coffees, nice fonts, and a clean design. My guess is that graphic designers designed the images and interactivity without any considerations of performance. Then that design was given to developers to be shoe-horned into a machine not capable of handling it.

Possibly different teams contracted out to do both jobs. The design is done by one team, finished, and then handed off to the next.

I'm sure the interface could be tweaked (remove some animations, lower the resolution, etc) to make it usable but instead there was a complete failure of management and it was shipped as-is.
This is one particular tax/policy, maybe it's a hasty generalization to assume everybody is against all their policies.
> Right, it's hard to see what the advantage of debit would ever be.

Not being able to indebt yourself is THE major advantage of debit card. Not everybody in this world is reasonable when it is about spending and finance management.

In some European countries with a more conservative mindset related to debts (Germany, France, ...), people will tend to have the exact opposite stance :

"Why would I ever need a credit card ? It is dangerous. My debit card is accepted everywhere"
You'd presumably need the parent to also do a system call to mark pages read-write after forking, and that would need to include the stack pages, and that sounds like lots of fun; especially since sometimes library functions fork (although most of that is to fork/exec and more specific apis for that exist now). Not that it isn't loads of fun anyway, but woe betide thee who forks and threads and makes the other threads have a read-only stack.

Probably you'd get people just marking as read-write and returning in sigsegv handlers, which I'm sure has great security properties... OTOH, at least there's an opportunity to deny the remap in the handler and get a decent crashdump from the program or a sliver of hope for managing the situation.
Does Taiwan pay taxes to China that its provinces pay? I haven't seen this discussed anywhere, but I'd assume if they don't, and China never went after them for it, then they've acknowledged that they are a distinct non-provincial entity.

Anyone know?
...or bzr, or monotone, or other contemporaries implementing extremely similar models. Git won because of its author's fame in an entirely different domain; both its use for the Linux kernel and the existence of GitHub are secondary to that.
So every version of every dependency of every package needs a review? It only takes one version of one dependency of any software package to be compromised by supply chain.
You (and the author) are not alone:

https://xkcd.com/1597/
I don't see the issue. This is how people fix everything else, it is what comes naturally, and it works every time. I would much prefer it this way, than what Fossil appears to do in section 3.3 of this article, having a single copy of the database per system.

mkdir ~/fossils
fossil clone https://sqlite.org/src ~/fossils/sqlite.fossil
mkdir ~/sqlite; cd ~/sqlite
fossil open ~/fossils/sqlite.fossil
Do you mean the UNIX way (cp, diff, patch)?
West: China invented gunpowder and failed to exploit it.

China: West invented nuclear power and failed to exploit it.
Helion is a non-ignition fusion reactor. They aim to avoid the need for ignition by having efficient energy recapture. The website goes into more detail, and the prototypes have demoed this capability.
the former is an ethics violation, the latter is just a good strategy to win against the multi-armed bandit (which is how resource portfolios are managed at pharma).

many pharma do invest some of their portfolio into things that are unlikely to have short-term or any payoff, and many of them also maintain compassionate programs to get expensive drugs to people who wouldn't be able to otherwise afford them. They do this because they are highly profitable, which unfortunately is as much explained by their marketing acumen as much as it is by solid research and development.
Welcome to Docker, I love you
"Perfectly good" Diablo Canyon was on the fritz throughout 2020 and 2021 and was the proximate cause of August 2020 capacity-related blackouts.

It is End of Life.

https://www.eia.gov/electricity/data/browser/#/plant/6099?fr...
Why do you say that? Not agreeing or disagreeing, just curious what the fossil fuel industry might have to gain from pushing adoption of nuclear power.
Where does it show the branches and merges?
As someone who has spent the last year or so trying to make Ethereum more stateless I strongly disagree that it is an easy problem to solve :)
I don’t care about GIT. Perforce is my favorite. Takes an hour to understand everything to be productive.
I used mercurial for years before being forced to use git, and historically hg came first (by only a few weeks, but still first)
As the poster pointed out, he's coming from Mecurial, which is a DVCS similar to Git.
Eureka CA?
I do own one. It was a gift for my parents’ wedding in 1957. The cord has been replaced twice but everything else is original.

You put bread in. It goes down. About 20 seconds later it rises, toasted perfectly.

It seriously is the greatest thing since sliced bread.
Barbados’s long-drawn-out promise of a republic
Right, I know that there are just a handful of banks that are porviding conncetion flows.

I had experience with Capital One I think, their connection flow was horrible and broke the UI of your app: Basically your user had to go into a Capital One webpage (which was pretty ugly, specially in mobile) and then there were several checkboxes that they had to click through to allow specific accounts to be "seen" by the Plaid like services. Then they took you back to your application and if the user selected not to share any account, your application would basically crash.

I cannot imagine the UI hell that Plaid will be when every bank implements their own propriertary flow for approving account visilibility.
I don't find this particular argument compelling, because there are other languages (e.g. Python and Golang) that have managed to make their way into the mainstream despite facing the same "we only use Java" challenge that hurts Haskell's adoption.
HK was not in the same situation since 1997. It was officially a part of China at that time. No comparison possible. HK does not have its own standing army.
I have discovered a truly marvelous proof of this, which this commenting space is too narrow to contain.
You misread my comment. 80% was in reference to a probability of failure. I think any chance of success 1:4 or greater can't exactly be called “incredibly low [probability] of success”, and even 1:4 seems unduly pessimistic.
The actual build that you provide to customers will run code from many/most/nearly all of them, I think your dev machine is the least of your worries
Trickle-down economics is different.
probably at forming societies, protecting each other - and so ourselves - from harm.
If your git history were a tree: cherry picking is ripping a leaf off and gluing it some arbitrary place on the tree, fast-forwarding is ripping the leaf off and moving it to the end of the branch it’s on, and rebasing is ripping a branch off and gluing it somewhere else.

EDIT: cherry picking is actually making a copy of the leaf and gluing it elsewhere. And fast forwarding isn’t really moving the leaf, it’s taking the leaf you call BRANCHNAME and now calling a leaf further up the branch BRANCHNAME.
I had a similar experience when I was a kid, with Gentoo rather than Arch.

It doesn't stay hard for very long. And when it gets easier, it stays easier basically forever, no matter what distro you use.

Manually configuring everything with Arch is a pretty good way to learn a lot about what goes into a working GNU/Linux system, and not as painful as some people make it out to be.
There have been several leaks and you know, maybe a state with a lot of earthquake activity isn't the best place to put a nuclear reactor.
If doctors go off-label they better be damn sure it works.
We're building a solution to solve exactly this at phylum. I'm not trying to be a sales shill, but if anyone is interested in discussing ideas on how to best defend open-source libraries from these types of attacks, please get in touch, I'd love to hear from you!

We're consuming everything we can about a package to figure this out. We've built a static analysis system to reason about code (it's not perfect, but we're getting better and better). We process all the data we can get, then build analytics, heuristics and ML models to extract evidence. The evidence is then pieced together to identify software supply chain risk.

In this case there is a lot of signal to show both bad and suspicious things are happening.

1. Obfuscation: this creates a comparatively deep AST of the code, and isn't difficult to identify.

2. Command execution: curl, wget, LOLBINs like certutil are pretty easy to identify. This isn't a slam dunk every time you see it, but it adds evidence to a potentially malicious claim.

3. URLs: These are uncommon in libraries and add evidence.

4. Pre/Post install scripts: These are fairly commonly used for other things as well, but invoking node on a source file that is likely obfuscated is a good sign something suspicious is happening.

We're trying to build everything fast enough to make the target far less attractive for attackers before it gets a lot worse.
> Similarly, I personally view the AGPL as a nonfree license

Is GPL a free license?

What’s the factor that makes AGPL nonfree in the way that GPL isn’t?
This would have huge accessibility issues, breaking screen readers and the like.
Oh? What changed?

The old quote: The best time to invest in nuclear was 40 years ago. The second best time is right now.
Why is this surprising? This honestly seems rather unsurprising to me. You have a thing with a high energy density. So you release energy from it. Do you collect that energy or just expend it in a destructive manner?

We can do the same thing with batteries if we really wanted to, but they don't have a high energy density compared to other things (and it would likely be a war crime...). We could easily do the same thing with nitrates (think dynamite) or other bomb ingredients. They all can create heat that we can use to turn turbines and create energy. We just would want to burn them in a controlled manner.
And usually people like your type seem to blindly trust government metrics
Too late in what sense? The problems time out and solve themselves?
I don't think it makes sense to eliminate these, but I'll toss in "Take Commit" as an alternative name that might be more obvious than "Cherry Pick". Still, once you know it, you know it. You'd still need to understand what Take Commit means to use it effectively, but it would make it easier for a dev to learn it the first time.
Certainly, but those other systems stuck around a while after GIT was around because people possibly thought SVN/etc were as good as it gets.

That said, Mercurial and Fossil came out within a year of GIT so GIT at least outcompeted them early on.
Doesn't seem arbitrary to me. It might be cultural though. Somehow the need for privacy is just not something that is in the lived experience of eg many Americans, apparently.

Say we've learned over time that the color purple is really dangerous and needs to be regulated (work with me here for a second) .

Now try explaining "Purple Considered Harmful" to someone who is colorblind. The fact that suddenly grape juice is bad, but orange juice is good... weird. Or the fact that you'd not be allowed to mix tomato ketchup with blueberry jam. And you'd just randomly get fined for trying to sell that "dark green" sweater. Madness!

It would all seem quite arbitrary to the color blind person. Meanwhile someone with color vision would instantly see that all those things are purple, and thus clearly harmful.

The example might seem bit contrived, but something similar might be going on with the European concept of privacy.

People have been hurt due to PII issues in recent history, so one would like to keep control of PII. But try to explain that tingling spidey sense that has kept one's family alive in the last century to someone who has never encountered Nazis or Soviets before, and has instead lived a life of unfettered freedom. That might be rather difficult. Especially if you can't get the base concept across, and need to do it in terms of (very arbitrary seeming) examples.
You can clone my ass when I'm dead.
Looks great.. I'm just trying to find the Windows binary?
I discovered LVGL and used it yesterday for the first time on a board I have developed:

https://forums.raspberrypi.com/viewtopic.php?f=147&t=322135&...
My workplace switched from hg to git. Hg didn't get support for all the other tools we use. The Jenkins hg maintainers were all using git when we checked, and it showed. That is but one example of a tool that didn't work with hg.
New ideas are always built on existing notions. Same with science fiction or any inventions. Nothing gets created out of nothing. Yes it is simple, because that's reality.

Imagine you are completely blind. The concept of colours would exist in your mind because you have access to literature mentioning it. You would know it's a thing, it exist, and yet, because you haven't been exposed to colors, you would have no memories of them of your own.

Now imagine if everybody in society was blind. Because nobody would have been exposed to colours, there would be no memories of them. It wouldn't be a thing as an idea in people's mind. As a result, there would be no way of thinking about the color red, or blue. It wouldn't be part of language either. Why describe something that we don't know that exist?
You are right there is a correlation but not because programmers love complexity.

It is easier to design complex systems and harder to simplify. Also complex systems have positive economic incentives like consulting training books or that if simple will not be sustainable.
The "battery" is actually a capacitor; those tend to have very low energy density compared to batteries, but on the other hand can be charged and discharged very quickly.
Online group event in-app purchase requirement reminder