Alternatives to Project Reactor logo

Alternatives to Project Reactor

RxJava, Akka, Spring, JavaScript, and Python are the most popular alternatives and competitors to Project Reactor.
194
83
+ 1
0

What is Project Reactor and what are its top alternatives?

Project Reactor is a popular Java framework for building reactive, scalable applications. It provides an efficient way to handle asynchronous programming through its core components Flux and Mono, which are used for processing streams of data. Key features of Project Reactor include support for backpressure, reactive streams, and integration with other frameworks like Spring. However, one limitation of Project Reactor is its steep learning curve for beginners.

  1. RxJava: RxJava is a widely used library for reactive programming in Java. It offers similar features to Project Reactor such as handling asynchronous data streams with observables and operators. The pros of RxJava include a large community for support and extensive documentation. However, it may have a steeper learning curve compared to Project Reactor.

  2. Vert.x: Vert.x is a lightweight, high-performance framework for building reactive applications in Java. It supports event-driven programming model and features a scalable, non-blocking architecture. The pros of Vert.x include high performance and low resource consumption, but it may not be as popular or well-documented as Project Reactor.

  3. Akka: Akka is a toolkit for building highly concurrent, distributed, and fault-tolerant systems in Java and Scala. It provides a powerful actor model for handling concurrency and parallelism. The pros of Akka include fault-tolerance and scalability, but it may have a steeper learning curve compared to Project Reactor.

  4. Quasar: Quasar is a library that enables high-performance, lightweight threads (fibers) for asynchronous and parallel programming in Java. It allows developers to write concurrent code using familiar programming constructs. The pros of Quasar include efficient, lightweight threads and easy integration with existing codebases, while the cons may include potential overhead for some use cases.

  5. Ratpack: Ratpack is a set of libraries for building high-performance, asynchronous, and reactive applications in Java. It is designed to support non-blocking I/O and asynchronous programming patterns. The pros of Ratpack include simplicity and performance, but it may not be as feature-rich or widely used as Project Reactor.

  6. Micronaut: Micronaut is a modern, JVM-based framework for building microservices and serverless applications in Java, Kotlin, and Groovy. It aims to provide fast startup times and low memory usage. The pros of Micronaut include efficiency and developer productivity, while the cons may include a smaller community compared to Project Reactor.

  7. Kotlin Coroutines: Kotlin Coroutines is a lightweight, reactive programming framework for asynchronous and concurrent programming in Kotlin. It simplifies asynchronous code with sequential syntax and support for suspending functions. The pros of Kotlin Coroutines include ease of use and seamless integration with Kotlin codebases, but it may not be as feature-rich as Project Reactor.

  8. RxJava 3: RxJava 3 is the next version of RxJava, which aims to improve performance and provide better support for reactive programming in Java. It builds on the success of RxJava 2 and introduces new features and enhancements. The pros of RxJava 3 include improved performance and functionality, but it may require migration effort for applications using RxJava 2.

  9. WebFlux: WebFlux is a reactive web framework provided by Spring, which integrates with Project Reactor to support reactive programming in Java. It allows developers to build asynchronous, non-blocking web applications using functional and reactive programming patterns. The pros of WebFlux include seamless integration with Spring ecosystem and extensive documentation, but it may have a dependency on Spring framework.

  10. Reactive Streams API: Reactive Streams API is a specification for asynchronous stream processing with non-blocking backpressure in Java. It defines a standard for interoperability between different reactive libraries and frameworks. The pros of Reactive Streams API include compatibility with various reactive implementations and standardization of reactive patterns, but it may lack some features compared to higher-level frameworks like Project Reactor.

Top Alternatives to Project Reactor

  • RxJava
    RxJava

    A library for composing asynchronous and event-based programs by using observable sequences for the Java VM. ...

  • Akka
    Akka

    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM. ...

  • Spring
    Spring

    A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments. ...

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

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

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • HTML5
    HTML5

    HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997. ...

  • PHP
    PHP

    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...

Project Reactor alternatives & related posts

RxJava logo

RxJava

388
1
Reactive Extensions for the JVM
388
1
PROS OF RXJAVA
  • 1
    Reactive Libraries as per Reactive Manifesto
