The claim "if you do this this specific way" does not hold if it's easy to get it wrong. One problem with shoehorning HTML files into Dart is that you run the risk of creating Frankensteins of the past on your own. If your project lacks maintainability, then you're a bad programmer.
#Pug language p android
This is why we split each language into its own files, why we use templates, why new programming languages are invented, why dartfmt is an asshole, why you use Android Studio and I use VSCode, it's all in the name of maintainability with various degrees of success. Mainly this, but I'd go a step further and claim everything we do is for maintainability. I think it's a fairy tale and therefore I won't make any decisions on the promise of an artist being able to do that. Never worked on a project where a designer just causally runs around in the code and just updates the look of the UI. There are designers with dev knowledge out there who can do that part too but they are 2 separate steps in the process. It's going to be a dev who makes the sitebuild or Flutter widgets. Nowadays, designs are usually handed over as vector graphics with tools like Figma. If a separate html file is needed for the devs to not do crazy stuff, I believe some training is in order instead of throwing rocks at the tech. A component eg is responsible for rendering a piece of the UI which includes props and markup.
Separation of concerns isn't the same as separation of techs. The separation of concerns bit: I had a similar argument why I didn't like JSX with react. It's "opinionated" but generally prefer its opinions over juniors'.
I personally set it to 120 and mandate its use in my team. I have a few comments here, I see some things differently:ĭartfmt has an option to format your code to whatever length you want.
0 kommentar(er)
