Alternatives to Swift logo

Alternatives to Swift

Objective-C, React Native, Kotlin, Golang, and Java are the most popular alternatives and competitors to Swift.
20.2K
13.3K
+ 1
1.3K

What is Swift and what are its top alternatives?

Swift is a powerful and intuitive programming language developed by Apple for iOS, macOS, watchOS, and tvOS app development. It combines modern language features with a simple and concise syntax, making it easier to write and maintain code. Key features of Swift include type inference, optionals, generics, closures, and protocols. However, Swift is limited by its compatibility with Apple platforms only, which restricts its usage for cross-platform development and limits its reach to a broader audience.

  1. Kotlin: Kotlin is a modern, expressive, and statically typed programming language developed by JetBrains. It is fully interoperable with Java, making it a popular choice for Android app development. Key features of Kotlin include null safety, extension functions, coroutines, and data classes. Pros of Kotlin compared to Swift include its interoperability with Java, strong support for functional programming, and wide adoption in the Android community. However, Kotlin is not natively supported by Apple platforms like Swift.
  2. React Native: React Native is a JavaScript framework developed by Facebook for building cross-platform mobile apps. It allows developers to write code in JavaScript and compile it into native code for iOS and Android. Key features of React Native include hot reloading, a large and active community, and support for third-party plugins. Pros of React Native compared to Swift include faster development cycles, code reusability between platforms, and a lower learning curve for JavaScript developers. However, React Native may not offer the same performance as native app development with Swift.
  3. Flutter: Flutter is an open-source UI toolkit developed by Google for building natively compiled applications for mobile, web, and desktop from a single codebase. It uses the Dart programming language and provides a rich set of pre-built widgets for designing user interfaces. Key features of Flutter include hot reload, customizable widgets, and high performance. Pros of Flutter compared to Swift include rapid development, support for multiple platforms, and a reactive programming model. However, Flutter may require developers to learn Dart, which could be a barrier for those familiar with Swift.
  4. Java: Java is a popular, high-level programming language known for its portability and performance. It is widely used for developing enterprise applications, web applications, and Android apps. Key features of Java include platform independence, automatic memory management, multi-threading support, and a large standard library. Pros of Java compared to Swift include a vast ecosystem of libraries and tools, strong community support, and cross-platform compatibility. However, Java may have a steeper learning curve for beginners coming from Swift.
  5. C#: C# is a versatile and object-oriented programming language developed by Microsoft for building Windows applications, web services, and mobile apps with Xamarin. It offers features such as type safety, automatic garbage collection, LINQ (Language Integrated Query), and async/await for asynchronous programming. Pros of C# compared to Swift include seamless integration with the .NET framework, strong tooling support in Visual Studio, and cross-platform development with Xamarin. However, C# is primarily targeted towards Windows development and may have less community support for mobile app development than Swift.
  6. Python: Python is a high-level, interpreted programming language known for its simplicity and readability. It is widely used for web development, data analysis, machine learning, and automation tasks. Key features of Python include dynamic typing, extensive standard library, easy syntax, and support for multiple programming paradigms. Pros of Python compared to Swift include its versatility for a wide range of applications, strong community support, and extensive third-party libraries. However, Python may not offer the same performance as Swift for mobile app development.
  7. Rust: Rust is a systems programming language developed by Mozilla, known for its focus on safety, speed, and concurrency. It is designed to prevent memory errors and ensure thread safety through a strict ownership system and borrow checker. Key features of Rust include zero-cost abstractions, pattern matching, fearless concurrency, and extensive compiler checks. Pros of Rust compared to Swift include its emphasis on performance and safety, support for low-level programming, and strong community backing. However, Rust may have a steeper learning curve for developers transitioning from Swift.
  8. Go: Go, also known as Golang, is a statically typed programming language developed by Google, designed for concurrency and scalability in modern applications. It offers features such as goroutines for lightweight threading, a garbage collector, strong standard library, and efficient compilation speed. Pros of Go compared to Swift include its simplicity, fast compilation times, built-in support for concurrency, and easy deployment. However, Go may not offer the same level of support for mobile app development as Swift.
  9. JavaScript: JavaScript is a widely used scripting language for web development, supported by all modern web browsers. It is known for its dynamic typing, prototypal inheritance, asynchronous programming model, and high flexibility. Pros of JavaScript compared to Swift include its ubiquity on the web, extensive libraries and frameworks such as React and Angular, and cross-platform compatibility. However, JavaScript may have performance limitations compared to Swift for high-performance mobile applications.
  10. Ruby: Ruby is a dynamic, object-oriented programming language known for its simplicity and productivity. It is commonly used for web development, automation, and scripting tasks. Key features of Ruby include its elegant syntax, metaprogramming capabilities, rich ecosystem of gems, and focus on developer happiness. Pros of Ruby compared to Swift include rapid prototyping, expressiveness, strong community support, and a focus on developer joy. However, Ruby may not offer the same level of performance optimization as Swift for complex mobile applications.

