Alternatives to PHP logo

Alternatives to PHP

JavaScript, Python, Java, HTML5, and Node.js are the most popular alternatives and competitors to PHP.
129.1K
71.4K
+ 1
4.6K

What is PHP and what are its top alternatives?

Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.
PHP is a tool in the Languages category of a tech stack.
PHP is an open source tool with 34.9K GitHub stars and 7.4K GitHub forks. Here’s a link to PHP's open source repository on GitHub

Top Alternatives to PHP

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

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

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

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

  • Ruby
    Ruby

    Ruby is a language of careful balance. Its creator, Yukihiro “Matz” Matsumoto, blended parts of his favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that balanced functional programming with imperative programming. ...

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

PHP alternatives & related posts

JavaScript logo

JavaScript

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

199.9K
168.9K
6.7K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
199.9K
168.9K
+ 1
6.7K
PROS OF PYTHON
  • 1.1K
    Great libraries
  • 947
    Readable code
  • 835
    Beautiful code
  • 780
    Rapid development
  • 682
    Large community
  • 426
    Open source
  • 385
    Elegant
  • 278
    Great community
  • 268
    Object oriented
  • 214
    Dynamic typing
  • 75
    Great standard library
  • 56
    Very fast
  • 51
    Functional programming
  • 43
    Scientific computing
  • 43
    Easy to learn
  • 33
    Great documentation
  • 26
    Matlab alternative
  • 25
    Productivity
  • 25
    Easy to read
  • 21
    Simple is better than complex
  • 18
    It's the way I think
  • 17
    Imperative
  • 15
    Very programmer and non-programmer friendly
  • 15
    Free
  • 14
    Machine learning support
  • 14
    Powerful
  • 14
    Powerfull language
  • 13
    Fast and simple
  • 12
    Scripting
  • 9
    Explicit is better than implicit
  • 8
    Unlimited power
  • 8
    Clear and easy and powerfull
  • 8
    Ease of development
  • 7
    Import antigravity
  • 6
    It's lean and fun to code
  • 6
    Print "life is short, use python"
  • 5
    I love snakes
  • 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
    Although practicality beats purity
  • 5
    Flat is better than nested
  • 5
    Great for tooling
  • 4
    Readability counts
  • 4
    Rapid Prototyping
  • 3
    Lists, tuples, dictionaries
  • 3
    Socially engaged community
  • 3
    Now is better than never
  • 3
    Web scraping
  • 3
    Complex is better than complicated
  • 3
    Multiple Inheritence
  • 3
    Plotting
  • 3
    Beautiful is better than ugly
  • 3
    CG industry needs
  • 3
    Great for analytics
  • 2
    Easy to setup and run smooth
  • 2
    Generators
  • 2
    If the implementation is easy to explain, it may be a g
  • 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
    Simple and easy to learn
  • 2
    Import this
  • 2
    Many types of collections
  • 2
    No cruft
  • 2
    Easy to learn and use
  • 2
    List comprehensions
  • 1
    Can understand easily who are new to programming
  • 1
    Because of Netflix
  • 1
    A-to-Z
  • 1
    Only one way to do it
  • 1
    It is Very easy , simple and will you be love programmi
  • 1
    Powerful language for AI
  • 1
    Flexible and easy
  • 1
    Better outcome
  • 1
    Batteries included
  • 1
    Pip install everything
  • 1
    Should START with this but not STICK with This
  • 1
    Good for hacking
  • 0
    Powerful
CONS OF PYTHON
  • 51
    Still divided between python 2 and python 3
  • 28
    Performance impact
  • 26
    Poor syntax for anonymous functions
  • 21
    GIL
  • 19
    Package management is a mess
  • 14
    Too imperative-oriented
  • 12
    Hard to understand
  • 12
    Dynamic typing
  • 10
    Very slow
  • 8
    Not everything is expression
  • 7
    Explicit self parameter in methods
  • 7
    Indentations matter a lot
  • 6
    Poor DSL capabilities
  • 6
    Incredibly slow
  • 6
    No anonymous functions
  • 6
    Requires C functions for dynamic modules
  • 5
    Hard to obfuscate
  • 5
    Threading
  • 5
    Fake object-oriented programming
  • 5
    The "lisp style" whitespaces
  • 4
    Official documentation is unclear.
  • 4
    Circular import
  • 4
    Lack of Syntax Sugar leads to "the pyramid of doom"
  • 4
    Not suitable for autocomplete
  • 4
    The benevolent-dictator-for-life quit
  • 2
    Meta classes
  • 1
    Training wheels (forced indentation)

related Python posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.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
Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 1.8M 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
Java logo

Java

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

related Java posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.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
Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.8M 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
HTML5 logo

HTML5

