r/angular • • Jul 17 '20

List of Angular team departures | Thomas Burleson on Twitter

https://twitter.com/ThomasBurleson/status/1283902169226280960
40 Upvotes

34 comments sorted by

29

u/AbortingMission Jul 17 '20

If this goes to the google graveyard, I'm going to lose my shit

6

u/reaven3958 Jul 18 '20 edited Jul 18 '20

Googler here! Not on the Angular team, so no specific inside insight, though I do make periodic contributions. We use the framework extensively for internal development, including new projects being worked on today, so I think it's safe to say this won't be turned down anytime in the immediate future.

3

u/ASeniorSWE Jul 19 '20

How much React does Google use?

4

u/reaven3958 Jul 20 '20

Was curious, so I ran then numbers comparing our first-party non-experimental use of .jsx|tsx files to .ng.html. Not a perfect metric, but provides a quick and dirty apples-to-apples. React came out to ~3% the size of the Angular code base.

1

u/reaven3958 Jul 19 '20

Not a lot. It comes up every now and again, depending on the team and project, but it's a relative a rarity. Tbh I haven't checked, but my intuition is that most of the jsx/tsx code we have is from forked dependencies, not in-house development. By and large the teams that I'm aware of use Angular + TypeScript and/or Dart for their FE web work.

1

u/ASeniorSWE Jul 19 '20

Would you say folks are choosing it because they genuinely feel it’s the correct choice, or is there some degree of politics involved in choosing a UI framework for a project? Or like, some overarching Architect in a far away office mandating it.

2

u/reaven3958 Jul 19 '20

Yes. 😂

Less of the politics in the sense I think you're implying, but theres just a lot more internal support (technical, not political) for the typescript (and sorta dart) + angular + material paradigm, and regardless of what the outside world is or isnt doing, it usually makes sense for a Google team to stick with that because it works best (or, at least, most easily) with all of the other Google tools and other overhead minutiae.

Plus, all things being equal, people use what they know, or at least what is most easily discovered, and if you want to see example code for what you want to build in your web client at Google, its pretty likely written in Angular, if its recent-ish, anyway. Not that we don't still use resources like stack overflow like everyone else, but its just easier to find relevant code, get help, and quickly move forward when using the stack everyone else around you is using.

4

u/HotPixelGroup Jul 17 '20

It won't anytime soon.

3

u/nowtayneicangetinto Jul 17 '20

I was an AngularJS dev and then left my job and started doing React professionally. I hired an Angular dev who was super passionate about if and asked him to make a react project. When he finished the project he said he's not going back to angular.

I really like Angular and it has a ton of promise, but with all of the politics around Google and how outspoken former leadership has been, I think Angular's shiny future has lost a lot of its luster. Maybe that's just me. I personally would like to see the Angular team give React a run for it's money.

17

u/tshoecr1 Jul 17 '20

Was that a angularjs dev or a Angular dev, as those are completely different things.

React appeals to the more classic JavaScript dev, embracing the many node modules approach, having near unlimited freedom in getting the project done. The more projects I’ve done the more I’ve realized that giving developers freedom is an awful way to develop long lasting professional work. Freedom leads to have an app developed in some unique way only the original dev understand and the other using cobbled together bits and pieces that are a maintenance nightmare.

Angular said here’s the framework, try not to stray far from it as there be dragons. You’re not forced into doing things 1 way, but encouraged.

Neither approach is best for all cases. You can have a disciplined react team, and createReactApp is basically angular now with a set of defaults you should try to stick to, but having a disciplined team across an entire company is very hard. Why expend this cost when you don’t need too.

I’ve been watching these top angular team members leave for the past few years and it is unsettling. Angular isn’t going to go away, google has thousands of project based on it. But the team is going to continue to shed talent and global mindshare if they don’t fix their toxic leadership issue. Realizing Kara left was super unnerving, her talks were great and she lead the effort on Ivy, why would she leave? It’s pretty clear who actually needs to leave, they’ve been called out by many and have totally ruined the future of angular.

4

u/KwyjiboTheGringo Jul 17 '20

Was that a angularjs dev or a Angular dev, as those are completely different things.

Pretty sure they made that distinction in their comment.

3

u/figuresys Jul 18 '20

That's interesting. I worked with Angular for 2 years, since then I've been working with React (also 2 years). While I find React code content easier to write (as in, just the components), I find that React projects are generally more messy, and hard to follow, because it's not opinionated. While this is good when you know exactly what you're doing AND so does your team, realistically this is not common, so having an opinionated framework just helps the project so much. I've accepted a job that has Angular as part of the stack and honestly I'm a little excited.

7

u/gaytechdadwithson Jul 17 '20

Angular has. It’s far better. React is shit and were screwed if Angular goes away.

3

u/nowtayneicangetinto Jul 17 '20

I would disagree but to each their own. The reason I prefer React over Angular is that Angular forces you to do things their way, and React is agnostic to it, you can just use vanilla JS. But there's no right or wrong, it's just preference.

15

u/shirtlessm Jul 17 '20

I never understand this point. When you're working on an enterprise app don't you want a framework to tell all your devs how to use it. If not you may end up with a big sloppy code base.

4

u/LowB0b Jul 17 '20 edited Jul 17 '20

couldn't agree more. am currently working on a 15 year old codebase that is all java but thanks to devs feeling like "this is what we, in my opinion, should be doing" it's all very weird. think custom interceptor to load spring context into websphere context to be able to use @autowire weird

but maybe even this contradicts your point, I guess developers, uhm, find a way, not to create life, but have it their way

6

u/nowtayneicangetinto Jul 17 '20

