All You Need To Know About CSS-in-JS – Hacker Noon

  • CSS-in-JS attached a style tag on top of the DOM while inline styles just attached the properties to the DOM node.Why does this matter?Not all CSS features can be aliased with JavaScript event handlers , many pseudo selectors aren’t possible, styling the html and body tags isn’t supported etc.With CSS-in-JS, you…
  • Some libraries (like jss, styled-components) even add support for neat, non-CSS-native features like nesting!Brilliant article going in depth on how they’re different.“Just write the darn CSS in CSS and be done with it.”Yes — while that’s the case for how it’s been done for a long-long time — the challenge is modern web is…
  • Shout-out to Vue for solving this problem beautifully even tho Vues styles have no access to components state.Here’s Bob Ross painting rocks to cool down the tension 😄What are the benefits of using CSS-in-JS?
  • CSS-in-JS leverages the full power of the JavaScript ecosystem to enhance CSS.“True rules isolation” — Scoped selectors are not enough.
  • JSS generates unique class names by default when it compiles JSON representation to CSS.Vendor Prefixing —The CSS rules are automatically vendor prefixed, so you don’t have to think about it.Code sharing — Easily share constants and functions between JS and CSS.Only the styles which are currently in use on your screen are…

TL;DR: Thinking in components — No longer do you have to maintain bunch of style-sheets. CSS-in-JS abstracts the CSS model to the component level, rather than the document level (modularity). You…
Continue reading “All You Need To Know About CSS-in-JS – Hacker Noon”

Building an app: React Native vs Ionic – Hacker Noon

Building an app: React Native vs #Ionic  #ReactJS #JavaScript

  • In this article, we are going to make a comparison of two frameworks, React Native and Ionic, based on our real time experience in frontend development.When developing various products, either for ourselves or for the clients, there has always been a question that interested us: how can we narrow down time and cost of product development.Android and especially iOS developers have always been valued greatly and cost a lot, and when developing for two platforms one has to spend twice as much money.At some point we were experimenting with Cordova, but it didn’t feel as if we can get something valuable out of it.Then we noticed Ionic.
  • Now we would like to give you detailed frameworks comparison and explain you why React Native is better solution for our developers.We were always trying to get more expertise on different technologies and use them in practice in order to define the best solution.
  • We also kept on watching Ioinc2, which was supposed to become an innovation that would solve many issues that we had while working with Ionic1.The approaches of given frameworks are very different but for us React Native is an ultimate winner.We chose main React Native advantages that are superior in relation to Ionic1/2:Response time that could be compared to native apps.Ability to reuse the code parts (not all code) for desktop (web apps) and mobile (mobile apps) and even for the server.
  • (:-))Incredibly convenient toolchain for developers that allows to quickly develop and debug the app.Big amount of elaborated components from Facebook.Even bigger amount of components from community.Ability to realize the ideas of functional programming in development which ensures great stability and reliability of the app and relative scaling simplicity.However, we don’t make a point here that React Native is 100% perfect.
  • We also chose some of React Native disadvantages in comparison with Native Apps:Those code parts that are linked to work with hardware solutions, camera, external libraries integration, etc are still done in Native parts.The interface between javascript and native part is not so simple (but not more complicated than cordova).

When you start to use new technology, you cannot be sure it will be the best solution. In this article, we are going to make a comparison of two frameworks, React Native and Ionic, based on our real t
Continue reading “Building an app: React Native vs Ionic – Hacker Noon”

What’s Happening with Navigation in React Native? – Revisify

What’s happening with navigation in React Native?  #JavaScript #ReactJS

  • What’s Happening with Navigation in React Native?There’s something nice about the background image…When I began learning React Native the docs and developers said that to handle navigation between scenes in your app you should use Navigator and a depreciated component, NavigatorIOS, was no longer recommended.
  • After seeing a post on the React Native subreddit and then doing some digging, I found out that Navigator and NavigationExperimental will be depreciated in favour of one last library React-Navigation.
  • It’s all a bit of a mess but I will clear everything up from what I’ve found while building my app.NavigatorIOSThe first solution to navigation in React Native was NavigatorIOS.
  • Like NavigatorIOS and Navigator, NavigationExperimental is being depreciated.React NavigationThe new recommended solution is React Navigation which hopes to overcome the issues of the previous solutions.
  • It also has support for deep linking.Navigation in React Native has been a mess, but the developers in the community are doing a great job at finalising a long-term solution with React Navigation.

When I began learning React Native the docs and developers said that to handle navigation between scenes in your app you should use Navigator and a depreciated component, NavigatorIOS, was no longer…
Continue reading “What’s Happening with Navigation in React Native? – Revisify”

[React Native 011.2] Comparing ListViews Ionic 2 vS React Native

Comparing ListViews Ionic 2 vS React Native -  #ionic #reactNative @reactnative

  • This is the first episode of a series in which we will compare several aspects of Ionic 2 and React Native.In general, people say React Native has better performance.
  • We will confirm this and also see where else React Native tops Ionic.
  • We’re not using any optimization in React Native or Ionic.
  • In future episodes, we will check out this optimization in Ionic.
  • In the comparison, since we are not using any of these optimizations, we can see how React Native is better than Ionic in terms of performance.

Compare 1k element listviews in Ionic 2 vS React Native
Continue reading “[React Native 011.2] Comparing ListViews Ionic 2 vS React Native”

Best Web Development & Programming Blogs for 2017

  • The blogs are more light-hearted and deal with coding more generally.
  • Even though this is a list of web developer blogs, we wanted to include two of our all-time favorite blogs.
  • His blog posts are great for back-end developers who focus on JavaScript and Node.js.
  • The blog has been around since 2005 and still posts fairly frequently to this day.
  • The blogs below are listed in alphabetical order.

There are a ton of great developer blogs out there, so we’ve curated a list of our team’s favorites along with top choices from some members of our community of expert developers.
Continue reading “Best Web Development & Programming Blogs for 2017”

Is Model-View-Controller dead on the front end? – Free Code Camp

Is Model-View-Controller dead on the front end?  by @alexnmoldovan #JavaScript #ReactJS

  • Similar to the Controller, the Model is breaking the Single Responsibility Principle, because you don’t have a separate way of managing UI State and Application State .
  • Developers didn’t seem to care much about the architecture itself.
  • With the popularity of React and component-based architecture , we saw the rise of unidirectional architectures for managing application state.
  • Our current discussion of front-end vs back-end architecture only came about in late 2010.
  • Through the five-year process, front-end architecture evolved into what it is today.

More and more front-end developers are adopting unidirectional architectures. So what’s the future for the classic Model-View-Controller (MVC) approach? In order to understand how we got to this…
Continue reading “Is Model-View-Controller dead on the front end? – Free Code Camp”

Is Model-View-Controller dead on the front end?

Is Model-View-Controller dead on the front end?:  by  @alexnmoldovan #reactjs #JavaScript

  • Similar to the Controller, the Model is breaking the Single Responsibility Principle, because you don’t have a separate way of managing UI State and Application State .
  • Developers didn’t seem to care much about the architecture itself.
  • With the popularity of React and component-based architecture , we saw the rise of unidirectional architectures for managing application state.
  • Our current discussion of front-end vs back-end architecture only came about in late 2010.
  • Through the five-year process, front-end architecture evolved into what it is today.

More and more front-end developers are adopting unidirectional architectures. So what’s the future for the classic Model-View-Controller…
Continue reading “Is Model-View-Controller dead on the front end?”