Alternatives to Kotlin logo

Alternatives to Kotlin

Scala, Swift, Java, Groovy, and Python are the most popular alternatives and competitors to Kotlin.
15.3K
647

What is Kotlin and what are its top alternatives?

Kotlin is a statically typed programming language for the JVM, Android and the browser, 100% interoperable with Java
Kotlin is a tool in the Languages category of a tech stack.
Kotlin is an open source tool with 49.4K GitHub stars and 5.8K GitHub forks. Here’s a link to Kotlin's open source repository on GitHub

Top Alternatives to Kotlin

  • Scala
    Scala

    Scala is an acronym for “Scalable Language”. This means that Scala grows with you. You can play with it by typing one-line expressions and observing the results. But you can also rely on it for large mission critical systems, as many companies, including Twitter, LinkedIn, or Intel do. To some, Scala feels like a scripting language. Its syntax is concise and low ceremony; its types get out of the way because the compiler can infer them. ...

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

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

  • Groovy
    Groovy

    It is a powerful multi-faceted programming language for the JVM platform. It supports a spectrum of programming styles incorporating features from dynamic languages such as optional and duck typing, but also static compilation and static type checking at levels similar to or greater than Java through its extensible static type checker. It aims to greatly increase developer productivity with many powerful features but also a concise, familiar and easy to learn syntax. ...

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

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

  • Flutter
    Flutter

    Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android. ...

Kotlin alternatives & related posts

Scala logo

Scala

10.9K
7.7K
1.5K
A pure-bred object-oriented language that runs on the JVM
10.9K
7.7K
+ 1
1.5K
PROS OF SCALA
  • 188
    Static typing
  • 178
    Pattern-matching
  • 175
    Jvm
  • 172
    Scala is fun
  • 138
    Types
  • 95
    Concurrency
  • 88
    Actor library
  • 86
    Solve functional problems
  • 81
    Open source
  • 80
    Solve concurrency in a safer way
  • 44
    Functional
  • 24
    Fast
  • 23
    Generics
  • 18
    It makes me a better engineer
  • 17
    Syntactic sugar
  • 13
    Scalable
  • 10
    First-class functions
  • 10
    Type safety
  • 9
    Interactive REPL
  • 8
    Expressive
  • 7
    SBT
  • 6
    Case classes
  • 6
    Implicit parameters
  • 4
    Rapid and Safe Development using Functional Programming
  • 4
    JVM, OOP and Functional programming, and static typing
  • 4
    Object-oriented
  • 4
    Used by Twitter
  • 3
    Functional Proframming
  • 2
    Spark
  • 2
    Beautiful Code
  • 2
    Safety
  • 2
    Growing Community
  • 1
    DSL
  • 1
    Rich Static Types System and great Concurrency support
  • 1
    Naturally enforce high code quality
  • 1
    Akka Streams
  • 1
    Akka
  • 1
    Reactive Streams
  • 1
    Easy embedded DSLs
  • 1
    Mill build tool
  • 0
    Freedom to choose the right tools for a job
CONS OF SCALA
  • 11
    Slow compilation time
  • 7
    Multiple ropes and styles to hang your self
  • 6
    Too few developers available
  • 4
    Complicated subtyping
  • 2
    My coworkers using scala are racist against other stuff

related Scala posts

Shared insights
on
JavaJavaScalaScalaApache SparkApache Spark

I am new to Apache Spark and Scala both. I am basically a Java developer and have around 10 years of experience in Java.

I wish to work on some Machine learning or AI tech stacks. Please assist me in the tech stack and help make a clear Road Map. Any feedback is welcome.

Technologies apart from Scala and Spark are also welcome. Please note that the tools should be relevant to Machine Learning or Artificial Intelligence.

See more
Marc Bollinger
Infra & Data Eng Manager at Thumbtack · | 5 upvotes · 1.9M views

