You still need API routes for stuff like data-heavy async dropdowns, or anything else that's hard to express as a pure URL -> HTML, but it cuts down the number of routes you need by 90% or more.
I've been using React since its initial release; I think both RSC and App Router are great, and things are better than ever.
It's the first stack that allows me to avoid REST or GraphQL endpoints by default, which was the main source of frontend overhead before RSC. Previously I had to make choices on how to organize API, which GraphQL client to choose (and none of them are perfect), how to optimize routes and waterfalls, etc. Now I just write exactly what I mean, with the very minimal set of external helper libs (nuqs and next-safe-action), and the framework matches my mental model of where I want to get very well.
Anti-React and anti-Next.js bias on HN is something that confuses me a lot; for many other topics here I feel pretty aligned with the crowd opinion on things, but not on this.
I'm having issues with this gradient too. (Though I'm running a fever after being vaccinated yesterday, so my perception might be different than usual today).
It feels like that optical illusion with disappearing background [1] where your brain attempts to re-tune itself, and it's kind of uncomfortable.
I'm not sure. Maybe they did both and the real article is somethere in peer review pipeline. (Do you imply that no posts on replicationindex should be trusted since they're not properly peer reviewed?)
One possible reason is that blog posts are more widely shared on social media, and I agree that this is kind of a hit piece, mostly as a reaction to Ioannidis' contrarian stance on COVID-19, so publicity was probably an objective here.
This looks like something I've been hoping for ever since Dan hinted at it on twitter, but I'm kinda worried when it's going to become generally available.
My worry is mostly due to suspense for data fetching (which I really care about) and concurrent mode (which I care less about but which is still nice) releases, which were announced in late 2018 and promised by mid 2019, but then delayed at least twice since then.
Microsoft is betting on pylance for VSCode instead of pyright, though, and pylance is not open-source [0].
I wonder if Guido will be ok with that. For me pylance looks like the biggest evidence that embrace-extend-extingish mindset is still alive in Microsoft, unfortunately.
There's also a Russian saying, "The strictness of Russian laws is balanced out by the fact that they don't have to be enforced".
Precedent: a new Personal Data Protection Law was passed two years ago. It included the crazy clause that all personal data of Russian citizens must be stored and processed on servers located in Russia. Facebook didn't comply, and I'm sure many other websites didn't comply too, but nobody cares, AFAICT.
On the other hand, our government can decide at any moment that they don't like some website, person or other entity, and they'll quickly find a way to get rid of this entity without breaking the law.
Yes. Any social network, instant messenger or anything else which uses crypto will have to share keys so that government can decrypt "anything they like".
So, Facebook will either comply, or it'll have to pay the fine (800k-1m rubles ≈ $15000), or it will be banned.
The law also prescribes for all "organizers of information distribution" to store the voice call recordings for 6 months and to store metadata for 3 years. Nobody is sure what "organizers of information distribution" means, but at the very least it includes all phone calls and instant messages.
The FSB's announcement doesn't speak of any new technical capability, it just says that they formalized the legal procedure by which everyone should share their crypto keys with the government.
My experience is closer to yours than to the author of the original post.
1) I have a phonological loop and can easily imagine music.
2) My visuospatial sketchpad (see https://en.wikipedia.org/wiki/Baddeley%27s_model_of_working_...) is almost entirely spatial. I don't know the color of the floor in my kitchen, unless I paid attention to it specifically and verbally in the past. But I can use memory palace successfully.
3) I wonder if for me it's just an undeveloped habit which could be improved: I have dreams with pictures and colors once a few months, and sometimes I see pictures when I'm half asleep, but it's really hard to put myself into that state intentionally.
There are many possible paths I can take, but the one I'm considering the most at this point is freemium with private/protected quests or realms being a paid feature.
This service was originally Perl-specific, before I decided to expand on the idea, leave my job and work on it full-time.
I'm always looking for new communities, but it's meaningless to create empty placeholders for each other language and expect that people would come, we need some amount of initial content first.
If you want to help me start a new realm, either with ideas for stencils and quests, or with how to bring a group of people to it, please let me know. (My email is [email protected].)
No, I'm just saying that HN traffic is a rare opportunity, and I know Questhub onboarding experience sucks, so most of these visitors will be lost.
With that being said, of course there are lots of plans for improvements (most of them listed in Meta realm), but people, mostly from Perl community, used it successfully for a few months.
You still need API routes for stuff like data-heavy async dropdowns, or anything else that's hard to express as a pure URL -> HTML, but it cuts down the number of routes you need by 90% or more.