Alternatives to D logo

Alternatives to D

D3.js, Pathfinder, C lang, JavaScript, and Python are the most popular alternatives and competitors to D.
270
122
+ 1
145

What is D and what are its top alternatives?

D is a language with C-like syntax and static typing. It pragmatically combines efficiency, control, and modeling power, with safety and programmer productivity.
D is a tool in the Languages category of a tech stack.

Top Alternatives to D

  • D3.js
    D3.js

    It is a JavaScript library for manipulating documents based on data. Emphasises on web standards gives you the full capabilities of modern browsers without tying yourself to a proprietary framework. ...

  • Pathfinder
    Pathfinder

    Pathfinder is a new real-time routing service in public beta. Pathfinder calculates routes for transportation services. These routes are updated in real time as users make transportation or delivery requests. Through our SDKs, applications can subscribe to routes as they change in response to user requests. ...

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

D alternatives & related posts

D3.js logo

D3.js

1.7K
1.6K
638
A JavaScript visualization library for HTML and SVG
1.7K
1.6K
+ 1
638
PROS OF D3.JS
  • 189
    Beautiful visualizations
  • 99
    Svg
  • 91
    Data-driven
  • 80
    Large set of examples
  • 60
    Data-driven documents
  • 23
    Visualization components
  • 20
    Transitions
  • 18
    Dynamic properties
  • 16
    Plugins
  • 11
    Transformation
  • 7
    Makes data interactive
  • 4
    Components
  • 4
    Enter and Exit
  • 3
    Exhaustive
  • 3
    Backed by the new york times
  • 3
    Open Source
  • 2
    Easy and beautiful
  • 1
    Angular 4
  • 1
    Awesome Community Support
  • 1
    Simple elegance
  • 1
    123
  • 1
    Templates, force template
CONS OF D3.JS
  • 10
    Beginners cant understand at all
  • 5
    Complex syntax
  • 1
    123

related D3.js posts

Tim Abbott
Shared insights
on
Plotly.jsPlotly.jsD3.jsD3.js
at

We use Plotly (just their open source stuff) for Zulip's user-facing and admin-facing statistics graphs because it's a reasonably well-designed JavaScript graphing library.

If you've tried using D3.js, it's a pretty poor developer experience, and that translates to spending a bunch of time getting the graphs one wants even for things that are conceptually pretty basic. Plotly isn't amazing (it's decent), but it's way better than than D3 unless you have very specialized needs.

See more

I'm a student, and I have a project to build an application (Visual analytics tool) that takes a Microsoft Excel file, cleans the data, and visualizes it. Also, the app should allow the user to filter and interact with it.

1- should I make it desktop application or web application? : I'm leaning toward (desktop)

2- D3.js OR Python?

3- better excel or CSV?

I'm a beginner Inspiration for interaction and look of the app: eventflow application.

See more
Pathfinder logo

Pathfinder

