schtoo · HackerTrans

13 yıl öncediscuss

Imagine this scenario:

I've developed my app. Designer gets hired later and spits out a cool new layout and design... No feature changes at all.

similarly...

Then next year, management decides we need to give the app a "fresh new look" for v2.

[If I'm using React or JQuery-only] From what I can tell, this will cause me to have to dive through a whole bunch of JS code where I'm sifting through business logic and imperative code to find JSX/html sprinkled throughout and make the necessary changes. Also, since I'm changing actual code the chances of introducing new bugs in this process is high.

[If I'm using Angular] Go through html. Change html and css. Leave code and business logic alone.

This is not an entirely contrived situation (at least not for me). As I'm working towards a releasable product, one of the areas that go through the most change and flux is the design and layout.

schtoo

13 yıl öncediscuss

I don't get it. Anyone whose created sites with only JQuery and felt that pain has moved to frameworks like angular/ember/knockout/etc. Those frameworks help decouple the html from your js. This seems exactly opposite.

It like developing with JQuery where you had something like:

$('.whatever').append('<div>Hello ' + this.props.name + '</div>');

and now with JSX you can do (minus the React structure around it):

<div>{'Hello ' + this.props.name}</div>

So... looks a bit nicer... less quotes...? But so what. I don't want to tightly couple my presentation to my logic.

schtoo

13 yıl öncediscuss

Because its easier to see the html in context of the whole page or partial... because any significant html contains presentation properties (class names typically but also attrs like placeholder, etc) that I would rather not mix with code/logic... because my html typically contains elements whose sole purpose is to assist in layout which (again) i'd rather not mix with code/logic...

comments