Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Next.js 10

nextjs.org

Post reply on HN
Print view View original

121–130 of 206 posts

Re: Next.js 10

#121

Post by edgyquant »

fraktl wrote: post #86
jmondi wrote: post #66

Earlier quoted context omitted.

> but every react site I've ever used is still buggy and slow as hell This is just as asinine as saying "every Ruby on Rails site I've ever used is still buggy and slow as hell". No, every terribly coded site youve used is slow as hell.

Which means that React attracts people who aren't really developers but they want to jump in on the hype train, right?

No. People have said this about every web framework since PHP5 and its not true. Web development does tend to favor fast iteration which can lead to problems if the tech debt compounds but that doesn’t mean the people aren’t developers, at all.

Re: Next.js 10

#122

Post by holoduke »

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.rerender();
   }
I will use something like bootstrap for css. My backend can be anything. UI is just fetching data via API's I really don't like templating and compiling on the frontend. It makes the development process slow.

Re: Next.js 10

#123

Post by atom_arranger »

yawnxyz wrote: post #109
bamazizi wrote: post #71

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…

I'm rewriting a bunch of my Vue components into Svelte, and turning my Nuxt (which were previously React/Next) projects into Sapper, and it's a crazy easy process. My Svelte codebase is tiny compared to my Vue codebase. I'm slightly "worried" about Sapper not being at v1.0 yet but... it's been working great for my MVPs

Relatively recent news, Sapper is not getting a 1.0.0. Svelte is going in a different direction in the future.

https://www.youtube.com/watch?v=qSfdtmcZ4d0&t=3s

Re: Next.js 10

#124

Post by aloukissas »

pier25 wrote: post #14
aloukissas wrote: post #6

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…

My bet is because of the ecommerce part of the platform (integration /w headless ecommerce companies like BigCommerce).

Re: Next.js 10

#125

Post by vosper »

holoduke wrote: post #122

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…

Seems like you're asking for UI components (page, panel, button) that you can just use? This isn't the problem Next is trying to solve. You might be better off with something like MaterialUI, Ant, Bootstrap, of any of the many other batteries-included UI frameworks.

Or I guess Web Components were supposed to solve this problem, too, but I think they missed their window.

Re: Next.js 10

#126

Post by vosper »

atom_arranger wrote: post #123
yawnxyz wrote: post #109

Earlier quoted context omitted.

I'm rewriting a bunch of my Vue components into Svelte, and turning my Nuxt (which were previously React/Next) projects into Sapper, and it's a crazy easy process. My Svelte codebase is tiny compared to my Vue codebase. I'm slightly "worried" about Sapper not being at v1.0 yet but... it's been working great for my MVPs

Relatively recent news, Sapper is not getting a 1.0.0. Svelte is going in a different direction in the future. https://www.youtube.com/watch?v=qSfdtmcZ4d0&t=3s

I'm surprised to hear this - more details would be appreciated.

If someone doesn't beat me to it, I'll come back this afternoon and TL;DR the 22 minute video linked here.

Re: Next.js 10

#127

Post by fraktl »

edgyquant wrote: post #121
fraktl wrote: post #86

Earlier quoted context omitted.

Which means that React attracts people who aren't really developers but they want to jump in on the hype train, right?

No. People have said this about every web framework since PHP5 and its not true. Web development does tend to favor fast iteration which can lead to problems if the tech debt compounds but that doesn’t mean the people aren’t developers, at all.

So what you're saying is that React spawned an army of people who we can call developers, despite them not knowing how browsers and HTTP works, what algorithms are, how to approach developing your javascript app so it doesn't become spaghetti mess in 24 seconds and abusing terminology from systems programming just in order to make their field appear more serious than it is?

Now, what word could we use for people who are not.. well, "developers"? Programmers maybe?

Re: Next.js 10

#128

Post by eyelidlessness »

robertoandred wrote: post #77

I've never really trusted these image auto-optimizers. I always just do it my hand so I know what's actually happening.

The problem with doing something like that manually is that it’s painful at scale, and easy to forget. If scale isn't an issue, sure roll your own. But for my uses, I’m more likely to use tooling as a default, preview, then override when the preview doesn’t do what I want/expect.

Re: Next.js 10

#129

Post by fold_left »

pier25 wrote: post #10

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…

https://github.com/LukasBombach/next-super-performance adds partial hydration to next. I was tempted by this some time ago, but ended up leaving it due to concern about straying too far off-piste from next itself.

Re: Next.js 10

#130

Post by eyelidlessness »

TheMagicHorsey wrote: post #62

Am I the only developer that feels that React ... and perhaps the whole web paradigm ... is about the worst way to think about and develop client GUIs? After using Google's new Flutter framework (which is built to develop cross platform apps: iOS, Android, Web, embedded) I felt like I had my eyes open. The structure seems so much more logical and easy to navigate. The Web (and React) paradigm of putting some code in…

JSX is not HTML, even though its syntax is very similar. It’s a data structure that’s renderer-agnostic. It can be rendered to HTML, or to a live DOM, or to other outputs. IIRC, Netflix uses React to render at least some components on entirely non-web interfaces like smart TVs.

To me, that fact is what makes React (and other libraries like Preact that have a similar interface) more compelling than the template-oriented alternatives. As far as I’m aware, Flutter takes basically the same approach, just with different syntax. I believe the same is true of SwiftUI. And Elm, and the various UI libraries for Clojure.

And as another comment mentioned, you can use a variety of CSS-in-JS approaches, which at least last time I looked is actually the more common approach in the React community.

Add in TypeScript (or whatever static type system in whatever compile to JS language), and you’re basically comparing bike sheds at this point.

Post reply on HN