Alternatives to Spring Framework logo

Alternatives to Spring Framework

Spring MVC, Spring Boot, Play, Java EE, and Django are the most popular alternatives and competitors to Spring Framework.
2K
857
+ 1
0

What is Spring Framework and what are its top alternatives?

Spring Framework is a comprehensive framework for building enterprise Java applications. It provides support for various tasks such as dependency injection, aspect-oriented programming, transaction management, MVC framework, and more. However, Spring can sometimes be considered complex and heavyweight for smaller projects.

  1. Micronaut: Micronaut is a modern, JVM-based full-stack framework designed for building modular, easily testable microservices and serverless applications. Key features include minimal startup time, reduced memory footprint, and support for cloud-native applications. Pros include efficiency and improved performance, while a potential con could be a smaller community compared to Spring.
  2. Quarkus: Quarkus is a Kubernetes-native Java framework made for GraalVM & OpenJDK HotSpot. It aims to significantly reduce the memory footprint and boot times of Java applications. Key features include developer joy, Flexibility, and secure. Pros include faster boot times and lower memory consumption, while cons could be the learning curve for new developers and limited community support compared to Spring.
  3. Dropwizard:Dropwizard is a high-performance Java framework for building production-ready RESTful web services. It combines various libraries like Jetty, Jackson, Metrics, Jersey, and Guava into a simple, lightweight package. Key features include easy deployment, ops-friendly, and robust support for metrics and health checks. Pros include ease of use and simplicity, while cons could be its opinionated approach and limited flexibility compared to Spring.
  4. Vert.x: Vert.x is a toolkit for building reactive applications on the JVM. It allows for high concurrency with minimal resource consumption and supports various programming languages. Key features include event-driven architecture, unblocking nature, and polyglot support. Pros include high performance and scalability, while a potential con could be a steeper learning curve for developers unfamiliar with reactive programming concepts.
  5. Play Framework: Play Framework is a web development framework built on Akka and Scala, offering a reactive and modern approach to building web applications. Key features include stateless and RESTful architecture, hot reload functionality, and support for both Java and Scala. Pros include high productivity and real-time feedback, while cons could be a more limited ecosystem compared to Spring.
  6. JHipster: JHipster is a development platform that generates a production-ready Spring Boot + Angular/React/Vue Web application. It combines Spring Boot with Angular, React, or Vue to offer a powerful full-stack solution. Key features include CRUD generation, Microservices, and Continuous Deployment. Pros include rapid application development and a wide variety of supported technologies, while potential cons could be complexity and a learning curve for beginners.
  7. Spark: Spark is a micro framework for creating web applications in Java. It is similar to Sinatra but for Java and offers a simple and expressive syntax. Key features include REST API development, easy configuration, and lightweight footprint. Pros include simplicity and ease of use, while a potential con could be its minimalistic approach compared to the feature-rich Spring Framework.
  8. Ratpack: Ratpack is a set of Java libraries for building modern HTTP applications. It focuses on high performance and developer productivity by leveraging non-blocking I/O and Groovy DSL. Key features include reactive programming, asynchronous handling, and simplicity. Pros include performance and scalability, while cons could be limited community support and a potentially smaller ecosystem compared to Spring.
  9. Grails: Grails is a Groovy-based web application framework that embraces the coding by convention paradigm. It leverages the JVM ecosystem and offers seamless integration with popular libraries like Hibernate and Quartz. Key features include rapid application development, convention-over-configuration, and easy testing. Pros include high productivity and seamless integration, while cons could be the learning curve for developers unfamiliar with Groovy or convention-based frameworks.
  10. Lagom: Lagom is a Java microservices framework that offers a development environment for building distributed systems. It focuses on delivering reactive, resilient, and message-driven systems. Key features include CQRS + Event Sourcing, Service Provisioning, and distributed data management. Pros include scalability and fault tolerance, while cons could be the specialized use case compared to the more general-purpose Spring Framework.

Top Alternatives to Spring Framework

  • Spring MVC
    Spring MVC

    A Java framework that follows the Model-View-Controller design pattern and provides an elegant solution to use MVC in spring framework by the help of DispatcherServlet. ...

  • Spring Boot
    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • Play
    Play

    Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications. ...

  • Java EE
    Java EE

    It is developed using the Java Community Process, with contributions from industry experts, commercial and open source organizations, Java User Groups, and countless individuals. It offers a rich enterprise software platform and with over 20 compliant implementations to choose from. ...

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • Hibernate
    Hibernate

    Hibernate is a suite of open source projects around domain models. The flagship project is Hibernate ORM, the Object Relational Mapper. ...

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

Spring Framework alternatives & related posts

Spring MVC logo

Spring MVC

