Need advice about which tool to choose?Ask the StackShare community!
ES6 vs Objective-C: What are the differences?
ES6: The next version of JavaScript. Goals for ECMAScript 2015 include providing better support for large applications, library creation, and for use of ECMAScript as a compilation target for other languages. Some of its major enhancements include modules, class declarations, lexical block scoping, iterators and generators, promises for asynchronous programming, destructuring patterns, and proper tail calls; Objective-C: The primary programming language you use when writing software for OS X and iOS. Objective-C is a superset of the C programming language and provides object-oriented capabilities and a dynamic runtime. Objective-C inherits the syntax, primitive types, and flow control statements of C and adds syntax for defining classes and methods. It also adds language-level support for object graph management and object literals while providing dynamic typing and binding, deferring many responsibilities until runtime.
ES6 and Objective-C can be categorized as "Languages" tools.
"ES6 code is shorter than traditional JS" is the top reason why over 98 developers like ES6, while over 211 developers mention "Ios" as the leading cause for choosing Objective-C.
Slack, StackShare, and ebay are some of the popular companies that use ES6, whereas Objective-C is used by Uber Technologies, Instagram, and Pinterest. ES6 has a broader approval, being mentioned in 1461 company stacks & 1725 developers stacks; compared to Objective-C, which is listed in 851 company stacks and 363 developer stacks.
1 code deploys for both: Android and iOS. There is a huge community behind React Native. And one of the best things is Expo. Expo uses React Native to make everything even more and more simple. Awesome technologies. Some other important thing is that while using React Native, you are reusing all JavaScript knowledge you have in your team. You can move easily a frontend dev to develop mobile applications.
A huge PRO of Expo, is that it includes a full building process. You run 1 line in the terminal, and 10 minutes after you have 2 builds done. Double check EAS Expo.
This post is a bit of an obvious one, as we have a web application, we obviously need to have HTML and CSS in our stack. Though specifically though, we can talk a bit about backward compatibility and the specific approaches we want to enforce in our codebase.
HTML : Not much explanation here, you have to interact with HTML for a web app. We will stick to the latest standard: HTML 5.
CSS: Again if we want to style any of our components within he web, we have to use to style it. Though we will be taking advantage of JSS in our code base and try to minimize the # of CSS stylesheets and include all our styling within the components themselves. This leaves the codebase much cleaner and makes it easier to find styles!
Babel: We understand that not every browser is able to support the cool new features of the latest node/JS features (such as redue, filter, etc) seen in ES6. We will make sure to have the correct Babel configuration o make our application backward compatible.
Material UI (MUI): We need to make our user interface as intuitive and pretty as possible within his MVP, and the UI framework used by Google will provide us with exactly that. MUI provides pretty much all the UI components you would need and allows heavy customization as well. Its vast # of demos will allow us to add components quickly and not get too hung up on making UI components.
We will be using the latest version of create-react-app which bundles most of the above along many necessary frameworks (e.g. Jest for testing) to get started quickly.
For our front-end, React is chosen because it is easy to develop with due to its reusable components and state functions, in addition to a lot of community support. Because React is popular, it would be easy to hire for it here at our company MusiCore. Our team also has experience with React already. React can be written with ES6 and ES6 has a lot of popularity and versatility when it comes to creating classes and efficient functions. Node.js will be used as a runtime environment to compile the code. Node.js also has many different types of open-source packages that can help automate some of the tasks we want to do for the application. CSS 3 will be used to style components and is the standard for that.
Optimize-js
I will not describe this tool a lot here, because it's already good done by author on github
I just want to mention that this tool wrap up all immediately-invoked functions or likely-to-be-invoked functions in parentheses what is do a great optimization a JavaScript file for faster initial execution and parsing (based on my experience).
The performance of application where I've introduced optimize-js improved on 20% in a common (tested in Chrome and IE11).
- Clarification on Readme to the optimize-js
- Some of Nolan thoughts on the virtues of compile-time optimizations can be found in "Parens and Performance" – counterpost
Is it maintaining now? - Unfortunately, no (but feel free to send PR)
Pros of ES6
- ES6 code is shorter than traditional JS109
- Module System Standardized52
- Extremly compact2
- Destructuring Assignment2
Pros of Objective-C
- Ios212
- Xcode115
- Backed by apple62
- Osx47
- Interface builder40
- Good old fashioned ooe with a modern twist10
- Goober, please2
- Object-oriented1
- Handles well null values (no NullPointerExceptions)1
Sign up to add or upvote prosMake informed product decisions
Cons of ES6
- Suffers from baggage1
Cons of Objective-C
- UNREADABLE1
Sign up to add or upvote consMake informed product decisions
What is ES6?
What is Objective-C?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Objective-C?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with ES6?
What tools integrate with Objective-C?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+29
+31
+43
+37
+26
+39