Alternatives to Rust logo

Alternatives to Rust

C, Swift, Python, Go, and Haskell are the most popular alternatives and competitors to Rust.
2.2K
2.6K
+ 1
893

What is Rust and what are its top alternatives?

Rust is a systems programming language that combines strong compile-time correctness guarantees with fast performance. It improves upon the ideas of other systems languages like C++ by providing guaranteed memory safety (no crashes, no data races) and complete control over the lifecycle of memory.
Rust is a tool in the Languages category of a tech stack.
Rust is an open source tool with 52.7K GitHub stars and 7.6K GitHub forks. Here’s a link to Rust's open source repository on GitHub

Top Alternatives to Rust

  • C

    C

  • Swift

    Swift

    Writing code is interactive and fun, the syntax is concise yet expressive, and apps run lightning-fast. Swift is ready for your next iOS and OS X project — or for addition into your current app — because Swift code works side-by-side with Objective-C. ...

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

  • Go

    Go

    Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...

  • Haskell

    Haskell

    It is a general purpose language that can be used in any domain and use case, it is ideally suited for proprietary business logic and data analysis, fast prototyping and enhancing existing software environments with correct code, performance and scalability. ...

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

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

  • PHP

    PHP

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

Rust alternatives & related posts

C logo

C

5K
3.3K
228
One of the most widely used programming languages of all time
5K
3.3K
+ 1
228
PROS OF C
  • 62
    Performance
  • 45
    Low-level
  • 33
    Portability
  • 28
    Hardware level
  • 18
    Embedded apps
  • 12
    Pure
  • 9
    Performance of assembler
  • 7
    Ubiquity
  • 4
    Old
  • 4
    Great for embedded
  • 2
    No garbage collection to slow it down
  • 2
    Compiles quickly
  • 2
    OpenMP
CONS OF C
  • 5
    Low-level
  • 3
    No built in support for concurrency
  • 2
    Lack of type safety
  • 2
    No built in support for parallelism (e.g. map-reduce)

related C posts

Shared insights
on
GoGoCCPythonPythonRustRust
at

One important decision for delivering a platform independent solution with low memory footprint and minimal dependencies was the choice of the programming language. We considered a few from Python (there was already a reasonably large Python code base at Thumbtack), to Go (we were taking our first steps with it), and even Rust (too immature at the time).

We ended up writing it in C. It was easy to meet all requirements with only one external dependency for implementing the web server, clearly no challenges running it on any of the Linux distributions we were maintaining, and arguably the implementation with the smallest memory footprint given the choices above.

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

Why Uber developed H3, our open source grid system to make geospatial data visualization and exploration easier and more efficient:

We decided to create H3 to combine the benefits of a hexagonal global grid system with a hierarchical indexing system. A global grid system usually requires at least two things: a map projection and a grid laid on top of the map. For map projection, we chose to use gnomonic projections centered on icosahedron faces. This projects from Earth as a sphere to an icosahedron, a twenty-sided platonic solid. The H3 grid is constructed by laying out 122 base cells over the Earth, with ten cells per face. H3 supports sixteen resolutions: https://eng.uber.com/h3/

