I get that it has many "components" that all change at the same viewport width media queries, but with flexbox and css grid there's a much lower barrier to entry than there used to be to make your own css responsive. On the other hand, if you don't want to design anything and just want to present your data/controls as soon as possible, you should grab a component-pack for your specific framework, like a Google Material Design or Ant Design one, that directly exports components in your frameworks format.
Oh, that was precisely my reaction, that it is very obscure, I barely heard about it. Certainly less than Angular, Elm, Svelte and Cycle.js. Also, if you are just looking around for variety, see lit-element and stencil.js, which produce Web Components.
I meant that you would have the same component code running on the server for server rendering and on the client for clientside rendering. Personally, I feel like server side rendering is overhyped, the cases when it's advantageous are fairly limited. Having a completely static homepage + clientside-rendered-only inner pages makes more sense.
Only if you are making something like a shop or Medium.com, with a lot of dynamic public content, would you want to render on the server to give new visitors that are following a deep link a fast experience.
However, if you do plan on pumping out dynamic HTML serverside, perhaps you should skip fully featured frameworks altogether, and use something like STIMULUS to just give your pages interactivity.
I get that it has many "components" that all change at the same viewport width media queries, but with flexbox and css grid there's a much lower barrier to entry than there used to be to make your own css responsive. On the other hand, if you don't want to design anything and just want to present your data/controls as soon as possible, you should grab a component-pack for your specific framework, like a Google Material Design or Ant Design one, that directly exports components in your frameworks format.
Oh, that was precisely my reaction, that it is very obscure, I barely heard about it. Certainly less than Angular, Elm, Svelte and Cycle.js. Also, if you are just looking around for variety, see lit-element and stencil.js, which produce Web Components.
I meant that you would have the same component code running on the server for server rendering and on the client for clientside rendering. Personally, I feel like server side rendering is overhyped, the cases when it's advantageous are fairly limited. Having a completely static homepage + clientside-rendered-only inner pages makes more sense.
Only if you are making something like a shop or Medium.com, with a lot of dynamic public content, would you want to render on the server to give new visitors that are following a deep link a fast experience.
However, if you do plan on pumping out dynamic HTML serverside, perhaps you should skip fully featured frameworks altogether, and use something like STIMULUS to just give your pages interactivity.
Thanks for providing information I'll do look into that