3 ms·
I recently started to look at native web components (custom elements), at first I thought I could replace {insert your framework here} with it, but it seems tha
by norman784 5y ago
I recently started to look at native web components (custom elements), at first I thought I could replace {insert your framework here} with it, but it seems that it doesn't solve the issue, you still need some kind of framework built on top of it to achieve the same goal.
If you have some recommendations or want to share your experience with working only with web standards I want to read them :)
- pjmlp 5y agoEasy, Java and .NET SSR frameworks (which support components for two decades now), + vanilaJS for Ajax like behaviours. Loads fast, easy to debug without tons of layers in the middle. And yes, I also do manually make use of script and vendor JS libraries. Naturally it only works when doing side gigs on my own, on big Web projects where my role is mostly BE/DevSecOps, I go with the flow.
- leonardopainter 5y agoThat isn't a solution. Everybody moved away from this approach for web applications for good reasons.
- pjmlp 5y agoThe craziness of SPA frameworks running headless browsers, rediscovering SSR as if they are inventing something that no one else thought about, proves otherwise.
- stickfigure 5y agoHaving been on this ride since before HTML was a thing... I'm going to make a prediction: JS SSR will be a brief flash in the pan. In another ten years, we're going to look at it the same way we look at JSF today. "What were we thinking?"
- pjmlp 5y agoGiven the WebAssembly adoption rate of frameworks like Blazor, plenty of people miss JSF and WebForms today.
- leonardopainter 5y agoWell, I think when they moved away, they also increased the complexity of their applications as well.
- imtringued 5y agoI agree, I am writing some apps like that and we still want some minimal level of interactivity that is suited to react. E.g. a file uploader.