While I do agree that your approach leads to good result, I still don't see why you wouldn't add a compilation step to minimize/tree shake/TypeScript/etc.

If you're good enough to be conservative in what you pull in, you'll still be that, except you get to benefit from all the things a compilation step can offer. It still strikes me as a somewhat arbitrary limitation to impose on yourself.

I use webpack for almost all my projects, and TypeScript for a bunch of them. I'm also very mindful of what packages I use and the result is nice little bundle. I wouldn't be able to get the results I want if I limited myself by not having a compilation step.

The new reddit is also a better experience than the old reddit, so there's that

And to expand upon pjc50's comment, the mobile experience still pushes the app, even though I'm logged in and always dismiss it.

(I know full well why they want people to the install the app, but I still find it unfortunate that they a) don't remember that I dismiss it/have an option to never ask me and b) despite the redesign and having a relatively good mobile experience (assuming you didn't first hit an `amp.` link) still push the app.

And by better you mean worse? I second 'pjc50 here - new Reddit is slow on both mobile and PC, inefficient to read (wastes a lot of space), has questionable interactions thanks to JS abuse, and generally turns what was a condensed link aggregator into a poor Facebook clone.

Not in my experience - it's terribly slow on mobile, still fairly slow on desktop, and wastes huge amounts of space.

Ironically it's more robust than most of sites I see on the internet.

Wow, I've never heard anyone express that opinion before. Even my wife (a non-technical user) hates the new design.