Clojure vs Ionic: What are the differences?
Clojure can be classified as a tool in the "Languages" category, while Ionic is grouped under "Cross-Platform Mobile Development".
"It is a lisp", "Concise syntax" and "Persistent data structures" are the key factors why developers consider Clojure; whereas "Allows for rapid prototyping", "Hybrid mobile" and "It's angularjs" are the primary reasons why Ionic is favored.
Clojure and Ionic are both open source tools. Ionic with 38.5K GitHub stars and 13.1K forks on GitHub appears to be more popular than Clojure with 7.85K GitHub stars and 1.25K GitHub forks.
Sellsuki, Zenefits, and MAK IT are some of the popular companies that use Ionic, whereas Clojure is used by CircleCI, Groupon, and Zalando. Ionic has a broader approval, being mentioned in 393 company stacks & 361 developers stacks; compared to Clojure, which is listed in 95 company stacks and 80 developer stacks.
What is Clojure?
What is Ionic?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Stitch is run entirely on AWS. All of our transactional databases are run with Amazon RDS, and we rely on Amazon S3 for data persistence in various stages of our pipeline. Our product integrates with Amazon Redshift as a data destination, and we also use Redshift as an internal data warehouse (powered by Stitch, of course).
The majority of our services run on stateless Amazon EC2 instances that are managed by AWS OpsWorks. We recently introduced Kubernetes into our infrastructure to run the scheduled jobs that execute Singer code to extract data from various sources. Although we tend to be wary of shiny new toys, Kubernetes has proven to be a good fit for this problem, and its stability, strong community and helpful tooling have made it easy for us to incorporate into our operations.
I adopted Clojure and ClojureScript because:
- it's 1 language, multiple platforms.
- Simple syntax.
- Designed to avoid unwanted side effects and bugs.
- Immutable data-structures.
- Compact code, very expressive.
- Source code is data.
- It has super-flexible macro.
- Has metadata.
great framework,lots of resources,great community,easy to create UI
To complement Java. The REPL lets me interactively exercise Java code. I can write performant and safe libraries in Java, and then use them in Clojure. I also find the data-centric aspect of Clojure (excellent build-in structures, literal syntax for easily creating those structures, functions that act well on abstractions of those structures) good for data processing.
This fits a sweet spot between Ruby and Java.
We use Clojure mostly for its "Minority Report"-like interactive development in situations that require 'semi-automatic programming' (data inspection, admin tasks, API exploration, scrapers, etc.). We have also used Clojure successfully to build some components of our stack very quickly and reliably, in the backend and the frontend.
just started learning clojure, maybe around two weeks or so. i'm addicted. this is what i want to be working with and learning for the foreseeable future. the elegance of the language is refreshing. the community is really amazing. i've finally found a language that fits my passion for programming.
Clojure simplifies and reduces the coding efforts involved in creating CloudRepo. The fact that it runs in the JVM gives us access to all the libraries that we could ever need. Our code base is much smaller and easier to reason about than it would have been had we gone with pure Java.
We use Ionic as it is an awesome framework to build mobile hybrid apps with nativ access. Also Ionic has a nice community!
Cross-Platform goodness. I am a noob here...learning how to implement Ionic is on the top of my ToDo's
used on a recent project, an internal custom app developed for both ios and android.