HNHacker News
TopNewBestAskShowJobs

Rauchg

3,589 karma · joined December 8, 2009

Guillermo Rauch. https://twitter.com/rauchg https://vercel.com
submissionscomments
Rauchg··on Rich Harris joins Vercel to work on Svelte full time
Hey! Guillermo, CEO of Vercel here. Security is the absolute top priority at Vercel, and you should be seeing continued progress in that area in the coming weeks and months.

We're heavily investing in security all the way from the SDK and its supply chain[1] to platform, product and cloud.

We proudly use the best infrastructure and products available to help our customers scale without stress. AGA is quite incredible[2] and so is Cloudflare[3] and we are honored to be able to work closely with the purveyors of the finest infrastructure on the Internet!

[1] https://news.ycombinator.com/item?id=29003089

[2] https://news.ycombinator.com/item?id=29158742

[3] https://twitter.com/swyx/status/1456665048949018626

Rauchg··on How long does it take ordinary people to get good at chess?
Cool tidbit from the post:

> For reference, the most improved player is (as of oct 2021) an 11 year old world chess champion from the Ukraine. His rate of improvement averaged out to 33 points per month over a period of 6 years.

Rauchg··on Next.js 12
Thanks for the feedback. I’ll bring this to the team
Rauchg··on Next.js 12
We are going all in on swcpack (spack) as well. One of the benefits of swc-as-platform is the rich ecosystem of tooling we will see develop from it. Transforming, bundling, prettifying, optimizing… all at peak performance.
Rauchg··on Next.js 12
Stories like this[1] are not uncommon:

> One of our users upgraded from Next.js 2.0-beta to 11 in 5 minutes.

> As @timneutkens said in the Q&A, Next.js incrementally improving without breaking changes is worth the investment.

If this is not the case, please let us know. We try to be very careful around this, and always leave breadcrumbs for easy upgrades in the DX if we absolutely must change something to move the project forward.

[1] https://twitter.com/rauchg/status/1405241003653484546

Rauchg··on Next.js 12
I think esbuild is a fantastic project as well as a huge inspiration. I'll share two quick thoughts[1] I have on SWC that made it a fantastic choice for Next.js:

1. SWC is designed for extensibility

We were able to use `swc` as a crate[2], without the need to fork the project

This allowed us to effectively (no divergence) and efficiently (no loss in performance) extend it, especially to add syntax and plugin compatibility that is more common in the Next.js ecosystem. We added support for `<style jsx>`, with more React optimizations and Babel plugins coming.

2. We love the Rust ecosystem

It has a stellar, growing community. It has the best long-term performance prospects for us (e.g: absolute control over memory management) and safety. We don't want to be in a position where there's another enticing migration in just a couple years, and we think Rust is a durable non-regrettable choice.

[1] https://twitter.com/rauchg/status/1425520232202792962

[2] https://github.com/padmaia/next.js/blob/cf1d081c5b2f55085ceb...

Rauchg··on Next.js 12
A huge bet we're placing on our Rust compiler is that we'll control the supply chain much more tightly. The core infrastructure of the project will ship as an architecture-optimized binary (for local dev) or WebAssembly (for browser dev).

In the process, we're being careful and empathetic about the incremental upgrade paths and ecosystem compatibility, so we're shipping a number of packages that'll completely disappear in the future.

You'll see us drop a ton of deps and weight in the short term. Watch this space. Thanks for your feedback, I'm on the same page.

Rauchg··on Next.js 12
The introduction of Middleware is specifically in alignment with our zero-config principle.

You should be able to open `pages/` and understand exactly the flow of traffic.

You'll open `pages/`, find `_middleware.js` which processes your request first, and then the rest of the routes. No magic, and heavily inspired in successful predecessors like Express.js.

Always open for feedback, let me know if this makes sense!

Rauchg··on Next.js 12
Our absolute top priority is security, hence why it's under an experimental flag that forces you to whitelist the allowed domains that you accept URL imports from.

Not only that, but before the feature goes GA, we plan to double down on our Web runtime alignment, and execute URL imports exclusively in the context of the browser sandbox (e.g.: the V8 Isolate that backs a ServiceWorker).

This is the trajectory that we are taking for most code execution at development time, and it's the technique that backs nextjs.org/live, which is the version of the dev server that runs 100% in the native browser (no VMs!).

URL Imports represent an opportunity to build a system for sharing ES modules that's much safer than what folks are doing what npm today, in my humble opinion.

Rauchg··on PlanetScale – Database for Developers
Indeed, thank you!
Rauchg··on PlanetScale – Database for Developers
From the Vercel point of view, this promises to answer one of the most frequent, interesting, and technically challenging questions since we first launched our "immutable deploys".

That is: how can I pair a brand new frontend preview deploy, with a serverless database with the specific schema my new feature needs?

This technology makes the whole serverless stack feel complete.

Rauchg··on Show HN: Clerk – all of user management as-a-service, not just authentication
Really good stuff. The Next.js integration story is already really quite good[1] and the Clerk team has really good ideas on how to make it even better and more seamless.

It's great to see a service focus on taking away all the pain related to user management, not just login.

[1] https://frontend-docs.clerk.dev/react/quick-starts/next.js

