DEV Community

Cover image for Should .ng component authoring format get dropped? 😱
Tomasz Ducin for This is Angular

Posted on

Should .ng component authoring format get dropped? 😱

There's been quite some fire around the .ng component authoring format, introduced as experimental in AnalogJS meta-framework. You can listen more about it here:

TL;DR; the community seems pretty divided. I don't want to state my opinion here, and I'm last to judge. But the fact is: a lot of hard work has been put into the experiment and, due to some controversies, the AnalogJS team is planning to drop the support entirely.

Do you think it's a good idea?

Vote in the poll

and leave a comment under the PR. Thanks!

Top comments (2)

alaindet profile image
Alain D'Ettorre

That's a heated debate. I personally respect the work of Brandon, but I honestly believe the .ng is not the way to go for Angular, for two simple reasons

  • It is a radically different and yet not official syntax, meaning it would be dropped by the market anyway to avoid the risk of fragmentation
  • It forces people to migrate existing code and to be as concise as possible, given everything is in one file like Vue and Svelte. Although having short code is important, even for short components I like to have separate files for HTML and TypeScript in order to easily navigate them, like many Angular devs
draylegend profile image
Vladimir Drayling

I prefer .analog - it refers to analogjs and not to angular's "functionality"