Google: Angular and Wiz Are Merging • Hacker News Board

Re: Google: Angular and Wiz Are Merging

#131

Post by neonsunset » Fri, Mar 22, 2024, 12:28 AM UTC

bheadmaster wrote: post #126

ildjarn wrote: post #124

Earlier quoted context omitted.

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.

It's not the case in C#. It is discouraged, but mainly because there just used to be so much sloppily written async code that managed to bring down threadpool to its knees despite hillclimbing and blocked threads detection doing a lot of heavy lifting, so the community has grown scar tissue against this. It's rarely an issue if ever in the last 5 years or so.

Re: Google: Angular and Wiz Are Merging

#132

Post by wentin » Fri, Mar 22, 2024, 12:50 AM UTC

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…

> 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.

It sounds no different from Svelte borrowing concepts from SolidJS, or Vue borrowing ideas from Svelte, from you said — if it is just adding some features that Wiz has, it doesn't sound like merging? Why put a shocking title that Angular is merging with Wiz, when Wiz has no name recognition in the outer dev community — like we don't know what that means?

Re: Google: Angular and Wiz Are Merging

#133

Post by [deleted] » Fri, Mar 22, 2024, 12:54 AM UTC

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?

[deleted]

Re: Google: Angular and Wiz Are Merging

#134

Post by wentin » Fri, Mar 22, 2024, 12:54 AM UTC

baggachipz wrote: post #64

JamesonNetworks wrote: post #40

Ugh, this isn’t Angular anymore. This will be just like the v1 -> v2 transition. Presignal -> signal. The second they start deprecating the previous syntax, we will hit very difficult migrations

We just got done porting everything from AngularJS to Angular D:

A joke or really? At this point, I would just port it into Svelte, it is the same amount of effort anyway and it has been so long!

Re: Google: Angular and Wiz Are Merging

#135

Post by johny_morte » Fri, Mar 22, 2024, 12:57 AM UTC

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…

Hey, im working with angular for almost 5 years now.. What changes should we -developers - expect in the developer experience. In other words how we work with angular. Are you aiming for the "drop-in" replacement same as with ivy back then? Or new standards are comming with this? Thx!

Re: Google: Angular and Wiz Are Merging

#136

Post by wentin » Fri, Mar 22, 2024, 12:59 AM UTC

whalesalad wrote: post #108

lakomen wrote: post #70

I've been working with Angular for 2 years, then moved to Vue and have been with it for, idk 3-4 years now. I like the theory of Angular, the modularity, the way it works, but I HATE rxjs and the complexity of it. And the whole thing on top of rxjs, ngrx. You can't just simply take one value and compare it, no you have to use pipes and rxjs. Also there's an Angular discord and they're very hostile towards anyone not…

Vue is the best framework I have ever used. I can't imagine why anyone would use anything else. Angular has gotta be the worst imho, perhaps Ember. There are big communities around these tools though so I guess the approach resonates with certain folks.

I hate to be THAT GAL, but... try Svelte! I love it more than Vue.

Re: Google: Angular and Wiz Are Merging

#137

Post by pohuing » Fri, Mar 22, 2024, 1:10 AM UTC

miiiiiike wrote: post #130

hmcdona1 wrote: post #113

Earlier quoted context omitted.

> 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 woul…

Which is strange. Google knows how to write docs. Or at least I've been very happy with the flutter docs. But now working on angular frontend is awful tooling wise. I don't even get useful inline docs for a lot of libraries.

Re: Google: Angular and Wiz Are Merging

#138

Post by Drac707 » Fri, Mar 22, 2024, 4:01 AM UTC

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…

is wiz gonna get open source now that is getting merged?

Re: Google: Angular and Wiz Are Merging

#139

Post by [deleted] » Fri, Mar 22, 2024, 4:20 AM UTC

miiiiiike wrote: post #130

hmcdona1 wrote: post #113

Earlier quoted context omitted.

> 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 woul…

[deleted]

Re: Google: Angular and Wiz Are Merging

#140

Post by scroll-break » Fri, Mar 22, 2024, 5:16 AM UTC

miiiiiike wrote: post #130

hmcdona1 wrote: post #113

Earlier quoted context omitted.

> 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 woul…

First, create an AnimalService with an emoji property of whale

You can leave all the FlowerService related code in place as it will allow a comparison with the AnimalService.