mirkonasato

> They mostly target lower income internet natives

Seems to me they're increasingly targeting businesses, with their Udemy for Business offering that is a subscription service. I have a course published there and currently get about half of the revenue from the Udemy for Business share.

The TechCrunch article also mentions this: "It also has, in more recent years, expanded to enterprise services, where Udemy works with companies like Adidas, General Mills, Toyota, Wipro, Pinterest and Lyft and others — 5,000 in all — to develop and administer subscription-based professional development courses."

Ok, ease of deployment in that specific context makes some sense. You could still have separate source files, and bundle them together for deployment, but that would add a build step so it's a trade off.

All the other reasons I heard, I don't really see what they have to do with having a single or multiple files.

I never used Bottle and don't doubt the comments saying it's a great framework, but I'm more interested on the "single file" approach in general.

bottle.py may be a single file but it's 4,425 lines long. That doesn't strike me as particularly simple. Any project could potentially be "a single file" if it's a very long file.

Why would splitting it into a few separate files make it more complex? There's a reason why every modern programming language supports modules, and that's precisely to break down complexity into smaller, simpler units.