Alternatives to JUCE logo

Alternatives to JUCE

Qt, Faust, T3, AudioKit, and JavaScript are the most popular alternatives and competitors to JUCE.
38
73
+ 1
10

What is JUCE and what are its top alternatives?

JUCE is a C++ framework for developing cross-platform applications, particularly audio and digital signal processing software. It provides a wide range of tools and libraries to aid in creating interactive applications with high-quality audio output. Key features include support for multiple platforms, extensive documentation, rapid development workflow, and a large community of users. However, some limitations of JUCE include a steep learning curve for beginners and a somewhat rigid structure that may not fit all project requirements.

  1. Qt: Qt is a popular C++ framework for developing cross-platform applications with a focus on GUI development. Key features include a wide range of libraries, tools for internationalization, and a large developer community. Pros of Qt include a user-friendly interface, extensive documentation, and good performance. However, Qt can be resource-intensive and has a complex build system compared to JUCE.

  2. Max/MSP: Max/MSP is a visual programming language specifically designed for music and multimedia applications. Key features include a modular design, a graphical interface, and real-time audio processing capabilities. Pros of Max/MSP include easy experimentation and prototyping, a large library of pre-built modules, and a strong community. However, Max/MSP is not as suitable for traditional C++ development as JUCE.

  3. OpenFrameworks: OpenFrameworks is an open-source C++ toolkit for creative coding and graphical applications. Key features include a simplified syntax, a large collection of add-ons, and a focus on artistic expression. Pros of OpenFrameworks include rapid prototyping, flexibility for experimentation, and good performance. However, OpenFrameworks may require more manual setup and configuration than JUCE.

  4. FAUST: FAUST is a functional programming language specifically designed for real-time audio signal processing. Key features include a concise syntax, high-performance capabilities, and easy integration with other languages. Pros of FAUST include simplicity, efficiency in DSP tasks, and easy deployment. However, FAUST may not be as versatile as JUCE in terms of overall application development.

  5. Cinder: Cinder is a C++ framework for creative coding and multimedia applications. Key features include a robust set of libraries, a focus on graphics and multimedia, and compatibility with various platforms. Pros of Cinder include a wide range of built-in functionalities, good performance, and a supportive community. However, Cinder may not be as specialized for audio processing as JUCE.

  6. Protocore: Protocore is an open-source toolkit for building interactive performance systems in C++. Key features include support for real-time audio processing, a modular architecture, and a flexible design for experimentation. Pros of Protocore include customizable modules, real-time performance capabilities, and community-driven development. However, Protocore may require more manual setup and configuration compared to JUCE.

  7. TouchDesigner: TouchDesigner is a visual development platform for creating interactive 3D art, visualizations, and simulations. Key features include a node-based interface, real-time rendering capabilities, and support for multimedia content. Pros of TouchDesigner include ease of use for visual projects, a large library of built-in tools, and interactive performance features. However, TouchDesigner focuses more on visual applications than audio processing like JUCE.

  8. RackAFX: RackAFX is an audio plugin design tool for creating VST plugins in C++. Key features include a graphical user interface for DSP design, support for various audio formats, and integration with popular digital audio workstations. Pros of RackAFX include a streamlined workflow for plugin development, compatibility with industry-standard formats, and comprehensive tutorials. However, RackAFX is more specialized for audio plugins and may not be as versatile as JUCE for general application development.

  9. The Synthesis ToolKit in C++ (STK): The Synthesis ToolKit in C++ (STK) is a set of C++ classes for audio synthesis and processing. Key features include a wide range of synthesis algorithms, real-time performance capabilities, and support for various platforms. Pros of STK include a lightweight framework, a focus on audio synthesis, and a wide range of built-in algorithms. However, STK may require more manual coding compared to the visual interface provided by JUCE.

  10. Magnum: Magnum is a lightweight and modular C++11/C++14 graphics middleware for games and interactive applications. Key features include a flexible architecture, a wide range of graphics features, and a focus on performance optimization. Pros of Magnum include a modular design for customizable projects, good performance for graphics-intensive applications, and a growing community. However, Magnum is more specialized for graphics rendering and may not offer the same level of audio processing capabilities as JUCE.

Top Alternatives to JUCE

  • Qt
    Qt

    Qt, a leading cross-platform application and UI framework. With Qt, you can develop applications once and deploy to leading desktop, embedded & mobile targets. ...

  • Faust
    Faust

    It is a stream processing library, porting the ideas from Kafka Streams to Python. It provides both stream processing and event processing, sharing similarity with tools such as Kafka Streams, Apache Spark/Storm/Samza/Flink. ...

  • T3
    T3

    T3 is different than most JavaScript frameworks. It's meant to be a small piece of an overall architecture that allows you to build scalable client-side code. T3 is explicitly not an MVC framework. It's a framework that allows the creation of loosely-coupled components while letting you decide what other pieces you need for your web application. You can use T3 with other frameworks like Backbone or React, or you can use T3 by itself. ...

  • AudioKit
    AudioKit

    We made AudioKit open-source because we believe that clear, powerful audio development is best developed and maintained through a large, active base of developers and users. Our core code, tests, examples, and website are all available for contributions. ...

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

JUCE alternatives & related posts

Qt logo

Qt

