[root_axis]

Cool project, but I dislike the semi-arrogant tone taken by the author.

> Have you ever opened a years-old project that used the favorite Web framework-du-jour, and tried to make sense of it now? Would you be able to maintain such a piece of software?

Yes? Even if the answer were no, why would this framework be any different? The author seems to suggest that his perspective on "maintainable" is universal when it's actually just his opinion. Having strong opinions is fine, we all have opinions, but trying to play up your own framework as if it's objectively more maintainable is eye-roll worthy, especially in the context of JS land.

> Who will remember the (hypothetical) peculiarities of the willUpdate method in version 14.2.132 of framework X?

This is a banal criticism that can be applied to any piece of software that introduces breaking changes. The idea that the author will never release breaking changes is absurd, especially on the web.

> Code shouldn’t have to be completely rewritten to be compatible with the next major version of Typescene

"completely" and "compatible" are pretty vague caveats. Is it a complete rewrite if I have to rewrite 25% of code? 50%? 60%? I'm sure someone can point out an example of a framework that required "a complete rewrite" in order to be "compatible" with the next major version, but this isn't typical.

> No-nonsense object-oriented (OO), event-driven approach.

OO is nonsense (someone's opinion).

> you’ll only need external modules to import complex UI components or application behaviors that aren’t included in the framework itself.

You'll only need external modules for complex UI and behaviors that aren't included in a minimalist framework... So, just like every other framework out there.

> Most importantly, Typescene hasn’t been invented overnight, it’s not a Minimum Viable Product that introduces some clever new paradigm

What is an example of a framework that was "invented overnight" that introduces some clever new paradigm?

I'm not trying to come down on the author, and I'm not making a technical criticism of the project, but the "everyone else's shit stinks but mine smells like roses" is a turn off, for me personally.

[_delirium]

It didn't really bother me, but I might be reading it more strongly in the context of this being a single-person job. If a project took a strongly hyped tone while also having a large amount of money backing it, I might be annoyed (heck, this isn't a hypothetical, it happens all the time from Facebook/Google/Amazon!), but this is some random individual who is trying to explain why their project has advantages, when other frameworks are mostly backed by large corporations. In that context my reaction is more, "hey, good hustle, we'll see how it pans out". Maybe it's good, maybe it's not, but if it's not, it hardly threatens me, because there's no money and little manpower behind it anyway. There are other strategies to take with a more humble tone, but I'm not really offended by this strategy, and there's a risk that a more modest strategy would result in nobody giving it a second thought even if it did have significant pros. Not that my reaction is correct or anything, just thought I'd add a subjective reply.

[root_axis]

Sure thing. I'm not suggesting that there is anything wrong with the framework, and just because I find the tone of the blog somewhat arrogant doesn't mean that I'm offended by it; sometimes arrogance has a reasonable explanation, I just don't see that here.

> trying to explain why their project has advantages

IMO you can do that without the tacit suggestion that the competition produces unmaintanble code, or at least, explain why this framework is objectively more maintainable and not just one's particular opinion of what is maintainable.

> if a project took an arrogant tone while also having a large amount of money backing it, I might be annoyed

I'm not really annoyed either way, but in my totally subjective opinion a lone developer should take a more humble tone, it's not as if backing by a large corporation correlates with non- maintainability.

[jcormont]

Totally understand how this could rub someone the wrong way, but my intention here is mostly to clarify my own thought process. Not so much "everyone else's shit stinks but mine smells like roses", but rather "my own shit used to stink, so here are my goals for developing something that might work better".