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

Next.js 7

nextjs.org

Post reply on HN
Print view View original

31–40 of 40 posts

Re: Next.js 7

#31

Post by kabes »

anonytrary wrote: post #26
ldthorne wrote: post #3

Time and time again, the Next.js (and Zeit) team blow me away. The rate at which they release new, high-quality versions of their products is astounding, especially given how few people are working on this full time -- it's basically just Tim Neutkens, who's insane: he's constantly pushing updates, reviewing PRs, and finds time to be very active on the support channel. We use a bunch of Zeit's tools (particularly Nex…

Curious why you didn't mention Arunoda -- does he not work on it anymore. IIRC Arunoda started Next.js right after (perhaps because of) leaving Meteor ecosystem.

I don't think he created it, but he was there early on and works for Zeit. Still eternal grateful for him creating kadira.

Re: Next.js 7

#32

Post by sakarisson »

I really like the styled-jsx changes. One major issue I had was the fact that it's been difficult to pass styles onto child components without leaking them through the entire application. I'm really glad to see that they fixed this issue. Great job, Next.js team! I'm really blown away by Zeit in general.

Re: Next.js 7

#33

Post by anonytrary »

kabes wrote: post #31
anonytrary wrote: post #26

Earlier quoted context omitted.

Curious why you didn't mention Arunoda -- does he not work on it anymore. IIRC Arunoda started Next.js right after (perhaps because of) leaving Meteor ecosystem.

I don't think he created it, but he was there early on and works for Zeit. Still eternal grateful for him creating kadira.

Wow, TIL. Also a very nice display of Cunningham's law: "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer."

Re: Next.js 7

#34

Post by cutety »

thsowers wrote: post #20
cutety wrote: post #19

Earlier quoted context omitted.

As others have mentioned, Nuxt.js is what you’re looking for. And, it’s pretty great to work with. Prior to using it, I just got “done” building out my significant project with vue, just plain vue. When I started this next one, I decided to give Nuxt a shot, and it has been like the missing piece I was looking for in the previous app. It provides structure to you app, gives you everything you need to build out a fron…

Thanks for sharing your experiences, could you recommend any resources for plugging data into Nuxt? This is what I've always been curious about coming from Meteor

I can’t think of any particularly good articles, or things of that nature. But, you’ll mostly be utilizing Vuex to store, mutate, & fetch data. If you aren’t already familiar with it, the docs are great [1]. It’s fairly simple to use, and as your app grows you’ll likely find yourself writing more and more boiler plate store code, but fortunately, there are a ton of really great plugins/utilities the community has built for Vuex that help eliminate a lot of that boiler plate, and make it easier to work with an ever growing store. The Awesome Vue repo [2] has a pretty comprehensive list, and you can probably get some ideas of how you’d like to work with it from seeing all the options, for example Vuex-persistedstate & vuejs-storage allow you to interface with localstorage, while Vuex-pathify provides a nice, less verbose interface for actually working with the data in the store, and then there are things like vuex-api and vuex-rest-api that eliminate a lot of boilerplates code for interacting with apis to fetch/update data.

[1] https://vuex.vuejs.org/

[2] https://github.com/vuejs/awesome-vue/blob/master/README.md#v...

Re: Next.js 7

#35

Post by machiaweliczny »

The speed improvements calculations seem weird to me. Shouldn't one build done in 178s instead of 304s be 70% faster instead of 42% faster? (you can do 1.7 of build using the old amount of time)

Re: Next.js 7

#36

Post by timneutkens »

anonytrary wrote: post #33
kabes wrote: post #31

Earlier quoted context omitted.

I don't think he created it, but he was there early on and works for Zeit. Still eternal grateful for him creating kadira.

Wow, TIL. Also a very nice display of Cunningham's law: "the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer."

I'm going to post the same answer I gave in another thread on the initial post:

As said elsewhere, I mostly act as a curator of a very large effort of hundreds of individuals. The project was actually co-created by several other people who work on infrastructure at ZEIT (e.g..: Naoyuki Kanezawa led all the initial releases, designed important parts of the framework, Arunoda Susiripala contributed the test harness and key build pipeline infrastructure, and so on).

Re: Next.js 7

#37

Post by cercatrova »

cutety wrote: post #19
asselinpaul wrote: post #8

What's the closest framework for Vue.js and how close is it in terms of functionality? Asking because Next.js has been one of the reasons I've become more interested in the React ecosystem.

As others have mentioned, Nuxt.js is what you’re looking for. And, it’s pretty great to work with. Prior to using it, I just got “done” building out my significant project with vue, just plain vue. When I started this next one, I decided to give Nuxt a shot, and it has been like the missing piece I was looking for in the previous app. It provides structure to you app, gives you everything you need to build out a fron…

How is Nuxt different from vue-cli? I thought the latter had all the features of the former and I was struggling to understand the difference when I researched both.

Re: Next.js 7

#38

Post by true_religion »

erokar wrote: post #2

Not clear to me from the release notes if there now is an easy way to proxy to a server in development (if you for instance have a Django driven API on port 8000). This is easily done with create-react-app by just adding a line in package.json. In Next you've had to either set up and configure nginx locally or proxia via an Express server, both options that that are a bit of a hassle to set up for such a common case.

I have done it in the reverse way: have django act to proxy requests to the node server.

That way ypu can use django sessions, authentication, login, admin, etc.

The node server just does rendering, and creates client side JS based on data it is given by Django.

It took 25 lines of code, yes, but pretty much worth it if you have a long term project like a single app that your company is built around.

Re: Next.js 7

#39

Post by zerr »

tvalentius wrote: post #24
wiradikusuma wrote: post #15

Could anyone explain what Next.js is? I use React (using create-react-app), but I'm under impression that React is a JavaScript framework (like Spring is Java framework, or RoR is Ruby framework). So Next.js is a framework for a framework?

React is more of a library instead of a framework and it's just the view layer. Next.js is a framework(minimalist) for React. https://github.com/zeit/next.js/

And what would be the "maximalist"/rich framework for React? (with lots of pre-made RAD components I guess).

Re: Next.js 7

#40

Post by dcherman »

machiaweliczny wrote: post #35

The speed improvements calculations seem weird to me. Shouldn't one build done in 178s instead of 304s be 70% faster instead of 42% faster? (you can do 1.7 of build using the old amount of time)

What you're saying is that comparing the existing build time to the new one, the existing one is about 70% slower. You can also phrase it as comparing the new build time to the existing one, it's about 42% faster.

Both are true statements, however people generally like to discuss how much improved the new releases are versus how much worse the old ones are.

Fun fact, it's important to understand that relationship in other areas as well like the stock market; if your holdings lose 50% of their value, they then need to increase by 100% for you to be back neutral :)

Post reply on HN