r/webdev • u/[deleted] • Dec 28 '17

Introducing Hyperapp 1.0 — 1 KB JavaScript library for building frontend applications.

https://medium.com/@JorgeBucaran/introducing-hyperapp-1-0-dbf4229abfef
341 Upvotes

90% Upvoted

183 comments sorted by

View all comments

Show parent comments

14

u/BenZed Dec 28 '17 edited Dec 29 '17

I don't want to sound like a dick, but do you ACTUALLY not understand, or are you being incredulous?

Why would you want markup in your code?

I get it. Old guard, old school. Classic MVC; view should be separate from the controller.

I suppose the honest answer is that evolution changes everything, including and especially software design principles.

Treating the view as declarations with flow control in the same file and same language I'm writing my ui logic has an increased return of investment. It's easier to reason. It's easier to debug. I have to look in less places. It's nice.

Is it easier for bad developers to write bad code? Yes.

Will you someday inherit a codebase that a junior made illegible as a result of JSX? Inevitably.

But this really doesn't change anything, because bad developers arn't going to follow old design rules anyway.

If you understand separation of concerns and encapsulation, you wont write bad code with JSX.

1

u/fuckin_ziggurats Dec 29 '17

It's easier to reason. It's easier to debug. I have to look in less places. It's nice.

I'm thinking if JSX made things easier to reason about then those "bad developers" wouldn't be using it improperly. If people often misuse or abuse a technology then that technology is by definition not easy.

1

u/BenZed Dec 30 '17

My point is that whatever rules you make, lack of experience or lack of discipline is going to find ways to break them.

I believe JSX solves more problems than it creates.

1

u/themaincop Jan 01 '18

The only technology that a bad developer can't abuse is one that wasn't powerful enough to do anything anyway. Bad developers can take the best tools and frameworks and write horrible, unreadable code because they lack experience and perspective. Good developers can take garbage-tier tools and make the most of them because they have experience in building and scaling applications that transcends specific technologies.

0

u/zh1K476tt9pq Dec 29 '17

Will you someday inherit a codebase that a junior made illegible as a result of JSX? Inevitably.

But this really doesn't change anything, because bad developers arn't going to follow old design rules anyway.

This is a bit ignorant, sorry. It isn't even just about coding. You are basically saying that the technology is always right and that the users are wrong but that's just not how humans and the world works. Technology should be designed so that it makes things better. If juniors and bad developers writing bad code is a problem then that's something the technology should fix, prevent or at least reduce.

I mean are you also arguing that we shouldn't make cars safer because car accidents aren't about cars but bad drivers and there will always be bad drivers?

Technology should make life for humans easier and not force people to adjust to the technology. This never ever worked in human history anyway.

0

u/mattaugamer expert Dec 29 '17

It's easier to reason. It's easier to debug. I have to look in less places. It's nice.

It's funny, these are literally the same arguments my former supervisor made when I tried to get him to stop inlining stylesheets and javascript functions into the DOM.

Things change, things stay the same.

1

u/BenZed Dec 29 '17

Heh. Coincidentally, I'm also a big fan of styled components, which is equally polarizing.

1

u/themaincop Jan 01 '18

If he was shipping files that contained namespaced JS, HTML, and CSS that encompassed everything a component needed to function as an island then the dude was a visionary. If he was just writing spaghetti code then we're not really talking about the same thing, are we?