Re:Vercel April 2026 security incident
by gbgarbeb on Sunday April 19, 2026 @02:39PM
(#47826535)
10 years ago it was Heroku and Three.js.
[ Parent
| on HN ]
Re:Vercel April 2026 security incident
by seattle_spring on Sunday April 19, 2026 @03:34PM
(#47826964)
10 years ago it was Heroku and Ruby on Rails*
but now Ruby on Rails is not a circus like how Next.js is.
see [0]: Rails security Audit Report
Re:Vercel April 2026 security incident
by seattle_spring on Thursday April 23, 2026 @03:41PM
(#47880677)
Can you elaborate as to why your linked article would suggest nextjs to be a "circus"? If anything, DHH (founder of RoR) and his Looney-Tunes opinions are much closer to a circus sideshow than anything I've seen come out of Vercel.
More like 15. By 2016, Rails was supposedly dead and we were all going to be running the same code on the front end and back end in a full stack, MongoDB euphoria.
New one coming in 5 years. Cycle repeats itself.
I don't think so, AIs are going to freeze the tooling to what we have today since that's what's in the training corpus, and it's self reinforcing.
Re:Vercel April 2026 security incident
by telotortium on Monday April 20, 2026 @04:09AM
(#47831538)
Nah, the good LLMs can generally web search and read documentation well enough that the fact that pre-training isn’t up to the minute is not a serious concern. Badly-documented projects are more of a concern, but they weren’t likely to get much pre-AI usage either.