React Native vs Tcl
When comparing React Native vs Tcl, the Slant community recommends React Native for most people. In the question“What are the best tools for making a cross-platform application?” React Native is ranked 10th while Tcl is ranked 13th. The most important reason people chose React Native is:
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Allows you to develop native apps
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Pro Large, supportive community
Despite being such a young framework (early 2015), the support for React Native grew quickly. There is a forum, active tag on Stackoverflow and many other ways to get help from the community.

Pro Backed by Facebook
Facebook writes their mobile apps in React Native so the code base gets pretty thoroughly used in some highly demanding scenarios.
Pro More predictable control of the state
The one way data flow, makes it more predictable and easy to control.
Pro Standard library
Unlike *sh Tcl has a rich standard library.
Pro Sane quoting rules
Unlike in sh you don't need to quote your variable substitutions ('"$1"').
Expanding of arguments occurs mostly explicit and if yet expected in-place (e. g. using eval
or subst
) it follows strict and well clear rules.
So exec test $argv
would execute test with single argument.
And appending {*} before $argv
would execute test with all arguments (list expansion).
Pro Cross-platform
With a little care you can have the same script work on Linux, *BSD, OS X and Windows.
Pro Widely available
You can expect a reasonably recent version of Tcl to either installed or available in the repositories of any popular open source *nix.
Pro Everything is a string
Tcl can operate at the same level of abstraction as the POSIX shell, which makes it easier to manipulate the output of other programs.
Pro Tk and Expect
Pro Standalone packages
Tcl enables easy deployment through self-contained binaries known as starpacks.
Pro Rich scripting capabilities on a single line
Want to run something 5 times? Here you go: set i 0; time { puts done-[incr i] } 5
If you need real conditional cycle? Not a problem: for {set ready 0; set i 1} {$i <= 100 && !$ready} {incr i} { if {[exec do-some-thing] eq "ready" } {set ready 1} }
Want to measure performance of something or repeat it max 300 times and not longer than 1 seconds? Very simple: timerate { after 20 } 1000 300
How about notifying yourself when some http-server is back online? Sure thing: while {[catch { close [socket localhost 80] }]} { after 1000 }; puts "\7\7\7ONLINE!"
And you can do it also fully asynchronously using events etc.
Cons
Con If core team doesn't use a certain feature, it's not developed
Whenever there's functionality you need that they don't use in their apps, it's not going to get developed by them, even if it's obvious it should be in the core. They always say to either submit a PR or create a separate module.
Con Steep learning curve
React Native is not the most beginner-friendly framework for creating mobile apps with JavaScript. It requires that the developer know React, which is known to have a steep learning curve.
Con Many existing JS libraries are not usable on React Native; not exactly a 1-to-1 experience to writing React either
Example: Library that provides a full calendar with agenda view.
In the end it's much easier to develop in actual JavaScript with a solution such as Ionic, especially if your app needs to work well on the desktop.
Con React native only supports react which is getting old
React native is only based on react which is getting old. An old tech developer can't take much breaking changes so it gets more patchs. There is a limit, and react is too verbose and complex. better alternatives available today.