481
517
0
A Java framework which is used to build web applications
481
517
+ 1
0
PROS OF SPRING MVC
    Be the first to leave a pro
    CONS OF SPRING MVC
      Be the first to leave a con

      related Spring MVC posts

      NIDHISH PUTHIYADATH
      Lead Software Engineer at EDIFECS · | 1 upvote · 303.6K views

      Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC

      We built our customer facing portal application using Angular frontend backed by Spring boot.

      See more
      Spring Boot logo

      Spring Boot

      25.5K
      23.2K
      1K
      Create Spring-powered, production-grade applications and services with absolute minimum fuss
      25.5K
      23.2K
      + 1
      1K
      PROS OF SPRING BOOT
      • 149
        Powerful and handy
      • 134
        Easy setup
      • 128
        Java
      • 90
        Spring
      • 85
        Fast
      • 46
        Extensible
      • 37
        Lots of "off the shelf" functionalities
      • 32
        Cloud Solid
      • 26
        Caches well
      • 24
        Productive
      • 24
        Many receipes around for obscure features
      • 23
        Modular
      • 23
        Integrations with most other Java frameworks
      • 22
        Spring ecosystem is great
      • 21
        Auto-configuration
      • 21
        Fast Performance With Microservices
      • 18
        Community
      • 17
        Easy setup, Community Support, Solid for ERP apps
      • 15
        One-stop shop
      • 14
        Easy to parallelize
      • 14
        Cross-platform
      • 13
        Easy setup, good for build erp systems, well documented
      • 13
        Powerful 3rd party libraries and frameworks
      • 12
        Easy setup, Git Integration
      • 5
        It's so easier to start a project on spring
      • 4
        Kotlin
      • 1
        Microservice and Reactive Programming
      • 1
        The ability to integrate with the open source ecosystem
      CONS OF SPRING BOOT
      • 23
        Heavy weight
      • 18
        Annotation ceremony
      • 13
        Java
      • 11
        Many config files needed
      • 5
        Reactive
      • 4
        Excellent tools for cloud hosting, since 5.x
      • 1
        Java 😒😒

      related Spring Boot posts

      Praveen Mooli
      Engineering Manager at Taylor and Francis · | 18 upvotes · 3.8M views

      We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

      To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

      To build #Webapps we decided to use Angular 2 with RxJS

      #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

      See more

      Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

      Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

      See more
      Play logo

      Play

      748
      606
      496
      The High Velocity Web Framework For Java and Scala
      748
      606
      + 1
      496
      PROS OF PLAY
      • 81
        Scala
      • 55
        Web-friendly architecture
      • 55
        Built on akka
      • 50
        Stateless
      • 47
        High-scalable
      • 46
        Fast
      • 40
        Open source
      • 34
        Java
      • 27
        High velocity
      • 24
        Fun
      • 9
        Lightweight
      • 8
        Non-blocking io
      • 6
        Developer friendly
      • 5
        Simple template engine
      • 4
        Scalability
      • 3
        Pure love
      • 2
        Resource efficient
      CONS OF PLAY
      • 3
        Evolves fast, keep up with releases
      • 1
        Unnecessarily complicated

      related Play 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
      Tomas Zeman
      product manager at Broadcom · | 3 upvotes · 18.8K views
      Shared insights
      on
      PlayPlayApache TomcatApache Tomcat
      at

      I use Play as the best Java framewrk for web development. It is easy to use and I was able to learn it quickly. Before I was using Apache Tomcat , but I would never go back. Play is preselecting for you popular and usefull libraries, you can use templating with Twirl, JPA, Injections and much more.

      See more
      Java EE logo

      Java EE

      549
      460
      2
      The standard in community-driven enterprise software
      549
      460
      + 1
      2
      PROS OF JAVA EE
      • 1
        Inherits all java advantages
      • 1
        High level of security
      CONS OF JAVA EE
      • 2
        PAID

      related Java EE posts

      Shared insights
      on
      JavaScriptJavaScriptJava EEJava EE

      Hi, I'm looking to learn Java EE and JavaScript.... but confused about exactly the difference between J2EE and JavaScript.....are both interconnected or different??? And if I want to learn both, should I learn JavaScript first and then touch J2EE or learn J2EE first and then JavaScript??.... please suggest

      See more
      Hajed Khlifi
      Shared insights
      on
      DockerDockerGradleGradleJava EEJava EE

      Hi, I'm working on dockerizing a heavy Java EE application where the process of installation requires a complex process maintained by a Gradle project we've developed to install, configure and customize specific jar files to generate a runnable server application at the end for the user. I'm new to Docker. As I said, the problem is that we have got a long process to install the app. The first alternative pop into my head is to put the installer Gradle project in the docker image and manage stateful data using the writable layer (in this case, I need to add Gradle too and the writable layer will be too heavy). Any advice! Thank you

      See more
      Django logo

      Django

      37.1K
      33.5K
      4.2K
      The Web framework for perfectionists with deadlines
      37.1K
      33.5K
      + 1
      4.2K
      PROS OF DJANGO
      • 670
        Rapid development
      • 487
        Open source
      • 424
        Great community
      • 379
        Easy to learn
      • 276
        Mvc
      • 232
        Beautiful code
      • 223
        Elegant
      • 206
        Free
      • 203
        Great packages
      • 194
        Great libraries
      • 79
        Comes with auth and crud admin panel
      • 79
        Restful
      • 78
        Powerful
      • 75
        Great documentation
      • 71
        Great for web
      • 57
        Python
      • 43
        Great orm
      • 41
        Great for api
      • 32
        All included
      • 29
        Fast
      • 25
        Web Apps
      • 23
        Easy setup
      • 23
        Clean
      • 21
        Used by top startups
      • 19
        Sexy
      • 19
        ORM
      • 15
        The Django community
      • 14
        Allows for very rapid development with great libraries
      • 14
        Convention over configuration
      • 11
        King of backend world
      • 10
        Full stack
      • 10
        Great MVC and templating engine
      • 8
        Fast prototyping
      • 8
        Mvt
      • 7
        Easy to develop end to end AI Models
      • 7
        Batteries included
      • 7
        Its elegant and practical
      • 6
        Have not found anything that it can't do
      • 6
        Very quick to get something up and running
      • 6
        Cross-Platform
      • 5
        Easy Structure , useful inbuilt library
      • 5
        Great peformance
      • 5
        Zero code burden to change databases
      • 5
        Python community
      • 4
        Map
      • 4
        Just the right level of abstraction
      • 4
        Easy to change database manager
      • 4
        Modular
      • 4
        Many libraries
      • 4
        Easy to use
      • 4
        Easy
      • 4
        Full-Text Search
      • 3
        Scaffold
      • 1
        Fastapi
      • 1
        Built in common security
      • 1
        Scalable
      • 1
        Great default admin panel
      • 1
        Node js
      • 1
        Gigante ta
      • 0
        Rails
      CONS OF DJANGO
      • 26
        Underpowered templating
      • 22
        Autoreload restarts whole server
      • 22
        Underpowered ORM
      • 15
        URL dispatcher ignores HTTP method
      • 10
        Internal subcomponents coupling
      • 8
        Not nodejs
      • 8
        Configuration hell
      • 7
        Admin
      • 5
        Not as clean and nice documentation like Laravel
      • 4
        Python
      • 3
        Not typed
      • 3
        Bloated admin panel included
      • 2
        Overwhelming folder structure
      • 2
        InEffective Multithreading
      • 1
        Not type safe

      related Django posts

      Dmitry Mukhin
      Engineer at Uploadcare · | 25 upvotes · 2.4M views

      Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

      Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

      For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

      However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

      All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

      See more

      Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

      See more
      Laravel logo

      Laravel

      27.6K
      22.9K
      3.9K
      A PHP Framework For Web Artisans
      27.6K
      22.9K
      + 1
      3.9K
      PROS OF LARAVEL
      • 553
        Clean architecture
      • 392
        Growing community
      • 370
        Composer friendly
      • 344
        Open source
      • 324
        The only framework to consider for php
      • 220
        Mvc
      • 210
        Quickly develop
      • 168
        Dependency injection
      • 156
        Application architecture
      • 143
        Embraces good community packages
      • 73
        Write less, do more
      • 71
        Orm (eloquent)
      • 66
        Restful routing
      • 57
        Database migrations & seeds
      • 55
        Artisan scaffolding and migrations
      • 41
        Great documentation
      • 40
        Awesome
      • 30
        Awsome, Powerfull, Fast and Rapid
      • 29
        Build Apps faster, easier and better
      • 28
        Eloquent ORM
      • 26
        Promotes elegant coding
      • 26
        Modern PHP
      • 26
        JSON friendly
      • 25
        Most easy for me
      • 24
        Easy to learn, scalability
      • 23
        Beautiful
      • 22
        Blade Template
      • 21
        Test-Driven
      • 15
        Security
      • 15
        Based on SOLID
      • 13
        Clean Documentation
      • 13
        Easy to attach Middleware
      • 13
        Cool
      • 12
        Simple
      • 12
        Convention over Configuration
      • 11
        Easy Request Validatin
      • 10
        Simpler
      • 10
        Fast
      • 10
        Easy to use
      • 9
        Get going quickly straight out of the box. BYOKDM
      • 9
        Its just wow
      • 8
        Laravel + Cassandra = Killer Framework
      • 8
        Simplistic , easy and faster
      • 8
        Friendly API
      • 7
        Less dependencies
      • 7
        Super easy and powerful
      • 6
        Great customer support
      • 6
        Its beautiful to code in
      • 5
        Speed
      • 5
        Eloquent
      • 5
        Composer
      • 5
        Minimum system requirements
      • 5
        Laravel Mix
      • 5
        Easy
      • 5
        The only "cons" is wrong! No static method just Facades
      • 5
        Fast and Clarify framework
      • 5
        Active Record
      • 5
        Php7
      • 4
        Ease of use
      • 4
        Laragon
      • 4
        Laravel casher
      • 4
        Easy views handling and great ORM
      • 4
        Laravel Forge and Envoy
      • 4
        Cashier with Braintree and Stripe
      • 3
        Laravel Passport
      • 3
        Laravel Spark
      • 3
        Intuitive usage
      • 3
        Laravel Horizon and Telescope
      • 3
        Laravel Nova
      • 3
        Rapid development
      • 2
        Laravel Vite
      • 2
        Scout
      • 2
        Deployment
      • 1
        Succint sintax
      CONS OF LARAVEL
      • 54
        PHP
      • 33
        Too many dependency
      • 23
        Slower than the other two
      • 17
        A lot of static method calls for convenience
      • 15
        Too many include
      • 13
        Heavy
      • 9
        Bloated
      • 8
        Laravel
      • 7
        Confusing
      • 5
        Too underrated
      • 4
        Not fast with MongoDB
      • 1
        Slow and too much big
      • 1
        Not using SOLID principles
      • 1
        Difficult to learn

      related Laravel posts

      I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

      Need help deciding technology stack. Thanks.

      See more
      Christopher Wray
      Web Developer at Soltech LLC · | 15 upvotes · 173K views

      This week, we finally released NurseryPeople.com. In the end, I chose to provision our server on DigitalOcean. So far, I am SO happy with that decision. Although setting everything up was a challenge, and I learned a lot, DigitalOceans blogs helped in so many ways. I was able to set up nginx and the Laravel web app pretty smoothly. I am also using Buddy for deploying changes made in git, which is super awesome. All I have to do in order to deploy is push my code to my private repo, and buddy transfers everything over to DigitalOcean. So far, we haven't had any downtime and DigitalOceans prices are quite fair for the power under the hood.

      See more
      Hibernate logo

      Hibernate

      1.5K
      1.2K
      33
      Idiomatic persistence for Java and relational databases.
      1.5K
      1.2K
      + 1
      33
      PROS OF HIBERNATE
      • 22
        Easy ORM
      • 8
        Easy transaction definition
      • 3
        Is integrated with spring jpa
      CONS OF HIBERNATE
      • 3
        Can't control proxy associations when entity graph used

      related Hibernate posts

      Ganesa Vijayakumar
      Full Stack Coder | Technical Lead · | 19 upvotes · 4.7M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      NIDHISH PUTHIYADATH
      Lead Software Engineer at EDIFECS · | 1 upvote · 303.6K views

      Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC

      We built our customer facing portal application using Angular frontend backed by Spring boot.

      See more
      JavaScript logo

      JavaScript

      352.2K
      268.1K
      8.1K
      Lightweight, interpreted, object-oriented language with first-class functions
      352.2K
      268.1K
      + 1
      8.1K
      PROS OF JAVASCRIPT
      • 1.7K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.2K
        Lots of great frameworks
      • 897
        Fast
      • 745
        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
        Setup is easy
      • 12
        Future Language of The Web
      • 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
        Expansive community
      • 9
        Everyone use it
      • 9
        Can be used in backend, frontend and DB
      • 9
        Easy
      • 8
        Most Popular Language in the World
      • 8
        Powerful
      • 8
        Can be used both as frontend and backend as well
      • 8
        For the good parts
      • 8
        No need to use PHP
      • 8
        Easy to hire developers
      • 7
        Agile, packages simple to use
      • 7
        Love-hate relationship
      • 7
        Photoshop has 3 JS runtimes built in
      • 7
        Evolution of C
      • 7
        It's fun
      • 7
        Hard not to use
      • 7
        Versitile
      • 7
        Its fun and fast
      • 7
        Nice
      • 7
        Popularized Class-Less Architecture & Lambdas
      • 7
        Supports lambdas and closures
      • 6
        It let's me use Babel & Typescript
      • 6
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 6
        1.6K Can be used on frontend/backend
      • 6
        Client side JS uses the visitors CPU to save Server Res
      • 6
        Easy to make something
      • 5
        Clojurescript
      • 5
        Promise relationship
      • 5
        Stockholm Syndrome
      • 5
        Function expressions are useful for callbacks
      • 5
        Scope manipulation
      • 5
        Everywhere
      • 5
        Client processing
      • 5
        What to add
      • 4
        Because it is so simple and lightweight
      • 4
        Only Programming language on browser
      • 1
        Test
      • 1
        Hard to learn
      • 1
        Test2
      • 1
        Not the best
      • 1
        Easy to understand
      • 1
        Subskill #4
      • 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

      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 · 10.8M 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