Q&A with Guillermo Rauch during Vuejs Global (Amsterdam)

[Applause] [Music] so is next js planning to support rss out of the box um that's a great

question so one of the things that we've sort of not supported that well yet is the idea of generating things other than html pages so for example um a lot of people want to take this idea of well i want to pre-render certain things at build time and they pre-render their pages for example but what about the open graph images so the images that go on twitter almost everybody that i know is

delegating those to runtime or they don't support them at all so basically nexjs should give you the ability to say well i also want to pre-render images at build time and then i want to do some just in time at run time kind of this idea of like deciding when you do this rendering process whether at build time whether at runtime so that applies also very nicely to other formats not just images but sitemaps and rss

feeds so you should have the ability to use these techniques right now there's some hacks that you could use so for example you could define a function to generate your rss feed um and then you could do a rewrite so you can say for example slash rss should go to slash api rss and then you generate it with a nexus api function and then you send a cache control header so you make sure it's cached so that'd be a great way of supporting

rss but it it feels like to me that there should be a more natural nexus way of saying um this is not a regular page but this is another type of format that i want to generate and use the same capabilities of static generation just in time generation server rendering etc so great question um so there's another question for you on the chat um from dominique yes sorry if i totally mispronounced that um but if you have advantages of

next over knocks they would like to hear about them um i haven't used next that much yet i'm really excited about next three and that's when i'm actually gonna start using it for my own projects uh these days i only hack during the weekends but i love to try new technologies and i also always want to make sure that versailles has the best possible experience for all frameworks so uh i want to use next three and i'll have right of the bat i know that knox has a

lot of exciting things we don't have like next content is amazing um so i think at this point it probably comes down to what do you what does your project put more emphasis on and first of all i think view and react are have very or non-overlapping communities today so obviously the choice is simple if if you like the next style of doing things to use next if you like react use knocks if you like view um but for teams that are flexible or on the fence

i think it comes down to like okay what features are absolutely critical for this project um so for example next three is gaining capabilities for functions nexus already has it on the other hand if you want better integration with git based content nux content is amazing and actually doesn't have something like that so um and both frameworks always have ways of filling in the gaps so the differences in terms of feature functionality don't in the short term