Alternatives to Node.js logo

Alternatives to Node.js

AngularJS, PHP, Python, JavaScript, and React are the most popular alternatives and competitors to Node.js.
125.4K
103.9K
+ 1
8.4K

What is Node.js and what are its top alternatives?

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Node.js is a tool in the Frameworks (Full Stack) category of a tech stack.
Node.js is an open source tool with 83.4K GitHub stars and 22K GitHub forks. Here’s a link to Node.js's open source repository on GitHub

Top Alternatives to Node.js

  • 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. ...

  • PHP

    PHP

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

  • 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. ...

  • 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. ...

  • 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. ...

  • Django

    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • ASP.NET

    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

  • 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! ...

Node.js alternatives & related posts

AngularJS logo

AngularJS

45.5K
32.8K
5.2K
Superheroic JavaScript MVW Framework
45.5K
32.8K
+ 1
5.2K
PROS OF ANGULARJS
  • 887
    Quick to develop
  • 586
    Great mvc
  • 570
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 348
    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
  • 17
    Light weight
  • 17
    Awesome
  • 14
    Angular 2.0
  • 14
    Javascript mvw framework
  • 13
    Efficient
  • 13
    Great extensions
  • 10
    Easy to prototype with
  • 8
    Coffeescript
  • 8
    High performance
  • 7
    Lots of community modules
  • 7
    Mvc
  • 7
    Two-way binding
  • 6
    Clean and keeps code readable
  • 6
    Easy to e2e
  • 5
    Easy for small applications
  • 5
    One of the best frameworks
  • 4
    Works great with jquery
  • 4
    Fast development
  • 2
    Hierarchical Data Structure
  • 2
    Community
  • 2
    The two-way Data Binding is awesome
  • 2
    Typescript
  • 2
    Dart
  • 2
    I do not touch DOM
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 1
    Amazing community support
  • 1
    Readable code
  • 1
    Fkin awesome
  • 1
    Acoperișul
  • 1
    The powerful of binding, routing and controlling routes
  • 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
    Linear learning curve
  • 1
    Scopes
  • 1
    Programming fun again
  • 0
    Acoperișul 0757604335
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Shvzjn
  • 0
    Oautho loc
  • 0
    Js
  • 0
    Angular 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.1M 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 · | 20 upvotes · 806.6K 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
PHP logo

PHP

