61–70 of 105 posts
Earlier quoted context omitted.
But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.
There's nothing objective about that statement, since it depends on what you value. If you value having a language that is supported natively by every browser, I would argue JavaScript is - subjectively - quite fantastic!
Any further thoughts on the apparently controversial PATENTS file? https://github.com/facebook/react-native/blob/master/PATENTS
> it's "be a patent troll and suffer the consequences"
[1] https://twitter.com/floydophone/status/581486099240873985
Component-based file structure is firmly in the "good" column for me. It makes small components much more feasible. If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large. However, if you have a component-based structure, whenever you notice a very small piece of common functionali…
> If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large. Why exactly does this force you to keep your components large?
Earlier quoted context omitted.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
I think you overestimate Node's popularity, compared to other languages on the server side.
> Flexbox. The authors missed the opportunity of offering a saner API and favored sticking to the official spec instead. Flexbox is the saner API we've all be waiting for, in my opinion. I'm curious what the author's objections to it are. That's really my problem with the whole piece — statements like this are thrown out there without much justification or explanation.
I'd much rather be writing apps using constraint-based layout, much like AutoLayout. It took me a while to grok it, but it's much simpler once you get it.
When "The Bad" list start with the single word Javascript, it loses a lot of credibility for any unbiased judgment.
Earlier quoted context omitted.
See: https://twitter.com/ryanflorence/status/582016664847290368
Awesome, thanks. That should really be mentioned in the Quick Start and/or Tutorial in the docs. I think a lot of people would really appreciate that feature. :)
Earlier quoted context omitted.
> If you're forced to split out your view, your template, your stylesheet, your controller, your model, your business logic, et cetera into separate files you are forced to keep components large. Why exactly does this force you to keep your components large?
A typical component in my React app contains about 3 lines of HTML. Have you ever seen a 3 line HTML template?
Earlier quoted context omitted.
But JavaScript is a bad language, objectively. There's little debate on that subject. Most of us use it because we have to, even though there are much better languages available.
> Most of us use it because we have to, even though there are much better languages available. Node's popularity is a pretty dramatic counterexample to that assertion.
You can create a ListView and the performance (and feel) are great, but it's not a UITableView. You can draw a chevron and make it kind of look like a UITableView but if you have to manually re-create the native UI, it's not really native anymore, is it?
It certainly is slick to get instantaneous feedback when you edit your javascript file, though.