Alternatives to ASP.NET logo

Alternatives to ASP.NET

ASP.NET Core, PHP, Django, React, and JavaScript are the most popular alternatives and competitors to ASP.NET.
20K
5.5K
+ 1
7

What is ASP.NET and what are its top alternatives?

.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
ASP.NET is a tool in the Languages category of a tech stack.

Top Alternatives to ASP.NET

  • ASP.NET Core

    ASP.NET Core

    A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core. ...

  • PHP

    PHP

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

  • Django

    Django

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

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

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

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

  • Node.js

    Node.js

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

  • HTML5

    HTML5

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

ASP.NET alternatives & related posts

ASP.NET Core logo

ASP.NET Core

1.5K
1.5K
219
A cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux
1.5K
1.5K
+ 1
219
PROS OF ASP.NET CORE
  • 36
    C#
  • 26
    Visual Studio
  • 22
    NuGet
  • 21
    Performance
  • 16
    Open source
  • 11
    Productive
  • 11
    Easy to learn and use
  • 7
    Fast
  • 7
    Fast Performance With Microservices
  • 7
    Visual Studio Code
  • 6
    JetBrains Rider
  • 5
    Rapid Development
  • 5
    Easily Expose API
  • 5
    Azure Integration
  • 5
    Web Apps
  • 5
    One stop shop
  • 4
    Razor Pages
  • 3
    MVVM
  • 3
    Great MVC and templating engine with Razor
  • 3
    Scalable
  • 3
    Easy to learn
  • 3
    MVC
  • 3
    Cross Platform
  • 2
    Professionally Developed Packages
CONS OF ASP.NET CORE
  • 5
    Great Doc
  • 3
    Fast
  • 2
    Clean
  • 2
    Professionally written Nuget Packages, vs IMPORT junk
  • 1
    Long polling is difficult to implement

related ASP.NET Core posts

Taimoor Mirza
Associate Software Engineer at Intech Process Automation · | 4 upvotes · 200.7K views

For context, I currently use JavaScript (React) and Python (Flask) in my daily routine.

I need your help in choosing either Spring Boot or ASP.NET Core. Both frameworks seem to have mature ecosystems. I would like to hear your thoughts on the following points:

  • Difficulty level of both frameworks
  • Level of community support
  • Career prospects i.e do Spring based jobs pay more or vice versa
  • which one will be helpful if I decide to transition towards a more specialized field like data engineering.

I am asking this because it is something that I am also exploring in parallel. I know that Python and #SQL play a huge role in big data.

See more

Greetings Guys,

I want to develop an E-Commerce app and a web app.

For E-Commerce App ( Cross-Platform) - Thinking of React Native instead of Flutter or Kotlin Multiplatform

For Web App - Thinking of ASP.NET Core

My thoughts -

a) ASP.NET is really good for a big enterprise-level application like Java. So it should be great for an eCommerce app website for large customers.

b) Since I don't want to develop two different apps for android and iOS, cross-platform will be good. Will save budget and time. React native is popular with its support and libraries. So it seems good.

(P.S. - I might be biased because I know ASP.NET. But will welcome your insightful Answer).

So Is it a good choice - for a web app and a mobile app? Let me know if you think I should use other stacks for mobile and web?

For Database, Is Microsoft SQL Server appropriate? Which database should I select - SQL database or NoSQL Database? Please provide another option apart from SQL Server.

(P.S - I know SQL Server is used for Big banking services. So it can handle a large number of transactions. If I am wrong, please correct me.)

Thank you in advance :)

See more
PHP logo

PHP

