Live data from Hacker News

Next.js 10

nextjs.org

131–140 of 206 posts

Re: Next.js 10

#131
post #35

I tried nextjs because I thought it would be a good way to learn React but I found it really confusing. Is it really better to master React first then try nextjs?

I think create-react-app is much more beginner friendly. Fewer concepts to learn. Rolling your own or using script tags to begin with is also an option (see this course for an example: https://egghead.io/courses/the-beginner-s-guide-to-react )

And create-react-app would be all I would ever need except that SEO on single page apps that don't have data loaded upon load really sucks compared to server side rendered pages. Is there a way to build a site using create-react-app and enable server side rendering without implementing a whole other framework like Nextjs?

Re: Next.js 10

#132

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…

Basically what your example is describing is jQuery with some functions wrapped around some stuff. Sure, if you want to write a ton of imperative code, you can do that, but people who have been building UIs on the web for a couple decades have been down that road and have collectively determined it’s a nightmare.

Re: Next.js 10

#133

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…

Whenever the Next.js + Vercel combo gains a new feature, Vercel ensures that it's available in standalone Next.js too – even when deployed to other providers. That's true for all the features mentioned in the Next.js 10 blog post: Image optimization, Internationalization, but also Analytics. Since you mentioned the latter: Did you notice that we wrote a detailed documentation page about how to report those metrics to…

Yes, but that reporting was already part of 9.5?

Re: Next.js 10

#134
post #36

Earlier quoted context omitted.

It _can_ prerender all of those combinations. Here is a directory I made with 1000+ pages, prerendered and hosted for free on netlify: https://www.givepuppylove.com/organizations/ . I've found that single digit thousands is about the maximum you can currently have and keep build times reasonable. If you want to recognize the user's location and display the appropriate currency or language, you would probably want to…

What happens if there are millions of pages? Wish Next.js would have a "scalability issues and solutions" documentation...

For each page, you can set `fallback: 'blocking'`. If set, the page is not built at compile time. Instead, it will be compiled the first time it's requested. So the first request will take longer, then after that it'll be fast.

Alternatively, on a per-page decision you could decide to use server side generation (page built at compile time) or server side rendering (page compiled when requested).

You have options that let you spread out the time, but ultimately it's going to take time to build millions of pages.

Re: Next.js 10

#135
post #93

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?

If UX is user experience, the user flows of a product/application and how people generally feel about using/interacting with it.

The DX is the developer experience. It follows a similar idea. How do you feel about using git? What about Visual Studio Code versus neovim? How do you like using Elm? What don't you like about.

Think about all the libraries or frameworks you use. Some of them clearly offer a better experience than others, these are the types of things that affect the DX.

Take documentation for example, a piece of tech (whether it be an IDE, library, or CLT) with proper documentation full of examples, usage, and recipes is extremely nice. I would favor tech that has better documentation over others, documentation is just one part of the DX. Not the only part, but hopefully you can start to see what can increase or decrease the DX.

Re: Next.js 10

#136

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…

Seems very disingenuous.

The only thing on the list that's related to Vercel is the analytics platform. Even that is clearly listed as something you can leverage via your own provider.

Re: Next.js 10

#138
post #119
post #110

Earlier quoted context omitted.

Which UI component library, if any, do you use with Svelte ?

UI component libraries for Svelte are a little lacking in maturity in my experience. I would recommend including a CSS library such as Bootstrap or Materialize. Tailwind is also popular, but not my cup of tea.

So, React is backwards, but you are using Bootstrap instead? Lol. Webdevs at their best.

Re: Next.js 10

#139

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

TL;DW - parts of Sapper may be in a future version of Svelte, but looking to add support for mixed static and dynamic pages and improving development speed to change by using Snowpack.

Re: Next.js 10

#140
post #127

Earlier quoted context omitted.

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…

They literally are developers stop gate keeping its ignorant
Post reply on HN