This means they will be taking bailouts next year.
Readit Newseglove commented on Our Agreement with the Department of War openai.com/index/our-agre... · Posted by u/surprisetalk
eglove commented on Three-Hundred Nineteen Courses on Learning Development ethang.dev/courses... · Posted by u/eglove
Don't get too upset about the number of construction courses
eglove commented on How we rebuilt Next.js with AI in one week blog.cloudflare.com/vinex... · Posted by u/ghostwriternr
someone spent over 1000 dollars to replicate the functionality of Next.JS, even 1 dollar would seem too much somehow. I suppose that is me being overly retributive.
coulda forked it for free
eglove commented on How we rebuilt Next.js with AI in one week blog.cloudflare.com/vinex... · Posted by u/ghostwriternr
The article say that "Next.js is well-specified." I... don't think this is actually true. It certainly has lots of documentation, but as has come up time and time again, there are tons of undocumented or poorly documented behaviors that have been the cause of consternation.
So I kinda wonder, did they just create the framework that Next.js claims to be but never has been? And is Next.js without the hidden stuff actually a good framework? Who knows.
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.
eglove commented on How we rebuilt Next.js with AI in one week blog.cloudflare.com/vinex... · Posted by u/ghostwriternr
Clownflare engineers are in the chat now doing damage control and downvote opposition. Soon jgrahamc will appear and whitewash the theft.
"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-...
eglove commented on How we rebuilt Next.js with AI in one week blog.cloudflare.com/vinex... · Posted by u/ghostwriternr
> We also want to acknowledge the Next.js team. They've spent years building a framework that raised the bar for what React development could look like. The fact that their API surface is so well-documented and their test suite so comprehensive is a big part of what made this project possible.
Hi next.js devs, we like to acknowledge the effort you put for writing good tests so we were able to rip it off. You know claude already has next's entire source code in it's training data?
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.
eglove commented on How we rebuilt Next.js with AI in one week blog.cloudflare.com/vinex... · Posted by u/ghostwriternr
I'm deeply skeptical of the "X reimplemented and it was super easy" thing.
The devil is in the detail.
So many edge cases unlikely to be there.
So many details or fine details unlikely to be there.
Years of bug fixes.
If it is literally a drop in replacement and it passes all the tests, and you're replicating something with and extremely thorough test suite, then sure I'll give you the benefit of the doubt.
Otherwise, I don't believe people "rebuilt X product in a week".
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-...
Deleted Comment