No one forced you to migrate immediately. (Also, non-value-adding work? You don't think the rewrite to TS did not bring any value? And thanks to that rewrite that app can be upgraded even today to Angular v21. And likely it'll be the case for many years.)
React also went through a lot of churn. (Still does.) There's no magic optimal duration for keeping API stability. Not in general and not for specific projects.
Ecosystems sometimes undergo a phase-shift. Sometimes they take a long time, based on the size. Python 3 was released in 2008, just a year before Angular 1. And the last Py2 release was in 2020, about 2-3 years before the last AngularJS version. (And of course there are many businesses running on py2 still. I know at least one.) These things take plenty of time.
Angular1 was pretty opinionated, willing to break with the tradition of just add one more jQuery plugin.
Miško was working at Google, he persuaded some people to take a look at the framework that he and Adam Abrons were tinkering with.
Angular 2 was announced in 2014 January. And then v1 still got years of support, even the component architecture was "backported" around 1.5 (in 2016?)
You can run old v1 code side-by-side in a v2+ app up until v17. (At least the v17 docs describe the process in full and later docs link to this page. https://v17.angular.io/guide/upgrade )
...
Google did a pretty good job IMHO. Google throws products under the bus, but not so much OSS projects. (Though the sate of AOSP comes to mind.)
> Google throws products under the bus, but not so much OSS projects.
It abandoned the Material Design web components project, which, I think, attracted some Polymer people.
Speaking of Polymer, it has evolved into Lit; but I understand there is no more support for that project from Google. Lit has joined the OpenJS foundation to stay afloat. The Googlers that used to work on Lit, and on Material Design web components have mostly left.
Also, remember the Workbox project? A simple setup for service workers? It's barely alive.
The angular material design library is so much better than the react one. And it is supported by google. The material CDK is amazing to create custom components easily
I think JS is still overall more popular than TS, but if your team forces TS then yeah. It's like Java devs reluctantly switched to JS and were like, this needs more boilerplate.
Yeah, I spent years in Java and then even longer in .NET and it felt like everything I was getting a bit fed up of in those worlds had invaded JS. 20 years ago I could never have imagined defending JS as a language but, as time wore on, I started to appreciate its more stripped back syntax. And then a lot of what’s been added in later ES standards has been great so it seems even more unnecessary to layer TS on top.
It took me a while to appreciate JS too. Thought it was just the beginner language until I used it. Also had to learn the hard way that a web backend is hard to do efficiently without an event loop.
that's not a jungle, rights come from a social contract and all the complicated social technology we usually operate to try to manifest said rights.
in a jungle there are niches, and opportunities, and even though there are very strong participants, no one is invincible, especially outside their niche.
the jungle is a place where the social contract is decided by the physically strongest players. the strongest player in the jungle is the man and the jungle only exists because he decided to not level it and turn it into a palm oil farm. in that sense you're right, I completely agree, no one is invincible there.
cheaters or not there's no EU tech scene. of course it's hard to compete with a very successful capital-breeding flywheel that's ongoing for about a hundred years.
Poe's law applies, it's deadpan humor, finance Borat
IMHO it is very well executed, pushes the right buttons, and ultimately raises the question of financial realism (if the market acts like it's true is it true? how far is it from something that you can use to pay your taxes with? and so on)
> It's a satire blog that's confusing or misleading people (See top HN comments.)
I think it’s equally possible that we have a blind-leading-the-blind situation here, ie one guy didn’t get the joke, posted a serious chat gpt summary, and some people assumed it was a serious article. Seeing as that was the top comment for a while, I’d bet that this discussion is a great example of how using LLMs to “understand” things can actually have the reverse effect.
There's probably an audience that doesn't read mainstream business outlets, but still has some adjacency to it through VC/startup/entrepreneurship circles.
Is it confusing people though? Have you read the real one?
Poe's law is when sarcasm is confused for something serious. Using /s to mark you're sarcasm as sarcasm is a cop out (which I reflexively downvote on).
- sell software that interacts with your computer and can lead to data loss, you can
- give people software for free that can lead to data loss.
...
the Antigravity installer comes with a ToS that has this
The Service includes goal-oriented AI systems or workflows that perform
actions or tasks on your behalf in a supervised or autonomous manner that you
may create, orchestrate, or initiate within the Service (“AI Agents”). You
are solely responsible for: (a) the actions and tasks performed by an AI
Agent; (b) determining whether the use an AI Agent is fit for its use case;
(c) authorizing an AI Agent’s access and connection to data, applications,
and systems; and (d) exercising judgment and supervision when and if an AI
Agent is used in production environments to avoid any potential harm the AI
Agent may cause.
How is this different from a 5-10 year lease? You can sell the car to someone (or the construct) and he continue to service the debt or you can service the debt.
Now that am thinking about it (not accountant) does a lease show as debt or not?
I think the point is that Meta really really wanted to avoid getting their credit rating downgraded, and ... went shopping for off-book financial vehicles.
On one hand they (supposedly) have enough "discounted cash flow" to do whatever, on the other hand I guess even they know it's a bubble and fallow years are coming.
My understanding is that the residual value guarantee only covers "most modeled cases" and this case (which might be the only one where the datacenter could not be meaningfully utilized and the guarantee would be relevant) was the not-modelled one...
> This arrangement comes at a steep price. The interest rate on these bonds is as high as 6.58%, significantly above the 5.5% yield of bonds from similar companies to Meta.
so it's definitely not completely junk, but the market priced in the gap (though, for me, it doesn't seem that big of a price difference!)
The issue is the short, 4y renewal cycle, which allows Meta to attempt superficial arguments to avoid accounting consolidation for the variable interest entity that they...pretty much (a) control and (b) have skin in the game.
How easy it is to get married? Get the various birth certificates, get eligibility papers, get an appointment, oops, you are over the 3 months. Beep, 6 months in some DHS warehouse, have fun, try again later.
React also went through a lot of churn. (Still does.) There's no magic optimal duration for keeping API stability. Not in general and not for specific projects.
Ecosystems sometimes undergo a phase-shift. Sometimes they take a long time, based on the size. Python 3 was released in 2008, just a year before Angular 1. And the last Py2 release was in 2020, about 2-3 years before the last AngularJS version. (And of course there are many businesses running on py2 still. I know at least one.) These things take plenty of time.
Angular1 was pretty opinionated, willing to break with the tradition of just add one more jQuery plugin.
Miško was working at Google, he persuaded some people to take a look at the framework that he and Adam Abrons were tinkering with.
Angular 2 was announced in 2014 January. And then v1 still got years of support, even the component architecture was "backported" around 1.5 (in 2016?)
You can run old v1 code side-by-side in a v2+ app up until v17. (At least the v17 docs describe the process in full and later docs link to this page. https://v17.angular.io/guide/upgrade )
...
Google did a pretty good job IMHO. Google throws products under the bus, but not so much OSS projects. (Though the sate of AOSP comes to mind.)
reply