skysight-inc/HackerNews huggingface dataset:
Sourceforge changed hands and as far as I can tell, the new owners put some effort into getting rid of all the crap and even into protecting users from crap added by the original authors.

Filezilla, for example, initially participated in SourceForge's adware program under the old owner, but after the owner change, actually provided a clean version on Sourceforge (while the version on the website was and still is adware-bundled).
I think some of it also comes from treating symptoms instead of problems.

"Git doesn't do X so I'll just make this tool to add the feature"

One hundred tools and a few consolidations into toolkits later you have a massively complex tool chain scope creeped from some much smaller problem deep down in git
Wind/solar plus batteries are FAR cheaper - - and inherently less dangerous from accidents / tsunamis / terrorists. Those who espouse nuclear want us all to forget three mile island, Fujiyama, Chernobyl, and the numerous future accidents to come. Nuclear also contributes massive thermal emissions to the planet, not in greenhouse gases but in direct, once off thermal.
I had a calculus teacher who would routinely use IOTTMCO for various proofs. Intuitively Obvious to the Most Casual Observer, follow by a 5 page derivation
Network is more like `git log --graph --decorate --oneline`. Still git log, just in a slightly different format.
> remember that lowering the death rate has a linear effect

Intuitively you would expect that the treatment also lowers the rate of spread.
Thinking about my ideal place to live sends me into a spiral of conflicting requirements that ends up with the conclusion that any environment my simple human brain could think up will inevitably fail to satisfy somehow or feel like a static, boring utopia. I love nature and space but there is something about the change and pace of cities that is stimulating as well. The closest to how I’d want to live is probably like Mr. Miyagi with cool old architecture and space to tinker with old cars but nearby a city.
The dirtier non secret is that all the critical parts of a nuclear reactor become radioactive waste. We still have no long term plan for dealing with the radioactive waste that had already been generated.
Reflective Regret: Adventures in N64 Development [video]
And that goes for this Fossil too. When I look at the SQLite timeline, I see confusing swimlanes. I can't make heads or tails out of some of it.
My guess is they could, unless they state somewhere that the license text is licensed with the Creative Commons License or some other permissive license
The problem is nuclear has been the affordable solution for decades and hasn't been built, due to politics.
> This blindness to feminist ethics is revealing. In part it is a function of the era in which they worked, but not completely; they all lived through various waves of feminism. And yet the ethical battles they were involved in—even when about abortion—were, it seems, purely intellectual ones. One can imagine contemporary feminists seeing some maddening abstraction in their work, as they themselves did in the Oxford ethicists. Questions about female embodiment and intersectionality, so crucial to current feminist thinking, are absent from their “gender-neutral” work—and from this book.

Always lovely to read a retrospective of talented women that chastises them for not having been feminist enough.

I've read a few Murdoch novels and recommend them. As I read them, I did not find myself yearning for a discussion of "female embodiment and intersectionality" but your mileage may vary.
> > package managers are pretty similar. The major difference with Arch is you're heavily recommended not to do partial upgrades, but pacman will do it if you really want to. That's a difference in update philosophy between batched releases and rolling releases, not a difference in the package managers.

> No it’s a difference in package managers. Pacman doesn’t take into account library versions when resolving dependencies, it’s why partial upgrades aren’t supported because the only way to ensure every package you have installed is linked against the version of its dependencies you have installed is to have every package on your system come from a snapshot in time of the whole repo package tree.

Ding, ding, ding! This is the same dumb behavior that Homebrew has for the same dumb reason that the lead maintainer discussed here on HN just a few days ago.[1]

Pacman is extraordinarily naive as a package manager. And that's just talking about the absolute bare minimum, main job of a package manager, never mind the more peripheral features (like repo management) that are commonly incorporated into modern package managers like dnf and zypper nowadays, the lack of useful abstractions and metadata (like the representation of vendor and vendor change), or the comparatively obtuse CLI vs. modern subcommand interfaces.