112.5K
56.5K
4.5K
A popular general-purpose scripting language that is especially suited to web development
112.5K
56.5K
+ 1
4.5K
PROS OF PHP
  • 942
    Large community
  • 806
    Open source
  • 759
    Easy deployment
  • 482
    Great frameworks
  • 385
    The best glue on the web
  • 234
    Continual improvements
  • 181
    Good old web
  • 142
    Web foundation
  • 133
    Community packages
  • 124
    Tool support
  • 33
    Used by wordpress
  • 31
    Excellent documentation
  • 26
    Used by Facebook
  • 23
    Because of Symfony
  • 19
    Dynamic Language
  • 15
    Cheap hosting
  • 14
    Awesome Language and easy to implement
  • 14
    Very powerful web language
  • 13
    Fast development
  • 11
    Easy to learn
  • 11
    Composer
  • 10
    Flexibility, syntax, extensibility
  • 10
    Because of Laravel
  • 8
    Easiest deployment
  • 7
    Readable Code
  • 7
    Short development lead times
  • 7
    Worst popularity quality ratio
  • 7
    Fastestest Time to Version 1.0 Deployments
  • 6
    Faster then ever
  • 6
    Fast
  • 6
    Most of the web uses it
  • 5
    Open source and large community
  • 5
    Simple, flexible yet Scalable
  • 4
    Has the best ecommerce(Magento,Prestashop,Opencart,etc)
  • 4
    Large community, easy setup, easy deployment, framework
  • 4
    Open source and great framework
  • 4
    Easy to use and learn
  • 4
    Cheap to own
  • 4
    Easy to learn, a big community, lot of frameworks
  • 4
    Is like one zip of air
  • 4
    I have no choice :(
  • 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.7M 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.1M 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
Python logo

Python

152.3K
124.8K
6.5K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
152.3K
124.8K
+ 1
6.5K
PROS OF PYTHON
  • 1.1K
    Great libraries
  • 933
    Readable code
  • 824
    Beautiful code
  • 772
    Rapid development
  • 674
    Large community
  • 420
    Open source
  • 380
    Elegant
  • 270
    Great community
  • 262
    Object oriented
  • 209
    Dynamic typing
  • 71
    Great standard library
  • 53
    Very fast
  • 50
    Functional programming
  • 37
    Scientific computing
  • 36
    Easy to learn
  • 31
    Great documentation
  • 25
    Matlab alternative
  • 23
    Productivity
  • 23
    Easy to read
  • 20
    Simple is better than complex
  • 18
    It's the way I think
  • 17
    Imperative
  • 15
    Very programmer and non-programmer friendly
  • 15
    Free
  • 14
    Powerfull language
  • 14
    Powerful
  • 13
    Fast and simple
  • 12
    Scripting
  • 11
    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
    Print "life is short, use python"
  • 6
    It's lean and fun to code
  • 5
    Fast coding and good for competitions
  • 5
    Flat is better than nested
  • 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
    Great for tooling
  • 4
    Readability counts
  • 3
    Plotting
  • 3
    CG industry needs
  • 3
    Beautiful is better than ugly
  • 3
    Complex is better than complicated
  • 3
    Great for analytics
  • 3
    Multiple Inheritence
  • 3
    Now is better than never
  • 3
    Lists, tuples, dictionaries
  • 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
    Better outcome
  • 1
    It is Very easy , simple and will you be love programmi
  • 1
    Powerful language for AI
  • 1
    Should START with this but not STICK with This
  • 1
    Flexible and easy
  • 1
    Batteries included
  • 1
    Good
  • 1
    A-to-Z
  • 1
    Only one way to do it
  • 1
    Because of Netflix
  • 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 · | 39 upvotes · 4.2M 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.4M 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
JavaScript logo

JavaScript

224.5K
173.9K
7.8K
Lightweight, interpreted, object-oriented language with first-class functions
224.5K
173.9K
+ 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
  • 887
    Fast
  • 736
    Light weight
  • 416
    Flexible
  • 383
    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
    Because I love functions
  • 7
    JavaScript is the New PHP
  • 7
    Like it or not, JS is part of the web standard
  • 7
    Its everywhere
  • 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 · | 39 upvotes · 4.2M 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
React logo

React

113.6K
91.2K
3.8K
A JavaScript library for building user interfaces
113.6K
91.2K
+ 1
3.8K
PROS OF REACT
  • 760
    Components
  • 652
    Virtual dom
  • 563
    Performance
  • 486
    Simplicity
  • 436
    Composable
  • 175
    Data flow
  • 159
    Declarative
  • 124
    Isn't an mvc framework
  • 113
    Reactive updates
  • 111
    Explicit app state
  • 32
    JSX
  • 23
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    TypeScript support
  • 5
    Speed
  • 4
    Feels like the 90s
  • 4
    Scalable
  • 4
    Easy to start
  • 4
    Awesome
  • 3
    Fancy third party tools
  • 3
    Hooks
  • 3
    Functional
  • 3
    Server side views
  • 3
    Props
  • 2
    Rich ecosystem
  • 2
    Obama
  • 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
    Fragments
  • 1
    Start simple
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Beautiful and Neat Component Management
  • 1
    Sdfsdfsdf
  • 1
    Allows creating single page applications
  • 1
    Split your UI into components with one true state
  • 1
    Sharable
CONS OF REACT
  • 35
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 21
    Need to be familiar with lots of third party packages
  • 8
    JSX
  • 7
    Not enterprise friendly
  • 4
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.6M 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 · | 26 upvotes · 786.9K 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
Django logo

Django

26.7K
23.6K
3.8K
The Web framework for perfectionists with deadlines
26.7K
23.6K
+ 1
3.8K
PROS OF DJANGO
  • 634
    Rapid development
  • 468
    Open source
  • 401
    Great community
  • 353
    Easy to learn
  • 263
    Mvc
  • 215
    Beautiful code
  • 210
    Elegant
  • 193
    Free
  • 191
    Great packages
  • 178
    Great libraries
  • 68
    Restful
  • 65
    Comes with auth and crud admin panel
  • 65
    Powerful
  • 60
    Great documentation
  • 58
    Great for web
  • 44
    Python
  • 37
    Great orm
  • 34
    Great for api
  • 27
    All included
  • 22
    Web Apps
  • 21
    Fast
  • 18
    Used by top startups
  • 16
    Clean
  • 15
    Easy setup
  • 15
    Sexy
  • 12
    Convention over configuration
  • 10
    ORM
  • 9
    The Django community
  • 9
    Allows for very rapid development with great libraries
  • 6
    Great MVC and templating engine
  • 6
    King of backend world
  • 6
    Its elegant and practical
  • 5
    Mvt
  • 5
    Batteries included
  • 5
    Full stack
  • 5
    Fast prototyping
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 5
    Have not found anything that it can't do
  • 4
    Very quick to get something up and running
  • 4
    Easy to use
  • 4
    Easy
  • 4
    Cross-Platform
  • 3
    Map
  • 3
    Great peformance
  • 3
    Scaffold
  • 3
    Just the right level of abstraction
  • 3
    Modular
  • 3
    Full-Text Search
  • 3
    Zero code burden to change databases
  • 3
    Python community
  • 3
    Many libraries
  • 2
    Easy to change database manager
  • 1
    Node js
CONS OF DJANGO
  • 25
    Underpowered templating
  • 19
    Underpowered ORM
  • 19
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Admin
  • 7
    Not nodejs
  • 6
    Configuration hell
  • 4
    Not as clean and nice documentation like Laravel
  • 3
    Python
  • 3
    Not typed
  • 3
    Bloated admin panel included
  • 2
    Overwhelming folder structure
  • 1
    InEffective Multithreading

related Django posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
ASP.NET logo

ASP.NET

21.4K
6.8K
14
An open source web framework for building modern web apps and services with .NET
21.4K
6.8K
+ 1
14
PROS OF ASP.NET
  • 11
    Great mvc
  • 3
    Easy to learn
CONS OF ASP.NET
  • 1
    Not highly flexible for advance Developers
  • 1
    Entity framework is very slow

related ASP.NET posts

Greg Neumann

Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

See more

Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

ASP.NET / Node.js / Laravel. ......?

Please guide us

See more
Java logo

Java

91.6K
68.3K
3.6K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
91.6K
68.3K
+ 1
3.6K
PROS OF JAVA
  • 582
    Great libraries
  • 439
    Widely used
  • 398
    Excellent tooling
  • 385
    Huge amount of documentation available
  • 330
    Large pool of developers available
  • 203
    Open source
  • 199
    Excellent performance
  • 154
    Great development
  • 148
    Vast array of 3rd party libraries
  • 147
    Used for android
  • 59
    Compiled Language
  • 49
    Used for Web
  • 46
    Managed memory
  • 44
    Native threads
  • 44
    High Performance
  • 41
    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
    Universal platform
  • 20
    Good amount of APIs
  • 18
    Great Support
  • 13
    Great ecosystem
  • 11
    Lots of boilerplate
  • 11
    Backward compatible
  • 10
    Everywhere
  • 9
    Excellent SDK - JDK
  • 7
    Static typing
  • 6
    Long term language
  • 6
    Better than Ruby
  • 6
    Mature language thus stable systems
  • 6
    Portability
  • 6
    Cross-platform
  • 6
    It's Java
  • 5
    Vast Collections Library
  • 5
    Used for Android development
  • 5
    Clojure
  • 4
    Most developers favorite
  • 4
    Old tech
  • 3
    Best martial for design
  • 3
    Great Structure
  • 3
    Testable
  • 3
    Javadoc
  • 3
    Stable platform, which many new languages depend on
  • 2
    History
CONS OF JAVA
  • 30
    Verbosity
  • 25
    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
    Floating-point errors
  • 2
    There is not optional parameter
  • 2
    Code are too long
  • 2
    Non-intuitive generic implementation
  • 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 · | 39 upvotes · 4.2M 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 · | 27 upvotes · 1.2M 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