Top Alternatives to Swift

  • Objective-C
    Objective-C

    Objective-C is a superset of the C programming language and provides object-oriented capabilities and a dynamic runtime. Objective-C inherits the syntax, primitive types, and flow control statements of C and adds syntax for defining classes and methods. It also adds language-level support for object graph management and object literals while providing dynamic typing and binding, deferring many responsibilities until runtime. ...

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • Kotlin
    Kotlin

    Kotlin is a statically typed programming language for the JVM, Android and the browser, 100% interoperable with Java ...

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

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

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

  • Rust
    Rust

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

  • Xcode
    Xcode

    The Xcode IDE is at the center of the Apple development experience. Tightly integrated with the Cocoa and Cocoa Touch frameworks, Xcode is an incredibly productive environment for building amazing apps for Mac, iPhone, and iPad. ...

Swift alternatives & related posts

Objective-C logo

Objective-C

12.6K
6.4K
490
The primary programming language you use when writing software for OS X and iOS
12.6K
6.4K
+ 1
490
PROS OF OBJECTIVE-C
  • 212
    Ios
  • 115
    Xcode
  • 62
    Backed by apple
  • 47
    Osx
  • 40
    Interface builder
  • 10
    Good old fashioned ooe with a modern twist
  • 2
    Goober, please
  • 1
    Object-oriented
  • 1
    Handles well null values (no NullPointerExceptions)
CONS OF OBJECTIVE-C
  • 1
    UNREADABLE

related Objective-C posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 13 upvotes · 1.6M 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
Jesus Dario Rivera Rubio
Telecomm Engineering at Netbeast · | 10 upvotes · 1.2M views

We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

See more
React Native logo

React Native

33.4K
28.9K
1.2K
A framework for building native apps with React
33.4K
28.9K
+ 1
1.2K
PROS OF REACT NATIVE
  • 214
    Learn once write everywhere
  • 173
    Cross platform
  • 168
    Javascript
  • 122
    Native ios components
  • 69
    Built by facebook
  • 65
    Easy to learn
  • 45
    Bridges me into ios development
  • 39
    No compile
  • 39
    It's just react
  • 36
    Declarative
  • 22
    Fast
  • 13
    Virtual Dom
  • 12
    Insanely fast develop / test cycle
  • 12
    Livereload
  • 11
    Great community
  • 9
    It is free and open source
  • 9
    Native android components
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 7
    Highly customizable
  • 7
    Scalable
  • 6
    Awesome
  • 6
    Everything component
  • 6
    Great errors
  • 6
    Win win solution of hybrid app
  • 5
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    Awesome, easy starting from scratch
  • 4
    OTA update
  • 3
    As good as Native without any performance concerns
  • 3
    Easy to use
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Web development meets Mobile development
  • 1
    Ngon
