r/Angular2 • u/timdeschryver • Nov 06 '19
Article Google Maps is now an Angular component
https://blog.angularindepth.com/google-maps-is-now-an-angular-component-821ec61d2a018
7
u/Mokwa91 Nov 06 '19
Looks cool, but I really disagree the direction @angular/components is heading.
I think the should be focusing on close the immense list of issues that they have at this moment. People are getting very displeased with this library and choosing to go with others UI library's.
I have friends that opted for choosing other frameworks for new projects, seeing the poorly way that @angular - as a whole - treats it's community.
7
u/AbstractLogic Nov 06 '19
The team seems to be falling into the classic fallacy of doing what they want not what we want.
2
u/lax20attack Nov 06 '19 edited Nov 07 '19
They are doing what Google wants. No surprise, and it's free to use and build upon, so I don't understand the complaints.
4
u/AbstractLogic Nov 06 '19
I guess it's just a very different environment then I'm used to.
I came over from the dotnet world where the dotnet core framework team worked on only the framework and the Bing Maps guys worked on maps. They both delivered libraries... but the framework was the framework and the Maps library was just a library you could reference.
So I find it confusing when Google released Google Maps under the @angular framework.
2
u/Mokwa91 Nov 06 '19
Yes, that’s exactly what I felt with Ivy
4
u/AbstractLogic Nov 06 '19
It is odd because @angular claims they built a framework for google and us plebs just get it for free... so how can I be upset when they treat us as second class citizens? But... they push the framework like it's for us.
1
Nov 07 '19
I feel the same - but we haven't seen the impact of Ivy. Also regarding Bazel and MDC while having so many open issues and lacking components compared to Reacts Material UI or ngZorro. Anyway, the team is part of Google, so I can understand those decisions even though I don't like them (the decisions :-)).
1
Nov 06 '19
It's open source, feel free to put in a PR.
3
u/lppedd Nov 07 '19
He doesn't get paid to do it, unlike Google employees.
0
Nov 07 '19 edited Nov 07 '19
I’m glad not everyone in the open source community has your attitude.
4
u/lppedd Nov 08 '19
Well actually I contribute quite a lot. If you have the Attribute decorator support in IntelliJ it's because I put the effort for example. I just find it frustrating that important issues are delegated to the others, non Google, people.
1
0
Nov 06 '19
[deleted]
3
u/XPTranquility Nov 06 '19
We use https://angular-maps.com/. Is it any better?
2
u/AgentOrangeNZ Nov 07 '19 edited Nov 07 '19
I use
@agm/coreand its good in terms of its feature set - we use it for editing/managing polygons for spatial geometries etc. This@angluar/google-mapslibrary by comparison seems really basic.Also the scripts are loaded async and also other libs can be loaded too, such as the places api for address autocomplete etc.
17
u/Chazgatian Nov 06 '19 edited Nov 06 '19
Not sure if I agree on this direction. The Material components were a set of low level dumb components that could be used to compose applications. Now we are mixing a set of smart components that I (my company) have no intention of using.
The introduction to of these smart components will actually make my life worse. First, there's additional comments to sift through in the GitHub backlog. Second, we've basically told our development teams that anything in the Angular Material library is free game to use in your application per our design system. Now we need to create more guidance around this. Finally, it's really hard to get excited about any new components when there are still numerous issues that should be addressed, like virtual scrolling a table, and a date range picker.
IMO they should have created a new package consisting of these smart components instead of piggybacking off the Angular Material library.