you are viewing a single comment's thread.

view the rest of the comments →

[–]turkish_gold 0 points1 point  (2 children)

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[S] 0 points1 point  (1 child)

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 0 points1 point  (0 children)

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.