If Arch Linux is for users who want to understand their systems, both because having them set it up themselves is supposed to ensure they understand it better and because its tooling is supposed to be kept simple so as to make it easier to understand, one would think these differences would be more transparent to Arch users. But perhaps in many cases it's been a while since they used other tools, and they never dug that deep into them.

—

1: https://news.ycombinator.com/item?id=29081756
branching is just better in git. sorry. I like Hg, we used it for like 4 years, but switched to git, and have been using it for 10 years now, never looked back.
Looks like there isn't any
The alternative is not being in the trial at all.
“On the road” could easily mean (and IMO most commonly means) flying from their home city to a client site or sites.

Even if driving, most 75 year olds are competent to drive and especially those still capable to work a travel job.
"In the UK at least, it takes decades for planning permission and more decades for design, build, commissioning, and finally entry of a reactor into operational service."

In France it's another matter altogether, there are nuclear power stations everywhere and about 70% of the country's energy comes from nuclear. (Years ago, during a conference I was at in Avignon we even had a tour of the nearby UF6 gaseous diffusion plant and it was almost considered matter of fact.)

Compared to anglophone counties like the US, UK, Australia and NZ, France is heavenly peaceful when it comes to establishing new nuclear plants.

Why is it that if one speaks English one's overly likely to object to nuclear power?
Hey, you somehow removed the login/signup! Nice! :-)
This is something JavaScript itself should be looking at, why we have no standard library for JS I'll never know.
Affordable by looking at any other measure than the balance sheet, maybe.

Nuclear plants that are on time and on budget are exceptions, not the rule.
The reason is they didn't need the complexity of the git model. They came up with their own way of doing it and there's nothing wrong with that.
Arch has an installer. It's had one for years. It was completely broken for a long time but they released a new working version back in April. Unfortunately most people thought it was a joke since it was released on the first of April.

https://github.com/archlinux/archinstall
agreed.. cherry-picking is actually a ridiculously good name.
If a tool attracts enough ire that such arguments arise frequently, then a non-zero number of people are dissatisfied and could be satisfied by other tools. That is worthy of discussion.

Additionally, it is cathartic (and occasionally even productive) to complain about the warts and sharp edges of a popular tool, especially when the tool is the overwhelming the tool of choice in its domain.
I just feel like I have more complaints at meetings where I smell like rum, than when I smell like chewing gum
The same reason LisaDraw was good?

http://www.textfiles.com/bitsavers/pdf/apple/lisa/office_sys...

(The well-written documentation is another nice aspect of LisaDraw.)
> That said, Mercurial and Fossil came out within a year of GIT so GIT at least outcompeted them early on.

Git, Mercurial, and Bazaar all came out within three weeks of each other (late March/early April 2005).
clearcase, lock the branch, go on vacation. yeah good model. And then there's the multisite replication mess.

Maybe they fixed that in the 20 years since i used it.. but that was a disaster.
> Make some great memories with her, take lots of pictures and videos!

Good advice! My friend lost his mother to cancer this year. Not taking more photos and videos at the start of her illness - when she was most like herself - is one of his main regrets.
I remember this is one of those sites where you're not sure which one is the actual download button to click.
Jury finds crypto products are not securities
Sounds to me like you (or Python devs?) should be looking at clone(), which is basically a lower level version of fork() that provides precise control over every detail with which the new process is created, including what (if any) parent memory you want to share.

The manual page is quite informative: man clone
Hopefully it doesn't have any fake bids and the guy that wins pays and doesn't do a return or something shady.
My observation is that it all depends on scale. Huge projects (such as Linux code base) can’t survive with simple solutions (e.g. non-distributed VCS).

Loving complexity for the sake of complexity or sake of job-security or competitive advantage covers only small subset of situations.

