Cursor vs. DHTMLX

Less appropriate for people who don't use LLMs to code but instead to create artifacts. Cursor is a fluid development platform, not something that will create an artifact to run in the cloud. Well designed to work on teams, to manage the code and how the LLMs interact with the code itself. Great for deep vibe coding.

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.

Incentivized

• API creation.
• Integrations
• Plan mode for large tasks.
• Refactoring.

Incentivized

• We got a response and fix for every issue we opened a ticket for
• The components are full with quite a lot of feature
• The team is responsiveness is very quick

• The CLI agent can be quite finicky via ACP.
• It can be hard to understand how much different models will cost.
• Support can be unresponsive.

Incentivized

• We would like to have more cell controls (like a Date Time Picker, Date Range Picker)
• In the cell editing mode we would like to have a better integration into the Angular world

Cursor is the best AI-powered IDE available today. The agents intelligently absorb context from the code, memory, and rules, and are capable of iterating with subagents until acceptance criteria is met.

Incentivized

Cursor is useful for all our developer team. Each and every team member use Cursor for coding and also Cursor has various models like composer, codex, claude and openai models which helps a lot for quality codings. Also Cursor help to create documents in md file format with markdown and preview which helps a lot.

Incentivized

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.

graphical user interface is really the thing that setting apart because other code harnesses are really focused on commandline interfaces but whenever you want a good graphical interface with all of the tools and workflow that us software developers we want I think that Cursor is the one that has done it the best out of all of the code harnesses that we’ve tried

Incentivized

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.

Incentivized

• Development speed increased at least 25%
• The result of the final Product is better than before/without it
• We use it as a standard now

Incentivized

• Rapid development of web applications
• Rich data visualization tools, which makes it ideal for building data-driven applications
• Suited for building enterprise-level applications

Incentivized