@Altimor
The build quality of American homes is way worse compared to most European homes. Insulation sucks, and nothing is built to last.
I prefer to live in a smaller space with better build quality
@FromKulak
Brazil is a counter example of this. Politicians are very well paid and Brazil has one of the highest corruption rates in the world. Getting a high paycheck never stopped anyone from wanting to get even more money.
Switzerland is also a counter example, but the other way around.
@housecor
3 is only true as a recommendation if you're fetching on the client. If you're fetching in a server component, you can fetch locally within components without paying the price of client-server waterfalls.
@primalpoly
The Lord of the Rings Trilogy - Extended Edition.
I watch them every single year and still cry liters of tears during the last scenes of the RotK.
@ChristophMaile
@dvassallo
Wow didn't think our numbers in Switzerland were so good. Probably due to the pretty hard to get driving license. Many people fail multiple time until they're able to get it.
@RhysSullivan
IMO, the best recommendation here would be to make sure you properly implement authorization, ideally in your data access layer (see )
A file with a top-level "use server" is akin to a controller class found in other backend frameworks. Exported functions
@dan_abramov
@AdamRackis
@JLarky
@aidenybai
Opting for less short form and more longer form community engagement style like podcasts or interviews might be less exhaustive and more fruitful :) those were the ones where I learned the most.
The one you did with
@kentcdodds
was amazing and I think was very helpful to clarify
@culturaltutor
@lucasbagnocv
In Fribourg, Switzerland we celebrate both Christmas and Saint Nicholas day which is on December 3rd.
I still remember my primary school teacher telling us the story of Saint Nicholas and the butcher.
@jherr
Not exactly what you're asking for, but
@vercel
's style guide has one of the most complete setups I've seen out there:
I believe
@mrmckeb
is the main maintainer
@__cski
@housecor
Many React application fetch data locally within components:
function UserProfile() {
const query = useQuery({ queryFn: getUser })
// ...
}
This often cause client-server network waterfalls, because the component needs to render before it can start fetching.
The
Since I've been using
@RewindAI
, I've been able to be even more present in meetings by not worrying about taking notes thanks to its amazing recording feature. Rewind is truly a superpower. So excited about those new improvements!
@_walcliff
@interesting_aIl
Lol Brazilians do that all the time with public parking. If you don't pay you risk getting your car keyed, so you pay even knowing that it isn't legit
@theconfigurator
@greysen_paige
@enlightenedcoop
@Tojiro
Super useful when you have a work Google account, and you want to separate your work browsing experience (history, extensions, cookies...) from your personal one.
Plus, there's a nice shortcut to switch between profiles: CMD + SHIFT + M
@youyuxi
Yes, Vite is a valid solution, and so is Next.js. There are valid reasons for switching to Vite, as there to switch to Next.js. Each has its trade-offs and benefits.
We decided to switch to Next.js after considering those trade-offs and our own needs and decided to share our
@TkDodo
Better support (or docs/examples?) for the async request-response pattern, which is used for long-running tasks:
1. POST task
2. Poll task status until status is "completed"
3. GET task results
Computing the displayed loading status is always a headache when implementing this.
@feedthejim
- Primitives for client-side fetching and live updates (something similar to GraphQL subscriptions)
- Type-safe page params and search parameters
- Auto-optimization of SVG files (with SVGO?) when using it with the Image component.
- IDE/Code editor extension to display if page
The first published version of this blog post was about the App Router's stability. That one quickly became obsolete thanks to our friends at
@vercel
❤️
We recently shipped our new dashboard built with
@nextjs
13's App Router. Here's what we learned and what you need to know when building your production app with the App Router:
That's why we should learn how to carefully chose which authorities (people or orgs) we trust.
Look for intellectual honesty, expertize, and who already trust them as signals.
An individual scientist is guided purely by the empirical evidence... on matters where they have the expertise to judge the evidence. On other matters they have to trust the judgment of those other scientists who are, themselves, experts in that other field.
Had a fantastic time at the
@reactjs
conf! I met so many great people and had memorable conversations. The trip from Switzerland to Las Vegas was undoubtedly worthwhile.
Thank you to everyone who made this possible.
@rauchg
I'm blown away by it!
I started a conversation and midway, I asked him to correct any English mistakes I would make while we talked. He was able to both converse and politely correct any mistakes I would make.
@RhysSullivan
> you can’t put authorization on a function you didn’t realize was ever exposed
If you consolidate all data access and authorization in a data access layer, then you wouldn't need to worry if a function declared in your presentation/application layer (outside of the DAL) is
@AdamRackis
@ryanflorence
Linear has that with their sync engine. It is what makes it so fast. Check out this to see how it works:
@replicache
offers a similar solution. This is what powers
@thdxr
's demo
@avindrafernando
@housecor
@nextjs
@leeerob
The RC version of the docs is already updated with the new name. It probably will become the default docs when React 19 and Next.js 15 are released.
@yagiznizipli
@vercel
Hahaha true, but I lived twice in Istanbul for a few months.
I would have expected that they at least would have given a reason, even if it's a stupid fake reason.
@CFDevelop
A minority will read them. However, this minority teach ofhers around them, promote the tool, and might even produce even more educational content. Write for that minority
@JLarky
It looks like the page you requested isn’t static. If it’s static there wouldnt have been a cold start at all. The page would have been cached in a CDN and served as a static html file.
@jaredpalmer
@vercel
- a type-safe library to manage search params in Next.js
- a stacked PR tool that is easy to use and is well integrated with GitHub
- an infinite pagination solution for RSCs
- a live update/subscriptions solution for Next.js
- a component to auto-optimize and use SVG files
- an
@leeerob
@therajatkapoor
@vercel
The best solution here is probably to allow accounts to hold multiple email addresses like GitHub does. Your personal and pro email addresses.
@rickhanlonii
@TkDodo
But by doing this you miss on colocating data requirements within the component itself, no?
Devs are more likely to forget to remove the fetch present in a RSC/loader when they remove the child components that consume the data.
"But features aren’t done when they’re deployed. That’s when customers see them for the first time. It’s the most important time in a feature’s lifecycle but it’s also when product teams drop attention."
These guys get it.
New just dropped 🚨
Bucket is customer-centric feature management.
What is that? It's feature flagging with built-in customer evaluation for B2B product teams.
→ Rollout
→ Evaluate
→ Iterate
Check out the new site or this 🧵to learn more.
@brian_lovin
@linear
has shown and proven that you can build high-quality software successfully at a startup from an early stage. Quality and development speed doesn't need to be a tradeoff. So excited to also have
@QuillChat
,
@height_app
, and
@ClayHQ
sharing the same mindset!
@thdxr
@lil_dill
For sure. At the end, the drive to care for these things should come from within oneself 'cause it's hard to foresee and calculate the exact benefits of spending time on details and beauty.
I'd say people/companies are often too pragmatic in the way they build products, which
@dan_abramov
@inngest
@dan_abramov
another struggle is the lack of documentation on how to achieve request deduping with GraphQL queries. Like how can we make sure that components only request the data that they need, while not requesting the same data twice.
The React `cache` function doesn't seem
@t3dotgg
Google Play Music was the best by a large margin, before they ended it. The music recommendations were 👨🏽🍳💋 I'd use the radio feature all the time
@rickhanlonii
@TkDodo
I might be missing something, but it looks to me that Remix's solution still couples the child components to loaders. Data requirements are not colocated since components don't fetch their own data.
In large codebases this is often a source of issues. One can easily forget to
@dan_abramov
🖐🏼We are using it at
@inngest
.
The biggest issue so far is not having some sort of server context that can store a value which can be updated from a client component. Think of a user-set global filter that affects all the data fetches of the app.
We're using storing it in a
@WarrenInTheBuff
@thdxr
We only want to kill it when it's unnecessary. If your project requirements allow it, you can build a good API abstraction in-memory in the same way you can build a good REST API abstraction, without having to pay the price of having to go through the network.
@tomus_sherman
@rickhanlonii
@TkDodo
Yep, that's true. And it also improves data requirements colocation to the nearest "client boundary" where before the closest you could get was at the route level.
@mattpocockuk
@mattpocockuk
should "resolveJsonModule": true and "esModuleInterop": true also be deleted since they're also implied by "module": "preserve"?