127.1K
106.4K
2.2K
5th major revision of the core language of the World Wide Web
127.1K
106.4K
+ 1
2.2K
PROS OF HTML5
  • 447
    New doctype
  • 389
    Local storage
  • 334
    Canvas
  • 285
    Semantic header and footer
  • 240
    Video element
  • 121
    Geolocation
  • 105
    Form autofocus
  • 100
    Email inputs
  • 85
    Editable content
  • 79
    Application caches
  • 10
    Easy to use
  • 9
    Cleaner Code
  • 4
    Easy
  • 4
    Semantical
  • 3
    Websockets
  • 3
    Better
  • 3
    Audio element
  • 3
    Modern
  • 2
    Semantic Header and Footer, Geolocation, New Doctype
  • 2
    Content focused
  • 2
    Compatible
  • 2
    Portability
  • 1
    Very easy to learning to HTML
CONS OF HTML5
  • 1
    Easy to forget the tags when you're a begginner
  • 1
    Long and winding code

related HTML5 posts

Jonathan Pugh
Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2M 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
Paul Morgan
Researcher at Working on it · | 25 upvotes · 113.8K views
Shared insights
on
JavaJavaCSS 3CSS 3HTML5HTML5

Hey everyone, I have a matrix chart drawn in HTML5/CSS 3 dominantly using CSS grid. I would like to add interactive features and am unsure about the best tool. My programming knowledge is limited to 2 semesters of Java in college, so I'd have to learn the language as I go. I am open to anything, but the selected languages would be useful in future projects.

Here are the features I am attempting to add to the site linked as my blog:

  • Assign over 120 attributes each to over 400 elements (probably in a DB)

  • Procedurally position elements in a matrix chart based on user-inputted filters (filtering and searching)

  • Procedurally position matrix elements based on attributes weighted by user-input

  • Change style of elements based on user input (highlighting)

  • Allow saving matrix chart states to be revisited or shared

  • Provide a user-friendly interface for users to submit the above input

  • Build several columns or matrices that are separate but related and seamless to the viewer

See more
Node.js logo

Node.js

162.6K
137.1K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
162.6K
137.1K
+ 1
8.5K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 802
    Open source
  • 485
    Great for apis
  • 475
    Asynchronous
  • 420
    Great community
  • 390
    Great for realtime apps
  • 296
    Great for command line utilities
  • 82
    Websockets
  • 81
    Node Modules
  • 69
    Uber Simple
  • 59
    Great modularity
  • 58
    Allows us to reuse code in the frontend
  • 42
    Easy to start
  • 35
    Great for Data Streaming
  • 32
    Realtime
  • 28
    Awesome
  • 25
    Non blocking IO
  • 18
    Can be used as a proxy
  • 17
    High performance, open source, scalable
  • 16
    Non-blocking and modular
  • 15
    Easy and Fun
  • 14
    Easy and powerful
  • 13
    Same lang as AngularJS
  • 13
    Future of BackEnd
  • 12
    Fullstack
  • 11
    Fast
  • 10
    Cross platform
  • 10
    Scalability
  • 9
    Simple
  • 8
    Mean Stack
  • 7
    Great for webapps
  • 7
    Easy concurrency
  • 6
    Typescript
  • 6
    React
  • 6
    Fast, simple code and async
  • 6
    Friendly
  • 5
    Great speed
  • 5
    Easy to use and fast and goes well with JSONdb's
  • 5
    Scalable
  • 5
    Its amazingly fast and scalable
  • 5
    Control everything
  • 5
    Fast development
  • 4
    Isomorphic coolness
  • 4
    Easy to use
  • 4
    It's fast
  • 3
    Great community
  • 3
    Scales, fast, simple, great community, npm, express
  • 3
    TypeScript Support
  • 3
    Sooper easy for the Backend connectivity
  • 3
    Not Python
  • 3
    One language, end-to-end
  • 3
    Easy
  • 3
    Easy to learn
  • 3
    Less boilerplate code
  • 3
    Performant and fast prototyping
  • 3
    Blazing fast
  • 2
    Event Driven
  • 2
    Lovely
  • 2
    Npm i ape-updating
  • 1
    Creat for apis
  • 0
    Node
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 44
    New framework every day
  • 38
    Lots of terrible examples on the internet
  • 31
    Asynchronous programming is the worst
  • 23
    Callback
  • 18
    Javascript
  • 11
    Dependency based on GitHub
  • 11
    Dependency hell
  • 10
    Low computational power
  • 7
    Very very Slow
  • 7
    Can block whole server easily
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 2
    No standard approach
  • 1
    Bad transitive dependency management
  • 1
    Can't read server session

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2.3M 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 · | 41 upvotes · 5.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
Ruby logo

Ruby

