At my large corporation, we are required to use a centralized React library for internal apps. So it is not “react by default”, but instead “React is the only choice”. 100% agree that our path out is for the central library to be reimplemented as web components to open us up to using whatever framework we choose.

That's a very normal thing for a big shop --- if it wasn't React it would be something else --- so kind of tough to pin that constraint on React.

Europe accounts for 31% of baking mix sales while North America accounts for 24.5%.

https://www.grandviewresearch.com/industry-analysis/bakery-p...

> seem cake mix in stores my whole life

I checked my lagest local grocery store chain and they do have one brand of cake mixes. They never really crossed my mind before.

Chocolate chip and two types of pundcake.... though that's both among the simplest baking recipies so i still don't quite see the point.

There's also pre-made pie dough, that i could see using.

Pie dough is quite simple, but I imagine they use some chemistry to improve, as per the other food chemistry posts...

Yes and no. Its usually butter based dough needing to be kneaded finely and left to rest an hour before use, prefferably pre-baked in pan before adding filling for best result.

You can get it quite quick with a food processor or a kitchenaid mixer, but kneading such a dough by hand and having the time to let rest, flatten with a rolling pin and pre-bake in pan, push pie up a bit in the effort ranking.

So i feel there is real value in quickly putting a pre-flattened doough sheet in a pan, especially if some chemistry can skip the pre-bake step.

So i see the appeal much more for this product over pound cake mix which is just four, sugar, egg and leveling agent.

The EU contains about 30% more people than the USA alone. (450MM vs 340MM)

North America overall contains many more people than the EU. (340 + 129 + 40 for just USA, Mexico, Canada, plus another ~50MM in smaller countries. 560ish total)

The EU is only around 2/3 of the population of the continent of Europe.

Europe is also somewhat poorer than North America, to be fair.

Is cake mix expensive? Wouldn't powdered milk and egg be cheaper than real eggs? Is it actually more expensive to bake with cake mix than with short shelflife milk and egg?

These companies must be making bank.

You’re the only one who put “Open” in there. Both your parent and grandparent said JDK.

GraalVM is a separate product developed by an unrelated team. Its enterprise flavour is not considered an enterprise flavour of the JDK. The closest to an enterprise JDK from Oracle I can think of is the "Enterprise Performance Pack" for the 12-year-old Java 8, but it has nothing that isn't in the free and open recent releases (which actually include many more performance enhancements).

The idea there is that it's cheaper for companies with legacy software that isn't actively maintained to pay for some portion of the performance improvements in modern JVM generations than to ramp up maintenance to upgrade to modern Java, and this can help fund the continued evolution of OpenJDK.

what happens when the legacy code is migrated to the new java, which is supposedly easier to upgrade post java 8? who will pay for long term support if upgrading is so easy?

There's always legacy systems; it's part of the natural lifecycle of software. Also, what you buy is any kind of support, regardless of the version you're on. Support doesn't mean access to patches but an SLA for the tickets you file.

Because people keep forgetting Java is like C and C++, there are plenty of JDKs to chose from, and not all of them are related to the same codebase.

The immigration raid and what was happening at these plants is 100% different…not sure how you can even pretend they are the same. The system they are discussing is one where you’ve already been in the US legally for 6 years.

How is diff less effective? I see the diff in the formatting I prefer? With sed, I can project the source into a formatting most convenient for what I’m trying to do with sed. And I have no idea what you’re on about version control. It ruins sending patch files that require a line number around, but most places don’t do that any more.

What I would be curious on is tracing from errors back to the source code. Nearly every language I’ve used prints line number and offset on the line for the error. How that worked in the Diana world would be interesting to learn.

I can only recommend difftastic[1], which is a language aware diff. Independent of linter that shows the logical diff, not an assortment of characters or lines that changed.

[1]: https://github.com/Wilfred/difftastic

Where Europe is ahead of the US is really in neighborhood wide geothermal for heating and cooling. The US tends to only use networked multi building geothermal for corporate and university campuses while having little central planning for a neighborhood of individuals to migrate to geothermal.

You have to dig them up to fix the leaks…

Citation needed. Curbs are expensive. Sewer pipes are expensive (for the last 60 years, Montreal has separated rainwater and wastewater sewers in all new construction).

Montreal likely doesn’t do it because it would lower the density of buildings.

How so? This proposal doesn’t require you to run `git lfs install` to get the correct files…

If the architecture is irrelevant and it's just a matter of turning it on by default they could have done that with LFS long ago.

Git lfs can't do it by default because:

1. It is a separate tool that has to be installed separately from git

2. It works by using git filters and git hooks, which need to be set up locally.

Something built in to git doesn't have those problems.

But then they could have just taken the LFS plugin and made it a core part of git, if that were the only problems.

If it didn't have those problems, it wouldn't really be git lfs, it would be something else.

And what happens when an object is missing from the cloud storage or that storage has been migrated multiple times and someone turns down the old storage that’s needed for archival versions?

You obviously get errors in that case, which is not great.

But GP's point was that there is an entire other category of errors with git-lfs that are eliminated with this more native approach. Git-lfs allows you to get into an inconsistent state e.g. when you interrupt a git action that just doesn't happen with native git.

It's yet to be seen what it actually eliminates and what they're willing to actually enable by default.

The architecture does seem to still be in the general framing of "treat large files as special and host them differently." That is the crux of the problem in the first place.

I think it would shock no one to find that the official system also needs to be enabled and also falls back to a mode where it supports fetching and merging pointers without full file content.

I do hope all the UX problems will be fixed. I just don't see them going away naturally and we have to put our trust in the hope that the git maintainers will make enjoyable, seamless and safe commands.

The article is specifically about how Apple doesn’t use the double Irish loophole any more as they moved to Jersey…