3 ms·
First off, the idea of having a component in a single file feels like a really nice idea, as long as you don't have lots of common code. Secondly, the syntax f
by KronisLV 5y ago
First off, the idea of having a component in a single file feels like a really nice idea, as long as you don't have lots of common code.
Secondly, the syntax feels as odd and probably uncomfortable to use as AngularJS binding types: https://stackoverflow.com/a/35858878 https://stackoverflow.com/a/35858878
And in my experience, people didn't want to bother with creating new subcomponents in it and instead built few large ones just because of how uncomfortable it was to use.
I feel like they syntax here could also detract from the overall experience somewhat as well.
Instead, why not just write regular HTML files with inline <style> and <script> tags with optional comments that would make a smart build step perhaps extract some of the styles (e.g. all the rules that won't cause layout shift and therefore don't have to be blocking and can be a separate file) and scripts into separate files, transpile certain functions or patterns where needed etc?
- oehpr 5y ago"And in my experience, people didn't want to bother with creating new subcomponents in it and instead built few large ones just because of how uncomfortable it was to use." it speaks to how programmers are people, and subtle ux in a programming style will dramatically effect how it is used. I have no idea if nazca is a good or bad idea, but it clearly presents a new UX to create these components, and I can see how I might be more willing to use components created in this style than in Angulars.