191–200 of 208 posts
Earlier quoted context omitted.
Based on his HN linked Twitter and his LinkedIn from googling his name, that does not appear to be the case at all. Not sure why someone would lob an accusation like that.
Because it's verifiably true, all you have to do is know it in your heart.
Earlier quoted context omitted.
Thanks! We developed from scratch, I frankly wasn’t aware of the template when we started but also wanted a very specific look and feel (and the whole planet section on the bottom of the welcome page obviously had lots of work). Not aware of any issues. We did quite a tight integration with Shopify such as the entire website shop is 99% generated from the Shopify items (which in turn are generated from the Print On D…
I have a site ( https://familytreechart.com ) with a similar integration with Shopify but one thing I've never figured out is how to send someone to Shopify's checkout page with a preconfigured cart. It looks like you are managing the cart on the nextjs side. How are you generating the checkout page with the right items? I've resorted to creating a DraftOrder, but those don't allow for discount codes so I also had to…
You can add to cart, then add the discount, then redirect to checkout all within one link (working on an app to help merchants generate them).. I believe that is the proper flow but I cannot remember off the top of my head I just know that is all currently possible with a single link.
That said, I have been made aware that the checkout experience will be changing next year. I'm not sure what that entails yet just that it is coming.
Also, having worked with Shopify rather heavily since August, I love it.
[1] https://community.shopify.com/c/Shopify-Design/Cart-Use-perm...
Congrats Guillermo and the whole team at Vercel! Initially I was a bit skeptical about Next.js, but nowadays I really like this all-in-one experience. There are still some rough edges, but it's understandable given the scope of this project. I'd love to see more focus on TypeScript, integration with something like esbuild or Snowpack or maybe even a Deno version (there's already Aleph.js). What may not be obvious at…
I was a little disappointed, though, when they released the new Image component and it didn't seem to support AMP sites out of the box :(. I had to write my own wrapper function.
Earlier quoted context omitted.
Well, how about “dropbox is aimed at the general population of computer users, and not just computer savvy developers”?
Vercel is aimed at the general population of web developers, not just the savvy ones like you
I'm trying to decipher what this is. So far I've learned there's a thing called "Jamstack" that seems to be about static websites. How does one manage databases with this technology?
This means you have zero server side rendering, you're just serving up static files, which of course is faster and can utilize CDNs and such.
SSR is also still possible, that would basically give you a classic model of fetching data on request and then rendering the page. My impression is that this is meant more as a transition than a preferred option.
The SSR features are also optimised to the point that the data fetching and rendering is decoupled. So a client side (JS) navigation only needs to fetch the new page's data. The DX around this is super smooth (just expose an async function...)
Many congrats Vercel! I've been a big fan since Zeit platform version 1 - I remember the transition to platform version 2 was difficult but over time I can see how incredible of a platform you've become. Just a note from a fan - I hope you all can determine a way to approach the future with longevity and corporate independence. The web really needs your entire teams dedication towards performance, end user experience…
> avoid being acquired Don't think that's possible after raising such amounts of money. Their way out is now either getting aquired for loads of cash or going public. Going public also means loosing parts or all of your control over the company. Those investors will want to see their money back some time in the future.
No offense, I think people are crazy to rely on a stack they can easily make themselves vs. a series B startup. It's not that difficult to build and deploy full stack apps on your own server.
I pushed a new proof of concept to Github yesterday and deployed it in literally 3 clicks on Vercel.
Please show how to do this with AWS.
Then take a look at the features like preview deployments, CDN, environment variables etc. Does your solution cover all of them with the same ease?
I think people are crazy to accept abstraction on the machine layer but keep reinventing the wheel for the infra in the middle. These services let's you focus on the actual product.
Earlier quoted context omitted.
how many times do we need to link to the dropbox comment before HN commenters get it? https://news.ycombinator.com/item?id=9224
I Don't care. There are tons of examples of building shit on stacks that won't be around. How about investing a shit ton of time into Azure Kubernetes using Docker containers to find out they dropped support, just like this startup can drop out and never be heard of again. Good luck with that.
I have a bunch of apps on Vercel right now and zero worry that I will be able to deploy them somewhere else should they drop out for whatever reason. They are just Node/React apps.
Earlier quoted context omitted.
> avoid being acquired Don't think that's possible after raising such amounts of money. Their way out is now either getting aquired for loads of cash or going public. Going public also means loosing parts or all of your control over the company. Those investors will want to see their money back some time in the future.
MSFT/GitHub would be an epic acquisitor for Vercel.