CONS OF REACT NATIVE
  • 23
    Javascript
  • 19
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Slow
  • 2
    Generate large apk even for a simple app
  • 2
    Some compenents not truly native

related React Native posts

Collins Ogbuzuru
Front-end dev at Evolve credit · | 33 upvotes · 217.1K views

Your tech stack is solid for building a real-time messaging project.

React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

See more
Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 4.2M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Kotlin logo

Kotlin

15.2K
11.7K
647
Statically typed Programming Language targeting JVM and JavaScript
15.2K
11.7K
+ 1
647
PROS OF KOTLIN
  • 73
    Interoperable with Java
  • 55
    Functional Programming support
  • 50
    Null Safety
  • 46
    Official Android support
  • 44
    Backed by JetBrains
  • 37
    Concise
  • 36
    Modern Multiplatform Applications
  • 28
    Expressive Syntax
  • 27
    Target to JVM
  • 26
    Coroutines
  • 24
    Open Source
  • 19
    Statically Typed
  • 19
    Practical elegance
  • 17
    Android support
  • 17
    Type Inference
  • 14
    Readable code
  • 13
    Powerful as Scala, simple as Python, plus coroutines <3
  • 12
    Better Java
  • 10
    Pragmatic
  • 9
    Lambda
  • 8
    Better language for android
  • 8
    Expressive DSLs
  • 8
    Target to JavaScript
  • 6
    Used for Android
  • 6
    Less boilerplate code
  • 5
    Fast Programming language
  • 5
    Less code
  • 4
    Native
  • 4
    Less boiler plate code
  • 4
    Friendly community
  • 4
    Functional Programming Language
  • 3
    Spring
  • 3
    Official Google Support
  • 2
    Latest version of Java
  • 1
    Well-compromised featured Java alternative
CONS OF KOTLIN
  • 7
    Java interop makes users write Java in Kotlin
  • 4
    Frequent use of {} keys
  • 2
    Hard to make teams adopt the Kotlin style
  • 2
    Nonullpointer Exception
  • 1
    Friendly community
  • 1
    Slow compiler
  • 1
    No boiler plate code

related Kotlin posts

Shivam Bhargava
AVP - Business at VAYUZ Technologies Pvt. Ltd. · | 22 upvotes · 856.7K 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
Jakub Olan
Node.js Software Engineer · | 17 upvotes · 783.8K views

In our company we have think a lot about languages that we're willing to use, there we have considering Java, Python and C++ . All of there languages are old and well developed at fact but that's not ideology of araclx. We've choose a edge technologies such as Node.js , Rust , Kotlin and Go as our programming languages which is some kind of fun. Node.js is one of biggest trends of 2019, same for Go. We want to grow in our company with growth of languages we have choose, and probably when we would choose Java that would be almost impossible because larger languages move on today's market slower, and cannot have big changes.

See more
Golang logo

Golang

