Alternatives to HAML logo

Alternatives to HAML

Slim, Pug, YAML, JavaScript, and Python are the most popular alternatives and competitors to HAML.
443
315
+ 1
267

What is HAML and what are its top alternatives?

Haml is a markup language that’s used to cleanly and simply describe the HTML of any web document, without the use of inline code. Haml functions as a replacement for inline page templating systems such as PHP, ERB, and ASP. However, Haml avoids the need for explicitly coding HTML into the template, because it is actually an abstract description of the HTML, with some code to generate dynamic content.
HAML is a tool in the Languages category of a tech stack.
HAML is an open source tool with 3.6K GitHub stars and 565 GitHub forks. Here’s a link to HAML's open source repository on GitHub

Top Alternatives to HAML

  • Slim

    Slim

    Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself. ...

  • Pug

    Pug

    This project was formerly known as "Jade." Pug is a high performance template engine heavily influenced by Haml and implemented with JavaScript for Node.js and browsers. ...

  • YAML

    YAML

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

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

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

  • Java

    Java

    Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...

HAML alternatives & related posts

Slim logo

Slim

239
315
134
A PHP micro framework
239
315
+ 1
134
PROS OF SLIM
  • 29
    Microframework
  • 25
    API
  • 21
    Open source
  • 19
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Good document to upgrade from previous version
  • 5
    Clear and straightforward
  • 4
    Modular