104.5K
49.4K
4.5K
A popular general-purpose scripting language that is especially suited to web development
104.5K
49.4K
+ 1
4.5K
PROS OF PHP
  • 941
    Large community
  • 804
    Open source
  • 757
    Easy deployment
  • 481
    Great frameworks
  • 384
    The best glue on the web
  • 232
    Continual improvements
  • 180
    Good old web
  • 141
    Web foundation
  • 131
    Community packages
  • 123
    Tool support
  • 32
    Used by wordpress
  • 30
    Excellent documentation
  • 25
    Used by Facebook
  • 23
    Because of Symfony
  • 18
    Dynamic Language
  • 14
    Awesome Language and easy to implement
  • 13
    Very powerful web language
  • 13
    Cheap hosting
  • 13
    Fast development
  • 10
    Composer
  • 9
    Because of Laravel
  • 9
    Easy to learn
  • 9
    Flexibility, syntax, extensibility
  • 7
    Worst popularity quality ratio
  • 7
    Easiest deployment
  • 7
    Readable Code
  • 7
    Fastestest Time to Version 1.0 Deployments
  • 7
    Short development lead times
  • 6
    Fast
  • 6
    Most of the web uses it
  • 6
    Faster then ever
  • 5
    Open source and large community
  • 4
    I have no choice :(
  • 4
    Easy to learn, a big community, lot of frameworks
  • 4
    Cheap to own
  • 4
    Simple, flexible yet Scalable
  • 4
    Easy to use and learn
  • 3
    Great developer experience
  • 3
    Large community, easy setup, easy deployment, framework
  • 3
    Is like one zip of air
  • 3
    Open source and great framework
  • 3
    Has the best ecommerce(Magento,Prestashop,Opencart,etc)
  • 2
    FFI
  • 2
    Walk away
  • 2
    Safe the planet
  • 2
    Hard not to use
  • 2
    Fault tolerance
  • 2
    Interpreted at the run time
  • 2
    Great flexibility. From fast prototyping to large apps
  • 2
    Used by STOMT
CONS OF PHP
  • 19
    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 · | 42 upvotes · 1.5M 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 · | 24 upvotes · 1.7M 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
Django logo

Django

23.8K
20.6K
3.6K
The Web framework for perfectionists with deadlines
23.8K
20.6K
+ 1
3.6K
PROS OF DJANGO
  • 618
    Rapid development
  • 459
    Open source
  • 394
    Great community
  • 344
    Easy to learn
  • 256
    Mvc
  • 208
    Beautiful code
  • 207
    Elegant
  • 187
    Free
  • 186
    Great packages
  • 173
    Great libraries
  • 63
    Restful
  • 60
    Powerful
  • 59
    Comes with auth and crud admin panel
  • 55
    Great documentation
  • 52
    Great for web
  • 41
    Python
  • 35
    Great orm
  • 31
    Great for api
  • 24
    All included
  • 20
    Web Apps
  • 19
    Fast
  • 16
    Used by top startups
  • 14
    Clean
  • 13
    Sexy
  • 12
    Easy setup
  • 10
    Convention over configuration
  • 7
    ORM
  • 7
    Allows for very rapid development with great libraries
  • 7
    The Django community
  • 5
    Its elegant and practical
  • 5
    Great MVC and templating engine
  • 4
    Full stack
  • 4
    Mvt
  • 4
    Easy Structure , useful inbuilt library
  • 4
    Fast prototyping
  • 4
    Easy to develop end to end AI Models
  • 3
    Easy
  • 3
    Easy to use
  • 3
    King of backend world
  • 3
    Cross-Platform
  • 3
    Batteries included
  • 3
    Have not found anything that it can't do
  • 2
    Scaffold
  • 2
    Zero code burden to change databases
  • 2
    Full-Text Search
  • 2
    Map
  • 2
    Modular
  • 2
    Very quick to get something up and running
  • 2
    Many libraries
  • 2
    Python community
  • 2
    Great peformance
  • 2
    Just the right level of abstraction
  • 1
    Easy to change database manager
CONS OF DJANGO
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 7
    Admin
  • 6
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 3
    Python
  • 2
    Overwhelming folder structure
  • 2
    Bloated admin panel included
  • 2
    Not typed
  • 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
React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.5M 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
Johnny Bell
Software Engineer at Weedmaps · | 26 upvotes · 377.9K views
Shared insights
on
Vue.js
React

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
JavaScript logo

JavaScript

192.5K
147.2K
7.7K
Lightweight, interpreted, object-oriented language with first-class functions
192.5K
147.2K
+ 1
7.7K
PROS OF JAVASCRIPT
  • 1.6K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.1K
    Lots of great frameworks
  • 884
    Fast
  • 733
    Light weight
  • 411
    Flexible
  • 376
    You can't get a device today that doesn't run js
  • 279
    Non-blocking i/o
  • 229
    Ubiquitousness
  • 184
    Expressive
  • 48
    Extended functionality to web pages
  • 42
    Relatively easy language
  • 39
    Executed on the client side
  • 24
    Relatively fast to the end user
  • 20
    Pure Javascript
  • 15
    Functional programming
  • 8
    Async
  • 6
    JavaScript is the New PHP
  • 6
    Because I love functions
  • 6
    Full-stack
  • 6
    Setup is easy
  • 5
    Expansive community
  • 5
    Its everywhere
  • 5
    Can be used in backend, frontend and DB
  • 5
    Future Language of The Web
  • 5
    Like it or not, JS is part of the web standard
  • 4
    Popularized Class-Less Architecture & Lambdas
  • 4
    Supports lambdas and closures
  • 4
    Evolution of C
  • 4
    For the good parts
  • 4
    Easy to hire developers
  • 4
    Everyone use it
  • 4
    Love-hate relationship
  • 3
    Everywhere
  • 3
    Promise relationship
  • 3
    Agile, packages simple to use
  • 3
    What to add
  • 3
    Easy to make something
  • 3
    Nice
  • 3
    Only Programming language on browser
  • 3
    Because it is so simple and lightweight
  • 3
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 3
    Function expressions are useful for callbacks
  • 3
    Photoshop has 3 JS runtimes built in
  • 3
    No need to use PHP
  • 3
    Versitile
  • 3
    Most Popular Language in the World
  • 3
    Can be used both as frontend and backend as well
  • 3
    Easy
  • 3
    Clojurescript
  • 3
    Stockholm Syndrome
  • 3
    It let's me use Babel & Typescript
  • 3
    Client side JS uses the visitors CPU to save Server Res
  • 3
    Its fun and fast
  • 3
    1.6K Can be used on frontend/backend
  • 3
    Powerful
  • 3
    Scope manipulation
  • 3
    Hard not to use
  • 3
    Client processing
  • 3
    It's fun
  • 1
    Acoperișul 0757604335
  • 1
    JavaScript j.s
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 · | 38 upvotes · 3.7M 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
Python logo

Python

131K
105.2K
6.5K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
131K
105.2K
+ 1
6.5K
PROS OF PYTHON
  • 1.1K
    Great libraries
  • 927
    Readable code
  • 817
    Beautiful code
  • 768
    Rapid development
  • 671
    Large community
  • 418
    Open source
  • 379
    Elegant
  • 268
    Great community
  • 261
    Object oriented
  • 209
    Dynamic typing
  • 70
    Great standard library
  • 52
    Very fast
  • 48
    Functional programming
  • 35
    Scientific computing
  • 33
    Easy to learn
  • 30
    Great documentation
  • 25
    Matlab alternative
  • 23
    Productivity
  • 22
    Easy to read
  • 19
    Simple is better than complex
  • 17
    It's the way I think
  • 17
    Imperative
  • 15
    Very programmer and non-programmer friendly
  • 14
    Powerful
  • 14
    Free
  • 13
    Fast and simple
  • 13
    Powerfull language
  • 12
    Scripting
  • 9
    Machine learning support
  • 9
    Explicit is better than implicit
  • 8
    Unlimited power
  • 8
    Ease of development
  • 7
    Import antigravity
  • 7
    Clear and easy and powerfull
  • 6
    It's lean and fun to code
  • 6
    Print "life is short, use python"
  • 5
    Flat is better than nested
  • 5
    Fast coding and good for competitions
  • 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
    CG industry needs
  • 3
    Beautiful is better than ugly
  • 3
    Multiple Inheritence
  • 3
    Complex is better than complicated
  • 3
    Great for analytics
  • 3
    Socially engaged community
  • 3
    Rapid Prototyping
  • 3
    Lists, tuples, dictionaries
  • 3
    Plotting
  • 2
    Generators
  • 2
    Simple and easy to learn
  • 2
    Import this
  • 2
    No cruft
  • 2
    Easy to learn and use
  • 2
    List comprehensions
  • 2
    Special cases aren't special enough to break the rules
  • 2
    Now is better than never
  • 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
  • 1
    Many types of collections
  • 1
    Better outcome
  • 1
    Batteries included
  • 1
    Ys
  • 1
    Good
  • 1
    Pip install everything
  • 1
    Easy to setup and run smooth
  • 1
    Because of Netflix
  • 1
    Flexible and easy
  • 1
    Web scraping
  • 1
    Should START with this but not STICK with This
  • 1
    Powerful language for AI
  • 1
    It is Very easy , simple and will you be love programmi
  • 1
    Only one way to do it
  • 1
    A-to-Z
  • 0
    Pro
  • 0
    Powerful
CONS OF PYTHON
  • 50
    Still divided between python 2 and python 3
  • 27
    Performance impact
  • 26
    Poor syntax for anonymous functions
  • 19
    Package management is a mess
  • 19
    GIL
  • 13
    Too imperative-oriented
  • 12
    Hard to understand
  • 11
    Dynamic typing
  • 9
    Very slow
  • 8
    Not everything is expression
  • 7
    Explicit self parameter in methods
  • 7
    Indentations matter a lot
  • 6
    Poor DSL capabilities
  • 6
    No anonymous functions
  • 6
    Requires C functions for dynamic modules
  • 5
    Threading
  • 5
    The "lisp style" whitespaces
  • 5
    Hard to obfuscate
  • 4
    Fake object-oriented programming
  • 4
    Incredibly slow
  • 4
    Lack of Syntax Sugar leads to "the pyramid of doom"
  • 4
    The benevolent-dictator-for-life quit
  • 3
    Official documentation is unclear.
  • 3
    Circular import
  • 3
    Not suitable for autocomplete
  • 1
    Training wheels (forced indentation)
  • 1
    Meta classes

related Python posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M 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.3M 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
Node.js logo

Node.js

108.7K
88.4K
8.3K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
108.7K
88.4K
+ 1
8.3K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 791
    Open source
  • 480
    Great for apis
  • 471
    Asynchronous
  • 417
    Great community
  • 387
    Great for realtime apps
  • 292
    Great for command line utilities
  • 78
    Node Modules
  • 76
    Websockets
  • 65
    Uber Simple
  • 53
    Allows us to reuse code in the frontend
  • 53
    Great modularity
  • 38
    Easy to start
  • 33
    Great for Data Streaming
  • 29
    Realtime
  • 25
    Awesome
  • 23
    Non blocking IO
  • 16
    Can be used as a proxy
  • 15
    High performance, open source, scalable
  • 14
    Non-blocking and modular
  • 13
    Easy and Fun
  • 12
    Same lang as AngularJS
  • 11
    Easy and powerful
  • 10
    Future of BackEnd
  • 9
    Fast
  • 8
    Scalability
  • 8
    Cross platform
  • 8
    Fullstack
  • 7
    Mean Stack
  • 7
    Simple
  • 5
    Easy concurrency
  • 5
    Great for webapps
  • 5
    React
  • 4
    Friendly
  • 4
    Easy to use and fast and goes well with JSONdb's
  • 4
    Typescript
  • 4
    Fast, simple code and async
  • 3
    Its amazingly fast and scalable
  • 3
    Scalable
  • 3
    Great speed
  • 3
    Fast development
  • 3
    Isomorphic coolness
  • 3
    Control everything
  • 2
    It's fast
  • 2
    Not Python
  • 2
    Blazing fast
  • 2
    One language, end-to-end
  • 2
    TypeScript Support
  • 2
    Easy to learn
  • 2
    Javascript2
  • 2
    Easy to use
  • 2
    Less boilerplate code
  • 2
    Sooper easy for the Backend connectivity
  • 2
    Great community
  • 2
    Scales, fast, simple, great community, npm, express
  • 2
    Performant and fast prototyping
  • 1
    Easy
  • 1
    Lovely
  • 0
    Event Driven
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 40
    New framework every day
  • 34
    Lots of terrible examples on the internet
  • 28
    Asynchronous programming is the worst
  • 22
    Callback
  • 16
    Javascript
  • 11
    Dependency based on GitHub
  • 10
    Dependency hell
  • 10
    Low computational power
  • 7
    Can block whole server easily
  • 6
    Very very Slow
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 1
    No standard approach

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 42 upvotes · 1.5M 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
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M 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
HTML5 logo

HTML5

86.2K
67K
2.2K
5th major revision of the core language of the World Wide Web
86.2K
67K
+ 1
2.2K
PROS OF HTML5
  • 444
    New doctype
  • 388
    Local storage
  • 334
    Canvas
  • 285
    Semantic header and footer
  • 237
    Video element
  • 120
    Geolocation
  • 105
    Form autofocus
  • 98
    Email inputs
  • 84
    Editable content
  • 79
    Application caches
  • 9
    Cleaner Code
  • 8
    Easy to use
  • 4
    Semantical
  • 4
    Easy
  • 3
    Websockets
  • 3
    Better
  • 3
    Modern
  • 3
    Audio element
  • 2
    Content focused
  • 2
    Compatible
  • 2
    Portability
  • 2
    Semantic Header and Footer, Geolocation, New Doctype
CONS OF HTML5
    Be the first to leave a con

    related HTML5 posts

    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.4M views

    I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

    For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

    Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

    I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

    I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

    I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

    I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

    For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

    For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

    For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

    I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

    So that's my latest mobile stack. What tools do you use? Have you tried these ones?

    See more
    Jeyabalaji Subramanian

    At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

    (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

    (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

    (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

    (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

    In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

    By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

    In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

    See more