CONS OF RXJAVA
    Be the first to leave a con

    related RxJava posts

    Luis Pena
    Cloud Solution Architect at AWS · | 2 upvotes · 179.8K views
    Shared insights
    on
    QuarkusQuarkusRxJavaRxJava

    Can I mix RxJava with Quarkus?

    See more
    Akka logo

    Akka

    1.1K
    88
    A platform to build and run apps that are elastic, agile, and resilient.
    1.1K
    88
    PROS OF AKKA
    • 32
      Great concurrency model
    • 17
      Fast
    • 12
      Actor Library
    • 10
      Open source
    • 7
      Resilient
    • 5
      Message driven
    • 5
      Scalable
    CONS OF AKKA
    • 3
      Mixing futures with Akka tell is difficult
    • 2
      Closing of futures
    • 2
      No type safety
    • 1
      Very difficult to refactor
    • 1
      Typed actors still not stable

    related Akka posts

    To solve the problem of scheduling and executing arbitrary tasks in its distributed infrastructure, PagerDuty created an open-source tool called Scheduler. Scheduler is written in Scala and uses Cassandra for task persistence. It also adds Apache Kafka to handle task queuing and partitioning, with Akka to structure the library’s concurrency.

    The service’s logic schedules a task by passing it to the Scheduler’s Scala API, which serializes the task metadata and enqueues it into Kafka. Scheduler then consumes the tasks, and posts them to Cassandra to prevent data loss.

    See more
    Shared insights
    on
    AkkaAkkaKafkaKafka

    I decided to use Akka instead of Kafka streams because I have personal relationships at @Lightbend.

    See more
    Spring logo

    Spring

    4K
    1.1K
    Provides a comprehensive programming and configuration model for modern Java-based enterprise applications
    4K
    1.1K
    PROS OF SPRING
    • 230
      Java
    • 157
      Open source
    • 136
      Great community
    • 123
      Very powerful
    • 114
      Enterprise
    • 64
      Lot of great subprojects
    • 60
      Easy setup
    • 44
      Convention , configuration, done
    • 40
      Standard
    • 31
      Love the logic
    • 13
      Good documentation
    • 11
      Dependency injection
    • 11
      Stability
    • 9
      MVC
    • 6
      Easy
    • 3
      Makes the hard stuff fun & the easy stuff automatic
    • 3
      Strong typing
    • 2
      Code maintenance
    • 2
      Best practices
    • 2
      Maven
    • 2
      Great Desgin
    • 2
      Easy Integration with Spring Security
    • 2
      Integrations with most other Java frameworks
    • 1
      Java has more support and more libraries
    • 1
      Supports vast databases
    • 1
      Large ecosystem with seamless integration
    • 1
      OracleDb integration
    • 1
      Live project
    CONS OF SPRING
    • 15
      Draws you into its own ecosystem and bloat
    • 4
      Poor documentation
    • 3
      Verbose configuration
    • 3
      Java
    • 2
      Java is more verbose language in compare to python
    • 1
      Very difficult

    related Spring posts

    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

    I am consulting for a company that wants to move its current CubeCart e-commerce site to another PHP based platform like PrestaShop or Magento. I was interested in alternatives that utilize Node.js as the primary platform. I currently don't know PHP, but I have done full stack dev with Java, Spring, Thymeleaf, etc.. I am just unsure that learning a set of technologies not commonly used makes sense. For example, in PrestaShop, I would need to work with JavaScript better and learn PHP, Twig, and Bootstrap. It seems more cumbersome than a Node JS system, where the language syntax stays the same for the full stack. I am looking for thoughts and advice on the relevance of PHP skillset into the future AND whether the Node based e-commerce open source options can compete with Magento or Prestashop.

    See more
    JavaScript logo

    JavaScript

    371.4K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    371.4K
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 899
      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
      Its everywhere
    • 12
      Future Language of The Web
    • 12
      Setup is easy
    • 11
      JavaScript is the New PHP
    • 11
      Because I love functions
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Everyone use it
    • 9
      Can be used in backend, frontend and DB
    • 9
      Easy
    • 9
      Expansive community
    • 8
      For the good parts
    • 8
      Easy to hire developers
    • 8
      No need to use PHP
    • 8
      Most Popular Language in the World
    • 8
      Powerful
    • 8
      Can be used both as frontend and backend as well
    • 7
      It's fun
    • 7
      Its fun and fast
    • 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
    • 7
      Evolution of C
    • 7
      Hard not to use
    • 7
      Versitile
    • 7
      Nice
    • 6
      Easy to make something
    • 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
      It let's me use Babel & Typescript
    • 5
      Clojurescript
    • 5
      Everywhere
    • 5
      Scope manipulation
    • 5
      Function expressions are useful for callbacks
    • 5
      Stockholm Syndrome
    • 5
      Promise relationship
    • 5
      Client processing
    • 5
      What to add
    • 4
      Because it is so simple and lightweight
    • 4
      Only Programming language on browser
    • 1
      Subskill #4
    • 1
      Test2
    • 1
      Easy to understand
    • 1
      Not the best
    • 1
      Easy to learn
    • 1
      Hard to learn
    • 1
      Easy to learn and test
    • 1
      Love it
    • 1
      Test
    • 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 · 13.3M 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
    Python logo

    Python

    250.4K
    6.9K
    A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
    250.4K
    6.9K
    PROS OF PYTHON
    • 1.2K
      Great libraries
    • 965
      Readable code
    • 848
      Beautiful code
    • 789
      Rapid development
    • 692
      Large community
    • 439
      Open source
    • 394
      Elegant
    • 283
      Great community
    • 274
      Object oriented
    • 222
      Dynamic typing
    • 78
      Great standard library
    • 62
      Very fast
    • 56
      Functional programming
    • 52
      Easy to learn
    • 47
      Scientific computing
    • 36
      Great documentation
    • 30
      Productivity
    • 29
      Matlab alternative
    • 29
      Easy to read
    • 25
      Simple is better than complex
    • 21
      It's the way I think
    • 20
      Imperative
    • 19
      Very programmer and non-programmer friendly
    • 19
      Free
    • 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
      Fast coding and good for competitions
    • 6
      There should be one-- and preferably only one --obvious
    • 6
      High Documented language
    • 6
      Readability counts
    • 6
      Rapid Prototyping
    • 6
      I love snakes
    • 6
      Now is better than never
    • 6
      Flat is better than nested
    • 6
      Great for tooling
    • 5
      Great for analytics
    • 5
      Web scraping
    • 5
      Lists, tuples, dictionaries
    • 4
      Complex is better than complicated
    • 4
      Socially engaged community
    • 4
      Plotting
    • 4
      Beautiful is better than ugly
    • 4
      Easy to learn and use
    • 4
      Easy to setup and run smooth
    • 4
      Simple and easy to learn
    • 4
      Multiple Inheritence
    • 4
      CG industry needs
    • 3
      List comprehensions
    • 3
      Powerful language for AI
    • 3
      Flexible and easy
    • 3
      It is Very easy , simple and will you be love programmi
    • 3
      Many types of collections
    • 3
      If the implementation is easy to explain, it may be a g
    • 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
      No cruft
    • 3
      Generators
    • 3
      Import this
    • 2
      Can understand easily who are new to programming
    • 2
      Securit
    • 2
      Should START with this but not STICK with This
    • 2
      A-to-Z
    • 2
      Because of Netflix
    • 2
      Only one way to do it
    • 2
      Better outcome
    • 2
      Good for hacking
    • 2
      Batteries included
    • 2
      Procedural programming
    • 1
      Sexy af
    • 1
      Automation friendly
    • 1
      Slow
    • 1
      Best friend for NLP
    • 0
      Powerful
    • 0
      Keep it simple
    • 0
      Ni
    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 · 13.3M 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
    Shared insights
    on
    TensorFlowTensorFlowDjangoDjangoPythonPython

    Hi, I have an LMS application, currently developed in Python-Django.

    It works all very well, students can view their classes and submit exams, but I have noticed that some students are sharing exam answers with other students and let's say they already have a model of the exams.

    I want with the help of artificial intelligence, the exams to have different questions and in a different order for each student, what technology should I learn to develop something like this? I am a Python-Django developer but my focus is on web development, I have never touched anything from A.I.

    What do you think about TensorFlow?

    Please, I would appreciate all your ideas and opinions, thank you very much in advance.

    See more
    Node.js logo

    Node.js

    193.1K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    193.1K
    8.5K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 805
      Open source
    • 487
      Great for apis
    • 477
      Asynchronous
    • 425
      Great community
    • 390
      Great for realtime apps
    • 296
      Great for command line utilities
    • 86
      Websockets
    • 84
      Node Modules
    • 69
      Uber Simple
    • 59
      Great modularity
    • 58
      Allows us to reuse code in the frontend
    • 42
      Easy to start
    • 35
      Great for Data Streaming
    • 32
      Realtime
    • 28
      Awesome
    • 25
      Non blocking IO
    • 18
      Can be used as a proxy
    • 17
      High performance, open source, scalable
    • 16
      Non-blocking and modular
    • 15
      Easy and Fun
    • 14
      Easy and powerful
    • 13
      Future of BackEnd
    • 13
      Same lang as AngularJS
    • 12
      Fullstack
    • 11
      Fast
    • 10
      Scalability
    • 10
      Cross platform
    • 9
      Simple
    • 8
      Mean Stack
    • 7
      Great for webapps
    • 7
      Easy concurrency
    • 6
      Typescript
    • 6
      Fast, simple code and async
    • 6
      React
    • 6
      Friendly
    • 5
      Control everything
    • 5
      Its amazingly fast and scalable
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 5
      Scalable
    • 5
      Great speed
    • 5
      Fast development
    • 4
      It's fast
    • 4
      Easy to use
    • 4
      Isomorphic coolness
    • 3
      Great community
    • 3
      Not Python
    • 3
      Sooper easy for the Backend connectivity
    • 3
      TypeScript Support
    • 3
      Blazing fast
    • 3
      Performant and fast prototyping
    • 3
      Easy to learn
    • 3
      Easy
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      One language, end-to-end
    • 3
      Less boilerplate code
    • 2
      Npm i ape-updating
    • 2
      Event Driven
    • 2
      Lovely
    • 1
      Creat for apis
    • 0
      Node
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 45
      New framework every day
    • 40
      Lots of terrible examples on the internet
    • 33
      Asynchronous programming is the worst
    • 24
      Callback
    • 19
      Javascript
    • 11
      Dependency hell
    • 11
      Dependency based on GitHub
    • 10
      Low computational power
    • 7
      Very very Slow
    • 7
      Can block whole server easily
    • 7
      Callback functions may not fire on expected sequence
    • 4
      Breaking updates
    • 4
      Unstable
    • 3
      Unneeded over complication
    • 3
      No standard approach
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session

    related Node.js posts

    Anurag Maurya

    Needs advice on code coverage tool in Node.js/ExpressJS with External API Testing Framework

    Hello community,

    I have a web application with the backend developed using Node.js and Express.js. The backend server is in one directory, and I have a separate API testing framework, made using SuperTest, Mocha, and Chai, in another directory. The testing framework pings the API, retrieves responses, and performs validations.

    I'm currently looking for a code coverage tool that can accurately measure the code coverage of my backend code when triggered by the API testing framework. I've tried using Istanbul and NYC with instrumented code, but the results are not as expected.

    Could you please recommend a reliable code coverage tool or suggest an approach to effectively measure the code coverage of my Node.js/Express.js backend code in this setup?

    See more
    Shared insights
    on
    Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

    I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

    For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

    1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

    2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

    3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

    See more
    HTML5 logo

    HTML5

    153.3K
    2.2K
    5th major revision of the core language of the World Wide Web
    153.3K
    2.2K
    PROS OF HTML5
    • 448
      New doctype
    • 389
      Local storage
    • 334
      Canvas
    • 285
      Semantic header and footer
    • 240
      Video element
    • 121
      Geolocation
    • 106
      Form autofocus
    • 100
      Email inputs
    • 85
      Editable content
    • 79
      Application caches
    • 10
      Easy to use
    • 9
      Cleaner Code
    • 5
      Easy
    • 4
      Websockets
    • 4
      Semantical
    • 3
      Audio element
    • 3
      Content focused
    • 3
      Better
    • 3
      Modern
    • 2
      Compatible
    • 2
      Very easy to learning to HTML
    • 2
      Semantic Header and Footer, Geolocation, New Doctype
    • 2
      Portability
    CONS OF HTML5
    • 2
      Easy to forget the tags when you're a begginner
    • 1
      Long and winding code

    related HTML5 posts

    Shared insights
    on
    MySQLMySQLPHPPHPJavaScriptJavaScriptHTML5HTML5

    Hey guys, I need some advice on one thing. Currently, I am a fresher and know HTML5, CSS, JavaScript, PHP and, MySQL. Recently I got a client project through one of my friends and he wants me to build an E-learning Management System. Are these skills enough to build an LMS website?

    Thanks in advance!! ;)

    See more
    Jan Vlnas
    Senior Software Engineer at Mews · | 26 upvotes · 482.6K views
    Shared insights
    on
    HTML5HTML5JavaScriptJavaScriptNext.jsNext.js

    Few years ago we were building a Next.js site with a few simple forms. This required handling forms validation and submission, but instead of picking some forms library, we went with plain JavaScript and constraint validation API in HTML5. This shaved off a few KBs of dependencies and gave us full control over the validation behavior and look. I describe this approach, with its pros and cons, in a blog post.

    See more
    PHP logo

    PHP

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

    related PHP posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 46 upvotes · 4.4M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more

    Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.

    I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL

    I want to have some advice on whether these are enough to implement my project.

    See more