cockatiel_day

I'll add, it's kind of baffling to hear that things are stable, there are just ton of issues you can't get to.

I'd posit that Next has a ton of users, and a ton of issues, because it prematurely marks features as stable, and then markets them aggressively. Instead of working through these issues in beta with a manageable number of early adopters with aligned expectations, Next gets more than they can handle, frustrated that features sold as production ready are not. This, to me, is a questionable business strategy, not a sound technical one.

Hey Lee, thank you for replying. It's nice to be heard! I know that everyone is working hard, and no software of Next's ambition is perfect, much less at this stage, but all the same, I think there's a threshold for stable that isn't being met, and I think that's doing your users a disservice.

The issues I'm experiencing are for the App Router. Namely, and to keep things reasonable scoped, with parallel routes. These are being recommended for common use cases, but a lot of things are broken along their way (along with intercepting routes)... I'd recommend searching issues for the full breadth, but here are a few that jump to mind:

Server actions don't work in parallel routes unless that route was hard navigated: https://github.com/vercel/next.js/issues/54173

Parallel routes don't unmount if navigated from with anything other than router.back()... this might be a documentation issue, as I recently got this to work as expected in one case with a null page.js at the root of the parallel route: https://github.com/vercel/next.js/issues/49662

CSS Modules don't work on hard navigation... entire paths render unstyled: https://github.com/vercel/next.js/issues/52245 https://github.com/vercel/next.js/issues/56524

Speaking of CSS Modules, they import multiple times in indeterminate order. This breaks precedence and the cascade, making styles indeterminate. There are hacks that mitigate this, but even with the hacks it causes problems: https://github.com/vercel/next.js/issues/51030

These aren't exactly edge cases, and to get at the heart of my complaint, they haven't been acknowledged, or haven't been followed up on for months, despite being marked stable. I don't mean to suggest that you all aren't doing the best you can, and I certainly don't mean to suggest that you can do better technically, but as a user it's concerning to get in deep and continually run into beta issues on what's meant to be stable, and be in the dark as to when they'll get resolved, much less if the team is even aware of them.

My ongoing concern with Next is the Vercel's team unresponsiveness to page-breaking bugs coming off of features marked "stable" and in the docs.

Lately, it seems like most issues aren't even being acknowledged. It's pretty frustrating to encounter a bug in a documented use case, spend hours trying to fix it, realize it's a Next issue that was filed months ago but has yet to receive a response from Vercel, or to have reproduced and explained the issue and be ignored for months and counting.

The issue count at Next is huge, and I'm sure overwhelming, but if you're going to hype "stable" features that are beta at best, there ought to be some measure of support (or at least acknowledgment) for when they don't work.

People invest their livelihoods in these frameworks, and false claims are damaging. I'm currently knee deep in a project that can't budget a rewrite, so I'm just hoping someone at some point notices these issues and they get fixed. Not great. I've yet to encounter a project that calls features "stable" as carelessly as Next does. I've never felt so burned by open-source marketing.

If I was starting a new project today, I would stay away from Next.

Remix's approach to fetching is unique and compelling for Rest APIs.

However, if you're working with a GraphQL API, you can eliminate all these much-mentioned fetch waterfall issues by using Relay as a client... Relay inspects the data needs of all your page's components and compiles them to a single page query. Relay also has a number of nice developer interfaces for common/annoying problems like pagination that I don't think are possible w/ Remix's approach.

This article is informative, but I think it misleadingly implies that you can't avoid waterfall fetches in Next (or that it only might be possible someday w/ React Server Components)... you can.

Second the cockatiel recommendation!

They are very rewarding pets, if still demanding... you get out what you put in.

Parrots lead active emotional lives. Relationships mean a lot to them, they come with expectations, and they know when they are not being taken seriously.

I think there is a common misconception in the bird owner universe that a cockatiel is some kind of starter parrot, and to get the full experience you need to get a larger cockatoo, a macaw, or some other bird that can live more than 60 years, scream as loud as a jet engine, and take your nose off... it’s not true. Give a cockatiel companionship and respect and they’re every bit as engaging and interesting (and loving) as anything bigger or more exotic.

I have a good bunch of squirrels I feed outside my home office... I can attest they are delightful creatures when you get to know them. They’re smart, gentle, engaging, and all have a different and developing personality.

Yes, they’re rodents, but rodents are a big family!

This article is 100% true.

My first job out of college 10 years ago was in a lab focused on Alzheimer’s research. Our Principle Investigator made an art of writing grant applications for studies that would appear to be in line with mainstream theory, but were really intended to test theories he actually thought were worth testing, presented in results as an “interesting” aside. He believed the amyloid theory had been conclusively disproven.

He explained to me that people like him work for decades, quasi-retire into positions accepting grant applications, and have a conscious or unconscious agenda to preserve or validate their life’s work. His money quote was “science is like the Catholic Church, a lot of nice sentiments but full of people”.

I don’t have any evidence or examples, but I suspect this dynamic is not limited to Alzheimer’s research.

Another anchor to research not mentioned in the article is how much sponsoring universities take from research labs. To put a university endorsement on our research, which is needed to be credible, the university took half (half!) our grant money.