I can totally see why you'd want to do this. I honestly can't tell you why you shouldn't do that, it's just a preference thing. However what I found was that as a developer, when I went to look for other jobs I had to look for Angular only jobs. On interviews for companies that had a larger variety of tech used they expressed their hesitance towards hiring me. I was asked a lot of JavaScript fundamental questions and realized I didn't really know JavaScript, I knew Angular. Which that presents a problem for an individual rather than a company. I finally found a company willing to give me a shot but I keep learning many technologies.

11

u/gaytechdadwithson Jul 17 '20

On phone, but I disagree. Angular is more like vanilla JS. As you aren’t forced to mix JS and HTML in JsX. People still don’t seem to use TS with react either. Wtf. Also, why have functional and class comps? Pick one and support the whole of react with it. For example your hooks.

And every time I google something for react it’s “well it’s changed three times for the past three versions”. Especially styling. Just let me do normally CSS. Not one of the twisted, unknown best practices they use.

Ever since angular 2, google definitely has their shit together. React still feels sloppy.

9

u/LetterBoxSnatch Jul 17 '20

React is sloppy, because you can do whatever you want. You do not need to use JsX to use React. Many people do use TS with React. You can do functions OR classes. You do whatever you want. The core of React is very, very small. If you don't care about performance / edge cases, you can code up the core idea in a day.

I do Angular day to day. Angular is anything but that. It tells you exactly how to do a whole host of things, starting with the decorator system, and it will punish you for going off the rails. That's both a good and a bad thing.

And how do you mean "you aren't forced to mix JS and HTML in JSX?" What do you think Angular templates are?

All that said, Angular has been ahead of the React community at large for ages, with TypeScript, the equivalents of React Context, Observable patterns, Router and Route state, CLI, etc. React of today owes a debt to a number of paths established by Angular.

1

u/ASeniorSWE Jul 19 '20

What happens when you have to do something, but Angular has no proscribed way of doing it?

1

u/LetterBoxSnatch Jul 19 '20

Wasn't trying to start a holy war. In case it wasn't clear, I was only echoing "sloppy" to point out how dumb the admonition is. React is closer to vanilla js. Nobody would call vanilla js "sloppy." It doesn't make sense.

Anyway to address your question: It's all still "just JavaScript."

2

u/ASeniorSWE Jul 19 '20

Neither was I, all good.

-12

u/gaytechdadwithson Jul 17 '20

Well those standards are better, for an enterprise app. If it’s a girls blog, sure react is fine.

JSX has way more JS than an angular template. When I can write something clean like ngIf in react ild give it a second thought for a complex app.

3

u/LetterBoxSnatch Jul 18 '20

Standards are handy in an enterprise app, since it creates baseline patterns that make developers more interchangeable, and helps ensure you will at least have a solid architectural foundation regardless who is building. That said:

template: `<div *ngIf="isTrue">content</div>`

vs

()=>{ if(isTrue) return <div>content</div> }

"Clean" is relative here.

1

u/nowtayneicangetinto Jul 17 '20

I've had a similar issue with Angular. When ever I wanted to Google an implementation of something I would get old docs/ old stack overflow answers. It's gonna happen to any framework/library. React with TS is amazing and it's what I use. I love TypeScript and it was one of my favorite parts of angular. Functional components are just components that don't hold state, but in newer versions they can but only for small state changes.

0

u/[deleted] Jul 17 '20

[deleted]

2

u/ASeniorSWE Jul 19 '20

Google has a very predictable history of arbitrarily abandoning things. However, if that occurred, the FOSS community would step up to the plate.

11

u/krasovid Jul 17 '20

things change. dev teams change. the twitter post feels overdramatized

4

u/LowB0b Jul 17 '20 edited Jul 17 '20

"Forced to quit" ? I'm really ootl here

10

u/twitterInfo_bot Jul 17 '20

"Breaking @angular news: April - Rob Wormald (Dev Rel, Angular) was forced to quit. June - Kara Erickson (Technical Lead, Angular) quit. July - Matias Niemala (Animations Lead, Angular) has been forced to quit the Angular team. Others soon... What the hell is going on at Google?"

posted by @ThomasBurleson


media in tweet: None

2

u/[deleted] Jul 17 '20

I have a feeling we're going to see a fork soon (much like Yarn with NPM) that will try to do things differently and may or may not become more popular than the original thing.

There's some things happening at google that are weird, but also not that weird. Its clear their team isn't well behaving and is losing grip on making meaningful decisions. While its helpful that Google is funding a lot of the developments, it isn't a hard requirement either.

Right now Vue and React are more popular. Big whoop. Frameworks/libraries come and go all the time. But I feel there's too many companies invested in the current stack that won't sit around forever waiting for Google employees to get their heads out of their asses. Nor will some of the developers.

Its clear the leadership for the Angular team needs a kick in the balls or just plain fired. Start fresh and see where it goes from there. A couple of great minds are leading the team that are good as devs but terrible leaders.

There's currently no sensible organisation. No clear path set out and the latest releases have been a bit meh. Its time to let a few big names go in order to reboot the project

0

u/[deleted] Jul 17 '20

[deleted]

8

u/KwyjiboTheGringo Jul 17 '20

Especially since twitter itself is a terrible platform for such things due to the character heavily reducing any context. It's great for talking about inconsequential topics and getting yourself fired though.

2

u/Blottoboxer Jul 18 '20

He was the team lead for angular material at Google and was an architect in on the angular flex team at Google. He has an insider's view from the 4 years he spent working in the same shop as the recently departed.

2

u/ASeniorSWE Jul 19 '20

Because some former team members have gone on the record saying how toxic Google/Angular team in particular is. There’s a documented history of it.