22.4K
13.8K
3.3K
An open source programming language that makes it easy to build simple, reliable, and efficient software
22.4K
13.8K
+ 1
3.3K
PROS OF GOLANG
  • 549
    High-performance
  • 395
    Simple, minimal syntax
  • 363
    Fun to write
  • 302
    Easy concurrency support via goroutines
  • 273
    Fast compilation times
  • 194
    Goroutines
  • 181
    Statically linked binaries that are simple to deploy
  • 151
    Simple compile build/run procedures
  • 137
    Great community
  • 136
    Backed by google
  • 53
    Garbage collection built-in
  • 46
    Built-in Testing
  • 44
    Excellent tools - gofmt, godoc etc
  • 39
    Elegant and concise like Python, fast like C
  • 37
    Awesome to Develop
  • 26
    Used for Docker
  • 26
    Flexible interface system
  • 25
    Great concurrency pattern
  • 24
    Deploy as executable
  • 21
    Open-source Integration
  • 19
    Easy to read
  • 17
    Fun to write and so many feature out of the box
  • 16
    Go is God
  • 14
    Its Simple and Heavy duty
  • 14
    Concurrency
  • 14
    Powerful and simple
  • 14
    Easy to deploy
  • 13
    Best language for concurrency
  • 11
    Rich standard library
  • 11
    Safe GOTOs
  • 10
    Easy setup
  • 10
    Clean code, high performance
  • 10
    High performance
  • 9
    Simplicity, Concurrency, Performance
  • 8
    Cross compiling
  • 8
    Hassle free deployment
  • 8
    Single binary avoids library dependency issues
  • 7
    Gofmt
  • 7
    Simple, powerful, and great performance
  • 7
    Used by Giants of the industry
  • 6
    Garbage Collection
  • 5
    WYSIWYG
  • 5
    Very sophisticated syntax
  • 5
    Excellent tooling
  • 4
    Kubernetes written on Go
  • 4
    Keep it simple and stupid
  • 4
    Widely used
  • 2
    No generics
  • 1
    Looks not fancy, but promoting pragmatic idioms
  • 1
    Operator goto
CONS OF GOLANG
  • 42
    You waste time in plumbing code catching errors
  • 25
    Verbose
  • 23
    Packages and their path dependencies are braindead
  • 16
    Google's documentations aren't beginer friendly
  • 15
    Dependency management when working on multiple projects
  • 10
    Automatic garbage collection overheads
  • 8
    Uncommon syntax
  • 7
    Type system is lacking (no generics, etc)
  • 5
    Collection framework is lacking (list, set, map)
  • 3
    Best programming language
  • 1
    A failed experiment to combine c and python

related Golang posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.9M 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 · 4.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
Java logo

Java

134.5K
101.8K
3.7K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
134.5K
101.8K
+ 1
3.7K
PROS OF JAVA
  • 601
    Great libraries
  • 445
    Widely used
  • 400
    Excellent tooling
  • 395
    Huge amount of documentation available
  • 334
    Large pool of developers available
  • 208
    Open source
  • 203
    Excellent performance
  • 158
    Great development
  • 150
    Used for android
  • 148
    Vast array of 3rd party libraries
  • 60
    Compiled Language
  • 52
    Used for Web
  • 46
    High Performance
  • 46
    Managed memory
  • 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
    Lots of boilerplate
  • 11
    Backward compatible
  • 10
    Everywhere
  • 9
    Excellent SDK - JDK
  • 7
    Static typing
  • 7
    Cross-platform
  • 7
    It's Java
  • 6
    Mature language thus stable systems
  • 6
    Better than Ruby
  • 6
    Long term language
  • 6
    Portability
  • 5
    Clojure
  • 5
    Used for Android development
  • 5
    Vast Collections Library
  • 4
    Best martial for design
  • 4
    Most developers favorite
  • 4
    Old tech
  • 3
    Javadoc
  • 3
    History
  • 3
    Testable
  • 3
    Great Structure
  • 3
    Stable platform, which many new languages depend on
  • 2
    Type Safe
  • 2
    Faster than python
  • 0
    Job
CONS OF JAVA
  • 33
    Verbosity
  • 27
    NullpointerException
  • 17
    Nightmare to Write
  • 16
    Overcomplexity is praised in community culture
  • 12
    Boiler plate code
  • 8
    Classpath hell prior to Java 9
  • 6
    No REPL
  • 4
    No property
  • 3
    Code are too long
  • 2
    Non-intuitive generic implementation
  • 2
    There is not optional parameter
  • 2
    Floating-point errors
  • 1
    Java's too statically, stronglly, and strictly typed
  • 1
    Returning Wildcard Types
  • 1
    Terrbible compared to Python/Batch Perormence

related Java posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 11.9M 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 · 4M 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
Python logo

Python

