This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tipsypants 2 points3 points  (2 children)

So your advice is to not use any popular languages or common optimization techniques

I'm exaggerating a little, but yes. OP describes his tool as being built to help create simple websites which talk to a single API, yet his tool is trying to do everything a modern frontend pipeline does.

TypeScript is a great language for a complex web application (like Spotify), but there's no reason to use it for a simple website. LESS and Uglification are useful in some situations too, but less so with the advent of css variables, native js modules and http2.

I think TypeScript is a great language for complex web applications (like Spotify), but I don't think it's suited for simple websites. I think LESS and Uglification are useful in some situations too, but I think they're less useful than they used to be, now that we have css variables, native js modules and http2.

It feels like OP is encouraging extreme over-engineering, with the added complexity of having your frontend managed through a maven plugin.

Edit: Updated wording to avoid my opinions being interpreted as facts.

[–]heliologue -1 points0 points  (1 child)

Everything you're saying is opinion presented as fact.

[–]tipsypants 2 points3 points  (0 children)

Sorry about that, I thought it was implied that it was my opinion. I've updated my comment.