Alternatives to Markdown logo

Alternatives to Markdown

MarkUp, JavaScript, Python, PHP, and HTML5 are the most popular alternatives and competitors to Markdown.
12.1K
8.4K
+ 1
962

What is Markdown and what are its top alternatives?

Markdown is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML.
Markdown is a tool in the Languages category of a tech stack.

Top Alternatives to Markdown

  • MarkUp

    MarkUp

    It allows you to turn your website into a dynamic canvas ready for feedback and collaboration. Streamline your feedback with a quicker, easier, and clearer process. ...

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

  • ES6

    ES6

    Goals for ECMAScript 2015 include providing better support for large applications, library creation, and for use of ECMAScript as a compilation target for other languages. Some of its major enhancements include modules, class declarations, lexical block scoping, iterators and generators, promises for asynchronous programming, destructuring patterns, and proper tail calls. ...

  • C#

    C#

    C# (pronounced "See Sharp") is a simple, modern, object-oriented, and type-safe programming language. C# has its roots in the C family of languages and will be immediately familiar to C, C++, Java, and JavaScript programmers. ...

Markdown alternatives & related posts

MarkUp logo

MarkUp

25
22
0
Turn your website into a dynamic canvas ready for feedback
25
22
+ 1
0
PROS OF MARKUP
    Be the first to leave a pro
    CONS OF MARKUP
      Be the first to leave a con

      related MarkUp posts

      JavaScript logo

      JavaScript

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

      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 · | 37 upvotes · 3.5M 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

      117K
      91.3K
      6.4K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      117K
      91.3K
      + 1
      6.4K
      PROS OF PYTHON
      • 1.1K
        Great libraries
      • 920
        Readable code
      • 814
        Beautiful code
      • 763
        Rapid development
      • 668
        Large community
      • 414
        Open source
      • 375
        Elegant
      • 264
        Great community
      • 257
        Object oriented
      • 206
        Dynamic typing
      • 68
        Great standard library
      • 51
        Very fast
      • 47
        Functional programming
      • 33
        Scientific computing
      • 31
        Easy to learn
      • 29
        Great documentation
      • 25
        Matlab alternative
      • 22
        Productivity
      • 21
        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
        Free
      • 14
        Powerful
      • 13
        Fast and simple
      • 13
        Powerfull language
      • 12
        Scripting
      • 9
        Machine learning support
      • 9
        Explicit is better than implicit
      • 8
        Ease of development
      • 8
        Unlimited power
      • 7
        Import antigravity
      • 7
        Clear and easy and powerfull
      • 6
        Print "life is short, use python"
      • 6
        It's lean and fun to code
      • 5
        Great for tooling
      • 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
        Flat is better than nested
      • 4
        Readability counts
      • 3
        Multiple Inheritence
      • 3
        Complex is better than complicated
      • 3
        Lists, tuples, dictionaries
      • 3
        Plotting
      • 3
        Rapid Prototyping
      • 3
        Great for analytics
      • 3
        Socially engaged community
      • 3
        Beautiful is better than ugly
      • 3
        CG industry needs
      • 2
        No cruft
      • 2
        Easy to learn and use
      • 2
        List comprehensions
      • 2
        Generators
      • 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
      • 2
        Simple and easy to learn
      • 2
        Import this
      • 1
        Powerful language for AI
      • 1
        Because of Netflix
      • 1
        Pip install everything
      • 1
        Web scraping
      • 1
        Better outcome
      • 1
        Batteries included
      • 1
        Easy to setup and run smooth
      • 1
        It is Very easy , simple and will you be love programmi
      • 1
        Only one way to do it
      • 1
        A-to-Z
      • 1
        Many types of collections
      • 1
        Flexible and easy
      • 0
        Pro
      • 0
        Powerful
      CONS OF PYTHON
      • 49
        Still divided between python 2 and python 3
      • 26
        Poor syntax for anonymous functions
      • 26
        Performance impact
      • 18
        GIL
      • 18
        Package management is a mess
      • 13
        Too imperative-oriented
      • 12
        Hard to understand
      • 10
        Dynamic typing
      • 8
        Very slow
      • 8
        Not everything is expression
      • 7
        Indentations matter a lot
      • 7
        Explicit self parameter in methods
      • 6
        Poor DSL capabilities
      • 6
        No anonymous functions
      • 6
        Requires C functions for dynamic modules
      • 5
        Hard to obfuscate
      • 5
        The "lisp style" whitespaces
      • 4
        The benevolent-dictator-for-life quit
      • 4
        Lack of Syntax Sugar leads to "the pyramid of doom"
      • 4
        Threading
      • 4
        Fake object-oriented programming
      • 4
        Incredibly slow
      • 3
        Not suitable for autocomplete
      • 3
        Official documentation is unclear.
      • 2
        Circular import
      • 1
        Training wheels (forced indentation)
      • 1
        Meta classes

      related Python posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M 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.2M 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

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

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

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

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

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

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 23 upvotes · 1.5M 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

      77.1K
      58K
      2.2K
      5th major revision of the core language of the World Wide Web
      77.1K
      58K
      + 1
      2.2K
      PROS OF HTML5
      • 442
        New doctype
      • 386
        Local storage
      • 334
        Canvas
      • 284
        Semantic header and footer
      • 237
        Video element
      • 119
        Geolocation
      • 104
        Form autofocus
      • 98
        Email inputs
      • 84
        Editable content
      • 79
        Application caches
      • 8
        Cleaner Code
      • 6
        Easy to use
      • 4
        Semantical
      • 3
        Websockets
      • 3
        Modern
      • 3
        Easy
      • 2
        Content focused
      • 2
        Compatible
      • 2
        Better
      • 2
        Portability
      • 2
        Audio element
      • 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.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
        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

        74.4K
        53.1K
        3.5K
        A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
        74.4K
        53.1K
        + 1
        3.5K
        PROS OF JAVA
        • 572
          Great libraries
        • 433
          Widely used
        • 396
          Excellent tooling
        • 378
          Huge amount of documentation available
        • 328
          Large pool of developers available
        • 197
          Open source
        • 192
          Excellent performance
        • 150
          Great development
        • 143
          Used for android
        • 142
          Vast array of 3rd party libraries
        • 54
          Compiled Language
        • 46
          Used for Web
        • 42
          Managed memory
        • 42
          Native threads
        • 40
          High Performance
        • 35
          Statically typed
        • 31
          Easy to read
        • 29
          Great Community
        • 25
          Reliable platform
        • 23
          JVM compatibility
        • 22
          Sturdy garbage collection
        • 19
          Cross Platform Enterprise Integration
        • 18
          Universal platform
        • 16
          Great Support
        • 16
          Good amount of APIs
        • 11
          Lots of boilerplate
        • 10
          Great ecosystem
        • 10
          Backward compatible
        • 9
          Everywhere
        • 7
          Excellent SDK - JDK
        • 6
          Mature language thus stable systems
        • 5
          Better than Ruby
        • 5
          Portability
        • 5
          Cross-platform
        • 5
          Static typing
        • 5
          Clojure
        • 5
          It's Java
        • 4
          Old tech
        • 4
          Vast Collections Library
        • 3
          Most developers favorite
        • 3
          Stable platform, which many new languages depend on
        • 3
          Long term language
        • 3
          Great Structure
        • 3
          Best martial for design
        • 3
          Used for Android development
        • 2
          Testable
        • 1
          Javadoc
        CONS OF JAVA
        • 29
          Verbosity
        • 23
          NullpointerException
        • 15
          Overcomplexity is praised in community culture
        • 13
          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 · | 37 upvotes · 3.5M 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 · 812.9K 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
        ES6 logo

        ES6

        38.3K
        28.6K
        156
        The next version of JavaScript
        38.3K
        28.6K
        + 1
        156
        PROS OF ES6
        • 105
          ES6 code is shorter than traditional JS
        • 49
          Module System Standardized
        • 1
          Extremly compact
        • 1
          Destructuring Assignment
        CONS OF ES6
        • 1
          Suffers from baggage

        related ES6 posts

        Nick Parsons
        Director of Developer Marketing at Stream · | 35 upvotes · 1.2M 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
        Ali Soueidan
        Creative Web Developer at Ali Soueidan · | 18 upvotes · 706K 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
        C# logo

        C#

        29.7K
        22.3K
        1.8K
        Simple, general-purpose, object-oriented programming language for the .NET platform
        29.7K
        22.3K
        + 1
        1.8K
        PROS OF C#
        • 320
          Cool syntax
        • 269
          Great lambda support
        • 244
          Great generics support
        • 188
          Language integrated query (linq)
        • 162
          Extension methods
        • 77
          Properties with get/set methods
        • 76
          Automatic garbage collection
        • 70
          Backed by microsoft
        • 58
          Automatic memory management
        • 54
          Amaizing Crossplatform Support
        • 29
          High performance
        • 28
          Beautiful
        • 25
          LINQ
        • 22
          Great ecosystem of community packages with Nuget
        • 19
          Vibrant developer community
        • 13
          Dead-simple asynchronous programming with async/await
        • 12
          Great readability
        • 9
          Strongly typed by default, dynamic typing when needed
        • 8
          Productive
        • 7
          Easy separation of config/application code
        • 7
          Visual Studio - Great IDE
        • 6
          Object oriented programming paradigm
        • 6
          Open source
        • 5
          Operator overloading
        • 5
          Events management using delegates
        • 5
          OOPS simplified with great syntax
        • 4
          Conditional compilation
        • 3
          Comprehensive platform libraries
        • 3
          Good language to teach OO concepts
        • 3
          Great community
        • 3
          Organized and clean
        • 3
          High-performance
        • 3
          Coherent language backed by an extensive CLR
        • 3
          Cool
        • 2
          Concise syntax, productivity designed
        • 2
          Unity
        • 2
          Top level code
        • 2
          Linq expressions
        • 1
          Lovely
        • 1
          Interfaces
        • 0
          Interfaces
        CONS OF C#
        • 11
          Poor x-platform GUI support
        • 6
          Closed source
        • 6
          Requires DllImportAttribute for getting stuff from unma
        • 5
          Fast and secure

        related C# posts

        Conor Myhrvold
        Tech Brand Mgr, Office of CTO at Uber · | 37 upvotes · 3.5M 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
        Yshay Yaacobi

        Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

        Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

        After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

        See more