There’re a lot more cases where seemingly simple problem has a lot of hidden complexity, and only complex enough solutions succeed at successfully solving it and staying competitive on the market…
Or you could just... look at your statement?
Probably not, but I don’t have a need for that - I’m really just after the video and notifications. I imagine it could be possible with some hacking but I haven’t got it yet.
How do the leaks compare to the continuous streams of coal ash and radon now that the load is being picked up by coal and natty plants?
China is investing far more in renewables than nukes - by 2030 the plan is for 7.7% of total energy from nukes vs 20% from renewables.

If you ignore the colourful but factually incorrect rhetoric and look at the reality, nuclear power is expensive compared to renewables, and renewables will only get cheaper over time.

But more importantly, when you consider a complete lifecycle analysis instead of cherry picking operational emissions and ignoring the rest, nukes are not a genuine low carbon energy source.

https://theecologist.org/2015/feb/05/false-solution-nuclear-...
Yeah, me too. I'm usually only working on a couple of files at a time but then there a conflict. I try to resolve and just keep digging the hole deeper until I just save off my files, do a new checkout and patch them in manually post what ever merge was giving me hell so there won't be any conflicts.
Timely. I was recently force upgraded to Win11. Today in fact.

Last week I force-downgraded after I got an exception because it is my busy time of year. That exception was not respected and I realized fighting it weekly would be the same time investment as fixing compatibility issues.

"What compatibility issues? Win11 is fine, I have had no problems." My coworkers say.

Well on Day 1, 2 pretty important pieces of software crashed and exited on first run. And then the screen snipping tool failed to take a snapshot and helpfully suggested I reinstall the OS.

I actually really like the MSFT stack, but I know enough to avoid any totally new release for a while. I actually feel confident enough that I no longer try and skip major releases (like I skipped Vista, 8).
The Fukushima disaster was a stark lesson that had nothing to do with "militant ecoactivists".
I've seen some talks about implementing this at the programming level but can't remember the specifics. Basically treating dependencies similar to apps on a smartphone where they each run in a namespace or security context and there's control over what data gets passed in and out of the module or package. (In stark contrast to the current model where everything just runs in a global namespace)
Maybe the wrong culture. I use GH to reference source code from my phone quite a lot. I spend half my time on the phone, and when I'm in a meeting, my phone is the obvious way to be in those meetings. Ensuring I have first class access to everything from my phone is a huge priority.

The author may have a point about having better views of the source from GH/GL, but they are absolutely providing a decent experience for it already.
> Here's a fair warning: this article is reductio ad absurdum, therefore you shouldn't take it as gospel.

Yeah, i'm pretty sure the author doesn't know what that phrase means.
Until it didn't.
Solar farms can be pretty big, but we have the space for it. If you look at a map of the United States, there's a lot of land in the Southwest that gets a lot of sunlight and isn't usable for growing crops. It's an ecosystem, and anything that intrudes on that ecosystem will be somewhat disruptive, but as long as reasonable care is taken I don't see it as a problem to use a smallish fraction of that land for solar production.
I just got rid of my 7 year old Breville and replaced it with the Wirecutter recommended Cuisinart.
You're also hiding history if you repeatedly edit the code while you're debugging it, and sometimes undo 17 changes and re-do them differently in your edit buffer and such.

A True Scotsmans non-history-destroying version control system would reveal and be able to replay every single editing keystroke that went into a change.
Ooh thanks! Yeah Frigate is fantastic and has saved me so much hassle. The Coral device is pretty much a requirement for performance but it does work really well :D

