DHTMLX delivers versatile JavaScript/HTML5 libraries and UI widgets designed for building modern enterprise web apps of any complexity. With these out-of-the-box components, web developers can streamline their coding processes and integrate advanced functionality, to reduce development time. The actual DHTMLX product lineup comprises a range of web-based tools that can cover most of the contemporary business needs. DHTMLX
$79
one-time fee lowest cost single component
Oracle Java SE
Score 8.0 out of 10
N/A
Oracle Java SE is a programming language and gives customers enterprise features that minimize the costs of deployment and maintenance of their Java-based IT environment.
N/A
Pricing
DHTMLX
Oracle Java SE
Editions & Modules
DHTMLX Gantt Individual - Professional Functionality with Standard Support
$699
one-time fee for 1 developer
DHTMLX Gantt Commercial - Professional Functionality with Premium Support
$1399
one-time fee for 5 developers
DHTMLX Gantt Enterprise - Professional Functionality with Premium Support
$2999
one-time fee for 20 developers
DHTMLX Gantt Ultimate - Professional Functionality with Ultimate Support
$5999
one-time fee for an unlimited number of developers
No answers on this topic
Offerings
Pricing Offerings
DHTMLX
Oracle Java SE
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
UI widgets are available standalone or "a la carte," or as part of bundles built around a theme (e.g. complete edition, scheduling components, planning components, etc.).
Rapid development of web applications: DHTMLX provides a set of pre-built UI widgets that can be easily integrated into web applications, which makes it well suited for developing applications quickly. DHTMLX is well suited for building enterprise-level applications that require complex UI elements and data visualization. DHTMLX is less appropriate for Simple applications: If you are building a simple application that does not require a complex UI, DHTMLX may be overkill, and you may be better off using a lighter-weight framework.
Oracle Java SE is well suited to long-running applications (e.g. servers). Java Swing (UI toolkit) is now rather outdated, lacking support for modern UI features. JavaFX, the potential replacement for Swing, has now been separated out of Java core. Ideally, there would be a path to migrate a large application incrementally from Swing to JavaFX, but due to different threading models and other aspects, it is difficult. At this point, it is probably better to use an embedded web browser (e.g. JxBrowser) to provide a modern UI in HTML/Javascript and keep just the business logic in Java.
Commercial Licensing in 2019. Oracle will charge commercial organizations using Java SE for upgrading to the latest bug fixes and updates. Organizations will now need to either limit their implementation of Java SE or may need to drop it altogether.
Slow Performance. Due to the all of the abstraction of the JVM, Java SE programs take much more resources to compile and run compared to Python.
Poor UI appearance on all of the major GUI libraries (Swing, SWT, etc.). Through Android Studio, it is easy to get a native look/feel for Java apps, but when it comes to desktops, the UI is far from acceptable (does not mimic the native OS's look/feel at all).
With regard to the two major components we used, namely the tabular representation and the graphical modeler, we were able to effectively replace the existing building blocks of our applications by integrating them. We were able to retain existing functionalities and benefit from a significant enhancement with what DHTMLX offers natively. This made it easy for us to get our end-users to adopt the change.
Oracle Java SE provides the new features along with timely security patches. New features like Record patterns and pattern matching for switches are very useful. With every new release of Java, it is getting better. Sequenced collections are also an interesting feature added to Java. With all these new features, backward compatibility is also maintained.
Java is such a mature product at this point that there is little support from the vendor that is needed. Various sources on the internet, and especially StackOverflow, provide a wealth of knowledge and advice. Areas that may benefit from support is when dealing with complex multithreading issues and security libraries.
We looked at Kendo UI for ASP.Net Core as it has a Gantt chart but it was not as close a fit to our requirements as the DHTMLX Gantt Resource Management component. We'd have had to do much more work to make this fit.
Chose to go with Java instead of Python or C++ due to the expertise on the ground with the technology, for its ease of integration with our heterogeneous setup of production servers, and for the third party library support which we've found was able to address some challenging aspects of our business problem.
The different versions make it harder to work with other companies where some use newer versions while some use older versions, costing time to make them compatible.
Licenses are getting to be costly, forcing us to consider OpenJDK as an alternative.
New features take time to learn. When someone starts using them, everyone has to take time to learn.
