Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Rauchg
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
Rauchg
3y ago
> Turns out Vercel are trying to kill solutions like Tamagui No one is trying to kill Tamagui. Why would we want that? > the higher ups there are investors in Tailwind I don’t know any investors in Tailwind at Vercel. I’m certainly no
32.
▲
by
Rauchg
3y ago
Indeed. We're super happy and honored to support Svelte!
33.
▲
Speeding up the dbt docs by 20x with React Server Components
(dagster.io)
4 points
by
Rauchg
3y ago
|
0 comments
34.
▲
by
Rauchg
3y ago
So is my own site: https://twitter.com/rauchg/status/1652093980958683137 Scores need to be adjusted by and looked at through the lens of complexity. Next.js powers some of the most sophisticated web applications i
35.
▲
by
Rauchg
3y ago
Good article! I always notice this same effect when I visit my parents in Argentina or I'm in Europe. > Using a global CDN can help get your assets to your users quicker, and most companies by this point are using something like Clo
36.
▲
by
Rauchg
3y ago
Except my preference for SSR as the default dates as far back as 2014 and is rooted in the laws of physics[1] Downloading an empty shell, downloading code to render a bunch of spinners, to then incur in a bunch of waterfalls of data and mo
37.
▲
by
Rauchg
3y ago
I believe that was just their demonstration. They're calling it implicit code execution so it's ought to be done transparently to the user for the queries that qualify as requiring code.
38.
▲
by
Rauchg
3y ago
Do note that while Astro is a fine choice, your blog has much snappier page transitions with speculative prefetching and pre-rendering, while maintaining an equally good Lighthouse score. As projects scale this matters more. For example, ha
39.
▲
by
Rauchg
3y ago
It's both inline editing and the ability to link arbitrary rendered text to its originating CMS and content flow. More detail here of how this scales to any content model complexity: https://twitter.com/rauchg/stat
40.
▲
Migrating Rauchg.com to Next.js App Router and RSC
(twitter.com)
2 points
by
Rauchg
3y ago
|
0 comments
41.
▲
by
Rauchg
4y ago
Totally, I don't like surprising behaviors either. At the time we made that decision the `CDN-Cache-Control` proposal didn't exist, so it was a tricky spot. There also really wasn't a UI opportunity in this case (although one
42.
▲
by
Rauchg
4y ago
Unless I'm misunderstanding you: it's not about dev or prod. It's that you want Vercel to cache a dynamic page, but not your visitor. That allows you to be in control of the ship: if you purge the CDN, you don't risk a c
43.
▲
by
Rauchg
4y ago
The gist is (which the support engineer referred to as the internal RFC): instead of stripping `cache-control` `s-maxage` / `stale-while-revalidate` values, we should support Targeted HTTP Cache Control[1] (i.e.: `cdn-cache-control` an
44.
▲
by
Rauchg
4y ago
We'll definitely be looking into usage limits after the fix rolls out.
45.
▲
by
Rauchg
4y ago
Re-posting my Twitter update[1] here: We've concluded our analysis. 1. We're refunding the overages 2. We identified the root cause The root cause is that the Astro bundle handed to the deployment process is monolithic. There was
46.
▲
Clerk Raises $15M Series A
(clerk.com)
1 points
by
Rauchg
4y ago
|
0 comments
47.
▲
by
Rauchg
4y ago
Interestingly, I have the exact opposite bet: “SPAs were a zero interest rate phenomenon”. Putting the burden of compute on clients, and shipping slower apps for the sake of DX and convenience. Customer-first wins. Looking forward to see ho
48.
▲
by
Rauchg
4y ago
I actually strongly advocate for: SSR and server is the absolute best default[1], and Next.js gives you tremendous flexibility on where to place your compute[2], including skipping SSR altogether[3], with the best-in-class static export tha
49.
▲
by
Rauchg
4y ago
To clarify: there's no "native" fetch to patch. Both Nuxt and Next have been adding it to the runtime to normalize it across Node.js versions and environments, and to add critical capabilities that the Web standard lacked (li
50.
▲
by
Rauchg
4y ago
Sorry about the bad experience, can you share what errors you ran into? Feel free to email: rauchg@vercel.com We’ll try to debug by running the demo ourselves in the mean time!
51.
▲
by
Rauchg
4y ago
Nice references, thanks for sharing!
52.
▲
by
Rauchg
4y ago
Very excited to see the Rust-ification of Python tooling, similar to what we’re seeing in the JavaScript[1] tooling ecosystem. [1] https://leerob.io/blog/rust
53.
▲
by
Rauchg
4y ago
As another commenter mentions, you can also certainly combine the two technologies, if you don't opt to go full stack with Next.js (e.g.: with Prisma or Kysely, combined with Planetscale)
54.
▲
by
Rauchg
4y ago
I'm biased (having started Next.js), but I found a comment on the recent HN thread "The Market for Lemons"[1] thread quite insightful. Basically, @christophilus makes the case that projects they'd work with always end up
55.
▲
by
Rauchg
4y ago
You'll also be happy to hear this :) https://twitter.com/robpalmer2/status/1620869647322189824 > ECMAScript excitement > Congrats to Justin Ridgewell @vercel & @legendecas on advancing the "Asy
56.
▲
by
Rauchg
4y ago
The way to think about our edge runtime is (which is something you're seeing across the board in the industry) is that there's a pure subset of WinterCG APIs, plus Next.js enabling a compatibility layer on top to play nicely w
57.
▲
by
Rauchg
4y ago
One fascinating thing (especially in view of this topic) about `next/image` is that the primary reason we decided not to optimize upon `next build` or `next export` is that we'd have all these customers migrating from Gatsby telli
58.
▲
by
Rauchg
4y ago
> They advertised open standards and then did a bait-and-switch to proprietary systems I'd love more detail on this. We have made major investments in open source and ensuring Vercel is an open platform. ◆ The Vercel Build Output AP
59.
▲
by
Rauchg
4y ago
That's definitely what RSC accomplishes, which I mentioned in my comment.
60.
▲
by
Rauchg
4y ago
> Both then STILL send the full data model to the UI (check the __NEXT_DATA__ on Walmart.com and __TGT_DATA__ on Target.com) because Next.js doesn't quite offer the right amount of control over what to send back (compare this to Ast
More ›