I’ll definitely be writing up a few more things soon! I tend to go through bursts of sorting my Home Assistant stuff out.
When I get into a three way merge it's usually just too late in the day, so I will just save off my stuff and merge in manually :) like you said. Two things to compare against is plenty.
Right proprietary software is the root of all evil, I get it, is some people's position. But what are the arguments that made them believe so, that proprietary software is unethical? How and why (do they believe) "proprietary software" is unethical?
Interesting, that's a pretty good illustration of the low capacity factors of wind and solar given that renewables figure includes 356GW of hydro power. And it shows them increasing nuclear power 4x but renewables only 50% by 2030.
does perforce still just allow one branch per repo?
"Listen to me, coppertop. We don't have time for twenty questions. Right now there's only one rule, our way or the highway."
- Switch, _The_Matrix_
Indeed, I wasn’t trying to say you did. Just my own experience regarding a low cost 7b alternative. Nice article.
The heavy metals used in batteries and solar panels are also very toxic [1]. Only reason we don't talk about them is because they can be offshored since they can't be weaponized.

[1] https://www.bbc.com/future/article/20150402-the-worst-place-...
There are actually a few startups that work on improving the situation. One is https://www.planblue.com which builds underwater satellites to build a global seafloor database. A lot of untapped opportunity.
"Detached head" is Git's way of saying "I don't know how to find my children when you say something like 'git checkout abcd1234'". Fossil can do this, so you can point someone to a historical checkin and Fossil won't get lost should you later commit on top of it. Git's warning you that if you do that, you may end up with an orphaned commit.
I think it's misleading to compare peak nuclear generation against peak solar/wind- in order to be comparable with nuclear's baseload, renewables need to be built in conjunction with a boatload of batteries. Otherwise you just end up burning fossil fuels at night time.
I think I'm on 1.4.something

It works, I'm not all that impressed with Angular 47 or whatever they are up to now, nor React, and, to repeat myself, it works.

When you have tens and hundreds of thousands of lines of code and a only handful of people, it ain't worth it to rewrite everything to make it just work the same and look the same.
Your arguments here are a bit peculiar. Have you integrated the judge's response to the situation, where he not only ruled that there was no conflict of interest, but mentioned that the university's actions may constitute felony witness intimidation?
My problem with this, is you can replace "Haskell" with any other language in that sentence, and it still works.
> OpenCore is an impressive piece of software.

100% agree with this in every way possible.

Cannot detract from how many features it (Audio support for boot chimes? Full graphics support? How many Linux bootloaders have that?). Tons and tons of configuration options and settings that you'll need to get a working Hackintosh.

Yes, OpenCore is an extremely impressive piece of software. It would be nice if Linux bootloaders even approached the featureset and level of polish that OpenCore has.
You can DIY. There's also plenty of reputation dependency scanners out there (especially in the corporate world) that will look at license, commit rate, number of committers, release frequency, transitive dependencies, etc and generate "safety" score for you

E.g. "This is maintained by a huge network of contributors who contribute to other huge projects" vs "This is a single developer with a couple commits a year"
Also, solar apparently pollutes a heck of a lot more than nuclear.

It’s still > 100x better than fossil fuels, and I’m still putting some on my roof, but the figures in the article are surprising.
D) they sell cannabis and are not allowed to use the regular banking system.
A fusion reactor vacuum vessel will be bigger than the core of a fission reactor of equivalent power, certainly. But I wonder if a better metric is containment vessel size: there's a lot of very radioactive, very contaminated equipment inside a PWR containment vessel that isn't the core itself.

>orders of magnitude more

Really? Wikipedia says "a typical large 1000 MWe nuclear reactor produces 25–30 tons of spent fuel per year". I don't see a commercial fusion reactor being quite that bad, unless reactor lifetime ends up being very short.

Helion's promotional images keep showing the reactor vessel in a shipping container, which is narrowly true, but doesn't show the support equipment on the other side of a five meter thick concrete radiation shield. No vacuum pump near a running fusion reactor will survive long.

There are all sorts of fascinating engineering problems for a commercial reactor. Photos of the Wendelstein 7-X show it covered with ports for sensors, which you couldn't do with a power reactor, because anything you attach directly to the vacuum vessel will be destroyed. It'll probably end up terribly ugly, the usual intestinal tangle of any industrial plant, a big spiky sausage with pressure sensors at the ends of long tubes to reduce their neutron flux. If you have to mount any sensor directly to the vessel then you use ten or twenty fold redundancy, since replacement is impossible.