243.6K
198.7K
6.9K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
243.6K
198.7K
+ 1
6.9K
PROS OF PYTHON
  • 1.2K
    Great libraries
  • 961
    Readable code
  • 847
    Beautiful code
  • 787
    Rapid development
  • 689
    Large community
  • 437
    Open source
  • 393
    Elegant
  • 282
    Great community
  • 272
    Object oriented
  • 220
    Dynamic typing
  • 77
    Great standard library
  • 60
    Very fast
  • 55
    Functional programming
  • 49
    Easy to learn
  • 45
    Scientific computing
  • 35
    Great documentation
  • 29
    Productivity
  • 28
    Easy to read
  • 28
    Matlab alternative
  • 24
    Simple is better than complex
  • 20
    It's the way I think
  • 19
    Imperative
  • 18
    Free
  • 18
    Very programmer and non-programmer friendly
  • 17
    Powerfull language
  • 17
    Machine learning support
  • 16
    Fast and simple
  • 14
    Scripting
  • 12
    Explicit is better than implicit
  • 11
    Ease of development
  • 10
    Clear and easy and powerfull
  • 9
    Unlimited power
  • 8
    It's lean and fun to code
  • 8
    Import antigravity
  • 7
    Print "life is short, use python"
  • 7
    Python has great libraries for data processing
  • 6
    Although practicality beats purity
  • 6
    Now is better than never
  • 6
    Great for tooling
  • 6
    Readability counts
  • 6
    Rapid Prototyping
  • 6
    I love snakes
  • 6
    Flat is better than nested
  • 6
    Fast coding and good for competitions
  • 6
    There should be one-- and preferably only one --obvious
  • 6
    High Documented language
  • 5
    Great for analytics
  • 5
    Lists, tuples, dictionaries
  • 4
    Easy to learn and use
  • 4
    Simple and easy to learn
  • 4
    Easy to setup and run smooth
  • 4
    Web scraping
  • 4
    CG industry needs
  • 4
    Socially engaged community
  • 4
    Complex is better than complicated
  • 4
    Multiple Inheritence
  • 4
    Beautiful is better than ugly
  • 4
    Plotting
  • 3
    Many types of collections
  • 3
    Flexible and easy
  • 3
    It is Very easy , simple and will you be love programmi
  • 3
    If the implementation is hard to explain, it's a bad id
  • 3
    Special cases aren't special enough to break the rules
  • 3
    Pip install everything
  • 3
    List comprehensions
  • 3
    No cruft
  • 3
    Generators
  • 3
    Import this
  • 3
    If the implementation is easy to explain, it may be a g
  • 2
    Can understand easily who are new to programming
  • 2
    Batteries included
  • 2
    Securit
  • 2
    Good for hacking
  • 2
    Better outcome
  • 2
    Only one way to do it
  • 2
    Because of Netflix
  • 2
    A-to-Z
  • 2
    Should START with this but not STICK with This
  • 2
    Powerful language for AI
  • 1
    Automation friendly
  • 1
    Sexy af
  • 1
    Slow
  • 1
    Procedural programming
  • 0
    Ni
  • 0
    Powerful
  • 0
    Keep it simple
CONS OF PYTHON
  • 53
    Still divided between python 2 and python 3
  • 28
    Performance impact
  • 26
    Poor syntax for anonymous functions
  • 22
    GIL
  • 19
    Package management is a mess
  • 14
    Too imperative-oriented
  • 12
    Hard to understand
  • 12
    Dynamic typing
  • 12
    Very slow
  • 8
    Indentations matter a lot
  • 8
    Not everything is expression
  • 7
    Incredibly slow
  • 7
    Explicit self parameter in methods
  • 6
    Requires C functions for dynamic modules
  • 6
    Poor DSL capabilities
  • 6
    No anonymous functions
  • 5
    Fake object-oriented programming
  • 5
    Threading
  • 5
    The "lisp style" whitespaces
  • 5
    Official documentation is unclear.
  • 5
    Hard to obfuscate
  • 5
    Circular import
  • 4
    Lack of Syntax Sugar leads to "the pyramid of doom"
  • 4
    The benevolent-dictator-for-life quit
  • 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 · | 44 upvotes · 11.9M 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 · 4.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
