A badly made native app is worse than a well built react-native app. There are plenty of anti-patterns that will ruin your native app.
In stories like this its much more likely that they just got sick of refactoring a big ugly code base so got buy in to throw it all away and starting over and the justification is native. Wait like 5 years and there will be a new react-native corss platform app because the native apps have too much cruft. Assuming we still have human in the loop then.
One could argue that by making benefits hard to access, you under-provision and over-reward. This makes fraud more lucrative getting you into a viscous cycle. Normal people less likely to use benefits and dedicated fraudsters more likely.
Has no one heard of the concept of industrial zoning? When you live next to an industrial zone you get all the consequences. I love how literally all these projects are on shuttered sites of various plants that were presumably louder and more polluting than these new data centers.
2008 was literally people getting mortgages on unrealized gains, and then getting more loans. Even if the market wouldn't support the sale, they borrow against it and then get another load and causing an asset bubble. Its not ancient history.
The point is you should realize your gains before you reinvest the money. Circular borrowing causes asset bubbles. You could collateralize against OTHER assets, but unrealized gains you should be paying taxes on if you are borrowing against them. It's really just closing a loophole. If the loophole is BIG enough, the you could lower the rate for everyone!
Loans against unrealized gains should just be taxed directly as income. Not indirectly creating more loopholes. Same way stock buybacks should be taxed at the same rate as short term capital gains.
my m1 max macbook pro 14 has small little divots out of the edge on the right side (not on the left) presuambly because of where my wrist sits when using the track pad. It would be nice it there was some radius on it to not cause that.
did they ever add #define? bridging constants from the build system to swift with static NSString * const kConstValue = @XSTR(CONST_VALUE); is soooo annoying.
nodejs itself doesn't have very many breakages; i have plenty of code that is unchanged from 0.12 to 24. npm is a whole other kettle of fish but I don't think you can blame the core project for the sins of everyone that publishes to the package manager. Python2 -> Python3 on the other hand had a lot of breakage in "standard" code.
I would expect Apple to actually simplify the problem and not overreach and just do activation / provisioning / deactivation / lock and none of the other stuff MDMs try to do that introduces the complexity.
A non-terrible MDM that actually works would be really nice. The rest I doubt they get much traction on. Gmail is too easy, Google docs and sheets if you don't need Microsoft is also way better than Apple's free apps.
I remember when they invented kibibytes and mibibytes and shaking my head and being like they have forever destroyed the meaning of words and things will be off by 2% forever. And is has been.
Its so funny to me that people freak out about amortization when I spent several years at a public company having to document my work as being R&D to amortize it to make our EBITDA look better.
The judge should really fine apple in the form of a 100% refund of everyones fees for the duration of this behavior. That's the only way the pain is great enough to force forward compliance.