Rauchg··on My stack is HTML+CSS
Definitely. But notice he's not using the <picture> tag in this post for his image. "Just HTML+CSS" cannot possibly be connected to the 100 score conclusion (same for dismissing WordPress, which could have yielded that element as well.)
Rauchg··on My stack is HTML+CSS
The point is that "just HTML+CSS" is not the recipe for performance. You get into the same nuance as any other technology: how you use HTML+CSS is the recipe for performance. In fact, his image in this blog post doesn't have `width` and `height` set, so had it been higher up on the page and part of the "Largest Contentful Paint", not sure we'd have a 100 here.

This is where frameworks can be really helpful, and I wouldn't dismiss them. It gets quite tedious to keep up with the new attributes, cross-browser and cross-platform differences, image optimization CDNs and so on :)

Rauchg··on My stack is HTML+CSS
This is an inaccurate over-simplification. If you just use HTML and CSS, you can also have really bad Lighthouse scores. For example, vanilla `<img>` will ship the same image to every device, regardless of viewport size. Vanilla `<img>` doesn't enforce setting `width` and `height`, which makes your layouts shift. Slow-loading images and layout shifts are the very things that will downgrade the "100" score he's currently proud of.

Frontend performance is basically an iceberg[1]. We tend to look at the top and that's where the fashionable "silver bullet" currently is (whether Rust+wasm or HTML+CSS or a JS framework). Then we find deeper in the iceberg that even a `box-shadow` property[2] can ruin our day, and let alone images, YouTube and Twitter embeds, and all the things that make the web more interesting and powerful than a black page with white text.

Oh and it gets even more fun! A Lighthouse score in itself is an over-simplification. There's more to a great experience than the initial impression the site makes, like what happens to FPS when you scroll or click around[2]

[1] https://rauchg.com/2020/next-for-vercel#realistic

[2] https://ishadeed.com/article/new-facebook-css#using-an-image...

Rauchg··on Vercel raise $40M Series B
Hey chrisweekly. "deck.now.sh" we chose to redirect because it had some very so slightly out-of-date information. Thanks for calling this out. The right thing here would be to add a banner to the presentation instead, giving an option to go visit the documentation or newer presentations.
Rauchg··on Show HN: Nhost – Open source Firebase alternative with GraphQL
Congrats on shipping! This looks amazing
Rauchg··on An Honest Review of Gatsby
In principle, the two are very similar. However, the way we implement it is similar to database replication. Once a static page is produced, we can store it for usage across the entire edge network. This means you get the benefits of traditional static generation too: less backend load, higher availability, lower latency.
Rauchg··on New Stripe Website
This is gorgeous! The "Designed for developers" section is brilliant and shows off the new[1] Stripe CLI

[1] https://twitter.com/stripe/status/1191772393523400704

Rauchg··on Ask HN: Without Einstein, would General Relativity be discovered by now?
Some interesting reads on the subject:

- https://en.wikipedia.org/wiki/Relativity_priority_dispute#Th...

- https://www.mathpages.com/home/kmath650/kmath650.htm

Rauchg··on Next.js 9.4 – Fast Refresh, Incremental Static Regeneration
It's true that there will be a limit to what dependency tracking can do, because if you rename the nickname of an author of a blog post that is in 1,000,000 pages, then we'll fire 1,000,000 function invocations preemptively to recompute all pages.

That's why Next.js is focused on enabling both eager and lazy pre-rendering behaviors (AOT and JIT). There is no silver bullet :)

Rauchg··on Next.js 9.4 – Fast Refresh, Incremental Static Regeneration
Awesome! This is how we use Next.js at Vercel.

For those interested, I recently put together these slides https://jamstack-toronto.now.sh/ for Jamstack Toronto that goes more in-depth into this.

tl;DR: static pages for landing pages, static site generation for content like our blog, static dashboard with SWR against our REST API.

Video should be out soon!

Rauchg··on Pointermove event latency in web browsers
I totally agree, you want both. Negative latency!

https://rauchg.com/2014/7-principles-of-rich-web-application...

Rauchg··on Vercel, formerly Zeit, raises $21M Series A
Vercel CEO here. We are incredibly delighted to bring the new brand to the world and share the news of our funding.

For everyone who's been on this journey with us so far, thank you, and we look forward to a lot more!

Rauchg··on Launch HN: Art in Res (YC W20) – Buy art directly from artists
Awesome
Rauchg··on Get Static
As pointed out in the article, not only do you avoid 502 Bad Gateway, but rolling static sites is also trivially downtime-free, meaning no 503s either[1]

[1] https://rauchg.com/2020/2019-in-review#s1

Rauchg··on GitHub's new notifications: a case of regressive design
> I haven’t spoken to anyone who likes the new UI. Do you?

I've heard many people in our team rave about how the notifications overhaul has made them far more efficient.

https://twitter.com/timneutkens/status/1195176650008252416

https://twitter.com/timneutkens/status/1194675684020383744

Rauchg··on Where Sci-Hub Is
There are no issues with the platform (https://zeit-status.co/). The deploy has been blocked due to ToS violations.
Rauchg··on 2019 in Review
To be clear, not monoliths but 'monolithic functions'. e.g.: each function defined in the pages/api/ directory of your Next.js app gets bundled together with all its dependencies at deployment time.

Overall, the development experience should feel like a monolith. One command to do all your local dev, and deploy all at once.

Rauchg··on Microsoft’s Azure DevOps: An Unsatisfying Adventure
We moved to Azure DevOps for Windows testing for multiple large projects (Next.js, Now Desktop, Hyper) and it's been an absolute pleasure. Much better than our previous Windows CI solutions.
← PreviousPage 3 of 10Next →