It looks very cool, but i take a look at their homepage and saw an example where css html and js is all put in a ".stelve" file and thats the point i dont like because it seems kinda confusing and not clear to me. Also i like more "component" based design where a component has all stuff splitted in their own files and all result together in a "component".
I'm a full stack software engineer, linux system administrator, tech support specialist, and LGBT+ rights activist. I love old technology and collect old computers. Come say hi!
I'm a full stack software engineer, linux system administrator, tech support specialist, and LGBT+ rights activist. I love old technology and collect old computers. Come say hi!
Its ok in a small project but if youre working on large enterprise software which produces a lot of income, you want the code base as understandable as possible in less time.
I'm a full stack software engineer, linux system administrator, tech support specialist, and LGBT+ rights activist. I love old technology and collect old computers. Come say hi!
Isn't that the objective of Svelte? It's perfectly understandable on bigger projects. A single .svelte file is a single component. Whatever CSS or JS that's in it handles the styling or behavior of that specific component (scoped styling). Then you build your app using those building blocks. It seems more understandable than having them all in separate files.
Svelte doesn't really have an opinion about how you manage your styles. AFAIK you still need the style tag, but you could use PostCSS to import an external CSS file.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It looks very cool, but i take a look at their homepage and saw an example where css html and js is all put in a ".stelve" file and thats the point i dont like because it seems kinda confusing and not clear to me. Also i like more "component" based design where a component has all stuff splitted in their own files and all result together in a "component".
That's the main point of the template section of the article :p
then may i should invest more than 5 minutes and take a closer look at the site
I personally prefer all the stuff in the same file, but that's just more of a preference
Its ok in a small project but if youre working on large enterprise software which produces a lot of income, you want the code base as understandable as possible in less time.
I find them equally understandable, but not everyone does.
Isn't that the objective of Svelte? It's perfectly understandable on bigger projects. A single .svelte file is a single component. Whatever CSS or JS that's in it handles the styling or behavior of that specific component (scoped styling). Then you build your app using those building blocks. It seems more understandable than having them all in separate files.
Might want to take a 2nd look. Svelte is very cool. Thanks Hannah.
Svelte doesn't really have an opinion about how you manage your styles. AFAIK you still need the style tag, but you could use PostCSS to import an external CSS file.