Lumosity is home to the world's largest cognitive training database, a responsibility we take seriously. For most of the company's history, our analysis of user behavior and training data has been powered by an event stream--first a simple Node.js pub/sub app, then a heavyweight Ruby app with stronger durability. Both supported decent throughput and latency, but they lacked some major features supported by existing open-source alternatives: replaying existing messages (also lacking in most message queue-based solutions), scaling out many different readers for the same stream, the ability to leverage existing solutions for reading and writing, and possibly most importantly: the ability to hire someone externally who already had expertise.

We ultimately migrated to Kafka in early- to mid-2016, citing both industry trends in companies we'd talked to with similar durability and throughput needs, the extremely strong documentation and community. We pored over Kyle Kingsbury's Jepsen post (https://aphyr.com/posts/293-jepsen-Kafka), as well as Jay Kreps' follow-up (http://blog.empathybox.com/post/62279088548/a-few-notes-on-kafka-and-jepsen), talked at length with Confluent folks and community members, and still wound up running parallel systems for quite a long time, but ultimately, we've been very, very happy. Understanding the internals and proper levers takes some commitment, but it's taken very little maintenance once configured. Since then, the Confluent Platform community has grown and grown; we've gone from doing most development using custom Scala consumers and producers to being 60/40 Kafka Streams/Connects.

We originally looked into Storm / Heron , and we'd moved on from Redis pub/sub. Heron looks great, but we already had a programming model across services that was more akin to consuming a message consumers than required a topology of bolts, etc. Heron also had just come out while we were starting to migrate things, and the community momentum and direction of Kafka felt more substantial than the older Storm. If we were to start the process over again today, we might check out Pulsar , although the ecosystem is much younger.

To find out more, read our 2017 engineering blog post about the migration!

See more
Swift logo

Swift

20.3K
13.4K
1.3K
An innovative new programming language for Cocoa and Cocoa Touch.
20.3K
13.4K
+ 1
1.3K
PROS OF SWIFT
  • 259
    Ios
  • 180
    Elegant
  • 126
    Not Objective-C
  • 107
    Backed by apple
  • 93
    Type inference
  • 61
    Generics
  • 54
    Playgrounds
  • 49
    Semicolon free
  • 38
    OSX
  • 36
    Tuples offer compound variables
  • 24
    Clean Syntax
  • 24
    Easy to learn
  • 22
    Open Source
  • 21
    Beautiful Code
  • 20
    Functional
  • 12
    Dynamic
  • 12
    Linux
  • 11
    Protocol-oriented programming
  • 10
    Promotes safe, readable code
  • 9
    No S-l-o-w JVM
  • 8
    Explicit optionals
  • 7
    Storyboard designer
  • 6
    Optionals
  • 6
    Type safety
  • 5
    Super addicting language, great people, open, elegant
  • 5
    Best UI concept
  • 4
    Its friendly
  • 4
    Highly Readable codes
  • 4
    Fail-safe
  • 4
    Powerful
  • 4
    Faster and looks better
  • 4
    Swift is faster than Objective-C
  • 4
    Feels like a better C++
  • 3
    Easy to learn and work
  • 3
    Much more fun
  • 3
    Protocol extensions
  • 3
    Native
  • 3
    Its fun and damn fast
  • 3
    Strong Type safety
  • 3
    Easy to Maintain
  • 2
    Protocol as type
  • 2
    All Cons C# and Java Swift Already has
  • 2
    Esay
  • 2
    MacOS
  • 2
    Type Safe
  • 2
    Protocol oriented programming
  • 1
    Can interface with C easily
  • 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
    Numbers with underbar
  • 1
    Optional chain
  • 1
    Great for Multi-Threaded Programming
  • 1
    Runs Python 8 times faster
  • 1
    Objec
CONS OF SWIFT
  • 6
    Must own a mac
  • 2
    Memory leaks are not uncommon
  • 1
    Very irritatingly picky about things that’s
  • 1
    Complicated process for exporting modules
  • 1
    Its classes compile to roughly 300 lines of assembly
  • 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 · 873.6K 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 · 2.1M 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
Java logo

Java

135.1K
102.3K
3.7K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
135.1K
102.3K
+ 1
3.7K
PROS OF JAVA
  • 603
    Great libraries
  • 446
    Widely used
  • 401
    Excellent tooling
  • 396
    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
    Managed memory
  • 46
    High Performance
  • 45
    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
    Good amount of APIs
  • 20
    Universal platform
  • 18
    Great Support
  • 14
    Great ecosystem
  • 11
    Backward compatible
  • 11
    Lots of boilerplate
  • 10
    Everywhere
  • 9
    Excellent SDK - JDK
  • 7
    Cross-platform
  • 7
    It's Java
  • 7
    Static typing
  • 6
    Portability
  • 6
    Mature language thus stable systems
  • 6
    Better than Ruby
  • 6
    Long term language
  • 5
    Used for Android development
  • 5
    Clojure
  • 5
    Vast Collections Library
  • 4
    Best martial for design
  • 4
    Most developers favorite
  • 4
    Old tech
  • 3
    Testable
  • 3
    History
  • 3
    Javadoc
  • 3
    Stable platform, which many new languages depend on
  • 3
    Great Structure
  • 2
    Faster than python
  • 2
    Type Safe
  • 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 · 12.6M 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 · 4.1M 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
Groovy logo

Groovy

2.1K
778
212
A multi-faceted language for the Java platform
2.1K
778
+ 1
212
PROS OF GROOVY
  • 44
    Java platform
  • 33
    Much more productive than java
  • 29
    Concise and readable
  • 28
    Very little code needed for complex tasks
  • 22
    Dynamic language
  • 13
    Nice dynamic syntax for the jvm
  • 9
    Very fast
  • 7
    Can work with JSON as an object
  • 7
    Easy to setup
  • 6
    Supports closures (lambdas)
  • 6
    Literal Collections
  • 3
    Syntactic sugar
  • 3
    Optional static typing
  • 2
    Developer Friendly
CONS OF GROOVY
  • 3
    Groovy Code can be slower than Java Code
  • 1
    Absurd syntax
  • 1
    Objects cause stateful/heap mess

related Groovy posts

Alex A

Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?

See more

Presently, a web-based ERP is developed in Groovy on Grails. Now the ERP is getting revamped with more functionalities. Is it advisable to continue with the same software and framework or try something new especially Node.js over ExpressJS?

See more
Python logo

Python

244.6K
199.7K
6.9K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
244.6K
199.7K
+ 1
6.9K
PROS OF PYTHON
  • 1.2K
    Great libraries
  • 962
    Readable code
  • 847
    Beautiful code
  • 788
    Rapid development
  • 690
    Large community
  • 438
    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 · 12.6M 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.3M views

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

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

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

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

#FrameworksFullStack #Languages

See more
Golang logo

Golang

22.5K
13.8K
3.3K
An open source programming language that makes it easy to build simple, reliable, and efficient software
22.5K
13.8K
+ 1
3.3K
PROS OF GOLANG
  • 552
    High-performance
  • 396
    Simple, minimal syntax
  • 363
    Fun to write
  • 303
    Easy concurrency support via goroutines
  • 273
    Fast compilation times
  • 195
    Goroutines
  • 181
    Statically linked binaries that are simple to deploy
  • 151
    Simple compile build/run procedures
  • 137
    Great community
  • 137
    Backed by google
  • 53
    Garbage collection built-in
  • 47
    Built-in Testing
  • 44
    Excellent tools - gofmt, godoc etc
  • 40
    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
  • 17
    Go is God
  • 14
    Powerful and simple
  • 14
    Easy to deploy
  • 14
    Its Simple and Heavy duty
  • 14
    Concurrency
  • 13
    Best language for concurrency
  • 11
    Safe GOTOs
  • 11
    Rich standard library
  • 10
    Clean code, high performance
  • 10
    Easy setup
  • 10
    High performance
  • 9
    Simplicity, Concurrency, Performance
  • 8
    Cross compiling
  • 8
    Single binary avoids library dependency issues
  • 8
    Hassle free deployment
  • 7
    Used by Giants of the industry
  • 7
    Simple, powerful, and great performance
  • 7
    Gofmt
  • 6
    Garbage Collection
  • 5
    WYSIWYG
  • 5
    Very sophisticated syntax
  • 5
    Excellent tooling
  • 4
    Keep it simple and stupid
  • 4
    Widely used
  • 4
    Kubernetes written on Go
  • 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 · 12.6M 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.3M views

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

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

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

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

#FrameworksFullStack #Languages

See more
React Native logo

React Native

33.5K
29K
1.2K
A framework for building native apps with React
33.5K
29K
+ 1
1.2K
PROS OF REACT NATIVE
  • 214
    Learn once write everywhere
  • 174
    Cross platform
  • 168
    Javascript
  • 122
    Native ios components
  • 69
    Built by facebook
  • 65
    Easy to learn
  • 45
    Bridges me into ios development
  • 40
    It's just react
  • 39
    No compile
  • 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 · | 37 upvotes · 254.3K 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
Flutter logo

Flutter

16.8K
16.4K
1.2K
Cross-platform mobile framework from Google
16.8K
16.4K
+ 1
1.2K
PROS OF FLUTTER
  • 143
    Hot Reload
  • 123
    Cross platform
  • 105
    Performance
  • 89
    Backed by Google
  • 73
    Compiled into Native Code
  • 61
    Fast Development
  • 58
    Open Source
  • 53
    Fast Prototyping
  • 49
    Single Codebase
  • 48
    Expressive and Flexible UI
  • 36
    Reactive Programming
  • 34
    Material Design
  • 30
    Dart
  • 29
    Widget-based
  • 26
    Target to Fuchsia
  • 20
    IOS + Android
  • 17
    Easy to learn
  • 16
    Great CLI Support
  • 14
    You can use it as mobile, web, Server development
  • 14
    Tooling
  • 13
    Debugging quickly
  • 13
    Have built-in Material theme
  • 12
    Target to Android
  • 12
    Good docs & sample code
  • 12
    Community
  • 11
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 10
    Written by Dart, which is easy to read code
  • 10
    Easy Testing Support
  • 9
    Target to iOS
  • 9
    Real platform free framework of the future
  • 9
    Have built-in Cupertino theme
  • 8
    Easy to Widget Test
  • 8
    Easy to Unit Test
  • 1
    Large Community
CONS OF FLUTTER
  • 29
    Need to learn Dart
  • 11
    Lack of community support
  • 10
    No 3D Graphics Engine Support
  • 8
    Graphics programming
  • 6
    Lack of friendly documentation
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

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

The only two programming languages I know are Python and Dart, I fall in love with Dart when I learned about the type safeness, ease of refactoring, and the help of the IDE. I have an idea for an app, a simple app, but I need SEO and server rendering, and I also want it to be available on all platforms. I can't use Flutter or Dart anymore because of that. I have been searching and looks like there is no way to avoid learning HTML and CSS for this. I want to use Supabase as BASS, at the moment I think that I have two options if I want to learn the least amount of things because of my lack of time available:

  1. Quasar Framework: They claim that I can do all the things I need, but I have to use JavaScript, and I am going to have all those bugs with a type-safe programming language avoidable. I guess I can use TypeScript?, but that means learning both, and I am not sure if I will be able to use 100% Typescript. Besides Vue.js, Node.js, etc.

  2. Blazor and .NET: There is MAUI with razor bindings in .Net now, and also a Blazor server. And as far as I can see, the transition from Dart to C# will be easy. I guess that I have to learn some Javascript here and there, but I have to less things I guess, am I wrong? But Blazor is a new technology, Vue is widely used.

See more