Alternatives to TypeScript logo

Alternatives to TypeScript

Flow, JavaScript, Dart, Babel, and Elm are the most popular alternatives and competitors to TypeScript.
94.1K
72.4K
+ 1
502

What is TypeScript and what are its top alternatives?

TypeScript is a superset of JavaScript that adds static typing to the language, providing developers with the benefits of type checking and improved code quality. It also allows for modern ECMAScript features to be used in older browsers and environments through transpilation. However, TypeScript can have a learning curve for developers unfamiliar with statically typed languages and may require additional configuration for certain build setups.

  1. [Flow (https://flow.org/): Flow is a static type checker for JavaScript that focuses on gradual typing and is designed to work seamlessly with existing JavaScript codebases. Key features include type inference, null safety, and support for React components. Pros include smooth integration with JavaScript projects, while cons may include a steeper learning curve compared to TypeScript.
  2. [Babel (https://babel.dev/): Babel is a JavaScript compiler that allows developers to use the latest ECMAScript features by transforming them into backwards-compatible versions. Key features include extensive plugin support, customizability, and compatibility with various build tools. Pros include flexibility and compatibility, while cons may include the lack of static type checking features.
  3. [FlowType (https://flowtype.org/): FlowType is a static type checker for JavaScript developed by Facebook that focuses on type inference and gradual typing. Key features include error checking, type annotations, and interoperation with existing toolchains. Pros include ease of adoption for Facebook projects, while cons may include a smaller community compared to TypeScript.
  4. [ReasonML (https://reasonml.github.io/): ReasonML is a statically-typed language that compiles to JavaScript and is known for its emphasis on functional programming principles. Key features include a strong type system, pattern matching, and interoperability with JavaScript. Pros include robust type safety and functional programming capabilities, while cons may include a different syntax compared to TypeScript.
  5. [CoffeeScript (https://coffeescript.org/): CoffeeScript is a language that compiles to JavaScript and aims to improve JavaScript syntax by providing a more concise and readable alternative. Key features include syntactic sugar, function binding, and compatibility with JavaScript libraries. Pros include improved readability and reduced boilerplate code, while cons may include the lack of static type checking present in TypeScript.
  6. [Elm (https://elm-lang.org/): Elm is a functional programming language for front-end web development that compiles to JavaScript and prioritizes simplicity and reliability. Key features include a virtual DOM implementation, strong type inference, and architecture for building web applications. Pros include a supportive community and robust error messages, while cons may include a smaller ecosystem compared to TypeScript.
  7. [PureScript (https://www.purescript.org/): PureScript is a strongly-typed functional programming language that compiles to JavaScript and is known for its expressive type system. Key features include type inference, type classes, and immutability by default. Pros include advanced type safety and functional programming capabilities, while cons may include a potentially steep learning curve for developers new to functional programming.
  8. [ClojureScript (https://clojurescript.org/): ClojureScript is a functional programming language that compiles to JavaScript and is designed for building web applications using the Clojure programming language. Key features include a simple syntax, immutable data structures, and seamless interop with JavaScript. Pros include a focus on simplicity and minimalism, while cons may include a different paradigm compared to TypeScript.
  9. [Kotlin/JS (https://kotlinlang.org/): Kotlin is a statically-typed language that can also target JavaScript through Kotlin/JS, allowing developers to write code that runs on both the JVM and the browser. Key features include null safety, interoperability with JavaScript, and a concise syntax. Pros include seamless integration with existing Kotlin projects, while cons may include a potential learning curve for developers new to Kotlin.
  10. [Purescript (https://www.purescript.org/): PureScript is a small strongly, statically typed programming language inspired by Haskell and compiling to Javascript. The idea behind the language was to keep it as close to Haskell design as possible. The pros of using PureScript include pure functional programming experience, interoperability with JavaScript, and functional data serialization. However, the cons of using PureScript include a learning curve for developers who are not familiar with purely functional languages, and a smaller community size.

Top Alternatives to TypeScript

  • Flow
    Flow

    Flow is an online collaboration platform that makes it easy for people to create, organize, discuss, and accomplish tasks with anyone, anytime, anywhere. By merging a sleek, intuitive interface with powerful functionality, we're out to revolutionize the way the world's productive teams get things done. ...

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

  • Dart
    Dart

    Dart is a cohesive, scalable platform for building apps that run on the web (where you can use Polymer) or on servers (such as with Google Cloud Platform). Use the Dart language, libraries, and tools to write anything from simple scripts to full-featured apps. ...

  • Babel
    Babel

    Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support. ...

  • Elm
    Elm

    Writing HTML apps is super easy with elm-lang/html. Not only does it render extremely fast, it also quietly guides you towards well-architected code. ...

  • ES6
    ES6

    Goals for ECMAScript 2015 include providing better support for large applications, library creation, and for use of ECMAScript as a compilation target for other languages. Some of its major enhancements include modules, class declarations, lexical block scoping, iterators and generators, promises for asynchronous programming, destructuring patterns, and proper tail calls. ...

  • CoffeeScript
    CoffeeScript

    It adds syntactic sugar inspired by Ruby, Python and Haskell in an effort to enhance JavaScript's brevity and readability. Specific additional features include list comprehension and de-structuring assignment. ...

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

TypeScript alternatives & related posts

Flow logo

Flow

77
15
Simple project and task management for busy teams
77
15
PROS OF FLOW
  • 6
    Great for collaboration
  • 6
    Easy to use
  • 3
    Free
CONS OF FLOW
    Be the first to leave a con

    related Flow posts

    JavaScript logo

    JavaScript

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

    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 · | 44 upvotes · 12.7M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Dart logo

    Dart

    3.9K
    452
    A new web programming language with libraries, a virtual machine, and tools
    3.9K
    452
    PROS OF DART
    • 59
      Backed by Google
    • 53
      Flutter
    • 39
      Twice the speed of Javascript
    • 35
      Great tools
    • 30
      Scalable
    • 27
      Open source
    • 26
      Made for the future
    • 25
      Can be used on Frontend
    • 22
      Polymer Dart
    • 22
      Angular Dart
    • 18
      Cross platform
    • 16
      Like Java
    • 14
      Easy to learn
    • 13
      Dartanalyzer
    • 12
      Runs on Google Cloud Platform
    • 10
      Easy to Understand
    • 9
      Amazing concurrency primitives
    • 8
      Is to JS what C is to ASM
    • 7
      Flutter works with darts
    • 3
      R
    • 3
      Can run Dart in AWS Lambda
    • 1
      Looks familiar, with purposely implemented features
    CONS OF DART
    • 3
      Lack of ORM
    • 3
      Locked in - JS or TS interop is very hard to accomplish
    • 0
      A

    related Dart posts

    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
    Shared insights
    on
    DartDartFlutterFlutter

    Hi, I'm considering building a social marketplace app on android, ios and web, Flutter seems to be a good UI framework for cross-platform apps, it's safe type, hot reload, and native compiling on native machine code (thanks to Dart). My question is, for an MVP product is it a good choice? if yes, will it be on the mid-term, long term? Or will I have to change as the users grow?

    thank you

    See more
    Babel logo

    Babel

    22.3K
    391
    Use next generation JavaScript, today.
    22.3K
    391
    PROS OF BABEL
    • 165
      Modern Javascript works with all browsers
    • 77
      Open source
    • 60
      Integration with lots of tools
    • 56
      Easy setup
    • 26
      Very active on github
    • 2
      JSX
    • 2
      Love
    • 2
      Source maps
    • 1
      Extensions
    CONS OF BABEL
      Be the first to leave a con

      related Babel posts

      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
      Jonathan Pugh
      Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3M views

      I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

      For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

      Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

      I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

      I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

      I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

      I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

      For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

      For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

      For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

      I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

      So that's my latest mobile stack. What tools do you use? Have you tried these ones?

      See more
      Elm logo

      Elm

      745
      319
      A type inferred, functional reactive language that compiles to HTML, CSS, and JavaScript
      745
      319
      PROS OF ELM
      • 45
        Code stays clean
      • 44
        Great type system
      • 40
        No Runtime Exceptions
      • 33
        Fun
      • 28
        Easy to understand
      • 23
        Type safety
      • 22
        Correctness
      • 17
        JS fatigue
      • 12
        Ecosystem agrees on one Application Architecture
      • 12
        Declarative
      • 10
        Friendly compiler messages
      • 8
        Fast rendering
      • 7
        If it compiles, it runs
      • 7
        Welcoming community
      • 5
        Stable ecosystem
      • 4
        'Batteries included'
      • 2
        Package.elm-lang.org
      CONS OF ELM
      • 3
        No typeclasses -> repitition (i.e. map has 130versions)
      • 2
        JS interop can not be async
      • 2
        JS interoperability a bit more involved
      • 1
        More code is required
      • 1
        No JSX/Template
      • 1
        Main developer enforces "the correct" style hard
      • 1
        No communication with users
      • 1
        Backwards compability breaks between releases

      related Elm posts

      Shared insights
      on
      ReactReactReduxReduxElmElm

      React is awesome, but is just a view library, when we need to manage state, there is Redux.js. The ecosystem of redux is big, complex and hard to integrate. That's why we choose to create hydux. Hydux is simple, the main idea is from Elm, a pure functional vdom-based framework for front-end. We seperate the whole app with state, actions and views. Which means not only our views are a tree, but also our state and actions. Reuse state and actions are just like reuse react components, no need to consider dependences.

      See more
      ES6 logo

      ES6

      71.5K
      165
      The next version of JavaScript
      71.5K
      165
      PROS OF ES6
      • 109
        ES6 code is shorter than traditional JS
      • 52
        Module System Standardized
      • 2
        Extremly compact
      • 2
        Destructuring Assignment
      CONS OF ES6
      • 1
        Create Node.js
      • 1
        Suffers from baggage

      related ES6 posts

      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
      Ali Soueidan
      Creative Web Developer at Ali Soueidan · | 18 upvotes · 1.2M views

      Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

      For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

      To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

      DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

      Side note: I used npm for package management. 🎉

      *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

      See more
      CoffeeScript logo

      CoffeeScript

      3.4K
      1K
      A little language that compiles into JavaScript
      3.4K
      1K
      PROS OF COFFEESCRIPT
      • 199
        Easy to read
      • 179
        Faster to write
      • 126
        Syntactic sugar
      • 104
        Readable
      • 104
        Elegant
      • 73
        Pretty
      • 53
        Javascript the good parts
      • 48
        Open source
      • 44
        Classes
      • 35
        "it's just javascript"
      • 16
        Compact code
      • 15
        Easy
      • 13
        Simple
      • 13
        Not Javascript
      • 2
        Does the same with less code
      • 1
        I'm jobs I'm software engineer
      CONS OF COFFEESCRIPT
      • 3
        No ES6
      • 1
        Corner cases in syntax
      • 1
        Parentheses required in 0-ary function calls
      • 1
        Unclear what will be grouped to {…}

      related CoffeeScript posts

      Stitch’s frontend is used to configure data sources and destinations and monitor the status of each. Although we have been using AngularJS since its early days, we recently introduced React components into our front end, which many of our developers find easier to work with. We started using CoffeeScript when it was one of the few options for a more expressive alternative to vanilla JavaScript, but today we opt to instead write new code in ES6, which we feel is a more mature alternative.

      See more
      Eli Hooten

      We chose TypeScript at Codecov when undergoing a recent rewrite of a legacy front end. Our previous front end was a mishmash of vanilla JavaScript and CoffeeScript , and was expanded upon haphazardly as the need arose. Without a unifying set of paradigms and patterns, the CoffeeScript and JavaScript setup was proving hard to maintain and expand upon by an engineering team. During a move to Vue.js , we decided to also make the move to TypeScript. Integrating TypeScript and Vue.js is fairly well understood at this point, so the setup wasn't all that difficult, and we felt that the benefits of incorporating TypeScript would outweigh the required time to set it up and get our engineering team up to speed.

      Choosing to add TypeScript has given us one more layer to rely on to help enforce code quality, good standards, and best practices within our engineering organization. One of the biggest benefits for us as an engineering team has been how well our IDEs and editors (e.g., Visual Studio Code ) integrate with and understand TypeScript . This allows developers to catch many more errors at development time instead of relying on run time. The end result is safer (from a type perspective) code and a more efficient coding experience that helps to catch and remove errors with less developer effort.

      See more
      Java logo

      Java

      135.3K
      3.7K
      A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
      135.3K
      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.7M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Kamil Kowalski
      Lead Architect at Fresha · | 28 upvotes · 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