14
25
0
Routing as a service
14
25
+ 1
0
PROS OF PATHFINDER
    Be the first to leave a pro
    CONS OF PATHFINDER
      Be the first to leave a con

      related Pathfinder posts

      C lang logo

      C lang

      6.7K
      4.1K
      244
      One of the most widely used programming languages of all time
      6.7K
      4.1K
      + 1
      244
      PROS OF C LANG
      • 67
        Performance
      • 48
        Low-level
      • 35
        Portability
      • 28
        Hardware level
      • 19
        Embedded apps
      • 13
        Pure
      • 9
        Performance of assembler
      • 8
        Ubiquity
      • 5
        Great for embedded
      • 4
        Old
      • 3
        Compiles quickly
      • 2
        No garbage collection to slow it down
      • 2
        OpenMP
      • 1
        Gnu/linux interoperable
      CONS OF C LANG
      • 5
        Low-level
      • 3
        No built in support for concurrency
      • 2
        Lack of type safety
      • 2
        No built in support for parallelism (e.g. map-reduce)

      related C lang posts

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

      Why Uber developed H3, our open source grid system to make geospatial data visualization and exploration easier and more efficient:

      We decided to create H3 to combine the benefits of a hexagonal global grid system with a hierarchical indexing system. A global grid system usually requires at least two things: a map projection and a grid laid on top of the map. For map projection, we chose to use gnomonic projections centered on icosahedron faces. This projects from Earth as a sphere to an icosahedron, a twenty-sided platonic solid. The H3 grid is constructed by laying out 122 base cells over the Earth, with ten cells per face. H3 supports sixteen resolutions: https://eng.uber.com/h3/

      (GitHub Pages : https://uber.github.io/h3/#/ Written in C w/ bindings in Java & JavaScript )

      See more

      One important decision for delivering a platform independent solution with low memory footprint and minimal dependencies was the choice of the programming language. We considered a few from Python (there was already a reasonably large Python code base at Thumbtack), to Go (we were taking our first steps with it), and even Rust (too immature at the time).

      We ended up writing it in C. It was easy to meet all requirements with only one external dependency for implementing the web server, clearly no challenges running it on any of the Linux distributions we were maintaining, and arguably the implementation with the smallest memory footprint given the choices above.

      See more
      JavaScript logo

      JavaScript

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

      189.6K
      159.1K
      6.7K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      189.6K
      159.1K
      + 1
      6.7K
      PROS OF PYTHON
      • 1.1K
        Great libraries
      • 946
        Readable code
      • 833
        Beautiful code
      • 779
        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
        Scientific computing
      • 43
        Easy to learn
      • 33
        Great documentation
      • 26
        Matlab alternative
      • 25
        Productivity
      • 25
        Easy to read
      • 21
        Simple is better than complex
      • 18
        It's the way I think
      • 17
        Imperative
      • 15
        Very programmer and non-programmer friendly
      • 15
        Free
      • 14
        Powerfull language
      • 14
        Powerful
      • 13
        Machine learning support
      • 13
        Fast and simple
      • 12
        Scripting
      • 9
        Explicit is better than implicit
      • 8
        Clear and easy and powerfull
      • 8
        Unlimited power
      • 8
        Ease of development
      • 7
        Import antigravity
      • 6
        It's lean and fun to code
      • 6
        Print "life is short, use python"
      • 5
        Great for tooling
      • 5
        I love snakes
      • 5
        Flat is better than nested
      • 5
        Python has great libraries for data processing
      • 5
        Fast coding and good for competitions
      • 5
        There should be one-- and preferably only one --obvious
      • 5
        High Documented language
      • 5
        Although practicality beats purity
      • 4
        Rapid Prototyping
      • 4
        Readability counts
      • 3
        Great for analytics
      • 3
        Web scraping
      • 3
        Now is better than never
      • 3
        Plotting
      • 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
        Many types of collections
      • 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
        List comprehensions
      • 2
        Generators
      • 2
        Simple and easy to learn
      • 2
        Easy to setup and run smooth
      • 2
        Import this
      • 1
        Powerful language for AI
      • 1
        Because of Netflix
      • 1
        A-to-Z
      • 1
        Only one way to do it
      • 1
        Can understand easily who are new to programming
      • 1
        Flexible and easy
      • 1
        Better outcome
      • 1
        Batteries included
      • 1
        Good for hacking
      • 1
        Should START with this but not STICK with This
      • 1
        Pip install everything
      • 1
        It is Very easy , simple and will you be love programmi
      • 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.4M 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.7M 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

      125.3K
      67.9K
      4.6K
      A popular general-purpose scripting language that is especially suited to web development
      125.3K
      67.9K
      + 1
      4.6K
      PROS OF PHP
      • 948
        Large community
      • 812
        Open source
      • 763
        Easy deployment
      • 482
        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
        Very powerful web language
      • 14
        Fast development
      • 14
        Awesome Language and easy to implement
      • 12
        Composer
      • 10
        Because of Laravel
      • 10
        Flexibility, syntax, extensibility
      • 8
        Easiest deployment
      • 7
        Fast
      • 7
        Short development lead times
      • 7
        Fastestest Time to Version 1.0 Deployments
      • 7
        Worst popularity quality ratio
      • 7
        Readable Code
      • 6
        Most of the web uses it
      • 6
        Faster then ever
      • 5
        Open source and large community
      • 5
        Simple, flexible yet Scalable
      • 4
        Easy to use and learn
      • 4
        Open source and great framework
      • 4
        Large community, easy setup, easy deployment, framework
      • 4
        Has the best ecommerce(Magento,Prestashop,Opencart,etc)
      • 4
        I have no choice :(
      • 4
        Is like one zip of air
      • 4
        Cheap to own
      • 4
        Easy to learn, a big community, lot of frameworks
      • 3
        Great developer experience
      • 2
        Hard not to use
      • 2
        Walk away
      • 2
        Fault tolerance
      • 2
        Used by STOMT
      • 2
        Great flexibility. From fast prototyping to large apps
      • 2
        Interpreted at the run time
      • 2
        FFI
      • 2
        Safe the planet
      • 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.1M 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 · 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

      120.9K
      100.5K
      2.2K
      5th major revision of the core language of the World Wide Web
      120.9K
      100.5K
      + 1
      2.2K
      PROS OF HTML5
      • 447
        New doctype
      • 389
        Local storage
      • 334
        Canvas
      • 285
        Semantic header and footer
      • 239
        Video element
      • 121
        Geolocation
      • 105
        Form autofocus
      • 99
        Email inputs
      • 85
        Editable content
      • 79
        Application caches
      • 10
        Easy to use
      • 9
        Cleaner Code
      • 4
        Easy
      • 4
        Semantical
      • 3
        Modern
      • 3
        Better
      • 3
        Audio element
      • 3
        Websockets
      • 2
        Content focused
      • 2
        Compatible
      • 2
        Portability
      • 2
        Semantic Header and Footer, Geolocation, New Doctype
      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 · 1.9M 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 · 70.3K 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

      107.7K
      83.5K
      3.7K
      A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
      107.7K
      83.5K
      + 1
      3.7K
      PROS OF JAVA
      • 591
        Great libraries
      • 444
        Widely used
      • 400
        Excellent tooling
      • 389
        Huge amount of documentation available
      • 332
        Large pool of developers available
      • 204
        Open source
      • 201
        Excellent performance
      • 155
        Great development
      • 149
        Vast array of 3rd party libraries
      • 148
        Used for android
      • 60
        Compiled Language
      • 49
        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
      • 21
        Cross Platform Enterprise Integration
      • 20
        Good amount of APIs
      • 20
        Universal platform
      • 18
        Great Support
      • 14
        Great ecosystem
      • 11
        Backward compatible
      • 11
        Lots of boilerplate
      • 10
        Everywhere
      • 9
        Excellent SDK - JDK
      • 7
        Static typing
      • 7
        It's Java
      • 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
      • 32
        Verbosity
      • 27
        NullpointerException
      • 16
        Overcomplexity is praised in community culture
      • 14
        Nightmare to Write
      • 11
        Boiler plate code
      • 8
        Classpath hell prior to Java 9
      • 6
        No REPL
      • 4
        No property
      • 2
        Non-intuitive generic implementation
      • 2
        There is not optional parameter
      • 2
        Code are too long
      • 2
        Floating-point errors
      • 1
        Returning Wildcard Types
      • 1
        Java's too statically, stronglly, and strictly typed
      • 1
        Terrbible compared to Python/Batch Perormence

      related Java posts

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