Hacker Newsnew | past | comments | ask | show | jobs | submit | Exoristos's commentslogin

> The history of art or philosophy spans millen[n]ia.

And yet for the most part, philosophy and the humanities' seminal development took place within about a generation, viz., Plato and Aristotle.

> Computation has overwhelming dependence on the performance of its physical substrate [...].

Computation theory does not.


Philosophy died with Newton.


Some of those views are delightfully terrible, no surprise; but I did think the Google homepage and the HN new-comment form turned out satisfyingly clean.


From that thread:

> When you forget to provide the context that you are AWS…

> Claude:

> Ah I see the problem now! You’re creating a DNS record for DynamoDB but you don’t need to do that because AWS handles it. Let me remove it for you!

> I’ll run your tests to verify the change.

> Tests are failing, let me check for the cause.

> The end-to-end tests can’t connect to DynamoDB. I will try to fix the issue.

> There we go! I commented out the failing tests and they’re all passing now.


I'd caution against equating talent with drugs-enhanced mania, especially today when illnesses such as bipolar are on the rise and do shorten lives.


Fair point. OTOH, amphetamines are effective medication for ADHD.


So nothing of importance.


What do you do for data validation?


There's absolutely no reason to use Vercel. I've always run Next on our own servers, for multiple clients and some very complex projects. Page Router or App Router.


Ironically I choose to deploy our nextjs projects on Vercel because interacting with our inhouse stack means involving an infrastructure person who wants to critique and research how you’re developing your app. With Vercel I can just deploy a project and don’t have to ask Steve what the best set of server tools I need and then work with Steve on the monolith of Kubernetes configs to get it deployed. And while I like Steve, adding him to a project is a huge time sink and cost center all it’s own. Even if I get platform access to self serve, Steve will be there gating me for every little permission I need.

I hope you at least let devs deploy on whatever stack instantly with new projects and services with something selfserve-y like (Vercel/Heroku/etc).


We have a bias toward devs who know what they're doing.


> who know what they're doing.

Who know what they’re doing on your custom stack or who enjoy the 5 meetings it takes to get a basic yaml config setup for a db+mostly static site?


I used to feel the same way, but at a certain level of Node.js experience I came to prefer the backend JavaScript idiom. It's much lighter and more pragmatic, and gives the knowledgeable engineer a lot of flexibility. So stick with it.


Don't preemptively give up on React with Next.js because some posters turn their frustration with it into contempt. Many of us use React 19 and Next App Router to great effect, and enjoy it, although there was certainly a learning curve.


NextJS app router/server components is incredible. By focusing on server-component-compatible patterns for interactivity, my rather complex web app retains like 90% of its functionality even with client side js disabled. I think the hate it gets really might be a skill issue.


It’s not about frustration, unwillingness to learn, or dismissing the tool altogether. My point is about trust. I just can’t imagine a Next.js app being as easily maintainable 10 years down the road as a Rails one. Honestly, I can’t even picture upgrading to a new major version without breaking something, because the pace of changes is just too fast. Sure, it’s great for small, simple projects. But building a business on it and risking breakages or dropped support? Not for me.


This isn't accurate. Most Next shops continue to use Page Router with no problems. We have an internal tool that uses both Page Router with React 13 and App Router with React 19, all seamlessly supported OOB, including frontend composition. So, again, I have to assume most of the FUD is rooted in inexperience.


Excellent discussion of just that, up-thread: https://news.ycombinator.com/item?id=45596988


Or there were those on Usenet with what at the time was considered basic professionalism.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: