Awesome! Let us know if you have any feedback!
204 karma · joined February 28, 2015
It's a breeze to set up with any frontend framework, but will work especially well with Next.js (built by Vercel).
It seems as if this wasn't clear from the UI. Would you agree? It sounds like you've assumed that it's the entire Serverless Function feature that would not be available.
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 any service of your choice?
https://nextjs.org/docs/advanced-features/measuring-performa...
Sure, there's obviously a whole UI piece to this as well – but since you interact with Next.js programmatically and there's a quite sophisticated data storage that needs to back all of this as well, Vercel optionally provides you with a pre-built solution.
But again, to be clear: If you want to use Analytics + Next.js elsewhere, Next.js supports reporting them natively – even if not hosted on Vercel.
I agree strongly. There's been a lot of chance over the last couple of months, as Now 2.0 appeared and the entire platform started adapting to it.
However, I'd also like to let you know that the entire concept of "platform versions" is just a temporary way of slowly allowing everyone to migrate to Now 2.0 at their own pace. Once this process is complete, the whole concept of platform versions will disappear and I hardly doubt there will be any major changes from that point on.
https://github.com/zeit/now-builders/tree/master/packages
(These are just the default ones, you can add your own language using https://zeit.co/docs/v2/deployments/builders/developer-guide...)
With regards to 1.0 "just working": Aside from making 2.0 more intuitive, we're heavily investing into tools that allow you to automatically transition existing applications to 2.0, so that would definitely help a lot.
Or take a look at the Dribbble page: https://dribbble.com/notleo/projects/349841-Muffin
I still need to make a few changes before I'll be able to deploy the first development version. :)
When talking about cookies, there's also a way to limit those to certain URLs.
Firstly, I was mostly talking about languages like JavaScript that are running directly within the browser. When it comes to Back-end-techniques I don't see the necessity for this type of improvement, especially since most languages there are compiling before a request even comes in (or include some neat ways to cache the output).
To be clear: I haven't thought about using this "Snippet"-technique for software running on your mac/pc, it's thought for the web. I don't care about disc space or anything like that, in this post, I was just thinking of a new way to limit the size of the data packages that are downloaded from the server, each first time someone visits a site. And this "first hit" is really important to me and to many other developers out there. It's the first time a website or -app is actually downloading to a visitors client. Therefore I'm pretty focused on making it a good experience for the user.
I'm also thankful for that "compare 1 line of code to call library function versus e.g. 15 lines of code snippet" argument, I completely agree with you there. But when I say "snippets", I'm actually talking mainly about JS-functions (for example) that can be called on a specific DOM-Element, Object, String or whatever.
You can also take a look at the comments on my site, I posted a comment about "dynamic frameworks", maybe that will be a proper solution for the future. But as I already said, as long as this is not real yet, the "Snippet"-technique is probably the best way to achieve fast web-applications, in my opinion.
Sorry for not stating everything clear enough, again. I will make sure to do better in the future. :)
I also think that choosing small libraries wouldn't help us here, because there will always be some stuff that's not being used. And that's exactly what I'm trying to avoid as best as possible here.
Also, what's wrong with copy-and-pasting code? This changes neither the formatting of the code nor makes it less readable, if you ask me (and I'm of course not talking about indenting with spaces, of course - that's terrible).