454
138
A leading cross-platform application and UI framework
454
138
PROS OF QT
  • 17
    High Performance
  • 13
    Declarative, easy and flexible UI
  • 12
    Cross platform
  • 12
    Performance
  • 9
    Fast prototyping
  • 8
    Easiest integration with C++
  • 8
    Up to date framework
  • 7
    Python
  • 6
    Multiple license including Open Source and Commercial
  • 6
    Safe 2D Renderer
  • 5
    Great Community Support
  • 4
    HW Accelerated UI
  • 4
    Game Engine like UI system
  • 3
    No history of broken compatibility with a major version
  • 3
    JIT and QML Compiler
  • 3
    True cross-platform framework with native code compile
  • 3
    Reliable for industrial use
  • 3
    Pure C++
  • 3
    Been using it since the 90s - runs anywhere does it all
  • 2
    Open source
  • 2
    Easy Integrating to DX and OpenGL and Vulkan
  • 2
    From high to low level coding
  • 1
    Learning Curve
  • 1
    Great mobile support with Felgo add-on
  • 1
    Native looking GUI
CONS OF QT
  • 5
    Paid
  • 4
    C++ is not so productive
  • 2
    Lack of community support
  • 1
    Lack of libraries
  • 1
    Not detailed documentation

related Qt posts

Shared insights
on
QtQtLinuxLinux

Hi Everyone, I need to choose a graphics framework for app development on Linux. Since I know Qt from previous projects it would be a straightforward choice for me but the cost is a huge issue in this project. Any advice for a free and nice framework to use for app development? The requested UI contains some dynamic elements, like graphs, etc. Thanks in advance!

See more
Faust logo

Faust

26
0
A library for building streaming applications in Python
26
0
PROS OF FAUST
    Be the first to leave a pro
    CONS OF FAUST
      Be the first to leave a con

      related Faust posts

      T3 logo

      T3

      26
      0
      Client-side JavaScript framework for building large-scale web applications, created by Box
      26
      0
      PROS OF T3
        Be the first to leave a pro
        CONS OF T3
          Be the first to leave a con

          related T3 posts

          AudioKit logo

          AudioKit

          19
          0
          Powerful audio synthesis, processing, and analysis, without the steep learning curve.
          19
          0
          PROS OF AUDIOKIT
            Be the first to leave a pro
            CONS OF AUDIOKIT
              Be the first to leave a con

              related AudioKit posts

              JavaScript logo

              JavaScript

              361.6K
              8.1K
              Lightweight, interpreted, object-oriented language with first-class functions
              361.6K
              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
              Python logo

              Python

              245.3K
              6.9K
              A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
              245.3K
              6.9K
              PROS OF PYTHON
              • 1.2K
                Great libraries
              • 963
                Readable code
              • 847
                Beautiful code
              • 788
                Rapid development
              • 691
                Large community
              • 438
                Open source
              • 393
                Elegant
              • 282
                Great community
              • 273
                Object oriented
              • 221
                Dynamic typing
              • 77
                Great standard library
              • 60
                Very fast
              • 55
                Functional programming
              • 50
                Easy to learn
              • 46
                Scientific computing
              • 35
                Great documentation
              • 29
                Productivity
              • 28
                Matlab alternative
              • 28
                Easy to read
              • 24
                Simple is better than complex
              • 20
                It's the way I think
              • 19
                Imperative
              • 18
                Very programmer and non-programmer friendly
              • 18
                Free
              • 17
                Machine learning support
              • 17
                Powerfull language
              • 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
                Import antigravity
              • 8
                It's lean and fun to code
              • 7
                Print "life is short, use python"
              • 7
                Python has great libraries for data processing
              • 6
                High Documented language
              • 6
                I love snakes
              • 6
                Readability counts
              • 6
                Rapid Prototyping
              • 6
                Now is better than never
              • 6
                Although practicality beats purity
              • 6
                Flat is better than nested
              • 6
                Great for tooling
              • 6
                There should be one-- and preferably only one --obvious
              • 6
                Fast coding and good for competitions
              • 5
                Web scraping
              • 5
                Lists, tuples, dictionaries
              • 5
                Great for analytics
              • 4
                Beautiful is better than ugly
              • 4
                Easy to learn and use
              • 4
                Easy to setup and run smooth
              • 4
                Multiple Inheritence
              • 4
                CG industry needs
              • 4
                Socially engaged community
              • 4
                Complex is better than complicated
              • 4
                Plotting
              • 4
                Simple and easy to learn
              • 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
                Batteries included
              • 2
                Securit
              • 2
                Can understand easily who are new to programming
              • 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
              • 1
                Best friend for NLP
              • 1
                Sexy af
              • 1
                Procedural programming
              • 1
                Automation friendly
              • 1
                Slow
              • 0
                Keep it simple
              • 0
                Powerful
              • 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 · 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
              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
              Node.js logo

              Node.js

              189K
              8.5K
              A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
              189K
              8.5K
              PROS OF NODE.JS
              • 1.4K
                Npm
              • 1.3K
                Javascript
              • 1.1K
                Great libraries
              • 1K
                High-performance
              • 805
                Open source
              • 486
                Great for apis
              • 477
                Asynchronous
              • 424
                Great community
              • 390
                Great for realtime apps
              • 296
                Great for command line utilities
              • 85
                Websockets
              • 83
                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

              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
              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
              HTML5 logo

              HTML5

              149K
              2.2K
              5th major revision of the core language of the World Wide Web
              149K
              2.2K
              PROS OF HTML5
              • 447
                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
                Better
              • 3
                Audio element
              • 3
                Modern
              • 2
                Portability
              • 2
                Semantic Header and Footer, Geolocation, New Doctype
              • 2
                Content focused
              • 2
                Compatible
              • 1
                Very easy to learning to HTML
              CONS OF HTML5
              • 1
                Easy to forget the tags when you're a begginner
              • 1
                Long and winding code

              related HTML5 posts

              Jan Vlnas
              Senior Software Engineer at Mews · | 26 upvotes · 405.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
              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