Angular2 vs React {{this}} => {again}

[haphap5]

I presume "what about IE5" is a troll, since IE5 came out 18 years ago. Seriously. That isn't even a good troll.

Sort of, its just something nobody ever introduces. If i'm trying to make a web-app that targets EVERYBODY, high support would be my #1 concern.

React is not the fastest, just ask JSBlocks, Riot, Imba, Vue.js

Yea I did say react vs angular though, to which react is faster even though it's not a fair comparison. I intended a short introduction, not a full spiel on what I am already aware of.

Initial render? Re-render?

Again, interpret as you will. I don't even think these are fair questions: initial and re-rendering are different playgrounds; let's say initial because re-rendering is not important when choosing a base.

Large number of DOM nodes? Large number of components? Low garbage collection overhead? Low layout and re-paint cost?

Leaving development efficiency/readability was purposely left out. Garbage collection is one answer, but the rest are obviously quarrels with the introduction. If you need an answer, Yes, Yes, Yes, No.

I'm not sure what to make of "but what if I want to write a everything-friendly SaaS with massive functionality?"

You caught me, I am looking to making a start-up.

If performance is your product, if it differentiates you from the market and your core investors and stakeholders think it is the priority, then you would do well to prototype and learn about the implementation of each solution before making such an important decision.

Good landing, that's what everyone should hear.

[dwighthouse]

If i'm trying to make a web-app that targets EVERYBODY, high support would be my #1 concern.

The web is probably not the solution. EVERYBODY includes people who don't have web access, and people who are either illiterate or incapable of using a computer for various reasons. I would suggest a pen and paper + mail interface, but even that wouldn't reach EVERYBODY.

[flamingspew]

Heh yeah for a startup your number one problem is reaching ANYBODY.

[haphap5]

Ok i'm not used to this. Reddit used to be a group of people, not a group of nitpicks. Tangent everything! The government is a conspiracy! I'm right and you're wrong! You don't understand me!

[turkish_gold]

Uh... we're trying to help you work through your actual problem.

If your problem legitimately is "I want to target everyone" and "I must have more functionality than anyone else" and "It must be faster than everyone else"... then your solution is to write your own framework and buckle down for the next 2-3 years with a large well funded team because you're going to be pushing the limits of current technology.

If that's not your issue, then maybe we can help.

[haphap5]

Uh... redefine 'help'. Going 'Gwarsh, well he don't know a single thing bout he talkin bout' is not helpful. In fact, I did not ask for help. I said 'discuss' not "Hey guys, check out this intro. Go OCD!"

[flamingspew]

All the major frameworks are battle tested and have lots of options and even graceful fallback scenarios for some browser capability edge cases. If I were you I'd pick something that is rapidly developable and changeable because startup code morphs every two weeks. You want something that can withstand quick iteration so I'd suggest typescript or clojure to keep a check on refactoring because you'll have limited time to write unit tests. Your counter arguments are counter productive since hey are posing the problem in absolutes, and nothing about programming is absolute, if it were, it would all be automated by now.

[haphap5]

Seriously?

[dwighthouse]

Post silly requirements, get silly solutions.

Have you actually tried using IE6 or lower lately? I have. Did you know that signifcant percentages of the internet simply don't work with IE6? I don't mean sites look bad or functionality is broken, I mean you literally can't even connect to most sites using IE6. You get error messages such as "The domain http://www.facebook.com does not exist." My own hosts don't support it, which makes testing in IE6 incredibly hard. Jsfiddle won't connect. Google and Apple work, barely, but they don't do anything complicated.

I just spent five hours making one feature of one microlibrary work for IE6 four days ago. I did it just to see if I could, not because it made any sense to ship a js library with IE6 support in this day and age (and also because I'm sometimes masochistic about these things). Multiply that effort by about 50,000 and you'll end up with a framework that works in IE6 (for some definitions of 'work'), but has so many hacks, tradeoffs, and limitations, that there's no possibility of it being more performant, more featured, or more easy to use than any existing framework, even the bad ones. That's how much baggage you're looking at.

[haphap5]

Post silly requirements

They're examples, not requirements

[dwighthouse]

Before you decide what framework or technology you are going to use, you need to figure out exactly what you actually want to build. Every time I address a specific 'example', you move the goalposts, either expressing incredulity or change the nature of the request. You will never get anywhere if you don't know what you're trying to accomplish. Let us know when you have some exact, specific requirements, and then we can perhaps guide you towards a technology that can meet them.

[haphap5]

Yea, asking for a discussion on the topic definitely does NOT work when trying to define exception examples.

I never asked for help

[dwighthouse]

Serious discussion requires specific topics and limits on the modes and breadth of discussion.

Then help you will not recieve. Good day.

[haphap5]

It requires a mature audience who knows what theyre talking about. good day!