Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google: Angular and Wiz Are Merging

twitter.com

Post reply on HN
Print view View original

121–130 of 179 posts

Re: Google: Angular and Wiz Are Merging

#121

Post by mgechev »

RunSet wrote: post #110
mgechev wrote: post #98

Hey everyone, I'm working on this at Google and would be happy to answer your questions :) The tldr; is that we see a lot of similar requirements from developers across Angular and Wiz, so we're looking for opportunities to reuse work. Good example is the Angular Signals library that's now used in all the YouTube Mobile Web. In a similar way, Angular is bringing more fine-grained code loading that Wiz offers. Over ti…

Question (you might need to pass this one up the chain of command): Was basic HTML gmail deprecated because users so overwhelmingly preferred slow, bloated UIs that there was no demand for an alternative?

We’re building infrastructure for these products rather than the products themselves.

I’ll be happy to answer questions about Angular and our collaboration with Wiz :)

Re: Google: Angular and Wiz Are Merging

#123

Post by uxcolumbo »

datavirtue wrote: post #119
LispSporks22 wrote: post #114

Earlier quoted context omitted.

I’ve hated working on every Angular project I’ve worked on. No matter the team, the experience level or complexity, it’s always been an absolute misery. I cannot understand how it was invented/why it exists, how smart people at Google convinced themselves to use it. I cannot understand how they let it escape into the wild or even why those not forced to use it, choose it. I know I’ve begged before for this, and it’s…

It's worse, everyone jumped from Angular to the React bandwagon. I use these types of things as litmus tests for if I want to join a new company/team. No sense in cussing under my breath all day every day. It's really hard to smile after you just invented a new vulgar phrase to describe mangled tech.

So React is equally bad in your view? If so why?

What do you use?

Re: Google: Angular and Wiz Are Merging

#125

Post by bheadmaster »

pjmlp wrote: post #101
bheadmaster wrote: post #92

Earlier quoted context omitted.

If your post is intended to be a remark on how nothing in Go is "revolutionary", please read the first paragraph of my post, and notice how there isn't a single language in your list which is in all 7 categories. Additionally: - Erlang does not implement CSP, it implements Actor model - Java does NOT have all the listed features included in its default toolkit - hence the existence of Gradle, Maven and all other pack…

My opinion on Go's "innovation" is well known on HN, and gonuts back when I cared pre-1.0. I could go over those points, one by one into detail, including Russ Cox point of view on disabling binary distribution, but not feeling motivated to press the further the wound.

I have no idea who you are nor do I care about internet pseudocelebrities, sorry. Your opinions, to me, are just words from a random stranger, whose merit is only insofar as I can learn something new from them.

Re: Google: Angular and Wiz Are Merging

#126

Post by bheadmaster »

ildjarn wrote: post #124
lokhura wrote: post #74

Earlier quoted context omitted.

And C#, Python, Rust...

You can de-color an async function by blocking.

In most implementations, blocking in an async function has unintended side effect of blocking all other async function running on the same executor.

Re: Google: Angular and Wiz Are Merging

#127

Post by bheadmaster »

neonsunset wrote: post #97
adrianmsmith wrote: post #59

Earlier quoted context omitted.

The way concurrency works is pretty unique amongst mainstream languages. Java has just copied some parts of how concurrency works in Go, but that's nearly 20 years after Go was released. It's extremely easy to start up code concurrently with "go foo()". You can start up lots of such functions concurrently, as it works in userspace. Like async code, but no "colored functions" problem.

Quoting "colored functions" is a problem of skill. It is a tell of engineer's lack of understanding of concurrency.

Can you please elaborate why?

Re: Google: Angular and Wiz Are Merging

#128

Post by datavirtue »

tashoecraft wrote: post #55
ecmascript wrote: post #38

Earlier quoted context omitted.

I didn't care so much about the syntax but rather the over reliance on the subscriber pattern that you have to have like a subscriber to even read something as fundamental as query params. And the funny thing is that is will fire once and then again when the query params is actually set. So you will have an empty fire for when they are not yet set for some strange reason, presumably from when the observer is created.…

Sounds more like a misunderstanding of the framework and observables. The problem many faced with angular is they chose not to learn observables, then got angry. If you have different subscribers, all on the same state change, you may not have chosen to use ShareReplay, or filter, or bothered to use a tool like ngrx that has memoized selectors. The same problem you're complaining about is the same thing people in the…

That's the problem, you have to learn all that crap. Excuse me, you have to hold it properly.

Re: Google: Angular and Wiz Are Merging

#129

Post by tubthumper8 »

peer2pay wrote: post #106
throwaway4good wrote: post #31

I hear most Angular projects being stuck at around version 15 due not being able to migrate away from Angular Material "Legacy".

You can upgrade all the way to Angular 17 without having to adopt the new MDC components. Only this May with Angular 18 support for the legacy components will be dropped completely. That’s the reason we’re currently migrating all our remaining usages of Material components to ng-zorro.

They previously announced [1] these would be removed in v17, did that change?

[1] https://blog.angular.io/angular-v16-is-here-4d7a28ec680d

Re: Google: Angular and Wiz Are Merging

#130

Post by miiiiiike »

hmcdona1 wrote: post #113
miiiiiike wrote: post #50

For years I’ve been saying “Angular is the wrong choice now but it will be the right one someday…” I didn’t think it would take 5 years to get there. The Angular team has been doing incredible work lately. The only thing that I still don’t like about Angular is trying to learn anything from the reference docs. Have a reasonable developer tell me what a component viewProvider is and how it’s different from a provider…

> Have a reasonable developer tell me what a component viewProvider is and how it’s different from a provider using the @Component docs. It’s impossible. https://angular.io/api/core/Component#viewProviders Like this? - https://angular.io/guide/hierarchical-dependency-injection#u... - (new docs site) https://angular.dev/guide/di/hierarchical-dependency-injecti...

Exactly my point.

I linked to the reference docs, you linked to the usage docs. They're completely divorced from each other. There's not even a link from reference to usage docs.

For the reference docs to be useful you already have to know what the thing is, what it does, why you'd need it.

You can be on the component page where `viewProviders` is documented and get nothing from it if you're coming in fresh.

Why would ever design docs like that?

Angular is the only framework I've ever struggled to learn. It's a complicated framework but that's not the problem. The docs are the problem.

Post reply on HN