(GitHub Pages : https://uber.github.io/h3/#/ Written in C w/ bindings in Java & JavaScript )

See more
Swift logo

Swift

11.4K
7.9K
1.2K
An innovative new programming language for Cocoa and Cocoa Touch.
11.4K
7.9K
+ 1
1.2K
PROS OF SWIFT
  • 248
    Ios
  • 175
    Elegant
  • 123
    Not Objective-C
  • 105
    Backed by apple
  • 89
    Type inference
  • 58
    Generics
  • 51
    Playgrounds
  • 47
    Semicolon free
  • 37
    OSX
  • 34
    Tuples offer compound variables
  • 21
    Clean Syntax
  • 21
    Easy to learn
  • 20
    Open Source
  • 19
    Functional
  • 17
    Beautiful Code
  • 10
    Linux
  • 10
    Dynamic
  • 9
    Promotes safe, readable code
  • 8
    Protocol-oriented programming
  • 7
    Explicit optionals
  • 7
    No S-l-o-w JVM
  • 5
    Storyboard designer
  • 4
    Super addicting language, great people, open, elegant
  • 4
    Type safety
  • 4
    Optionals
  • 4
    Best UI concept
  • 3
    Feels like a better C++
  • 3
    Swift is faster than Objective-C
  • 3
    Faster and looks better
  • 2
    Easy to Maintain
  • 2
    Strong Type safety
  • 2
    Fail-safe
  • 2
    Its fun and damn fast
  • 2
    Highly Readable codes
  • 2
    Native
  • 2
    Protocol extensions
  • 2
    Powerful
  • 2
    Much more fun
  • 2
    Its friendly
  • 2
    Easy to learn and work
  • 1
    Protocol as type
  • 1
    Protocol oriented programming
  • 1
    Great for Multi-Threaded Programming
  • 1
    Objec
  • 1
    Type Safe
  • 1
    All Cons C# and Java Swift Already has
  • 1
    Free from Memory Leak
  • 1
    Swift is easier to understand for non-iOS developers.
  • 1
    Actually don't have to own a mac
  • 1
    Can interface with C easily
  • 1
    Esay
  • 1
    Numbers with underbar
  • 1
    MacOS
  • 1
    Optional chain
CONS OF SWIFT
  • 2
    Must own a mac
  • 2
    Memory leaks are not uncommon
  • 1
    Its classes compile to roughly 300 lines of assembly
  • 1
    Complicated process for exporting modules
  • 1
    Very irritatingly picky about things that’s
  • 1
    Is a lot more effort than lua to make simple functions
  • 0
    Overly complex options makes it easy to create bad code

related Swift posts

Shivam Bhargava
AVP - Business at VAYUZ Technologies Pvt. Ltd. · | 22 upvotes · 165.8K views

Hi Community! Trust everyone is keeping safe. I am exploring the idea of building a #Neobank (App) with end-to-end banking capabilities. In the process of exploring this space, I have come across multiple Apps (N26, Revolut, Monese, etc) and explored their stacks in detail. The confusion remains to be the Backend Tech to be used?

What would you go with considering all of the languages such as Node.js Java Rails Python are suggested by some person or the other. As a general trend, I have noticed the usage of Node with React on the front or Node with a combination of Kotlin and Swift. Please suggest what would be the right approach!

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

WordPress Magento PHP Java Swift JavaScript

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

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

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

Communication InAppChat Dating Matrimonial #messaging

See more
Python logo

Python

117.6K
91.8K
6.4K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
117.6K
91.8K
+ 1
6.4K
PROS OF PYTHON
  • 1.1K
    Great libraries
  • 922
    Readable code
  • 814
    Beautiful code
  • 763
    Rapid development
  • 668
    Large community
  • 414
    Open source
  • 375
    Elegant
  • 264
    Great community
  • 257
    Object oriented
  • 206
    Dynamic typing
  • 68
    Great standard library
  • 51
    Very fast
  • 47
    Functional programming
  • 33
    Scientific computing
  • 31
    Easy to learn
  • 29
    Great documentation
  • 25
    Matlab alternative
  • 22
    Productivity
  • 21
    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
    Free
  • 14
    Powerful
  • 13
    Powerfull language
  • 13
    Fast and simple
  • 12
    Scripting
  • 9
    Machine learning support
  • 9
    Explicit is better than implicit
  • 8
    Ease of development
  • 8
    Unlimited power
  • 7
    Import antigravity
  • 7
    Clear and easy and powerfull
  • 6
    Print "life is short, use python"
  • 6
    It's lean and fun to code
  • 5
    Great for tooling
  • 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
    Flat is better than nested
  • 4
    Readability counts
  • 3
    Multiple Inheritence
  • 3
    Complex is better than complicated
  • 3
    Lists, tuples, dictionaries
  • 3
    Plotting
  • 3
    Rapid Prototyping
  • 3
    Great for analytics
  • 3
    Socially engaged community
  • 3
    Beautiful is better than ugly
  • 3
    CG industry needs
  • 2
    No cruft
  • 2
    Easy to learn and use
  • 2
    List comprehensions
  • 2
    Generators
  • 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
  • 2
    Simple and easy to learn
  • 2
    Import this
  • 1
    Powerful language for AI
  • 1
    Because of Netflix
  • 1
    Pip install everything
  • 1
    Web scraping
  • 1
    Better outcome
  • 1
    Batteries included
  • 1
    Easy to setup and run smooth
  • 1
    It is Very easy , simple and will you be love programmi
  • 1
    Only one way to do it
  • 1
    A-to-Z
  • 1
    Many types of collections
  • 1
    Flexible and easy
  • 0
    Pro
  • 0
    Powerful
CONS OF PYTHON
  • 49
    Still divided between python 2 and python 3
  • 26
    Poor syntax for anonymous functions
  • 26
    Performance impact
  • 18
    GIL
  • 18
    Package management is a mess
  • 13
    Too imperative-oriented
  • 12
    Hard to understand
  • 10
    Dynamic typing
  • 8
    Very slow
  • 8
    Not everything is expression
  • 7
    Indentations matter a lot
  • 7
    Explicit self parameter in methods
  • 6
    Poor DSL capabilities
  • 6
    No anonymous functions
  • 6
    Requires C functions for dynamic modules
  • 5
    Hard to obfuscate
  • 5
    The "lisp style" whitespaces
  • 4
    The benevolent-dictator-for-life quit
  • 4
    Lack of Syntax Sugar leads to "the pyramid of doom"
  • 4
    Threading
  • 4
    Fake object-oriented programming
  • 4
    Incredibly slow
  • 3
    Not suitable for autocomplete
  • 3
    Official documentation is unclear.
  • 2
    Circular import
  • 1
    Training wheels (forced indentation)
  • 1
    Meta classes

related Python posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M 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.2M 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
Go logo

Go

11.4K
9.7K
3K
An open source programming language that makes it easy to build simple, reliable, and efficient software
11.4K
9.7K
+ 1
3K
PROS OF GO
  • 512
    High-performance
  • 375
    Simple, minimal syntax
  • 343
    Fun to write
  • 289
    Easy concurrency support via goroutines
  • 261
    Fast compilation times
  • 183
    Goroutines
  • 173
    Statically linked binaries that are simple to deploy
  • 144
    Simple compile build/run procedures
  • 129
    Backed by google
  • 125
    Great community
  • 46
    Garbage collection built-in
  • 40
    Built-in Testing
  • 36
    Excellent tools - gofmt, godoc etc
  • 33
    Elegant and concise like Python, fast like C
  • 28
    Awesome to Develop
  • 22
    Flexible interface system
  • 21
    Used for Docker
  • 21
    Great concurrency pattern
  • 18
    Deploy as executable
  • 17
    Open-source Integration
  • 14
    Fun to write and so many feature out of the box
  • 11
    Its Simple and Heavy duty
  • 11
    Easy to read
  • 10
    Powerful and simple
  • 9
    Go is God
  • 9
    Safe GOTOs
  • 9
    Easy to deploy
  • 7
    Hassle free deployment
  • 7
    Rich standard library
  • 7
    Concurrency
  • 7
    Best language for concurrency
  • 7
    Easy setup
  • 6
    Used by Giants of the industry
  • 6
    Simplicity, Concurrency, Performance
  • 6
    Clean code, high performance
  • 6
    High performance
  • 6
    Single binary avoids library dependency issues
  • 5
    Simple, powerful, and great performance
  • 5
    Cross compiling
  • 4
    Garbage Collection
  • 4
    Excellent tooling
  • 4
    Very sophisticated syntax
  • 4
    Gofmt
  • 4
    WYSIWYG
  • 3
    Kubernetes written on Go
  • 2
    Keep it simple and stupid
  • 1
    Widely used
  • 0
    No generics
  • 0
    Operator goto
CONS OF GO
  • 38
    You waste time in plumbing code catching errors
  • 23
    Verbose
  • 22
    Packages and their path dependencies are braindead
  • 15
    Dependency management when working on multiple projects
  • 12
    Google's documentations aren't beginer friendly
  • 10
    Automatic garbage collection overheads
  • 7
    Uncommon syntax
  • 6
    Type system is lacking (no generics, etc)
  • 2
    Collection framework is lacking (list, set, map)

related Go posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M 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.2M 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
Haskell logo

Haskell

851
880
471
An advanced purely-functional programming language
851
880
+ 1
471
PROS OF HASKELL
  • 82
    Purely-functional programming
  • 63
    Statically typed
  • 56
    Type-safe
  • 38
    Open source
  • 37
    Great community
  • 29
    Composable
  • 28
    Built-in concurrency
  • 27
    Built-in parallelism
  • 21
    Referentially transparent
  • 18
    Generics
  • 13
    Intellectual satisfaction
  • 13
    Type inference
  • 10
    If it compiles, it's correct
  • 7
    Flexible
  • 6
    Monads
  • 4
    Great type system
  • 3
    Proposition testing with QuickCheck
  • 2
    Best in class thinking tool
  • 2
    Great maintainability of the code
  • 2
    Fun
  • 2
    One of the most powerful languages *(see blub paradox)*
  • 2
    Highly expressive, type-safe, fast development time
  • 1
    Type classes
  • 1
    Better type-safe than sorry
  • 1
    Pattern matching and completeness checking
  • 1
    Kind system
  • 1
    Purely-functional Programming
  • 1
    Reliable
  • 0
    Orthogonality
  • 0
    Predictable
CONS OF HASKELL
  • 6
    Too much distraction in language extensions
  • 5
    Error messages can be very confusing
  • 3
    No best practices
  • 3
    No good ABI
  • 3
    Libraries have poor documentation
  • 2
    Sometimes performance is unpredictable
  • 2
    Poor packaging for apps written in it for Linux distros
  • 1
    Slow compilation

related Haskell posts

Vadim Bakaev
Shared insights
on
HaskellHaskellScalaScala

Why I am using Haskell in my free time?

I have 3 reasons for it. I am looking for:

Fun.

Improve functional programming skill.

Improve problem-solving skill.

Laziness and mathematical abstractions behind Haskell makes it a wonderful language.

It is Pure functional, it helps me to write better Scala code.

Highly expressive language gives elegant ways to solve coding puzzle.

See more
Java logo

Java

74.6K
53.3K
3.5K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
74.6K
53.3K
+ 1
3.5K
PROS OF JAVA
  • 572
    Great libraries
  • 433
    Widely used
  • 396
    Excellent tooling
  • 378
    Huge amount of documentation available
  • 328
    Large pool of developers available
  • 197
    Open source
  • 192
    Excellent performance
  • 150
    Great development
  • 143
    Used for android
  • 142
    Vast array of 3rd party libraries
  • 54
    Compiled Language
  • 46
    Used for Web
  • 42
    Managed memory
  • 42
    Native threads
  • 40
    High Performance
  • 35
    Statically typed
  • 31
    Easy to read
  • 29
    Great Community
  • 25
    Reliable platform
  • 23
    JVM compatibility
  • 22
    Sturdy garbage collection
  • 19
    Cross Platform Enterprise Integration
  • 18
    Universal platform
  • 16
    Great Support
  • 16
    Good amount of APIs
  • 11
    Lots of boilerplate
  • 10
    Great ecosystem
  • 10
    Backward compatible
  • 9
    Everywhere
  • 7
    Excellent SDK - JDK
  • 6
    Mature language thus stable systems
  • 5
    Better than Ruby
  • 5
    Portability
  • 5
    Cross-platform
  • 5
    Static typing
  • 5
    Clojure
  • 5
    It's Java
  • 4
    Old tech
  • 4
    Vast Collections Library
  • 3
    Most developers favorite
  • 3
    Stable platform, which many new languages depend on
  • 3
    Long term language
  • 3
    Great Structure
  • 3
    Best martial for design
  • 3
    Used for Android development
  • 2
    Testable
  • 1
    Javadoc
CONS OF JAVA
  • 29
    Verbosity
  • 23
    NullpointerException
  • 15
    Overcomplexity is praised in community culture
  • 13
    Nightmare to Write
  • 10
    Boiler plate code
  • 8
    Classpath hell prior to Java 9
  • 6
    No REPL
  • 4
    No property
  • 2
    Code are too long
  • 2
    There is not optional parameter
  • 2
    Floating-point errors
  • 1
    Terrbible compared to Python/Batch Perormence
  • 1
    Java's too statically, stronglly, and strictly typed
  • 1
    Non-intuitive generic implementation
  • 1
    Returning Wildcard Types

related Java posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M 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 · 816.6K 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
JavaScript logo

JavaScript

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

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 · | 37 upvotes · 3.5M 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
PHP logo

PHP

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

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

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

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

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