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

This means they will be taking bailouts next year.


Don't get too upset about the number of construction courses


coulda forked it for free


The primary reason I moved away from NextJS is the constant stream of bugs. Never seen any framework or library perform as poorly as it past v0.


"I'm also the director in charge of the entire Cloudflare Workers org, almost 80+ people at this point. I'm not just an IC engineer who has to find time to justify continuing to work on this. I can literally put people on it, and I've already been talking to the team about how to do exactly that." -Steve Faulkner https://github.com/cloudflare/vinext/issues/21#issuecomment-...


This is basically distillation for JavaScript frameworks. We're not creating new ones fast enough. So we'll just start distilling the ones we have.


God speed to the poor souls that have to make it actually work in the long run:

"I can say that with some authority. Yes, I'm the one who wrote most of this project, but I'm also the director in charge of the entire Cloudflare Workers org, almost 80+ people at this point. I'm not just an IC engineer who has to find time to justify continuing to work on this. I can literally put people on it, and I've already been talking to the team about how to do exactly that."

https://github.com/cloudflare/vinext/issues/21#issuecomment-...


"modern stacks" yeah... they use GraphQL sometimes. I'm sure they'll say Node is cutting edge too. That was exactly my point about tech stack. Dangling shiny keys in front of me in the form of technologies doesn't really cut it. I'm sure it helps for the recent grads though.


What's wrong with GraphQL? "CAN-OPEN-WORMS-EVERYWHERE"


They are more documentation driven. Every line of code and every change is meticulously documented and reviewed. This is the pre-agile, pre-automation way of doing things.


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

Search: