zachleat’s Twitter Archive—№ 44,480

@jpcafe10 @remix_run I do appreciate the feedback! I do think it’s fair to do a bit of refactoring to match the conventions used by the Next.js version at least. But if Remix isn’t doing any markdown processing and this is merely a routes scaling issue, maybe Remix isn’t relevant here at all?