Alternatives to Fabric.js logo

Alternatives to Fabric.js

Raphael, JavaScript, Python, jQuery, and React are the most popular alternatives and competitors to Fabric.js.
50
153
+ 1
0

What is Fabric.js and what are its top alternatives?

It provides interactive object model on top of canvas element. Fabric also has SVG-to-canvas (and canvas-to-SVG) parser. Using Fabric.js, you can create and populate objects on canvas; objects like simple geometrical shapes
Fabric.js is a tool in the Monitoring Tools category of a tech stack.
Fabric.js is an open source tool with 23.8K GitHub stars and 3.2K GitHub forks. Here’s a link to Fabric.js's open source repository on GitHub

Top Alternatives to Fabric.js

  • Raphael
    Raphael

    It is a cross-browser JavaScript library that draws Vector graphics for web sites. It will use SVG for most browsers, but will use VML for older versions of Internet Explorer. ...

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

  • jQuery
    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

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

Fabric.js alternatives & related posts

Raphael logo

Raphael

333
31
0
JavaScript library that draws Vector graphics for web sites
333
31
+ 1
0
PROS OF RAPHAEL
    Be the first to leave a pro
    CONS OF RAPHAEL
      Be the first to leave a con

      related Raphael posts

      JavaScript logo

      JavaScript

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

      200.6K
      169.6K
      6.7K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      200.6K
      169.6K
      + 1
      6.7K
      PROS OF PYTHON
      • 1.1K
        Great libraries
      • 947
        Readable code
      • 835
        Beautiful code
      • 780
        Rapid development
      • 682
        Large community
      • 426
        Open source
      • 385
        Elegant
      • 278
        Great community
      • 268
        Object oriented
      • 214
        Dynamic typing
      • 75
        Great standard library
      • 56
        Very fast
      • 51
        Functional programming
      • 43
        Easy to learn
      • 43
        Scientific computing
      • 33
        Great documentation
      • 26
        Matlab alternative
      • 25
        Easy to read
      • 25
        Productivity
      • 21
        Simple is better than complex
      • 18
        It's the way I think
      • 17
        Imperative
      • 15
        Free
      • 15
        Very programmer and non-programmer friendly
      • 14
        Machine learning support
      • 14
        Powerfull language
      • 14
        Powerful
      • 13
        Fast and simple
      • 12
        Scripting
      • 9
        Explicit is better than implicit
      • 8
        Ease of development
      • 8
        Clear and easy and powerfull
      • 8
        Unlimited power
      • 7
        Import antigravity
      • 6
        It's lean and fun to code
      • 6
        Print "life is short, use python"
      • 5
        Python has great libraries for data processing
      • 5
        High Documented language
      • 5
        Fast coding and good for competitions
      • 5
        I love snakes
      • 5
        Great for tooling
      • 5
        Flat is better than nested
      • 5
        There should be one-- and preferably only one --obvious
      • 5
        Although practicality beats purity
      • 4
        Readability counts
      • 4
        Rapid Prototyping
      • 3
        Plotting
      • 3
        Web scraping
      • 3
        Now is better than never
      • 3
        Great for analytics
      • 3
        Lists, tuples, dictionaries
      • 3
        Socially engaged community
      • 3
        Complex is better than complicated
      • 3
        Multiple Inheritence
      • 3
        Beautiful is better than ugly
      • 3
        CG industry needs
      • 2
        No cruft
      • 2
        Easy to learn and use
      • 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
        Many types of collections
      • 2
        List comprehensions
      • 2
        Simple and easy to learn
      • 2
        Generators
      • 2
        Easy to setup and run smooth
      • 2
        Import this
      • 1
        Better outcome
      • 1
        Good for hacking
      • 1
        Powerful language for AI
      • 1
        Should START with this but not STICK with This
      • 1
        Because of Netflix
      • 1
        A-to-Z
      • 1
        Only one way to do it
      • 1
        Flexible and easy
      • 1
        Batteries included
      • 1
        It is Very easy , simple and will you be love programmi
      • 1
        Can understand easily who are new to programming
      • 1
        Pip install everything
      • 0
        Powerful
      CONS OF PYTHON
      • 51
        Still divided between python 2 and python 3
      • 28
        Performance impact
      • 26
        Poor syntax for anonymous functions
      • 21
        GIL
      • 19
        Package management is a mess
      • 14
        Too imperative-oriented
      • 12
        Hard to understand
      • 12
        Dynamic typing
      • 10
        Very slow
      • 8
        Not everything is expression
      • 7
        Explicit self parameter in methods
      • 7
        Indentations matter a lot
      • 6
        Poor DSL capabilities
      • 6
        Incredibly slow
      • 6
        No anonymous functions
      • 6
        Requires C functions for dynamic modules
      • 5
        Hard to obfuscate
      • 5
        Threading
      • 5
        Fake object-oriented programming
      • 5
        The "lisp style" whitespaces
      • 4
        Official documentation is unclear.
      • 4
        Circular import
      • 4
        Lack of Syntax Sugar leads to "the pyramid of doom"
      • 4
        Not suitable for autocomplete
      • 4
        The benevolent-dictator-for-life quit
      • 2
        Meta classes
      • 1
        Training wheels (forced indentation)

      related Python posts

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

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

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

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

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

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

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

      See more
      Nick Parsons
      Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 1.8M 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
      jQuery logo

      jQuery

      181.9K
      60.6K
      6.6K
      The Write Less, Do More, JavaScript Library.
      181.9K
      60.6K
      + 1
      6.6K
      PROS OF JQUERY
      • 1.3K
        Cross-browser
      • 957
        Dom manipulation
      • 808
        Power
      • 660
        Open source
      • 610
        Plugins
      • 458
        Easy
      • 395
        Popular
      • 350
        Feature-rich
      • 281
        Html5
      • 227
        Light weight
      • 92
        Simple
      • 84
        Great community
      • 79
        CSS3 Compliant
      • 69
        Mobile friendly
      • 67
        Fast
      • 43
        Intuitive
      • 42
        Swiss Army knife for webdev
      • 35
        Huge Community
      • 11
        Easy to learn
      • 4
        Clean code
      • 3
        Because of Ajax request :)
      • 2
        Just awesome
      • 2
        Used everywhere
      • 2
        Powerful
      • 2
        Nice
      • 1
        Widely Used
      • 1
        Improves productivity
      • 1
        Open Source, Simple, Easy Setup
      • 1
        It Just Works
      • 1
        Industry acceptance
      • 1
        Allows great manipulation of HTML and CSS
      • 1
        Javascript
      • 1
        Easy Setup
      CONS OF JQUERY
      • 6
        Large size
      • 5
        Sometimes inconsistent API
      • 5
        Encourages DOM as primary data source
      • 2
        Live events is overly complex feature

      related jQuery posts

      Kir Shatrov
      Engineering Lead at Shopify · | 22 upvotes · 880.3K views

      The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

      Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

      #FrameworksFullStack #Languages

      See more
      Ganesa Vijayakumar
      Full Stack Coder | Technical Lead · | 19 upvotes · 3.3M views

      I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

      I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

      As per my work experience and knowledge, I have chosen the followings stacks to this mission.

      UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

      Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

      Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

      Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

      Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

      Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

      Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

      Happy Coding! Suggestions are welcome! :)

      Thanks, Ganesa

      See more
      React logo

      React

      146.8K
      121.4K
      4K
      A JavaScript library for building user interfaces
      146.8K
      121.4K
      + 1
      4K
      PROS OF REACT
      • 801
        Components
      • 663
        Virtual dom
      • 572
        Performance
      • 500
        Simplicity
      • 442
        Composable
      • 183
        Data flow
      • 165
        Declarative
      • 126
        Isn't an mvc framework
      • 116
        Reactive updates
      • 113
        Explicit app state
      • 44
        JSX
      • 27
        Learn once, write everywhere
      • 20
        Uni-directional data flow
      • 20
        Easy to Use
      • 16
        Works great with Flux Architecture
      • 11
        Great perfomance
      • 9
        Built by Facebook
      • 9
        Javascript
      • 7
        TypeScript support
      • 6
        Speed
      • 5
        Hooks
      • 5
        Excellent Documentation
      • 5
        Props
      • 5
        Functional
      • 5
        Easy as Lego
      • 5
        Closer to standard JavaScript and HTML than others
      • 5
        Cross-platform
      • 5
        Server Side Rendering
      • 5
        Feels like the 90s
      • 5
        Easy to start
      • 5
        Awesome
      • 5
        Scalable
      • 4
        Strong Community
      • 4
        Server side views
      • 4
        Fancy third party tools
      • 4
        Scales super well
      • 4
        Start simple
      • 4
        Super easy
      • 3
        Simple, easy to reason about and makes you productive
      • 3
        Fast evolving
      • 3
        SSR
      • 3
        Great migration pathway for older systems
      • 3
        Rich ecosystem
      • 3
        Simple
      • 3
        Has functional components
      • 3
        Allows creating single page applications
      • 3
        Has arrow functions
      • 3
        Very gentle learning curve
      • 3
        Sdfsdfsdf
      • 3
        Beautiful and Neat Component Management
      • 3
        Just the View of MVC
      • 2
        Split your UI into components with one true state
      • 2
        Fragments
      • 2
        Sharable
      • 2
        Every decision architecture wise makes sense
      • 2
        Permissively-licensed
      • 1
        Image upload
      • 1
        HTML-like
      • 1
        Recharts
      CONS OF REACT
      • 38
        Requires discipline to keep architecture organized
      • 27
        No predefined way to structure your app
      • 26
        Need to be familiar with lots of third party packages
      • 10
        JSX
      • 8
        Not enterprise friendly
      • 6
        One-way binding only
      • 3
        State consistency with backend neglected
      • 3
        Bad Documentation
      • 2
        Paradigms change too fast
      • 2
        Error boundary is needed

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 2.3M views

      I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

      See more
      Adebayo Akinlaja
      Engineering Manager at Andela · | 29 upvotes · 1.6M views

      I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

      A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

      In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

      If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

      See more
      PHP logo

      PHP

      129.4K
      71.6K
      4.6K
      A popular general-purpose scripting language that is especially suited to web development
      129.4K
      71.6K
      + 1
      4.6K
      PROS OF PHP
      • 948
        Large community
      • 814
        Open source
      • 763
        Easy deployment
      • 484
        Great frameworks
      • 384
        The best glue on the web
      • 234
        Continual improvements
      • 183
        Good old web
      • 145
        Web foundation
      • 134
        Community packages
      • 124
        Tool support
      • 35
        Used by wordpress
      • 33
        Excellent documentation
      • 28
        Used by Facebook
      • 23
        Because of Symfony
      • 21
        Dynamic Language
      • 16
        Cheap hosting
      • 15
        Easy to learn
      • 14
        Awesome Language and easy to implement
      • 14
        Fast development
      • 14
        Very powerful web language
      • 12
        Composer
      • 11
        Flexibility, syntax, extensibility
      • 10
        Because of Laravel
      • 8
        Easiest deployment
      • 7
        Worst popularity quality ratio
      • 7
        Fastestest Time to Version 1.0 Deployments
      • 7
        Fast
      • 7
        Readable Code
      • 7
        Short development lead times
      • 6
        Faster then ever
      • 6
        Most of the web uses it
      • 5
        Open source and large community
      • 5
        Simple, flexible yet Scalable
      • 4
        Easy to learn, a big community, lot of frameworks
      • 4
        Has the best ecommerce(Magento,Prestashop,Opencart,etc)
      • 4
        Is like one zip of air
      • 4
        Open source and great framework
      • 4
        Large community, easy setup, easy deployment, framework
      • 4
        Easy to use and learn
      • 4
        Cheap to own
      • 4
        I have no choice :(
      • 3
        Great developer experience
      • 2
        Great flexibility. From fast prototyping to large apps
      • 2
        Interpreted at the run time
      • 2
        FFI
      • 2
        Safe the planet
      • 2
        Hard not to use
      • 2
        Used by STOMT
      • 2
        Fault tolerance
      • 2
        Walk away
      • 1
        Simplesaml
      • 1
        Secure
      • 0
        Secure
      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 · 2.3M 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 · | 26 upvotes · 3.3M 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

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

      related HTML5 posts

      Jonathan Pugh
      Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2M 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
      Paul Morgan
      Researcher at Working on it · | 25 upvotes · 116.7K views
      Shared insights
      on
      JavaJavaCSS 3CSS 3HTML5HTML5

      Hey everyone, I have a matrix chart drawn in HTML5/CSS 3 dominantly using CSS grid. I would like to add interactive features and am unsure about the best tool. My programming knowledge is limited to 2 semesters of Java in college, so I'd have to learn the language as I go. I am open to anything, but the selected languages would be useful in future projects.

      Here are the features I am attempting to add to the site linked as my blog:

      • Assign over 120 attributes each to over 400 elements (probably in a DB)

      • Procedurally position elements in a matrix chart based on user-inputted filters (filtering and searching)

      • Procedurally position matrix elements based on attributes weighted by user-input

      • Change style of elements based on user input (highlighting)

      • Allow saving matrix chart states to be revisited or shared

      • Provide a user-friendly interface for users to submit the above input

      • Build several columns or matrices that are separate but related and seamless to the viewer

      See more
      Java logo

      Java

      113.4K
      88.2K
      3.7K
      A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
      113.4K
      88.2K
      + 1
      3.7K
      PROS OF JAVA
      • 593
        Great libraries
      • 444
        Widely used
      • 400
        Excellent tooling
      • 390
        Huge amount of documentation available
      • 333
        Large pool of developers available
      • 205
        Open source
      • 201
        Excellent performance
      • 155
        Great development
      • 149
        Vast array of 3rd party libraries
      • 148
        Used for android
      • 60
        Compiled Language
      • 51
        Used for Web
      • 46
        Managed memory
      • 45
        High Performance
      • 44
        Native threads
      • 43
        Statically typed
      • 35
        Easy to read
      • 33
        Great Community
      • 29
        Reliable platform
      • 24
        Sturdy garbage collection
      • 24
        JVM compatibility
      • 22
        Cross Platform Enterprise Integration
      • 20
        Universal platform
      • 20
        Good amount of APIs
      • 18
        Great Support
      • 14
        Great ecosystem
      • 11
        Backward compatible
      • 11
        Lots of boilerplate
      • 10
        Everywhere
      • 9
        Excellent SDK - JDK
      • 7
        It's Java
      • 7
        Static typing
      • 6
        Mature language thus stable systems
      • 6
        Better than Ruby
      • 6
        Long term language
      • 6
        Cross-platform
      • 6
        Portability
      • 5
        Clojure
      • 5
        Vast Collections Library
      • 5
        Used for Android development
      • 4
        Most developers favorite
      • 4
        Old tech
      • 3
        Javadoc
      • 3
        Stable platform, which many new languages depend on
      • 3
        History
      • 3
        Testable
      • 3
        Best martial for design
      • 3
        Great Structure
      • 2
        Faster than python
      • 2
        Type Safe
      CONS OF JAVA
      • 33
        Verbosity
      • 27
        NullpointerException
      • 16
        Nightmare to Write
      • 16
        Overcomplexity is praised in community culture
      • 12
        Boiler plate code
      • 8
        Classpath hell prior to Java 9
      • 6
        No REPL
      • 4
        No property
      • 3
        Code are too long
      • 2
        Non-intuitive generic implementation
      • 2
        There is not optional parameter
      • 2
        Floating-point errors
      • 1
        Java's too statically, stronglly, and strictly typed
      • 1
        Returning Wildcard Types
      • 1
        Terrbible compared to Python/Batch Perormence

      related Java posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.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 · | 28 upvotes · 1.8M 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