161–170 of 206 posts
Why are all these frameworks so big. Compiling, boiler plating, templating, huge API's etc. I just want a real component framework where i can have something like: include "MyComponentFramework.js" page = new Page(); panel = new Panel(); button = new Button().addCssClass("buttonclass"); Page.addComponent(panel) panel.addComponent(button) button.bind('click',function(){ panel.addComponent(someComponent); panel.rerende…
Can anyone compare this to something like Hugo or Jekyll? Why is the more complex JavaScript build chain worth it?
Try it on their own site:
Resulting in duplicate content to https://nextjs.org/
Maybe duplicate content isn't a problem with modern SEO - but it's a problem for my workflow and is potentially one reason why NextJS won't be on my list for any new projects.
As someone who only really built websites using jQuery / custom vanilla js and good ole CSS2, this stuff feels completely alien to me
I even did a 3 month django project with a view that was almost entirely JavaScript—it would have been a perfect candidate for react but I refused.
As a compromise with myself I used es6 js on that and eliminated use of jQuery from my code.
About a month ago I started work on react. I had very similar feelings going in and was annoyed at having to figure out the node dependency thing. And I was aghast at the “tool chain” which is the post processing you need to do on React and other modern front end.
However, I was really surprised at how much better it is to build front end using this rather than html templates and sprinkles of js.
I was also surprised to find out that the django community barely has a pulse compared to what is happening in react.
It’s safe back there, but there is no innovation. Once you see what is happening in modern web, it feels like a ghost town.
I think it’s a pretty good time to get into React right now. CRA just got an update, functional components are mainstream and now there is this nextjs.
I encourage you to give react a try, at the very least it will make you think more about why you’re building the way you are.
Can anyone compare this to something like Hugo or Jekyll? Why is the more complex JavaScript build chain worth it?
In short With Next you control when things are rendered: SSG/SSR/CSR, so you get much more flexibility and can cover more use-cases. And it is React based, which is a huge plus, especially if you adhere to a modern style.
I find it funny that even though it's been reported a number of times, the NextJS routing system is still flawed Try it on their own site: https://nextjs.org/index Resulting in duplicate content to https://nextjs.org/ Maybe duplicate content isn't a problem with modern SEO - but it's a problem for my workflow and is potentially one reason why NextJS won't be on my list for any new projects.
I understand this is a Vercel framework and probably a great distribution channel for new business and increasing overall revenue. But, I'm a bit disappointed the "next" version is more about Vercel's own internal business agenda. Promoted as amazing "DX" is not really true. It had a better DX compared to the other tools, that's why it grew so popular, but not seeing anything real DX related in version "10". Other to…
What is DX? New jargon?
Earlier quoted context omitted.
I feel the same way. We've switched from React to Svelte at work. Going back to React would be a step backwards for us, so much feels needlessly overengineered with awkward APIs. React was a great improvement on Angular, but luckily things are still moving forward.
Well, this sounds a bit typical JS dev talk. React isn't all that terrible, it's actually quite good and battle-proven. It has great libraries, many devs are familiar with it and if you know it well you can be pretty damn productive with it. Not to say Svelte doesn't have great innovative features, but I myself don't still feel that tempted to jump into Svelte. What some of us don't like, is the infamous JS churn whe…
The big elephant in the room most of these frameworks are missing is partial hydration. Instead of hydrating the whole page, only the interactive parts are hydrated, sending the absolutely minimal JS needed to the client. AFAIK only Marko has this feature today. Since it's developed and used at Ebay they focused on the best SSR+hydration experience from the start. Imba v2 will also have patial hydration (confirmed by…
Prediction: Google buys Vercel, kills Angular, steps further into e-commerce
Could be. Angular growth has stalled for the past year or so. Polymer is pretty much dead. OTOH hand why would Google invest in a React-based solution? Google could start from scratch an create the next best thing if they wanted to. To me it's pretty clear the future is a compiler based approach like Svelte, with support for SSR, partial hydration, static generation, and dynamically loading smaller parts of a page (e…
Wtf is hydration? Is that like when websites used to render json payloads on the page on first render?
This field is getting scammy with its nonsense. Create one more stupid word, and I swear I will lose my god damn mind.