Don't abandon AngularDart, don't give up on AngularDart #1866
Comments
|
My company is investing heavily in projects using AngularDart too. We are really fan this powerful framework and the possibility to use all Long life to the AngularDart and Components! |
|
good news, the framework 1 get updates 😆 Footnotes |
Really good news, I was really worried about the inactivity of repo. I hope Flutter will take the developers to try AngularDart |
|
@DevAlves1993
|
|
I see AngularDart as a much cleaner, nicer, organized and simple version of Angular. I particularly see TypeScript syntax very ugly and dirty. There are some areas of AngularDart that can improve, especially the router part and simpler forms of serialization. |
|
I started learning Angular with TypeScript using some Udemy tutorials but I didn't even understand anything. So I had to give up on Angular. But After Flutter announces Flutter for Web I started learning Dart. It is really easy to learn. Since Flutter for Web is not yet ready for production, I moved to AngularDart. I learned everything using Documents. I was not able to find any Video Tutorials. Documentation is perfect for a beginner to learn it. I would really need Angular Dart to be added with some more features without giving it up. |
|
Long life to the AngularDart and Components! |
|
We need an official status update. I heard Google uses AngularDart for AdWords and other teams also prefer Dart version. Is it still true? |
Problem that AdWords was on GWT and we know what happened( |
What happened? |
Google moved from GWT to Dart. And stopped support GWT. |
I really hope Google will not abandon AngularDart, otherwise my organization and I will be greatly damaged. |
This comment has been minimized.
This comment has been minimized.
|
Hi there -- thank you for your passion for AngularDart! It's always exciting to see others who are getting value out of this project. It's encouraging to see this issue get a ton of thumbs up. Firstly, let me (partly) reassure you. AngularDart is not going away and is as actively developed as ever, although we have shifted our focus a little. As you have noticed, our activity on GitHub has become more bursty in recent months. Because of the heavy usage of AngularDart internally within Google, we moved the primary source of truth to google3, our internal mono-repo. Our goal is to push out new code to GitHub periodically, and we're in the process of automating this so that we’re able to improve the frequency of these syncs. And as you've seen, in the past few days, a large number of changes have landed from a broad set of contributors that bring GitHub up to date. But yes: we also want to be honest that our focus has shifted somewhat, recognizing the heavy internal usage of AngularDart and comparatively low external developer base. AngularDart is ideal for large-scale data-heavy apps like AdWords with millions of lines of code, but there just aren't that many of this kind of app externally, and we've gradually recognized that. Externally we have a loyal but relatively small following, but AngularDart is probably never going to be a broad general-purpose web framework. Conversely, we have a growing audience of thousands of Google engineers using AngularDart internally, and so most of the features we build are with that audience in mind, knowing that what they need will likely also be of value to external developers. Lastly, we want to recognize that with the emergence of Flutter’s support for the web, we have other motivations to continue to develop Dart web scenarios - from improved IDE tooling to compilers. In fact, our level of investment in web tooling for Dart is higher than ever, with more engineers working in this space than at any previous point in the project's history. So, to summarize:
|
|
@timsneath, I think it is very important to have information about the next steps of Google products. First, it is a gratitude that we have Google sharing its technologies. As a company admired for its audacity, business models and technology many seek to mirror and use what is available to it, especially when open source. I have been following and using Dart Lang for several years. It is a wonderful technology. However, one point has always made me apprehensive and anxious about the future: Lack of clear communication about the next steps, especially about the scope of development and release milestones. As an open source product, in which many use and would also like to contribute to development, I see as important an additional effort to clearly manage communication, thereby aligning the expectations of both Google's internal team and external community. An improvement in this sense, in addition to aligning expectations, would cause the community in general to create greater confidence about the future and thus generate greater adoption of Dart Lang, AngularDart, etc. The technology is fantastic, I think adding a dash of management would make it even better. |
|
@timsneath How about AngularDart Components (angular_components) package? Will you also continue to release it on GitHub? |
|
@michalpie see here angulardart/angular_components#356 (comment) It is the same story as AngularDart, slower release cadence pace |
|
We have almost no interest to change from AngularDart to Flutter for web in the next years because we have so many components being used that would need a great amount of work to make the change. |
|
I am simply amazed by how little effort was put by Google in pushing the Dart Version of Angular. |
|
Is the version of Angular targeted by AngularDart internally at Google keeping up with the latest regular Angular releases (i.e. the 9.0 version)? The version on github seems to be a bit behind the main Angular releases. I am almost more inclined to use the regular Angular only to take advantage of the new Ivy capabilities versus those in the 5.0 Angular version targeted by AngularDart. In general, though, thanks so much for your work on this product! |
Hey @levinem – while both flavors of Angular (JS/TS vs Dart) share a history, they have diverged in many ways – mostly to align better with features in their respective platforms and to address issues with their core customers. |
Thanks @kevmoo , I had thought that AngularDart was a Dart interface to the Angular main compiler, but it sounds like the underlying compiler infrastructures are not fundamentally connected and that AngularDart will try to keep the main interfaces and concepts similar to those in the JS/TS Angular project to enable a familiar interface for existing JS/TS Angular developers. |
@levinem – I wouldn't go that far. The engineering teams are friendly, but they are separate teams. There is no explicit goal to keep things aligned – but there is no incentive to diverge either, unless there is a good reason. |
|
@timsneath I worked for 2 years on a project that was angularjs, in the last 8 months I was on the project, the team migrated to AngularDart. We rebuilt everything in AngularDart. We also created Dart-based command line tools to ease our development workflow. The team was sold on the migration due to A) Dart's capabilities, B) Ease of taking existing web elements (HTML, CSS, and JS) into AngularDart variations, and C) Google's own investment and use of AngularDart for its Adwords, and other internal products. The project is within the government space, so I cannot share details. But the product we developed consisted of over 15-20 microservices (including the angular-dart web client). I hope this can tell you that it is absolutely an enterprise application. We needed Dart's strong type system so that we reduce the ambiguity within our logic. AngularDart has a space externally from Google, but Google HAS to be public with its support. My last point, AngularDart, and the Dart platform itself, should allow If Google doesn't show support and love for Dart and AngularDart like it does for Flutter, then it's all going to fall apart. That would be a shame, because there's real gold here. And I concur with @supermuka about next steps for Dart and Angular Dart. These need to be public, even if short-term. Otherwise, no one will engage with what appears to be a ghost town run by ghosts. |
|
@timsneath
I totally agree with you, I am also working on several AngularDart projects for the Government of Brazil, I love AngularDart, I love the dart, we cannot let this wonderful tool die. |
|
We're actively working to onboard someone to start the external rolls of angulardart. We're blocked by some paperwork, but we're working through it. Thank you all for your interest and patience! |
|
Very good to know that there is work behind the scenes. |
|
I think this tweet from @timsneath "Group Product Manager for Flutter and Dart" from Google makes it clear. Flutter Web is the priority for Google
|
Guess I'll be cutting down on the AngularDart tutorials then. |
This is too bad... you don't have to draw everything on canvas. Angular Dart has so much potential... . Dart is getting fame because of Flutter, people start learning it,... Angular Dart is good for anyone familiar with Angular TS, and this is the right tool to use. Imagine... Angular Dart, Aqueduct, Flutter... we are kicking Javascript left and right... (as someone with background of .net C#, words can't describe how much I dislike Javascript) Come on. |
Absolutely! Granted that the sync goes through sometime in the near future, I think someone should fork it and try to build a community around it and hopefully keep it alive. Personally, I'd be more than happy to contribute, despite having some time constraints. |
Sometimes, I think, because AngularDart is so fantastic and Google uses it a lot internally, Google may not want to share with the community this powerful structure that allows to develop in a pleasant way, magnificent, robust and complex applications. I've been hoping to see updates for a long time, but it's becoming increasingly clear in the leaders' messages that the focus is different. Unfortunately! Perhaps there will be two ways to see the evolution of AngularDart: working at Google :) or the community fork and evolve the framework itself. |
|
You might want to stop copying that image into every reply, since it makes it harder to follow the thread :) I know that this is a nuanced message, which therefore runs the risk of misinterpretation, so let me reiterate a few things:
|
|
so, |
|
@timsneath can you share with us a road map for flutter web support, it is crucial information that I think Google must share with the community. |
|
We're pretty open about our roadmap and progress, @bshlomo. Most recently, we posted this: Our focus right now is getting web support into the Flutter |
|
angulardart for creating sites (full-fledged sites) is the best choice, flutter now has a number of disadvantages that not everyone is ready to accept, as an example, not being able to copy text |
|
Thank you @timsneath for the link abut flutter-web-support, very professional, and it seems that Google is doing a wonderful job. No one can ignore Google's investment in Flutter, and it is pretty clear where the efforts are, and what will be in the future, but it will preferable if Google will be more clear about when we can start using Flutter on the web, even some rouge estimation will be most valuable to a lot of teams out there |
|
@bshlomo as someone that's built & launched app on both Angular Dart & Flutter I would strongly recommend flutter for any new project. I can elaborate if you need but I don't want to derail this topic. Gitter is probably a better place to discuss, feel free to ping me. |
Could we have a |
You could create an article in medium or some other blog system. |
|
Thank you for your interest in this subject You can't pull thousands of developers after you, while they are asking (and not getting) some relevant information that is a standard in this industry and we call it "product's road map" The effort, difficulty, challenge, and risk (and we all appreciate the wonderful job Google is doing on this) can't cause Google to ignore our needs as users for valuable information that will help us make our own decisions, I am sure that Google doesn't want that we lose money and time by making wrong decisions that result from a lack of basic but committed information. Why send someone to start development with a dead product? About @jodinathan suggestion - article in medium - a very good idea |
|
@bshlomo Thumbs up dear-github/dear-github#44 may help a lot And it seems that GitHub prefers frontend frameworks/libs than any than repos: |
|
I use AngularDart extensively in a multitude of projects, in the company where I work, and particularly I love AngularDart. This can be done in two ways, at runtime by converting HTML to flutter widgets or at compile time using code generation to generate flutter widgets https://pub.dev/packages/flutter_widget_from_html https://medium.com/@muhammadtriwibowo/flutter-xml-based-layout-prototype-66d0f8fae9bd |
|
Please add tutorial, Angulardart + gRPC and shelf or aqueduct(dart for backend) mmmm? |
I was looking for the same but GRPC does not work over the web natively without hacks, so such tutorial might us in right direction. |
|
There are people who are using Angular Dart for building Chrome extensions that have many many users. |
|
Maybe it's time to close this issue since it's not going anywhere, @timsneath already answered Grpc does have support for web and calling shelf or aqueduct endpoint is not different from using an HttpClient |
|
As far as I know, we need to route GRPC request through a proxy, and certain things are still not supported for example streamed input and streamed output. The grpc-web example which I already looked through requires a GRPC web capable server, and currently the only working implementation of such server is written in node.js I was unable to find an example that makes us of Golang server. GRPC must be implemented as a protocol in the web browser similar to HTTP to make it work without hacks. |
|
You can use grpcwebproxy or Envoy for this which I've used in a pure Dart stack before. That being said, this is getting rather off-topic for this issue and further discussion related to GRPC in particular should probably be elsewhere... |
|
Closing issue to avoid it becoming a suggestion box for all new feature requests :) We have a new release coming imminently; our commitment to AngularDart is solid, albeit with a more pronounced focus on Google's large scale apps like Google Ads and Play Console. |
and others
Don't abandon AngularDart, don't give up on AngularDart, me and my company are investing heavily in AngularDart, we are migrating all our web applications to AngularDart, I love Flutter for Mobile, but Flutter is not WEB-productive. WEB, we can't use many existing HTML and CSS templates, because in Flutter we can't use HTML and CSS.
The text was updated successfully, but these errors were encountered: