Morning

EY Ravi, well if you asked me a few weeks ago. I would still be mad, but after a steap learnming curve in Typescript/ LiT /Webcomponents General I am being a little more productive again and that is the only thing I need the coming months (besides being on holiday) Hopefully I do a talk on this later this year at Duugfest You tried anything yet?

i have tinkered with it a little, mostly to check stability and such after @CodeSharePaul posts here and on Linked in, and sort of followin a few others

Yes I also think there is a barrier for us old devs same as it was with AngularJS. But must say Typescript is a nice way forward since it feels like a real programming language 🙂 And yes sorry to miss codegarden this year. My youngest daughter gets her exam results during the week and when she passes we pop some champagne (Mostly the parents are happy because we don't have these school fights every day anymore 😂 ) Will miss the launch of V14 as well, BBQ weekend with friends starts tomorrow

I personally don't mind that there is a new world for extending the backoffice. They have made it so we can bring our own framework. It's just something new to learn and we like learning new things as developers. I think by the time we get to v15 it will be a lot more stable. Having said that I don't think I will be doing any client work on STS versions anyway. So anything I do on STS versions will be for research and contribution purposes. I could be wrong though.

that last line is the key ..

I always advise clients to go from LTS to LTS these days, could be a massive upgrade to V17 but V14 will have a lot of breaking changes in v15/16 anyway IMO so better to to the hurdle once.. Hope for packages people don't use too many 3th party plugins/ other frameworks. That could conflict quite easily..

I'll also be wary of doing client work on v14 for a while, but at the same time the dependence on AngularJS had to go, it's been EOL for quite some time now. I also think moving to web components is sound and the ability to use good javascript tooling when building packages is a good thing too.

Yeah this had to be done, Pete Duncanson will be proud.

I'm also strongly for the move.. i just wish , there was a .NET way and not Blazor, but i love the people working that enterprise for giving it a go....

I see the management api as the .net way and then we just talk to those apis with our js front end stuff. When it was user controls which was a .net way, that felt dirty, lol

Yeah... though I agree with Richard, I wish they were more opinionated about the recommended way of building extensions. The "you can use anything you like!" approach will lead to chaos pretty quickly imho...