Rauchg

9 ms·

61.
Share GPT – Chrome extension for one click ChatGPT sharing(sharegpt.com)
2 points by Rauchg 4y ago|0 comments
62.
by Rauchg 4y ago
This is excellent. I've already found it valuable in a few searches, and I've only had it installed for 20 minutes.
63.
by Rauchg 4y ago
We're super excited about partnering with TiDB. This is the first truly serverless HTAP db in the market, which means the average app developer will never have to worry about complex data sync jobs or having entire categories of really
64.
by Rauchg 4y ago
Both things can be true. We continuously improve Next.js _and_ Vercel, and we invest in other frameworks as well (like Svelte[Kit]). Happy to hear any feedback you have about how we can make Next.js even better!
65.
by Rauchg 4y ago
Broadly in agreement, except support is not “random”. It’s deterministic, easily versioned and well tested. We are improving the DX further so that the feedback loop of what features are supported is nicer, with advice on what to do when so
66.
by Rauchg 4y ago
JSX is optional. It’s just a way of representing the nested object hierarchy that happens to be convenient and widely supported (TypeScript has built-in support)
67.
by Rauchg 4y ago
Congrats! Exciting news for YC
68.
by Rauchg 4y ago
Hey jokethrowaway. I'd love to get more color on your experience upgrading your Next.js sites: feel free to email rauchg@vercel.com. - On local: `npm i && next dev` is guaranteed to be stable. - On remote: your pipeline is guar
69.
Mailing: Build and test and send emails with React(github.com)
2 points by Rauchg 4y ago|0 comments
70.
Makeswift 2.0: visual builder for Next.js(makeswift.com)
1 points by Rauchg 4y ago|0 comments
71.
by Rauchg 4y ago
Since the post mentions Next.js, it's worth calling out two streams of ongoing work that solve major painpoints of SSR: 1. A filesystem convention (`*.server.ts`) for more cleanly separating client and server component trees 2. The int
72.
Reflect: An App to Think Better(reflect.app)
2 points by Rauchg 5y ago|0 comments
73.
by Rauchg 5y ago
I think I misunderstood his comment. I focused on the `index.html` example, but I think he was talking about servers (thanks for pointing that out). That said, the transition was good for servers too depending on what you were using. For ex
74.
by Rauchg 5y ago
That never stopped working. Neither on the edge side (as your live site indicates, which has been edge cached for 109 days in San Francisco), or on the deployment site, as the example below shows: Try it out: https://hi-there.ver
75.
by Rauchg 5y ago
You absolutely can! The data loader concept in Remix is semantically equivalent to `getServerSideProps` We are making sure both Remix and Next.js work excellently at the edge by compiling down to our Edge Functions primitive ( https:/&
76.
by Rauchg 5y ago
On a high level: if Svelte succeeds, the Web succeeds and Vercel succeeds. More concretely: we want Rich to help shape Vercel's support for frameworks as an open platform. We want to hear how, as a framework creator, the platform can b
77.
by Rauchg 5y ago
Absolutely. A core goal for us is to Lower the Barrier of Entry[1] to building for the Web. Building a beautiful and fast Web experience needs to feel myspace-code-easy (or as Rich Harris puts it: it has to be fun!). I think ultimately that
78.
by Rauchg 5y ago
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
79.
by Rauchg 5y ago
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.
80.
by Rauchg 5y ago
Thanks for the feedback. I’ll bring this to the team
81.
by Rauchg 5y ago
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.
82.
by Rauchg 5y ago
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.
83.
by Rauchg 5y ago
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 cra
84.
by Rauchg 5y ago
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 brows
85.
by Rauchg 5y ago
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 pro
86.
by Rauchg 5y ago
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 do
87.
SWR 1.0: The React hook for speedy data-fetching(swr.vercel.app)
3 points by Rauchg 5y ago|0 comments
88.
by Rauchg 5y ago
Indeed, thank you!
89.
by Rauchg 5y ago
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 prev
90.
Next.js 10.1 – 3x Faster Refresh, Image Improvements, Apple Silicon Support(nextjs.org)
7 points by Rauchg 6y ago|3 comments

More ›