I disagree. When people typically pronounce, for example, "1800s," they would say "Eighteen Hundreds," with the plural suffixing "hundred," implying a period of far longer than a decade. If trying to reference the decade following 1800, in conversation I would say "the Eighteen Noughts."
You might want to have a look at Remix [0]. I haven't used it extensively myself, but it does claim to handle errors well.
> Route Error Boundaries keep the happy path happy. Each route module can export an error boundary next to the default route component.
> If an error is thrown, client or server side, users see the boundary instead of the default component. Routes w/o trouble render normally, so users have more options than slamming refresh. If a route has no boundary, errors bubble up. Just put one at the top and chill out about errors in code review, yeah?
@kiwicopple - given you have keyword notifications set up on here [0], between this and your current AWS situation, this is not a good look
[0] https://news.ycombinator.com/item?id=42223240