31.1K
19.5K
3.9K
A dynamic, interpreted, open source programming language with a focus on simplicity and productivity
31.1K
19.5K
+ 1
3.9K
PROS OF RUBY
  • 604
    Programme friendly
  • 536
    Quick to develop
  • 488
    Great community
  • 467
    Productivity
  • 430
    Simplicity
  • 272
    Open source
  • 233
    Meta-programming
  • 204
    Powerful
  • 155
    Blocks
  • 138
    Powerful one-liners
  • 67
    Flexible
  • 57
    Easy to learn
  • 50
    Easy to start
  • 41
    Maintainability
  • 36
    Lambdas
  • 30
    Procs
  • 21
    Fun to write
  • 19
    Diverse web frameworks
  • 13
    Reads like English
  • 10
    Makes me smarter and happier
  • 9
    Rails
  • 8
    Elegant syntax
  • 7
    Very Dynamic
  • 6
    Matz
  • 5
    Object Oriented
  • 5
    Programmer happiness
  • 4
    Fun and useful
  • 4
    Generally fun but makes you wanna cry sometimes
  • 4
    Friendly
  • 3
    Elegant code
  • 3
    There are so many ways to make it do what you want
  • 3
    Easy packaging and modules
  • 2
    Primitive types can be tampered with
CONS OF RUBY
  • 7
    Memory hog
  • 7
    Really slow if you're not really careful
  • 3
    Nested Blocks can make code unreadable
  • 2
    Encouraging imperative programming
  • 1
    Ambiguous Syntax, such as function parentheses

related Ruby posts

Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.8M 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
Jonathan Pugh
Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2M 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
Django logo

Django

33.2K
30K
4K
The Web framework for perfectionists with deadlines
33.2K
30K
+ 1
4K
PROS OF DJANGO
  • 656
    Rapid development
  • 480
    Open source
  • 414
    Great community
  • 369
    Easy to learn
  • 270
    Mvc
  • 224
    Beautiful code
  • 216
    Elegant
  • 199
    Free
  • 196
    Great packages
  • 185
    Great libraries
  • 74
    Restful
  • 72
    Comes with auth and crud admin panel
  • 72
    Powerful
  • 69
    Great documentation
  • 64
    Great for web
  • 51
    Python
  • 39
    Great orm
  • 37
    Great for api
  • 28
    All included
  • 25
    Fast
  • 23
    Web Apps
  • 20
    Used by top startups
  • 20
    Clean
  • 19
    Easy setup
  • 17
    Sexy
  • 14
    Convention over configuration
  • 13
    Allows for very rapid development with great libraries
  • 13
    ORM
  • 12
    The Django community
  • 10
    King of backend world
  • 9
    Great MVC and templating engine
  • 8
    Full stack
  • 7
    Batteries included
  • 7
    Its elegant and practical
  • 6
    Have not found anything that it can't do
  • 6
    Very quick to get something up and running
  • 6
    Cross-Platform
  • 6
    Fast prototyping
  • 6
    Mvt
  • 5
    Zero code burden to change databases
  • 5
    Easy to develop end to end AI Models
  • 5
    Easy Structure , useful inbuilt library
  • 4
    Great peformance
  • 4
    Python community
  • 4
    Map
  • 4
    Easy
  • 4
    Many libraries
  • 4
    Modular
  • 4
    Easy to use
  • 4
    Easy to change database manager
  • 3
    Just the right level of abstraction
  • 3
    Scaffold
  • 3
    Full-Text Search
  • 1
    Scalable
  • 1
    Node js
  • 0
    Rails
  • 0
    Fastapi
CONS OF DJANGO
  • 25
    Underpowered templating
  • 22
    Autoreload restarts whole server
  • 21
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 8
    Not nodejs
  • 7
    Admin
  • 7
    Configuration hell
  • 5
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Python
  • 3
    Not typed
  • 2
    InEffective Multithreading
  • 2
    Overwhelming folder structure

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

25.3K
9.7K
35
An open source web framework for building modern web apps and services with .NET
25.3K
9.7K
+ 1
35
PROS OF ASP.NET
  • 19
    Great mvc
  • 11
    Easy to learn
  • 5
    C#
CONS OF ASP.NET
  • 1
    C#
  • 1
    Entity framework is very slow
  • 1
    Not highly flexible for advance Developers

related ASP.NET posts

Greg Neumann
Indie, Solo, Developer · | 8 upvotes · 1M views

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
Shared insights
on
ASP.NETASP.NETPostgreSQLPostgreSQLLaravelLaravel

I am looking for a new framework to learn and achieve more efficient development. I come mainly from Laravel, which greatly simplifies development, but is somewhat slow for the volumes of data that I usually handle (although very stable) and it falls far behind in terms of simultaneous connections.

I'm looking for something that responds well to high concurrency, adapts well to server resources (cores) without the need to be concerned about consciously multi-threading or similar things, has a good ORM and friendly integration with PostgreSQL, request validation, And of course, it is scalable.

The main use would be for API development and behind the scenes processing of large volumes of data (50M on average, although this goes hand in hand with the database and server capacity)..

The last framework I would include but couldn't is ASP.NET MVC.

See more