Alternatives to HTML5 logo

Alternatives to HTML5

Android SDK, JavaScript, WordPress, Java, and AngularJS are the most popular alternatives and competitors to HTML5.
110.9K
90.7K
+ 1
2.2K

What is HTML5 and what are its top alternatives?

HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997.
HTML5 is a tool in the Languages category of a tech stack.

Top Alternatives to HTML5

  • Android SDK
    Android SDK

    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • WordPress
    WordPress

    The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family. ...

  • Java
    Java

    Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...

  • AngularJS
    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • Python
    Python

    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...

  • PHP
    PHP

    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...

HTML5 alternatives & related posts

Android SDK logo

Android SDK

21.5K
16.4K
786
An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
21.5K
16.4K
+ 1
786
PROS OF ANDROID SDK
  • 285
    Android development
  • 153
    Necessary for android
  • 127
    Android studio
  • 85
    Mobile framework
  • 81
    Backed by google
  • 26
    Platform-tools
  • 21
    Eclipse + adt plugin
  • 4
    Powerful, simple, one stop environment
  • 2
    Free
  • 2
    Больно
CONS OF ANDROID SDK
    Be the first to leave a con

    related Android SDK posts

    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 886.5K views

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    Sezgi Ulucam
    Developer Advocate at Hasura · | 7 upvotes · 719.1K views

    I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

    The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

    See more
    JavaScript logo

    JavaScript

    251.5K
    197.5K
    7.8K
    Lightweight, interpreted, object-oriented language with first-class functions
    251.5K
    197.5K
    + 1
    7.8K
    PROS OF JAVASCRIPT
    • 1.6K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.1K
      Lots of great frameworks
    • 886
      Fast
    • 735
      Light weight
    • 416
      Flexible
    • 384
      You can't get a device today that doesn't run js
    • 284
      Non-blocking i/o
    • 233
      Ubiquitousness
    • 188
      Expressive
    • 51
      Extended functionality to web pages
    • 44
      Relatively easy language
    • 42
      Executed on the client side
    • 26
      Relatively fast to the end user
    • 22
      Pure Javascript
    • 17
      Functional programming
    • 11
      Async
    • 8
      Setup is easy
    • 7
      Its everywhere
    • 7
      Because I love functions
    • 7
      JavaScript is the New PHP
    • 7
      Like it or not, JS is part of the web standard
    • 7
      Full-stack
    • 6
      Expansive community
    • 6
      Future Language of The Web
    • 6
      Can be used in backend, frontend and DB
    • 5
      Evolution of C
    • 5
      Everyone use it
    • 5
      Love-hate relationship
    • 5
      Easy to hire developers
    • 5
      Supports lambdas and closures
    • 5
      Agile, packages simple to use
    • 5
      Popularized Class-Less Architecture & Lambdas
    • 5
      For the good parts
    • 4
      Everywhere
    • 4
      Hard not to use
    • 4
      Promise relationship
    • 4
      Scope manipulation
    • 4
      It's fun
    • 4
      Client processing
    • 4
      Nice
    • 4
      Easy to make something
    • 4
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 4
      Easy
    • 4
      Photoshop has 3 JS runtimes built in
    • 4
      Can be used both as frontend and backend as well
    • 4
      Most Popular Language in the World
    • 4
      It let's me use Babel & Typescript
    • 4
      What to add
    • 4
      Clojurescript
    • 4
      Function expressions are useful for callbacks
    • 4
      No need to use PHP
    • 4
      Its fun and fast
    • 4
      Powerful
    • 4
      Versitile
    • 4
      Client side JS uses the visitors CPU to save Server Res
    • 4
      1.6K Can be used on frontend/backend
    • 4
      Stockholm Syndrome
    • 3
      Because it is so simple and lightweight
    • 3
      Only Programming language on browser
    • 2
      JavaScript j.s
    • 2
      Acoperișul 0757604335
    CONS OF JAVASCRIPT
    • 21
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 14
      Javascript is the New PHP
    • 8
      No ability to monitor memory utilitization
    • 6
      Shows Zero output in case of ANY error
    • 5
      Can be ugly
    • 4
      Thinks strange results are better than errors
    • 2
      No GitHub
    • 1
      Slow

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    WordPress logo

    WordPress

    86K
    30.4K
    2K
    A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
    86K
    30.4K
    + 1
    2K
    PROS OF WORDPRESS
    • 411
      Customizable
    • 361
      Easy to manage
    • 351
      Plugins & themes
    • 258
      Non-tech colleagues can update website content
    • 246
      Really powerful
    • 144
      Rapid website development
    • 77
      Best documentation
    • 51
      Codex
    • 44
      Product feature set
    • 35
      Custom/internal social network
    • 15
      Open source
    • 8
      Great for all types of websites
    • 6
      Huge install and user base
    • 5
      Best
    • 5
      It's simple and easy to use by any novice
    • 5
      Perfect example of user collaboration
    • 5
      Open Source Community
    • 5
      Most websites make use of it
    • 5
      I like it like I like a kick in the groin
    • 4
      Community
    • 4
      API-based CMS
    • 3
      Easy To use
    • 2
      <a href="https://secure.wphackedhel">Easy Beginner</a>
    CONS OF WORDPRESS
    • 12
      Plugins are of mixed quality
    • 12
      Hard to keep up-to-date if you customize things
    • 9
      Not best backend UI
    • 2
      Complex Organization
    • 1
      Great Security

    related WordPress posts

    Dale Ross
    Independent Contractor at Self Employed · | 22 upvotes · 1.1M views

    I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

    I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

    Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

    See more
    Siddhant Sharma
    Tech Connoisseur at Channelize.io · | 12 upvotes · 846.4K views

    WordPress Magento PHP Java Swift JavaScript

    Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

    Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

    Posting my first article. Please have a look and do give feedback.

    Communication InAppChat Dating Matrimonial #messaging

    See more
    Java logo

    Java

    100.5K
    76.5K
    3.7K
    A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
    100.5K
    76.5K
    + 1
    3.7K
    PROS OF JAVA
    • 587
      Great libraries
    • 441
      Widely used
    • 400
      Excellent tooling
    • 387
      Huge amount of documentation available
    • 331
      Large pool of developers available
    • 203
      Open source
    • 200
      Excellent performance
    • 155
      Great development
    • 149
      Vast array of 3rd party libraries
    • 147
      Used for android
    • 60
      Compiled Language
    • 49
      Used for Web
    • 46
      Managed memory
    • 45
      High Performance
    • 44
      Native threads
    • 42
      Statically typed
    • 35
      Easy to read
    • 33
      Great Community
    • 29
      Reliable platform
    • 24
      JVM compatibility
    • 24
      Sturdy garbage collection
    • 21
      Cross Platform Enterprise Integration
    • 20
      Good amount of APIs
    • 20
      Universal platform
    • 18
      Great Support
    • 13
      Great ecosystem
    • 11
      Lots of boilerplate
    • 11
      Backward compatible
    • 10
      Everywhere
    • 9
      Excellent SDK - JDK
    • 7
      Static typing
    • 6
      Mature language thus stable systems
    • 6
      Better than Ruby
    • 6
      Long term language
    • 6
      Cross-platform
    • 6
      Portability
    • 6
      It's Java
    • 5
      Vast Collections Library
    • 5
      Clojure
    • 5
      Used for Android development
    • 4
      Most developers favorite
    • 4
      Old tech
    • 3
      Javadoc
    • 3
      Stable platform, which many new languages depend on
    • 3
      Best martial for design
    • 3
      Great Structure
    • 3
      History
    • 3
      Testable
    • 2
      Faster than python
    • 1
      Type Safe
    CONS OF JAVA
    • 32
      Verbosity
    • 27
      NullpointerException
    • 16
      Overcomplexity is praised in community culture
    • 14
      Nightmare to Write
    • 11
      Boiler plate code
    • 8
      Classpath hell prior to Java 9
    • 6
      No REPL
    • 4
      No property
    • 2
      Non-intuitive generic implementation
    • 2
      There is not optional parameter
    • 2
      Code are too long
    • 2
      Floating-point errors
    • 1
      Returning Wildcard Types
    • 1
      Java's too statically, stronglly, and strictly typed
    • 1
      Terrbible compared to Python/Batch Perormence

    related Java posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Kamil Kowalski
    Lead Architect at Fresha · | 28 upvotes · 1.4M views

    When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

    See more
    AngularJS logo

    AngularJS

    48.9K
    35.7K
    5.2K
    Superheroic JavaScript MVW Framework
    48.9K
    35.7K
    + 1
    5.2K
    PROS OF ANGULARJS
    • 887
      Quick to develop
    • 587
      Great mvc
    • 572
      Powerful
    • 521
      Restful
    • 503
      Backed by google
    • 349
      Two-way data binding
    • 343
      Javascript
    • 328
      Open source
    • 305
      Dependency injection
    • 197
      Readable
    • 75
      Fast
    • 64
      Directives
    • 63
      Great community
    • 56
      Free
    • 38
      Extend html vocabulary
    • 29
      Components
    • 26
      Easy to test
    • 24
      Easy to learn
    • 23
      Easy to templates
    • 23
      Great documentation
    • 21
      Easy to start
    • 18
      Awesome
    • 17
      Light weight
    • 14
      Angular 2.0
    • 14
      Javascript mvw framework
    • 13
      Great extensions
    • 13
      Efficient
    • 10
      Easy to prototype with
    • 8
      High performance
    • 8
      Coffeescript
    • 7
      Mvc
    • 7
      Two-way binding
    • 7
      Lots of community modules
    • 6
      Easy to e2e
    • 6
      Clean and keeps code readable
    • 5
      Easy for small applications
    • 5
      One of the best frameworks
    • 4
      Fast development
    • 4
      Works great with jquery
    • 3
      I do not touch DOM
    • 2
      Be a developer, not a plumber.
    • 2
      Declarative programming
    • 2
      Dart
    • 2
      Community
    • 2
      The two-way Data Binding is awesome
    • 2
      Hierarchical Data Structure
    • 2
      Typescript
    • 1
      Botionescu@gmail.com
    • 1
      The powerful of binding, routing and controlling routes
    • 1
      Fkin awesome
    • 1
      Opinionated in the right areas
    • 1
      Supports api , easy development
    • 1
      Common Place
    • 1
      Great
    • 1
      Very very useful and fast framework for development
    • 1
      Amazing community support
    • 1
      Readable code
    • 1
      Linear learning curve
    • 1
      Scopes
    • 1
      Programming fun again
    • 1
      Acoperișul
    • 1
      Consistency with backend architecture if using Nest
    • 0
      Httpș//Acoperișul 0757604335
    • 0
      Angular js
    • 0
      Oautho loc
    • 0
      Shvzjn
    • 0
      Acoperișul 0757604335
    • 0
      Js
    • 0
      Bot Ionescu
    • 0
      Google.com
    CONS OF ANGULARJS
    • 10
      Complex
    • 3
      Dependency injection
    • 2
      Learning Curve
    • 2
      Event Listener Overload
    • 1
      Hard to learn

    related AngularJS posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 22 upvotes · 1.1M views

    Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

    • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
    • Vue Styleguidist as our style guide and pool of developed Vue.js components
    • Vuetify as Material Component Framework (for fast app development)
    • TypeScript as programming language
    • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
    • ESLint, TSLint and Prettier for coding style and code analyzes
    • Jest as testing framework
    • Google Fonts and Font Awesome for typography and icon toolkit
    • NativeScript-Vue for mobile development

    The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

    • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
    • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
    • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
    • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
    • Large scaling. Vue.js can help to develop pretty large reusable templates.
    • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
    See more
    React logo

    React

    127K
    103.4K
    3.8K
    A JavaScript library for building user interfaces
    127K
    103.4K
    + 1
    3.8K
    PROS OF REACT
    • 773
      Components
    • 656
      Virtual dom
    • 566
      Performance
    • 490
      Simplicity
    • 437
      Composable
    • 175
      Data flow
    • 161
      Declarative
    • 124
      Isn't an mvc framework
    • 113
      Reactive updates
    • 111
      Explicit app state
    • 38
      JSX
    • 23
      Learn once, write everywhere
    • 19
      Uni-directional data flow
    • 17
      Easy to Use
    • 14
      Works great with Flux Architecture
    • 10
      Great perfomance
    • 8
      Built by Facebook
    • 7
      Javascript
    • 5
      Speed
    • 5
      TypeScript support
    • 4
      Easy to start
    • 4
      Awesome
    • 4
      Feels like the 90s
    • 4
      Hooks
    • 4
      Scalable
    • 3
      Fancy third party tools
    • 3
      Server side views
    • 3
      Props
    • 3
      Obama
    • 3
      Functional
    • 2
      Rich ecosystem
    • 2
      Allows creating single page applications
    • 2
      Sdfsdfsdf
    • 2
      Beautiful and Neat Component Management
    • 2
      Very gentle learning curve
    • 2
      Has functional components
    • 2
      Simple
    • 2
      Closer to standard JavaScript and HTML than others
    • 2
      Super easy
    • 2
      Has arrow functions
    • 2
      Strong Community
    • 2
      Great migration pathway for older systems
    • 2
      SSR
    • 2
      Fast evolving
    • 2
      Simple, easy to reason about and makes you productive
    • 2
      Excellent Documentation
    • 2
      Scales super well
    • 2
      Just the View of MVC
    • 2
      Server Side Rendering
    • 2
      Cross-platform
    • 1
      Permissively-licensed
    • 1
      Sharable
    • 1
      Every decision architecture wise makes sense
    • 1
      Fragments
    • 1
      Start simple
    • 1
      Split your UI into components with one true state
    • 0
      Recharts
    CONS OF REACT
    • 36
      Requires discipline to keep architecture organized
    • 23
      No predefined way to structure your app
    • 22
      Need to be familiar with lots of third party packages
    • 9
      JSX
    • 7
      Not enterprise friendly
    • 5
      One-way binding only
    • 2
      State consistency with backend neglected
    • 2
      Bad Documentation
    • 1
      Paradigms change too fast

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 1.8M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Adebayo Akinlaja
    Engineering Manager at Andela · | 27 upvotes · 1M views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more
    Python logo

    Python

    171.6K
    142.9K
    6.6K
    A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
    171.6K
    142.9K
    + 1
    6.6K
    PROS OF PYTHON
    • 1.1K
      Great libraries
    • 937
      Readable code
    • 830
      Beautiful code
    • 774
      Rapid development
    • 677
      Large community
    • 422
      Open source
    • 381
      Elegant
    • 273
      Great community
    • 266
      Object oriented
    • 211
      Dynamic typing
    • 73
      Great standard library
    • 54
      Very fast
    • 51
      Functional programming
    • 39
      Easy to learn
    • 39
      Scientific computing
    • 32
      Great documentation
    • 25
      Productivity
    • 25
      Matlab alternative
    • 24
      Easy to read
    • 20
      Simple is better than complex
    • 18
      It's the way I think
    • 17
      Imperative
    • 15
      Free
    • 15
      Very programmer and non-programmer friendly
    • 14
      Powerfull language
    • 14
      Powerful
    • 13
      Fast and simple
    • 12
      Scripting
    • 12
      Machine learning support
    • 9
      Explicit is better than implicit
    • 8
      Ease of development
    • 8
      Unlimited power
    • 8
      Clear and easy and powerfull
    • 7
      Import antigravity
    • 6
      It's lean and fun to code
    • 6
      Print "life is short, use python"
    • 5
      Great for tooling
    • 5
      There should be one-- and preferably only one --obvious
    • 5
      Python has great libraries for data processing
    • 5
      High Documented language
    • 5
      I love snakes
    • 5
      Although practicality beats purity
    • 5
      Flat is better than nested
    • 5
      Fast coding and good for competitions
    • 4
      Readability counts
    • 3
      Lists, tuples, dictionaries
    • 3
      CG industry needs
    • 3
      Now is better than never
    • 3
      Multiple Inheritence
    • 3
      Great for analytics
    • 3
      Complex is better than complicated
    • 3
      Plotting
    • 3
      Beautiful is better than ugly
    • 3
      Rapid Prototyping
    • 3
      Socially engaged community
    • 2
      List comprehensions
    • 2
      Web scraping
    • 2
      Many types of collections
    • 2
      Ys
    • 2
      Easy to setup and run smooth
    • 2
      Generators
    • 2
      Special cases aren't special enough to break the rules
    • 2
      If the implementation is hard to explain, it's a bad id
    • 2
      If the implementation is easy to explain, it may be a g
    • 2
      Simple and easy to learn
    • 2
      Import this
    • 2
      No cruft
    • 2
      Easy to learn and use
    • 1
      Flexible and easy
    • 1
      Batteries included
    • 1
      Powerful language for AI
    • 1
      Should START with this but not STICK with This
    • 1
      Good
    • 1
      It is Very easy , simple and will you be love programmi
    • 1
      Better outcome
    • 1
      إسلام هشام
    • 1
      Because of Netflix
    • 1
      A-to-Z
    • 1
      Only one way to do it
    • 1
      Pip install everything
    • 0
      Powerful
    • 0
      Pro
    CONS OF PYTHON
    • 51
      Still divided between python 2 and python 3
    • 29
      Performance impact
    • 26
      Poor syntax for anonymous functions
    • 21
      GIL
    • 19
      Package management is a mess
    • 14
      Too imperative-oriented
    • 12
      Dynamic typing
    • 12
      Hard to understand
    • 10
      Very slow
    • 8
      Not everything is expression
    • 7
      Indentations matter a lot
    • 7
      Explicit self parameter in methods
    • 6
      No anonymous functions
    • 6
      Poor DSL capabilities
    • 6
      Incredibly slow
    • 6
      Requires C functions for dynamic modules
    • 5
      The "lisp style" whitespaces
    • 5
      Fake object-oriented programming
    • 5
      Hard to obfuscate
    • 5
      Threading
    • 4
      Circular import
    • 4
      The benevolent-dictator-for-life quit
    • 4
      Official documentation is unclear.
    • 4
      Lack of Syntax Sugar leads to "the pyramid of doom"
    • 4
      Not suitable for autocomplete
    • 2
      Meta classes
    • 1
      Training wheels (forced indentation)

    related Python posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Nick Parsons
    Director of Developer Marketing at Stream · | 35 upvotes · 1.6M views

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    PHP logo

    PHP

    119.5K
    62.5K
    4.6K
    A popular general-purpose scripting language that is especially suited to web development
    119.5K
    62.5K
    + 1
    4.6K
    PROS OF PHP
    • 945
      Large community
    • 808
      Open source
    • 762
      Easy deployment
    • 481
      Great frameworks
    • 385
      The best glue on the web
    • 234
      Continual improvements
    • 182
      Good old web
    • 144
      Web foundation
    • 134
      Community packages
    • 124
      Tool support
    • 34
      Used by wordpress
    • 33
      Excellent documentation
    • 28
      Used by Facebook
    • 23
      Because of Symfony
    • 21
      Dynamic Language
    • 16
      Cheap hosting
    • 14
      Very powerful web language
    • 14
      Easy to learn
    • 14
      Fast development
    • 14
      Awesome Language and easy to implement
    • 12
      Composer
    • 10
      Because of Laravel
    • 10
      Flexibility, syntax, extensibility
    • 8
      Easiest deployment
    • 7
      Fastestest Time to Version 1.0 Deployments
    • 7
      Worst popularity quality ratio
    • 7
      Short development lead times
    • 7
      Readable Code
    • 6
      Most of the web uses it
    • 6
      Faster then ever
    • 6
      Fast
    • 5
      Simple, flexible yet Scalable
    • 5
      Open source and large community
    • 4
      I have no choice :(
    • 4
      Has the best ecommerce(Magento,Prestashop,Opencart,etc)
    • 4
      Is like one zip of air
    • 4
      Open source and great framework
    • 4
      Large community, easy setup, easy deployment, framework
    • 4
      Easy to use and learn
    • 4
      Cheap to own
    • 4
      Easy to learn, a big community, lot of frameworks
    • 3
      Great developer experience
    • 2
      Hard not to use
    • 2
      FFI
    • 2
      Interpreted at the run time
    • 2
      Great flexibility. From fast prototyping to large apps
    • 2
      Used by STOMT
    • 2
      Fault tolerance
    • 2
      Safe the planet
    • 2
      Walk away
    CONS OF PHP
    • 20
      So easy to learn, good practices are hard to find
    • 16
      Inconsistent API
    • 8
      Fragmented community
    • 5
      Not secure
    • 2
      No routing system
    • 1
      Hard to debug
    • 1
      Old

    related PHP posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.9M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.5M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more