Rust logo

Rust

5.8K
4.9K
1.2K
A safe, concurrent, practical language
5.8K
4.9K
+ 1
1.2K
PROS OF RUST
  • 145
    Guaranteed memory safety
  • 132
    Fast
  • 88
    Open source
  • 75
    Minimal runtime
  • 71
    Pattern matching
  • 63
    Type inference
  • 57
    Concurrent
  • 56
    Algebraic data types
  • 47
    Efficient C bindings
  • 43
    Practical
  • 37
    Best advances in languages in 20 years
  • 32
    Safe, fast, easy + friendly community
  • 30
    Fix for C/C++
  • 25
    Stablity
  • 24
    Zero-cost abstractions
  • 23
    Closures
  • 20
    Extensive compiler checks
  • 20
    Great community
  • 18
    Async/await
  • 18
    No NULL type
  • 15
    Completely cross platform: Windows, Linux, Android
  • 15
    No Garbage Collection
  • 14
    High-performance
  • 14
    Great documentations
  • 12
    Super fast
  • 12
    High performance
  • 12
    Generics
  • 11
    Guaranteed thread data race safety
  • 11
    Safety no runtime crashes
  • 11
    Macros
  • 11
    Fearless concurrency
  • 10
    Compiler can generate Webassembly
  • 10
    Helpful compiler
  • 9
    RLS provides great IDE support
  • 9
    Prevents data races
  • 9
    Easy Deployment
  • 8
    Painless dependency management
  • 8
    Real multithreading
  • 7
    Good package management
  • 5
    Support on Other Languages
CONS OF RUST
  • 27
    Hard to learn
  • 24
    Ownership learning curve
  • 12
    Unfriendly, verbose syntax
  • 4
    High size of builded executable
  • 4
    Many type operations make it difficult to follow
  • 4
    No jobs
  • 4
    Variable shadowing
  • 1
    Use it only for timeoass not in production

related Rust posts

Caue Carvalho
Shared insights
on
RustRustGolangGolangPythonPythonRubyRubyC#C#

Hello!

I'm a developer for over 9 years, and most of this time I've been working with C# and it is paying my bills until nowadays. But I'm seeking to learn other languages and expand the possibilities for the next years.

Now the question... I know Ruby is far from dead but is it still worth investing time in learning it? Or would be better to take Python, Golang, or even Rust? Or maybe another language.

Thanks in advance.

See more
James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 318.4K views
Shared insights
on
PythonPythonRustRust
at

Sentry's event processing pipeline, which is responsible for handling all of the ingested event data that makes it through to our offline task processing, is written primarily in Python.

For particularly intense code paths, like our source map processing pipeline, we have begun re-writing those bits in Rust. Rust’s lack of garbage collection makes it a particularly convenient language for embedding in Python. It allows us to easily build a Python extension where all memory is managed from the Python side (if the Python wrapper gets collected by the Python GC we clean up the Rust object as well).

See more
Xcode logo

Xcode

19K
14.4K
213
The complete toolset for building great apps
19K
14.4K
+ 1
213
PROS OF XCODE
  • 130
    IOS Development
  • 33
    Personal assistant on steroids
  • 29
    Easy setup
  • 17
    Excellent integration with Clang
  • 3
    Beautiful
  • 1
    Built-in everything
CONS OF XCODE
  • 6
    Massively bloated and complicated for smaller projects
  • 3
    Horrible auto completiting and text editing
  • 1
    Slow startup
  • 1
    Very slow emulator

related Xcode posts

Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 445.4K views

As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.

Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.

Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.

After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.

After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.

Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.

See more
Sezgi Ulucam
Developer Advocate at Hasura · | 7 upvotes · 956.8K views

I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

See more