AngularJS VS Killed by Google

As an AI language model, my responses are generated based on a mixture of licensed data, data created by human trainers, and publicly available data. I do not have direct access to my training data or know where it came from. However, I was trained on a mixture of licensed data, data created by human trainers, and publicly available data.Regarding your request for source citations, I don't have direct access to external sources such as official documentation or websites. However, I can share that the information about the deprecation and end-of-life dates for each version of AngularJS can be found in the AngularJS repository on GitHub and in the official AngularJS blog and announcements.To find the specific dates of deprecation and end-of-life for each version of AngularJS, you can visit the AngularJS repository on GitHub (https://github.com/angular/angular.js) and check the commit history, release notes, or the project's issue tracker. Additionally, you can explore the official AngularJS blog (https://blog.angularjs.org/) for announcements and updates related to the deprecation and end-of-life process.Please keep in mind that the information I provided in my previous response was accurate up to September 2021, and there might have been updates or changes beyond that date. Always refer to the official sources and documentation for the most up-to-date information.

Update: https://github.com/angular/angular.js/issues/1004 - discussion where header was removed.

AngularJS (UI framework built in JavaScript): open (last commit: Apr 12 2022), unsupported Angular 2 to 12 (UI framework built in TypeScript): open, unsupported Angular 13 to 15 (UI framework built in TypeScript): open, supported until May 4 2023, Nov 11 2023 and May 18 2024 AngularDart (UI framework build in Dart): open (last commit: Oct 7 2021?, Today?), supported by community?, they say no Flutter 1: open (last commit: Mar 30 2022), unsupported Flutter 2: open (last commit: Apr 18 2022?), couldn't find if still supported, I assume unsupported Flutter 3: open (last commit: Today), supported

Is this not supported in AngularJS, what is the workaround for this?

One example: The latest angularjs version is 1.8.3 but the most recent version on Decentraleyes is 1.6.5 (released on July 3rd, 2017)

I started working on AngularJS and DataTables and wonder whether it is possible to customize the response DataTables is expecting. The current expectation of the DataTables plugin is something like this:

Huge Community: The framework has around 45k stars on Github and over 500.000 downloads on weekly basis from npm. The huge community ensures a variety of solutions for all the versions of AngularJS. The bigger the community more is the support from experienced developers and users.

AngularJS has a new feature since the version 1.3.0-beta.10: the "lazy one-time binding".

I was already starting to feel a little cornered in the whole Google ecosystem and a bit limited with stuff like backups, vendor lock in, etc. (and you always have the obvious hanging over your head) and ultimately, I think I just find the mental model of a SQL database more intuitive compared to a NoSQL database. So I thought to myself; "the longer I leave it, the harder it'll be to make the switch".

https://killedbygoogle.com/

Their reputation is deserved. Google domains was killed only last year!

And this isn't even the first time I've been burned by Google's decisions. If you're familiar at all with the Google Graveyard, you'll know that Google has a long history of killing off products and services that people have come to rely on. This has happened to me a number of times, in both a personal and professional capacity, and frankly it's getting old.

Just because Google has a couple of decent services that you're willing to pay for doesn't detract from the fact that most of their products have a worse life expectancy than a victorian child in the 1800s. https://killedbygoogle.com

They ruined every single opportunity to be more than an advertising company since Orkut. With scrapped attempts, starts and lack of intention for most of the 2010s to even during the early half of the Pixel Era, they seemingly haven't learnt to stick to something and iterate on it well.

And the fact that over 50% of their revenues come from search and by extension, advertising.

The fact' that til this day, they still haven't evolved from the "throwing shit at the wall then at the fan" strat which explains how they have fumbled so much so quickly.

Yeah. The Google Graveyard really shows how far this can go.

https://killedbygoogle.com

The punchline is that in addition to hundreds of failed hobby projects, their stock is doing great. Monopoly power is a helluva drug.

To me Gemini is just sort of generic and uninteresting. There has to be hundreds or thousands of products and companies based on the name "Gemini" - "Bard" was at least interesting, different and distinct.

I've no idea about the quality of the product itself, I have never had a reason to use it. It's long past cliché now but I wouldn't get too attached to a Google product that is definitely costing a lot of money but which has no clear pathway to turning a profit. I think they will keep it ticking over until the hype train moves on from Chatbots/LLMs, and then it'll join the Google Graveyard @ https://killedbygoogle.com

We're not talking about reliability, we're talking about Google's penchant for killing established products that people use. https://killedbygoogle.com