I'm a software engineer from Israel. I'm mainly a Pythonista, but I also dabble in C++ and Embedded Linux. I write about code, technology and my personal life - from a programmer's perspective.
Just because a decision is forced by scale doesn't necessarily mean it's bad for small scale. For example, Git was created for the Linux kernel project and is designed to be performant in scale, but it's still a good decision to use it when you're a single developer.
I don't believe someone can buy domains for a spur-of-the-moment idea back-to-back even 3 days before he'll realize he has a problem. I would think that you can at least remember than you bought a domain yesterday and try to work on it a little.
I personally don't find the regular CBV to be difficult to use and I prefer CBV to FBV in 99% of cases. I actually find it easy that the flow is separated into different methods, so that when I want to change a specific behavior, I don't have to read the whole view.
That being said, I do find that I have to look at the source code for CBV from time to time, even though the documentation is quite good - but maybe "looking through source code" isn't quite as intimidating to me as to more beginner programmers.
A novice question - how significant is the relative size here. Sure - 4 is smaller than 32, but is that really the biggest concern with a JS library (and modern internet speeds)?