Alternatives to Rust logo

Alternatives to Rust

C lang, Swift, Python, Golang, and Haskell are the most popular alternatives and competitors to Rust.
3.4K
3.8K
+ 1
1.2K

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 68.2K GitHub stars and 9.4K GitHub forks. Here’s a link to Rust's open source repository on GitHub

Top Alternatives to Rust

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

  • Golang
    Golang

    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 lang logo

C lang

6.5K
4.1K
244
One of the most widely used programming languages of all time
6.5K
4.1K
+ 1
244
PROS OF C LANG
  • 67
    Performance
  • 48
    Low-level
  • 35
    Portability
  • 28
    Hardware level
  • 19
    Embedded apps
  • 13
    Pure
  • 9
    Performance of assembler
  • 8
    Ubiquity
  • 5
    Great for embedded
  • 4
    Old
  • 3
    Compiles quickly
  • 2
    No garbage collection to slow it down
  • 2
    OpenMP
  • 1
    Gnu/linux interoperable
CONS OF C LANG
  • 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 lang posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 16 upvotes · 1.2M 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

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
Swift logo

Swift

14.9K
10.9K
1.3K
An innovative new programming language for Cocoa and Cocoa Touch.
14.9K
10.9K
+ 1
1.3K
PROS OF SWIFT
  • 255
    Ios
  • 178
    Elegant
  • 125
    Not Objective-C
  • 106
    Backed by apple
  • 92
    Type inference
  • 60
    Generics
  • 54
    Playgrounds
  • 49
    Semicolon free
  • 39
    OSX
  • 35
    Tuples offer compound variables
  • 24
    Easy to learn
  • 23
    Clean Syntax
  • 21
    Open Source
  • 20
    Functional
  • 19
    Beautiful Code
  • 11
    Dynamic
  • 11
    Linux
  • 10
    Protocol-oriented programming
  • 10
    Promotes safe, readable code
  • 8
    No S-l-o-w JVM
  • 8
    Explicit optionals
  • 7
    Storyboard designer
  • 5
    Type safety
  • 5
    Optionals
  • 5
    Best UI concept
  • 5
    Super addicting language, great people, open, elegant
  • 4
    Its friendly
  • 4
    Swift is faster than Objective-C
  • 4
    Feels like a better C++
  • 4
    Highly Readable codes
  • 4
    Fail-safe
  • 4
    Powerful
  • 4
    Faster and looks better
  • 3
    Much more fun
  • 3
    Easy to learn and work
  • 3
    Protocol extensions
  • 3
    Native
  • 3
    Its fun and damn fast
  • 3
    Strong Type safety
  • 3
    Easy to Maintain
  • 2
    Protocol oriented programming
  • 2
    Esay
  • 2
    MacOS
  • 2
    Type Safe
  • 2
    All Cons C# and Java Swift Already has
  • 2
    Protocol as type
  • 1
    Objec
  • 1
    Can interface with C easily
  • 1
    Numbers with underbar
  • 1
    Optional chain
  • 1
    Runs Python 8 times faster
  • 1
    Actually don't have to own a mac
  • 1
    Free from Memory Leak
  • 1
    Swift is easier to understand for non-iOS developers.
  • 1
    Great for Multi-Threaded Programming
CONS OF SWIFT
  • 5
    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 · 366K 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
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 13 upvotes · 1.2M views

Excerpts from how we developed (and subsequently open sourced) Uber's cross-platform mobile architecture framework, RIBs , going from Objective-C to Swift in the process for iOS: https://github.com/uber/RIBs

Uber’s new application architecture (RIBs) extensively uses protocols to keep its various components decoupled and testable. We used this architecture for the first time in our new rider application and moved our primary language from Objective-C to Swift. Since Swift is a very static language, unit testing became problematic. Dynamic languages have good frameworks to build test mocks, stubs, or stand-ins by dynamically creating or modifying existing concrete classes.

Needless to say, we were not very excited about the additional complexity of manually writing and maintaining mock implementations for each of our thousands of protocols.

The information required to generate mock classes already exists in the Swift protocol. For Uber’s use case, we set out to create tooling that would let engineers automatically generate test mocks for any protocol they wanted by simply annotating them.

The iOS codebase for our rider application alone incorporates around 1,500 of these generated mocks. Without our code generation tool, all of these would have to be written and maintained by hand, which would have made testing much more time-intensive. Auto-generated mocks have contributed a lot to the unit test coverage that we have today.

We built these code generation tools ourselves for a number of reasons, including that there weren’t many open source tools available at the time we started our effort. Today, there are some great open source tools to generate resource accessors, like SwiftGen. And Sourcery can help you with generic code generation needs:

https://eng.uber.com/code-generation/ https://eng.uber.com/driver-app-ribs-architecture/

(GitHub : https://github.com/uber/RIBs )

See more
Python logo

Python

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

related Python posts

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

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

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

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

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

#FrameworksFullStack #Languages

See more
Golang logo

Golang

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

related Golang posts

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

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

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

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

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

#FrameworksFullStack #Languages

See more
Haskell logo

Haskell

1.1K
1.1K
496
An advanced purely-functional programming language
1.1K
1.1K
+ 1
496
PROS OF HASKELL
  • 87
    Purely-functional programming
  • 65
    Statically typed
  • 58
    Type-safe
  • 38
    Great community
  • 38
    Open source
  • 29
    Composable
  • 29
    Built-in concurrency
  • 28
    Built-in parallelism
  • 22
    Referentially transparent
  • 19
    Generics
  • 14
    Intellectual satisfaction
  • 13
    Type inference
  • 11
    If it compiles, it's correct
  • 7
    Flexible
  • 7
    Monads
  • 4
    Great type system
  • 4
    Proposition testing with QuickCheck
  • 3
    One of the most powerful languages *(see blub paradox)*
  • 2
    Great maintainability of the code
  • 2
    Fun
  • 2
    Purely-functional Programming
  • 2
    Kind system
  • 2
    Reliable
  • 2
    Highly expressive, type-safe, fast development time
  • 2
    Type classes
  • 2
    Better type-safe than sorry
  • 2
    Pattern matching and completeness checking
  • 2
    Best in class thinking tool
  • 0
    Orthogonality
  • 0
    Predictable
CONS OF HASKELL
  • 7
    Too much distraction in language extensions
  • 7
    Error messages can be very confusing
  • 4
    Libraries have poor documentation
  • 3
    No best practices
  • 3
    No good ABI
  • 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

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

related Java posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 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 · | 28 upvotes · 1.5M 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

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

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

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2M 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 · | 26 upvotes · 2.6M 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