Alternatives to YAML logo

Alternatives to YAML

JSON, RAML, Ansible, Docker Compose, and Python are the most popular alternatives and competitors to YAML.
242
161
+ 1
0

What is YAML and what are its top alternatives?

A human-readable data-serialization language. It is commonly used for configuration files, but could be used in many applications where data is being stored or transmitted.
YAML is a tool in the Languages category of a tech stack.

Top Alternatives to YAML

  • JSON

    JSON

    JavaScript Object Notation is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language. ...

  • RAML

    RAML

    RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. It is machine readable API design that is actually human friendly. ...

  • Ansible

    Ansible

    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use. ...

  • Docker Compose

    Docker Compose

    With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. ...

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

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

  • PHP

    PHP

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

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

YAML alternatives & related posts

JSON logo

JSON

1.4K
1.2K
8
A lightweight data-interchange format
1.4K
1.2K
+ 1
8
PROS OF JSON
  • 4
    Simple
  • 4
    Widely supported
CONS OF JSON
    Be the first to leave a con

    related JSON posts

    Ali Soueidan
    Creative Web Developer at Ali Soueidan · | 18 upvotes · 805.3K views

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

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

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

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

    Side note: I used npm for package management. 🎉

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

    See more

    I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

    • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

    • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

    • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

    • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

    • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

    • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

    • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

    See more
    RAML logo

    RAML

    154
    146
    37
    RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing
    154
    146
    + 1
    37
    PROS OF RAML
    • 13
      API Specification
    • 7
      Human Readable
    • 6
      API Documentation
    • 3
      Design Patterns & Code Reuse
    • 2
      API Modeling
    • 2
      Automatic Generation of Mule flow
    • 2
      Unit Testing
    • 1
      SDK Generation
    • 1
      API Mocking
    CONS OF RAML
      Be the first to leave a con

      related RAML posts

      Ansible logo

      Ansible

      14.1K
      11.2K
      1.3K
      Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine
      14.1K
      11.2K
      + 1
      1.3K
      PROS OF ANSIBLE
      • 276
        Agentless
      • 204
        Great configuration
      • 195
        Simple
      • 173
        Powerful
      • 151
        Easy to learn
      • 66
        Flexible
      • 54
        Doesn't get in the way of getting s--- done
      • 34
        Makes sense
      • 29
        Super efficient and flexible
      • 27
        Powerful
      • 11
        Dynamic Inventory
      • 8
        Backed by Red Hat
      • 7
        Works with AWS
      • 6
        Cloud Oriented
      • 6
        Easy to maintain
      • 4
        Because SSH
      • 4
        Multi language
      • 4
        Easy
      • 4
        Simple
      • 4
        Procedural or declarative, or both
      • 4
        Simple and powerful
      • 3
        Consistency
      • 3
        Vagrant provisioner
      • 2
        Fast as hell
      • 2
        Masterless
      • 2
        Well-documented
      • 2
        Merge hash to get final configuration similar to hiera
      • 2
        Debugging is simple
      • 1
        Work on windows, but difficult to manage
      • 1
        Certified Content
      CONS OF ANSIBLE
      • 5
        Dangerous
      • 5
        Hard to install
      • 3
        Bloated
      • 3
        Backward compatibility
      • 2
        Doesn't Run on Windows
      • 2
        No immutable infrastructure

      related Ansible posts

      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 4.6M views

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more
      Sebastian Gębski

      Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

      See more
      Docker Compose logo

      Docker Compose

      14.9K
      10.9K
      477
      Define and run multi-container applications with Docker
      14.9K
      10.9K
      + 1
      477
      PROS OF DOCKER COMPOSE
      • 121
        Multi-container descriptor
      • 109
        Fast development environment setup
      • 75
        Easy linking of containers
      • 66
        Simple yaml configuration
      • 58
        Easy setup
      • 15
        Yml or yaml format
      • 11
        Use Standard Docker API
      • 7
        Open source
      • 4
        Can choose Discovery Backend
      • 4
        Go from template to application in minutes
      • 2
        Scalable
      • 2
        Easy configuration
      • 2
        Kubernetes integration
      • 1
        Quick and easy
      CONS OF DOCKER COMPOSE
      • 8
        Tied to single machine
      • 5
        Still very volatile, changing syntax often

      related Docker Compose posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more

      Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

      We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

      See more
      Python logo

      Python

      152.3K
      124.8K
      6.5K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      152.3K
      124.8K
      + 1
      6.5K
      PROS OF PYTHON
      • 1.1K
        Great libraries
      • 933
        Readable code
      • 824
        Beautiful code
      • 772
        Rapid development
      • 674
        Large community
      • 420
        Open source
      • 380
        Elegant
      • 270
        Great community
      • 262
        Object oriented
      • 209
        Dynamic typing
      • 71
        Great standard library
      • 53
        Very fast
      • 50
        Functional programming
      • 37
        Scientific computing
      • 36
        Easy to learn
      • 31
        Great documentation
      • 25
        Matlab alternative
      • 23
        Productivity
      • 23
        Easy to read
      • 20
        Simple is better than complex
      • 18
        It's the way I think
      • 17
        Imperative
      • 15
        Very programmer and non-programmer friendly
      • 15
        Free
      • 14
        Powerfull language
      • 14
        Powerful
      • 13
        Fast and simple
      • 12
        Scripting
      • 11
        Machine learning support
      • 9
        Explicit is better than implicit
      • 8
        Ease of development
      • 8
        Unlimited power
      • 8
        Clear and easy and powerfull
      • 7
        Import antigravity
      • 6
        Print "life is short, use python"
      • 6
        It's lean and fun to code
      • 5
        Fast coding and good for competitions
      • 5
        Flat is better than nested
      • 5
        There should be one-- and preferably only one --obvious
      • 5
        Python has great libraries for data processing
      • 5
        High Documented language
      • 5
        I love snakes
      • 5
        Although practicality beats purity
      • 5
        Great for tooling
      • 4
        Readability counts
      • 3
        Plotting
      • 3
        CG industry needs
      • 3
        Beautiful is better than ugly
      • 3
        Complex is better than complicated
      • 3
        Great for analytics
      • 3
        Multiple Inheritence
      • 3
        Now is better than never
      • 3
        Lists, tuples, dictionaries
      • 3
        Rapid Prototyping
      • 3
        Socially engaged community
      • 2
        List comprehensions
      • 2
        Web scraping
      • 2
        Many types of collections
      • 2
        Ys
      • 2
        Easy to setup and run smooth
      • 2
        Generators
      • 2
        Special cases aren't special enough to break the rules
      • 2
        If the implementation is hard to explain, it's a bad id
      • 2
        If the implementation is easy to explain, it may be a g
      • 2
        Simple and easy to learn
      • 2
        Import this
      • 2
        No cruft
      • 2
        Easy to learn and use
      • 1
        Better outcome
      • 1
        It is Very easy , simple and will you be love programmi
      • 1
        Powerful language for AI
      • 1
        Should START with this but not STICK with This
      • 1
        Flexible and easy
      • 1
        Batteries included
      • 1
        Good
      • 1
        A-to-Z
      • 1
        Only one way to do it
      • 1
        Because of Netflix
      • 1
        Pip install everything
      • 0
        Powerful
      • 0
        Pro
      CONS OF PYTHON
      • 51
        Still divided between python 2 and python 3
      • 29
        Performance impact
      • 26
        Poor syntax for anonymous functions
      • 21
        GIL
      • 19
        Package management is a mess
      • 14
        Too imperative-oriented
      • 12
        Dynamic typing
      • 12
        Hard to understand
      • 10
        Very slow
      • 8
        Not everything is expression
      • 7
        Indentations matter a lot
      • 7
        Explicit self parameter in methods
      • 6
        No anonymous functions
      • 6
        Poor DSL capabilities
      • 6
        Incredibly slow
      • 6
        Requires C functions for dynamic modules
      • 5
        The "lisp style" whitespaces
      • 5
        Fake object-oriented programming
      • 5
        Hard to obfuscate
      • 5
        Threading
      • 4
        Circular import
      • 4
        The benevolent-dictator-for-life quit
      • 4
        Official documentation is unclear.
      • 4
        Lack of Syntax Sugar leads to "the pyramid of doom"
      • 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 · | 39 upvotes · 4.2M 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
      Director of Developer Marketing at Stream · | 35 upvotes · 1.4M 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
      JavaScript logo

      JavaScript

      224.5K
      173.9K
      7.8K
      Lightweight, interpreted, object-oriented language with first-class functions
      224.5K
      173.9K
      + 1
      7.8K
      PROS OF JAVASCRIPT
      • 1.6K
        Can be used on frontend/backend
      • 1.5K
        It's everywhere
      • 1.1K
        Lots of great frameworks
      • 887
        Fast
      • 736
        Light weight
      • 416
        Flexible
      • 383
        You can't get a device today that doesn't run js
      • 284
        Non-blocking i/o
      • 233
        Ubiquitousness
      • 188
        Expressive
      • 51
        Extended functionality to web pages
      • 44
        Relatively easy language
      • 42
        Executed on the client side
      • 26
        Relatively fast to the end user
      • 22
        Pure Javascript
      • 17
        Functional programming
      • 11
        Async
      • 8
        Setup is easy
      • 7
        Because I love functions
      • 7
        JavaScript is the New PHP
      • 7
        Like it or not, JS is part of the web standard
      • 7
        Its everywhere
      • 7
        Full-stack
      • 6
        Expansive community
      • 6
        Future Language of The Web
      • 6
        Can be used in backend, frontend and DB
      • 5
        Evolution of C
      • 5
        Everyone use it
      • 5
        Love-hate relationship
      • 5
        Easy to hire developers
      • 5
        Supports lambdas and closures
      • 5
        Agile, packages simple to use
      • 5
        Popularized Class-Less Architecture & Lambdas
      • 5
        For the good parts
      • 4
        Everywhere
      • 4
        Hard not to use
      • 4
        Promise relationship
      • 4
        Scope manipulation
      • 4
        It's fun
      • 4
        Client processing
      • 4
        Nice
      • 4
        Easy to make something
      • 4
        Can be used on frontend/backend/Mobile/create PRO Ui
      • 4
        Easy
      • 4
        Photoshop has 3 JS runtimes built in
      • 4
        Can be used both as frontend and backend as well
      • 4
        Most Popular Language in the World
      • 4
        It let's me use Babel & Typescript
      • 4
        What to add
      • 4
        Clojurescript
      • 4
        Function expressions are useful for callbacks
      • 4
        No need to use PHP
      • 4
        Its fun and fast
      • 4
        Powerful
      • 4
        Versitile
      • 4
        Client side JS uses the visitors CPU to save Server Res
      • 4
        1.6K Can be used on frontend/backend
      • 4
        Stockholm Syndrome
      • 3
        Because it is so simple and lightweight
      • 3
        Only Programming language on browser
      • 2
        JavaScript j.s
      • 2
        Acoperișul 0757604335
      CONS OF JAVASCRIPT
      • 21
        A constant moving target, too much churn
      • 20
        Horribly inconsistent
      • 14
        Javascript is the New PHP
      • 8
        No ability to monitor memory utilitization
      • 6
        Shows Zero output in case of ANY error
      • 5
        Can be ugly
      • 4
        Thinks strange results are better than errors
      • 2
        No GitHub
      • 1
        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 · | 39 upvotes · 4.2M 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
      PHP logo

      PHP

      112.5K
      56.5K
      4.5K
      A popular general-purpose scripting language that is especially suited to web development
      112.5K
      56.5K
      + 1
      4.5K
      PROS OF PHP
      • 942
        Large community
      • 806
        Open source
      • 759
        Easy deployment
      • 482
        Great frameworks
      • 385
        The best glue on the web
      • 234
        Continual improvements
      • 181
        Good old web
      • 142
        Web foundation
      • 133
        Community packages
      • 124
        Tool support
      • 33
        Used by wordpress
      • 31
        Excellent documentation
      • 26
        Used by Facebook
      • 23
        Because of Symfony
      • 19
        Dynamic Language
      • 15
        Cheap hosting
      • 14
        Awesome Language and easy to implement
      • 14
        Very powerful web language
      • 13
        Fast development
      • 11
        Easy to learn
      • 11
        Composer
      • 10
        Flexibility, syntax, extensibility
      • 10
        Because of Laravel
      • 8
        Easiest deployment
      • 7
        Readable Code
      • 7
        Short development lead times
      • 7
        Worst popularity quality ratio
      • 7
        Fastestest Time to Version 1.0 Deployments
      • 6
        Faster then ever
      • 6
        Fast
      • 6
        Most of the web uses it
      • 5
        Open source and large community
      • 5
        Simple, flexible yet Scalable
      • 4
        Has the best ecommerce(Magento,Prestashop,Opencart,etc)
      • 4
        Large community, easy setup, easy deployment, framework
      • 4
        Open source and great framework
      • 4
        Easy to use and learn
      • 4
        Cheap to own
      • 4
        Easy to learn, a big community, lot of frameworks
      • 4
        Is like one zip of air
      • 4
        I have no choice :(
      • 3
        Great developer experience
      • 2
        Hard not to use
      • 2
        FFI
      • 2
        Interpreted at the run time
      • 2
        Great flexibility. From fast prototyping to large apps
      • 2
        Used by STOMT
      • 2
        Fault tolerance
      • 2
        Safe the planet
      • 2
        Walk away
      CONS OF PHP
      • 20
        So easy to learn, good practices are hard to find
      • 16
        Inconsistent API
      • 8
        Fragmented community
      • 5
        Not secure
      • 2
        No routing system
      • 1
        Hard to debug
      • 1
        Old

      related PHP posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 44 upvotes · 1.7M 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
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.1M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      HTML5 logo

      HTML5

      99.5K
      79.9K
      2.2K
      5th major revision of the core language of the World Wide Web
      99.5K
      79.9K
      + 1
      2.2K
      PROS OF HTML5
      • 444
        New doctype
      • 388
        Local storage
      • 334
        Canvas
      • 285
        Semantic header and footer
      • 238
        Video element
      • 120
        Geolocation
      • 105
        Form autofocus
      • 98
        Email inputs
      • 84
        Editable content
      • 79
        Application caches
      • 9
        Cleaner Code
      • 9
        Easy to use
      • 4
        Easy
      • 4
        Semantical
      • 3
        Websockets
      • 3
        Better
      • 3
        Audio element
      • 3
        Modern
      • 2
        Content focused
      • 2
        Compatible
      • 2
        Portability
      • 2
        Semantic Header and Footer, Geolocation, New Doctype
      CONS OF HTML5
        Be the first to leave a con

        related HTML5 posts

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

        At FundsCorner, when we set out to pick up the front-end tech stack (around Dec 2017), we drove our decision based on the following considerations:

        (1) We were clear that we will NOT have a hybrid app. We will start with Responsive Web & once there is traction, we will rollout our Android App. However, we wanted to ensure that the users have a consistent experience on both the Web & the App. So, the front-end framework must also have a material design component library which we can choose from.

        (2) Before joining FundsCorner as a CTO, I had already worked with Angular. I enjoyed working with Angular, but I felt that I must choose something that will provide us with the fastest time from Concept to Reality.

        (3) I am strong proponent of segregating HTML & JavaScript. I.e. I was not for writing or generating HTML through JavaScript. Because, this will mean that the Front-end developers I have to hire will always be very strong on JavaScript alongside HTML5 & CSS. I was looking for a Framework that was on JavaScript but not HEAVY on JavaScript.

        (3) The first iteration of the web app was to be done by myself. But I was clear that when someone takes up the mantle, they will be able to come up the curve fast.

        In the end, Vue.js and Vuetify satisfied all the above criteria with aplomb! When I did our first POC on Vue.js I could not believe that front-end development could be this fast. The documentation was par excellence and all the required essentials that come along with the Framework (viz. Routing, Store, Validations) etc. were available from the same community! It was also a breeze to integrate with other JavaScript libraries (such as Amazon Cognito).

        By picking Vuetify, we were able to provide a consistent UI experience between our Web App and Native App, besides making the UI development ultra blazing fast!

        In the end, we were able to rollout our Web App in record 6 weeks (that included the end to end Loan Origination flow, Loans management system & Customer engagement module). www.jeyabalaji.com

        See more