After five years of operation, if you go to replace a sensor on the vessel and the threaded fitting crumbles away when you apply the wrench, what do you do? Weld on another one? What's the weld heat-affected zone look like inside the steel after it's spent five years soaked in hot hydrogen, helium, and is richly marbled with transmutation products, dozens of odd elements you don't ordinarily choose to alloy steel with?
> In 2020 alone China added 71.6GW of windpower.

The problem here is that China's share of total energy from renewables has decreased from about 33% in 1990 to 13% in 2018[1].

Solar and Wind are not particularly useful given they are unreliable. Hydro is useful as it is reliable, but after the three gorges dam project, there isn't a lot left on the table in terms of hydro for China.

Note that this is not because China is reducing renewables but rather it's energy needs are increasing so rapidly.

And 58% of China's energy usage - 74 Terrawatt hours - is from coal, and that number is increasing -- 220 million more tons of coal being added just this year[2]

[1] https://www.worlddata.info/asia/china/energy-consumption.php

[2] https://www.reuters.com/article/china-coal/chinas-coal-consu...
IIRC there has never been a date picker in mui, it was in a separate package called pickers, and the recent major version moved it to their labs package.

React Router, however, feels like the one major React package that constantly breaks things on major versions and requires refactoring to get back to where you were.
I had really bad experience with Fedora and Arch Linux just didn't give me any problems. Maybe it's better now, I don't know.
We can't afford to wait or not to hedge our bets. Nuclear is a hell of a hedge since we know it works. We know the French model works really well, but for some reason we, the country with the most heavily armed forces in the world, can't "protect" it. BS, moneyed interests and tree huggers are keeping us from fixing the problem until fusion comes along or uber cheap battery density 100x better than what we have currently comes along.
Complexity is fine in something like a programming language or a text editor where increasing mastery can mean better software and hopefully more money. How do I make more money by learning arcane Git commands?

We don't use DVCSes for their own sake, we use them to accomplish something else. To the extent that the DVCS gets in the way, it's an opportunity cost.
I have various recent widgets for the Amiga 500+ like the ACA500v2 and the open source PiStorm. The Amiga is second to none in my book.
I think the powers that be feel a lot more secure nowadays in their ability to stop a violent revolution since they can track everyone online.
"When your company won't be the first to market, because about 20% of your total development capacity needs to spent on keeping up"

In the world of JS and Typescript this ratio looks more like 80%. I swear that node hipsters at my last job spent four out of five of their working days wrangling with dependencies or their transpilers, linters, packagers, bundlers and whatever the hell else needs to happen to actually make a node program run. Meanwhile the geezers that worked on Java services reliably pushed new versions of their code sprint after sprint, no heroics, no drama required. What the fuck happened to those "modern stacks" that babysitting them takes the vast majority of developers time? It's a nightmare.
Yeah, I, too, read slashdot when those arguments were still current. Now, they just aren’t. The stats above are already levelized. The change in output is also smaller than what people believe: with solar and gas as two independent systems, some improvements to interconnects to allow averaging over larger regions, smart devices on the consumer side picking the right times to recharge (and maybe even de-charge when it’s useful), and the improvements in battery tech, the path is all but inevitable.

It also wasn’t solar or wind power that lead to blackouts in France last summer, but nuclear plants that ran out of cooling opportunities because the rivers they use were overheating. And in Texas, it was natural gas that failed.
Could this be because the existing vaccines were developed to generate immunity against the original strain of Covid? In other words would a new vaccine based on delta produce better results?
Your build number tags the source control commit it was built from in any reasonably sanely implemented CI/CD system.
Does Singapore have similar numbers for hospitalization and deaths?
And the reps are often smoking hot, so docs don't mind making a bit of time for conversation.