CONS OF SLIM
    Be the first to leave a con

    related Slim posts

    Y. Taborda
    Shared insights
    on
    PHP
    Lumen
    Yii
    Slim

    I'm about to start a new project to build a REST API, and I got to this point: Yii2 Vs Lumen Vs Slim, I used Yii 1.1 a while a go and it was awesome, really easy to work with, as a developer you don't have to worry about almost anything, just setup the framework, get your php extensions, and start coding your app.

    But, I was told about performance and someone recomended Lumen or Slim to work with a micro framework and a less bloated framework, what worries me is the lack of advantages that Yii2 offers, ACF and RBAC as a native tool on the framework, gii, the model validations and all the security props already in it.

    Is it worth it? Is the performance so great on those frameworks to leave aside the advantages of a framework like Yii2?

    How do you suggest to make the test to prove wich one is better?

    PHP Lumen Yii Slim

    See more
    Pug logo

    Pug

    1.1K
    998
    418
    Robust, elegant, feature rich template engine for nodejs
    1.1K
    998
    + 1
    418
    PROS OF PUG
    • 130
      Elegant html
    • 86
      Great with nodejs
    • 54
      Very short syntax
    • 53
      Open source
    • 52
      Structured with indentation
    • 21
      Free
    • 4
      Gulp
    • 4
      It's not HAML
    • 3
      Difficult For Front End Developers,learn backend
    • 3
      Really similar to Slim (from Ruby fame)
    • 3
      Easy setup
    • 2
      Clean syntax
    • 2
      Readable code
    • 1
      Disdain for angled brackets
    CONS OF PUG
      Be the first to leave a con

      related Pug posts

      YAML logo

      YAML

      206
      133
      0
      A straightforward machine parsable data serialization format designed for human readability and interaction
      206
      133
      + 1
      0
      PROS OF YAML
        Be the first to leave a pro
        CONS OF YAML
          Be the first to leave a con

          related YAML posts

          JavaScript logo

          JavaScript

          192.5K
          147.2K
          7.7K
          Lightweight, interpreted, object-oriented language with first-class functions
          192.5K
          147.2K
          + 1
          7.7K
          PROS OF JAVASCRIPT
          • 1.6K
            Can be used on frontend/backend
          • 1.5K
            It's everywhere
          • 1.1K
            Lots of great frameworks
          • 884
            Fast
          • 733
            Light weight
          • 411
            Flexible
          • 376
            You can't get a device today that doesn't run js
          • 279
            Non-blocking i/o
          • 229
            Ubiquitousness
          • 184
            Expressive
          • 48
            Extended functionality to web pages
          • 42
            Relatively easy language
          • 39
            Executed on the client side
          • 24
            Relatively fast to the end user
          • 20
            Pure Javascript
          • 15
            Functional programming
          • 8
            Async
          • 6
            JavaScript is the New PHP
          • 6
            Because I love functions
          • 6
            Full-stack
          • 6
            Setup is easy
          • 5
            Expansive community
          • 5
            Its everywhere
          • 5
            Can be used in backend, frontend and DB
          • 5
            Future Language of The Web
          • 5
            Like it or not, JS is part of the web standard
          • 4
            Popularized Class-Less Architecture & Lambdas
          • 4
            Supports lambdas and closures
          • 4
            Evolution of C
          • 4
            For the good parts
          • 4
            Easy to hire developers
          • 4
            Everyone use it
          • 4
            Love-hate relationship
          • 3
            Everywhere
          • 3
            Promise relationship
          • 3
            Agile, packages simple to use
          • 3
            What to add
          • 3
            Easy to make something
          • 3
            Nice
          • 3
            Only Programming language on browser
          • 3
            Because it is so simple and lightweight
          • 3
            Can be used on frontend/backend/Mobile/create PRO Ui
          • 3
            Function expressions are useful for callbacks
          • 3
            Photoshop has 3 JS runtimes built in
          • 3
            No need to use PHP
          • 3
            Versitile
          • 3
            Most Popular Language in the World
          • 3
            Can be used both as frontend and backend as well
          • 3
            Easy
          • 3
            Clojurescript
          • 3
            Stockholm Syndrome
          • 3
            It let's me use Babel & Typescript
          • 3
            Client side JS uses the visitors CPU to save Server Res
          • 3
            Its fun and fast
          • 3
            1.6K Can be used on frontend/backend
          • 3
            Powerful
          • 3
            Scope manipulation
          • 3
            Hard not to use
          • 3
            Client processing
          • 3
            It's fun
          • 1
            Acoperișul 0757604335
          • 1
            JavaScript j.s
          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 · | 38 upvotes · 3.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

          131K
          105.2K
          6.5K
          A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
          131K
          105.2K
          + 1
          6.5K
          PROS OF PYTHON
          • 1.1K
            Great libraries
          • 927
            Readable code
          • 817
            Beautiful code
          • 768
            Rapid development
          • 671
            Large community
          • 418
            Open source
          • 379
            Elegant
          • 268
            Great community
          • 261
            Object oriented
          • 209
            Dynamic typing
          • 70
            Great standard library
          • 52
            Very fast
          • 48
            Functional programming
          • 35
            Scientific computing
          • 33
            Easy to learn
          • 30
            Great documentation
          • 25
            Matlab alternative
          • 23
            Productivity
          • 22
            Easy to read
          • 19
            Simple is better than complex
          • 17
            It's the way I think
          • 17
            Imperative
          • 15
            Very programmer and non-programmer friendly
          • 14
            Powerful
          • 14
            Free
          • 13
            Fast and simple
          • 13
            Powerfull language
          • 12
            Scripting
          • 9
            Machine learning support
          • 9
            Explicit is better than implicit
          • 8
            Unlimited power
          • 8
            Ease of development
          • 7
            Import antigravity
          • 7
            Clear and easy and powerfull
          • 6
            It's lean and fun to code
          • 6
            Print "life is short, use python"
          • 5
            Flat is better than nested
          • 5
            Fast coding and good for competitions
          • 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
            CG industry needs
          • 3
            Beautiful is better than ugly
          • 3
            Multiple Inheritence
          • 3
            Complex is better than complicated
          • 3
            Great for analytics
          • 3
            Socially engaged community
          • 3
            Rapid Prototyping
          • 3
            Lists, tuples, dictionaries
          • 3
            Plotting
          • 2
            Generators
          • 2
            Simple and easy to learn
          • 2
            Import this
          • 2
            No cruft
          • 2
            Easy to learn and use
          • 2
            List comprehensions
          • 2
            Special cases aren't special enough to break the rules
          • 2
            Now is better than never
          • 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
          • 1
            Many types of collections
          • 1
            Better outcome
          • 1
            Batteries included
          • 1
            Ys
          • 1
            Good
          • 1
            Pip install everything
          • 1
            Easy to setup and run smooth
          • 1
            Because of Netflix
          • 1
            Flexible and easy
          • 1
            Web scraping
          • 1
            Should START with this but not STICK with This
          • 1
            Powerful language for AI
          • 1
            It is Very easy , simple and will you be love programmi
          • 1
            Only one way to do it
          • 1
            A-to-Z
          • 0
            Pro
          • 0
            Powerful
          CONS OF PYTHON
          • 50
            Still divided between python 2 and python 3
          • 27
            Performance impact
          • 26
            Poor syntax for anonymous functions
          • 19
            Package management is a mess
          • 19
            GIL
          • 13
            Too imperative-oriented
          • 12
            Hard to understand
          • 11
            Dynamic typing
          • 9
            Very slow
          • 8
            Not everything is expression
          • 7
            Explicit self parameter in methods
          • 7
            Indentations matter a lot
          • 6
            Poor DSL capabilities
          • 6
            No anonymous functions
          • 6
            Requires C functions for dynamic modules
          • 5
            Threading
          • 5
            The "lisp style" whitespaces
          • 5
            Hard to obfuscate
          • 4
            Fake object-oriented programming
          • 4
            Incredibly slow
          • 4
            Lack of Syntax Sugar leads to "the pyramid of doom"
          • 4
            The benevolent-dictator-for-life quit
          • 3
            Official documentation is unclear.
          • 3
            Circular import
          • 3
            Not suitable for autocomplete
          • 1
            Training wheels (forced indentation)
          • 1
            Meta classes

          related Python posts

          Conor Myhrvold
          Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.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
          Director of Developer Marketing at Stream · | 35 upvotes · 1.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
          PHP logo

          PHP

          104.5K
          49.4K
          4.5K
          A popular general-purpose scripting language that is especially suited to web development
          104.5K
          49.4K
          + 1
          4.5K
          PROS OF PHP
          • 941
            Large community
          • 804
            Open source
          • 757
            Easy deployment
          • 481
            Great frameworks
          • 384
            The best glue on the web
          • 232
            Continual improvements
          • 180
            Good old web
          • 141
            Web foundation
          • 131
            Community packages
          • 123
            Tool support
          • 32
            Used by wordpress
          • 30
            Excellent documentation
          • 25
            Used by Facebook
          • 23
            Because of Symfony
          • 18
            Dynamic Language
          • 14
            Awesome Language and easy to implement
          • 13
            Very powerful web language
          • 13
            Cheap hosting
          • 13
            Fast development
          • 10
            Composer
          • 9
            Because of Laravel
          • 9
            Easy to learn
          • 9
            Flexibility, syntax, extensibility
          • 7
            Worst popularity quality ratio
          • 7
            Easiest deployment
          • 7
            Readable Code
          • 7
            Fastestest Time to Version 1.0 Deployments
          • 7
            Short development lead times
          • 6
            Fast
          • 6
            Most of the web uses it
          • 6
            Faster then ever
          • 5
            Open source and large community
          • 4
            I have no choice :(
          • 4
            Easy to learn, a big community, lot of frameworks
          • 4
            Cheap to own
          • 4
            Simple, flexible yet Scalable
          • 4
            Easy to use and learn
          • 3
            Great developer experience
          • 3
            Large community, easy setup, easy deployment, framework
          • 3
            Is like one zip of air
          • 3
            Open source and great framework
          • 3
            Has the best ecommerce(Magento,Prestashop,Opencart,etc)
          • 2
            FFI
          • 2
            Walk away
          • 2
            Safe the planet
          • 2
            Hard not to use
          • 2
            Fault tolerance
          • 2
            Interpreted at the run time
          • 2
            Great flexibility. From fast prototyping to large apps
          • 2
            Used by STOMT
          CONS OF PHP
          • 19
            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 · | 42 upvotes · 1.5M 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 · | 24 upvotes · 1.7M 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

          86.2K
          67K
          2.2K
          5th major revision of the core language of the World Wide Web
          86.2K
          67K
          + 1
          2.2K
          PROS OF HTML5
          • 444
            New doctype
          • 388
            Local storage
          • 334
            Canvas
          • 285
            Semantic header and footer
          • 237
            Video element
          • 120
            Geolocation
          • 105
            Form autofocus
          • 98
            Email inputs
          • 84
            Editable content
          • 79
            Application caches
          • 9
            Cleaner Code
          • 8
            Easy to use
          • 4
            Semantical
          • 4
            Easy
          • 3
            Websockets
          • 3
            Better
          • 3
            Modern
          • 3
            Audio element
          • 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.4M 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
            Java logo

            Java

            80.8K
            59.4K
            3.5K
            A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
            80.8K
            59.4K
            + 1
            3.5K
            PROS OF JAVA
            • 576
              Great libraries
            • 436
              Widely used
            • 396
              Excellent tooling
            • 380
              Huge amount of documentation available
            • 329
              Large pool of developers available
            • 198
              Open source
            • 194
              Excellent performance
            • 150
              Great development
            • 144
              Used for android
            • 143
              Vast array of 3rd party libraries
            • 54
              Compiled Language
            • 46
              Used for Web
            • 43
              Managed memory
            • 42
              Native threads
            • 41
              High Performance
            • 36
              Statically typed
            • 32
              Easy to read
            • 30
              Great Community
            • 26
              Reliable platform
            • 23
              JVM compatibility
            • 23
              Sturdy garbage collection
            • 19
              Cross Platform Enterprise Integration
            • 18
              Universal platform
            • 16
              Good amount of APIs
            • 16
              Great Support
            • 11
              Lots of boilerplate
            • 10
              Backward compatible
            • 10
              Great ecosystem
            • 9
              Everywhere
            • 7
              Excellent SDK - JDK
            • 6
              Mature language thus stable systems
            • 5
              Cross-platform
            • 5
              Portability
            • 5
              Better than Ruby
            • 5
              Static typing
            • 5
              It's Java
            • 5
              Clojure
            • 4
              Vast Collections Library
            • 4
              Long term language
            • 4
              Old tech
            • 3
              Best martial for design
            • 3
              Great Structure
            • 3
              Most developers favorite
            • 3
              Stable platform, which many new languages depend on
            • 3
              Used for Android development
            • 2
              Testable
            • 1
              Javadoc
            CONS OF JAVA
            • 29
              Verbosity
            • 24
              NullpointerException
            • 15
              Overcomplexity is praised in community culture
            • 14
              Nightmare to Write
            • 10
              Boiler plate code
            • 8
              Classpath hell prior to Java 9
            • 6
              No REPL
            • 4
              No property
            • 2
              Code are too long
            • 2
              There is not optional parameter
            • 2
              Floating-point errors
            • 1
              Terrbible compared to Python/Batch Perormence
            • 1
              Java's too statically, stronglly, and strictly typed
            • 1
              Non-intuitive generic implementation
            • 1
              Returning Wildcard Types

            related Java posts

            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M views

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

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

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

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

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

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

            See more
            Kamil Kowalski
            Lead Architect at Fresha · | 27 upvotes · 934.4K views

            When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

            See more