skysight-inc/HackerNews huggingface dataset:
Yeah, I'm familiar with feature flags, but that doesn't really solve the problem of needing well-defined releases and that these releases themselves need to be patched and possibly supported for a long period of time as determined by contract or support commitments.

Also feature flags are not going to be able to cover all code changes. For example, it's hard to put code refactoring behind a feature flag.

Finally, wide-spread use of feature flags as a type of in-code branch certainly seems like code-smell to me. It's fine for a while, but after 20 years you're going to have a difficult time maintaining that repo unless it's done with sufficient discipline that those feature flags are quickly removed once the feature hits production. It will also screw with your automated static analysis tooling.
In general, as the sibling points out, runtimes can't tell which dependency a particular API call is coming from if it's all bundled into one blob. Unfortunately most APIs, for example in WASI for ease of writing POSIX code, don't have an argument for a capability assertion to be made. So you can only realistically associate one set of capabilities to a single VM unit.

So what you actually need to do is split your program into more VM units, not unlike code splitting in bundler-integrated JavaScript HTML5 routers. You can build that atop a WASM runtime, if you pass the ability to call other WASM modules into other WASM modules. And then you could pass literal capability tokens around. You just need to split your code up.

Then you can bridge them back again with trusted code, and you can add additional constraints on API calls between modules (e.g. callbacks don't work across units, or if they do, then they remember the capabilities they were instantiated with, something like that).

If there were an easier way to have your dependency management system do this code splitting for you, then it would be feasible.
> they both have more robust dependency resolvers (and dnf's is actually complete[1])

> 1: See the discussion of completeness here: https://arxiv.org/pdf/2011.07851.pdf

That's interesting. In what ways are these resolvers superior to pacman? I never had dependency resolution issues. Can you help me understand with concrete examples? Pacman is not cited anywhere on that paper.

> you don't need to resort to one of a dozen third-party ‘wrappers’ in order to use the bulk of packages available in those distros' ecosystems

Are you referring to the AUR? I believe that's more of a man power issue. Arch is a smaller project compared to the other major distributions. There aren't enough maintainers for all packages.
No, I didn't miss it, I was responding to the cynicism about "the news cycle", that's why I pointed out that a pandemic is a different sort of thing than a car accident.

If you are operating at your normal capacity factor but have reason to predict that you are on a trajectory to be completely overwhelmed along with every hospital within reasonable driving distance, it's different than if you are operating at your normal capacity factor and have to send a patient or two to the nearest hospital with more spare capacity.
All abstractions are leaky, but an abstraction meant to never lose the work of a power user is maybe more defensibly leaky than average.
Barbados and other countries mentioned in the article are evolving, while most European countries are devolving and losing both freedoms and prosperity in the collectivist EU.
The lawson criterion is the point at which the plasma is heated by fusion faster than it is cooled by losses. It is a lower threshold than ignition. Even without ignition, you still need to achieve it to produce net power.

Ironically, their efficient method of energy capture actually makes their job harder than for a thermal system where heat losses due to bremsstrahlung and neutron heating are partially recovered; indeed this is the output for a conventional fusion reactor. For helion, only the energy of the plasma is harvested and thus they must exceed breakeven by enough to not just maintain but to heat the plasma by some economically useful amount.
I eat food to charge and can store that energy as fat.
One day you'll understand how a thread works! Don't give up hope!
> Network is more like `git log --graph --decorate --oneline`

... across all forks, which makes the UI much more cluttered than it needs to be. What if you are only interested in commits in your own repo?

Github really does seem to lack a clean equivalent of `git log --graph`.
Again, someone has to buy the reactor. They are in the business of selling reactors, not electricity. They are talking about who is going to buy the reactor. They think big companies who own data centres are going to buy the physical reactors. You are talking about something else entirely.

> Helion’s CEO speculates that its first customers may turn out to be data centers, which have a couple of advantages over other potential customers. Data centers are power-hungry, and often already have power infrastructure in place in order to be able to accept backup generators. In addition, they tend to be a little away from population centers.

They are definitely talking about selling them physical reactors.
> Electric cars will change this though.

Yes, this is what we have to plan for. 20 to 30% of new cars sold in the US will be electric by 2030 (I suspect it'll even be higher than that). Projected to be 45% to 50% by 2035. We'll need more generation and some major grid improvements.
I’ve worked for several us financial institutions, including banks and that exchange seems extremely typical to me. Especially the “hold harmless” bits. Which particular part of that story telling rang false to you?
> Prior to joining the firm, Armen was a member of the technical staff at Bell Laboratories in Murray Hill.

Wow. Bell Labs too.
More like "I don't know what gitref to move (*well, change) if you commit". `git checkout` isn't relative to the current ref is it?
You don't know what data they needed. Maybe they needed reviews or product descriptions. The API doesn't cover everything but it does cover the exact use case I was replying to.
I have to admit I don't fully understand the problem as originally formulated. I've never had trouble figuring out what's going on in a Git repository. I do agree that GitHub's interface for these things is anemic. As for that part, I typically squash-merge on GitHub and that links to the PR, which is good enough for me.
I can't imagine any type of plant I'd like built in a mad rush less than a nuclear power one. I am not against it, but it is not a magic bullet, either.
> this is not because China is reducing renewables but rather it's energy needs are increasing so rapidly.

This is key (also: in the graph hydro isn't accounted for), and the reason why the current observed trend (huge push to renewables, increasing their share despite the rapid energy needs increase) is another key.

> Solar and Wind are not particularly useful given they are unreliable

Their variability can be reduced, maybe even totally compensated, by various methods: continental-scale deployment of wind turbines, using a mix of sources (wind, solar, biomass...), storage, smartgrid...

https://www.sciencedirect.com/science/article/pii/S136403211... shows that is is true in Europe (quote: ""we demonstrate that the European energy system would strongly profit from exploiting the implications of these regimes for continent-scale wind generation patterns."), and maybe also for China (quote: "Liu et al. investigated wind energy complementarity across China, demonstrating that whereas a combination of wind and solar resources over a given area reduces the occurrence of zero-power hours, wind resources alone are sufficient to provide baseline power production, if a large enough area is considered.")
This is literally an article about them closing a round of investment.

What exactly would they gain from keeping this particular card close to their chest?
I'm no longer with that company and it's possible that those devs were incompetent or always chased the next shiny framework or possibly both. But irregardless their output on the whole was about 20% that of those devs who used uncool old tech like Java/Spring and dotNET.
That depends upon where the person with that unique name lives, If the vocabulary is from the native language and the person lives in the same region then they don't have much of a trouble.

Then again non-unique names from native regions cannot be pronounced by non-native speakers, My name is far from unique and native English speakers have refereed to it as 'Ab...followed by several other syllables'.
Yeah, fast internet helps a lot, but being able to grab open source code, work on it, and then push in changes with something better than an email of diffs is certainly nice. The technology of pull requests/cloning has a lot of advantages when you want code to cross organizational boundaries.
Haven't read the paywalled article but the idea that nuclear is clean compared to coal is ridiculous as evidenced by Chernobyl and Fukushima and Three Mile Island and Windscale. Nuclear pollution is about 1 trillion trillion times worse than coal and is sufficiently common - roughly one major nuclear accident per decade to be non-negligible. It's not safe to assume nuclear power is getting safer when terrorism and nations that sponsor terrorists are getting worse.
It must have been a shock to discover that (as in many companies) bosses view employee monitoring/surveillance as a core aspect of their job as "supervisors" (literally "overseers.")
Your credit card gets compromised several times a year? Is this normal? I’ve had like one fraudulent charge in over 15 years of using credit cards.
What costs aren't being paid for exactly?
Fully private — there is no tracking / spying / advertising / etc

That's great! But it's a sad world where that's a feature you have to lead with and not just an inherent assumption :-S.
To be fair the median expert witness retainer is $2,000 and their fee may be a few hundred dollars per hour.

So let’s say this professor was getting paid even 100% of their salary on this one case, that is pretty meager fee to act inappropriately or commit the crime of perjury…which is the context of the university claiming their is a conflict and they would only permit the professor to act as a witness against the government if they don’t receive compensation. Even a fee matching their annual salary is meager fee in context of an act that would result in sanctions and inability to ever act as a expert witness again and/or termination of their non-tenured professorship as well as the professional humiliation.
There are lots of good arguments for nuclear, but considering that the US is the number one producer of natural gas (by, like, 50%) this isn't one of them.
Microsoft have their own functional language. Not exactly an internal protect.
Okay, so if I'm getting this straight, instructing researchers to not research unprofitable drugs is an ethics violation, while instructing them to research profitable ones is good strategy.
>[..]In my experience, they'll tend to have worse vsync issues and tearing.

Thankfully I've been able to avoid that for the most part, but I will say it's certainly easier to avoid with plasma's compositor.

>I doubt i3 is actually drawing shit on the screen faster than Plasma with animations off.

I'd definitely be interested in a raw speed comparison if there was a good method/benchmark, but I don't think that has ever been my limitation (although if I were running on lower spec hardware everything counts)

Plasma certainly has more features, but it's still definitely heavier than i3 (or most (all?) tilingWMs), LXQt, icewm, and the like.

On decent hardware there's not a huge point other than preference, but when you've got 2GB of RAM and a 12 year old CPU every bit helps https://i.imgur.com/vZszQFE.png
Salvia is a pretty fascinating psychadelic. I wouldn’t call the effects pleasant, but I wouldn’t call it unpleasant either. If the high lasted longer it would be unpleasant as it can be quite strong.
So it probably wasn't constructed with proximity to a fault in mind. Still, just about everyplace in California is near a fault line.
I'd second this. Been a good read. Learnt a lot. Now I have a DSL for some really strange usecases and its been a blast. Never thought having an interpreter of my own would be so much fun.
It’s good to have too much capacity, rather than just the right amount, as Texas learned during last winter.
Honestly, if you fail to comply with GDPR, you probably failed to comply with laws stretching at least back to 1995. GDPR mostly changed ability to hunt down violations, and further harmonised and clarified laws that were already in force. It's easier to comply in post-GDPR world than before it, and there's general guidance for let's call it "honest mistakes" as well as coverage on some internet-specific issues.

And Valley is pretty much there because when the long chain of capital-hungry events was building it up, we were still rebuilding from last war while funding preparation for take three thanks to Truman.
Guide to DRM-Free Living: Literature
> simply cannot do it, unless I clone the entire repo for every change

Note that you can have multiple working copies from one clone for a few years now. git worktree add <path> <branch>
"I use significantly less electricity now compared to 15 years ago."

You're lucky.

Often the more financially well off one is the easier it is to introduce energy efficiencies. Many poorer people are handicapped by the cost of house repairs, insulation upgrades, window double glazing, etc. Moreover, the condition of their houses are more likely to be in a worse state in respect of necessary maintenance, this further reduces their starting base. The same situation will also apply to their motor vehicles, they'll be the last to convert to electric cars, etc.
The best source control system I have used to date is Google's G4 with hg (mercurial) bindings, I think they called it Fig if memory serves me. I'm not sure if there is any product that is similar to it outside of Google.
Yes, huge amounts of it. Aside from electrified transport, there’s also a lot of industrial processes that use natural gas for direct heating. We need a lot of extra electricity generation to cover these cases. Some of these can be shifted when renewables are overproducing, others cannot.

Our grid literally cannot handle the demand that electrifying transit and industry would create.
This is awesome.

Always max out the 401k. Especially if you get an employer match.

Follow the simple steps outlined by Dave Ramsey / John Bogle / Tony Robbins / etc ad naseum. Accumulating wealth is easy and fairly certain if a few simple rules are followed.
Why bury when all those lines needed was replacement of worn parts? Burying power cables is expensive and increases maintenance costs an order of magnitude.

Much cheaper to replace hooks that are worn through so the cables don’t fall off the tower and start a fire.
Investing in less CO2 intensive building technologies. (The carbon dioxide emissions from the production of concrete are so high that if concrete were a country, it would be the third-largest emitter of CO2 behind China and the United States.)The central ingredient in concrete is cement, which is made by crushing limestone and clay and adding iron ore or ash. The mixture is heated in a kiln to more than 2,600 degrees Fahrenheit, a process that consumes vast quantities of fossil fuel.

When heated, the calcium carbonate in limestone breaks into calcium oxide and carbon dioxide, which is released into the air. The calcium oxide is ground with limestone and gypsum to make cement.

Half of the CO2 emissions in the production of concrete come from the reaction that breaks up the calcium carbonate and the other half from the fossil fuels required to heat the kilns and transport the materials.

Things we should also consider.
Getting rid of cars.
Investment in mass International and intranational public transit.

Meat alternatives that require less physical space.
reining in massive fishing fleets (half the oxygen and half the carbon captured comes from the ecological systems in the ocean which we ravage)
Invest in renewable energy, like tidal, solar, geothermal, etc

Even if we were to go 100% nuclear tomorrow (which just isn't possible, we'd (the entirety of earth) would run out of nuclear fuel in 90 years), that would account for about 1/4 the carbon emissions of the planet per year.

Climate change is more than just the amount of CO2 in the atmosphere, it's about how we as a species, integrate with the rest of the species on this planet.
Where all 50 states stand on making daylight saving time permanent
I feel the pain, seeing non-trivial updates for Ruby, Elasticsearch and Postgres (thanks AWS) this year.

Can not agree with the React part though.

They keep so many things backward compatible. React 16 is 3, 4 years old now? I've updated pretty big code base from early 16 to latest 16 version painlessly - like in a day. Used some of the available code-modes for some really old part of the project. It worked flawlessly. Currently there are console warnings to fix certain things and that is it. No breaking changes, no nothing.

Now, React 17 will be a problem - there are a lots of 3rd party UI libs that will not work with it. But I think we are pretty well set to use react 16 for the next couple of years, making it work for 6, 7 years total. I think that is a century in terms of FE and is great.

Also, "...React pulling a sneaky on everyone and introducing hooks, which was a pretty bad move, especially if you needed to migrate to them" - just don't use hooks then - no problem.
Data centers absolutely do not go for unproven and flaky electricity sources! They go for the most boring, proven, and even downright inefficient sources. They need robustness above all things.

Untested nuclear reactors (fusion or fission) are about as far away as possible from what they want as it is possible to get.

Not to mention that many data centres are bang in the middle of high density urban areas, or at least reasonably close to them, typically in some industrial area on the outskirts of town.

No council in their right mind would approve any kind of nuclear power without years and years of environmental impact studies, justifications, reams of paperwork, etc...

You might argue that it's "safe", but the bureaucrats won't care about your opinion. They'll be worried about perception in an era where people set communication towers on fire because they want to stop 5G "radiation".

Fusion is precisely the kind of technology that is best implemented as base load in a standard power plant type configuration. Far away from big cities and scaled for efficiency.

It makes zero sense to plop something this esoteric down somewhere downtown to occasionally power a data centre during a rare power outage.

This "suggested" use case is 100% intended to appeal to people like you, the "YC News" crowd type. It is absurd on its face. Hilariously improbable. But it sounds cool and it got you talking, so a successful marketing trick, I suppose.
Git merge does something pretty awful; it takes multiple changes and turns them into a single patch bomb in the destination branch.

What if the branch has 17 commits, the 9th of which introduces a regression? Moreover, suppose that the 9th commit of the original branch didn't exhibit the regression; rather, its change had that effect when it was merged into master.

You need all 17 commits, in their rebased versions, on master, so you can search through their history (e.g. with git bisect) and discover that the 9th one broke it.

Rebase is the correct thing: it calculates a new sequence of commits that are individually merged, and retained as separate commits that you can dig through in the new branch.

What's missing is this: the rebase of an entire branch into a new branch should record a second commit parent (for the final commit of the operation), pointing to the final commit of the original branch.

Like this:

X-Y-Z--<< branch
/
-A-B-C-D-E--<< master

rebase it:

X-Y-Z--<< branch
/ \___
/ \
-A-B-C-D-E-X'-Y'-Z'---<< master

where X', Y', Z' are the rebased versions of X, Y, Z.

A regular git rebase is missing that second parent link from Z' to Z. You just get this:

X-Y-Z--<< branch
/
/
-A-B-C-D-E-X'-Y'-Z'---<< master

The only way you can identify that Z' was cherry-picked from Z is by clues in the commit message: identical commit message text, or something like a Gerrit Change-Id.

Possibly, each cherry-picked commit should have the original as its parent:

X-Y-Z--<< branch
/ \_\_\___
/ \ \ \
-A-B-C-D-E-X'-Y'-Z'---<< master

now that is almost like iterating over the branch and doing a commit-by-commit merge.

At first we pretend that the branch is just X, and merge it to get X'. Then we merge Y', and then Z'. We never merge a sequence of two or more commits into one.

If you do that, you have both: nobody can say you're not merging, but you have the effect of a rebase.

A rebase (cherry-pick) is a kid of merge: of one commit (at a time), without recording all the parents.

A case can be made for rebasing commit-at-at-time using merge. (Not for private work, obviously; just already published, permanent history).

The nice thing about rebase is that it doesn't introduce the crufty parentage, which makes it ideal for rearranging unpublished history and then presenting a clutter-free end result.
A solar farm that produces the same power as a nuclear power station (1GW) requires 1000 3MW turbines (33% efficiency) at 700 meters apart.

That's 500 square kilometers of turbines (something like 200 square miles).

I once did the calculation and it came out to something like 10 times as much concrete and steel to build the turbines as it would have taken to build the nuclear power plant.
You might be interested in my project https://github.com/arxanas/git-branchless, which is intended to replicate such a workflow.
Corollary: Do hard things more often, per Martin Fowler - https://martinfowler.com/bliki/FrequencyReducesDifficulty.ht...

Upgrade everything all the time and it will never be hard. You'll have full context for breaking changes, and the diff from A to B is always smaller than from A to Q, and less likely to break in strange and confusing ways.
It will make the “text” on a pdf with only images searchable and selectable.
Anyone can contribute to an IRA, or probably a Roth IRA if they're not well off.

There's a path to tax-advantaged wealth for almost everyone.
I do care a lot about climate change. That's why I thought it was important to remind everyone who the real troublemakers are. If you actually want to cause a significant positive impact on this world, you should redirect your efforts there. Cryptocurrencies are nothing but a distraction.

Also, "cheerleading and shilling"? Do you see me calling people nocoiners?
A lot of places do what's called cogeneration: rather than buy electricity and gas, they just buy more gas and generate electricity on-prem, using the waste heat for heating their facilities/boilers/whatever.
The pagan saints of feminism.
As far as I understand, it takes a PDF that contains only image data (e.g. a scan of a price of paper) and uses OCR to recognize the text, then overlays the text on top of the image in the output PDF.

It would allow you to take a physically scanned document and create a PDF with selectable text you could copy+paste, search over, etc.