DHTMLX Scheduler VS bun

We are thrilled to present a highly anticipated release of DHTMLX Scheduler 7.0. It is another major step in the development of this JavaScript scheduling library. If the previous major update of Scheduler focused on the internal structure of the project, the new version is related to significant improvements on the user interface side.

For instance, the current unstable political and economic situation in the world certainly makes investors very cautious about financing any web project. It can be a serious problem for startups, where lack or shortage of investments often turn out to be an insurmountable obstacle. This year, we’ve launched a special DHTMLX discount program to assist startup businesses deliberating over the usage of our products in their apps. This initiative allows startups to purchase top DHTMLX JavaScript UI components (Gantt, Scheduler, Suite) with 70% discounts and benefit from them at the early stages of their web or cloud-based projects. In addition to a huge discount, this program provides personalized technical support and a large base of support materials.

Welcome to this tutorial, where we bring together two powerful tools: the DHTMLX Scheduler library and the Angular framework, to create a comprehensive hotel room booking application.

The new version of our JavaScript scheduling component was probably the most anticipated release of the last year. This quality-of-life update helped to make this library more developer-friendly thanks to significant changes under the hood. With these enhancements, we simplified the way new features will be added to Scheduler in future releases.

DHTMLX Scheduler is a pure JavaScript library for developing responsive event calendars with 10 views and a set of handy features. The timeline view allows users to create an unlimited number of events within a horizontally scrollable layout and edit their duration via drag-n-drop. Besides, users can create recurring events and multisection events that can be assigned to several resources.

As an answer to the challenges of the last twelve months, the company continued our course on providing full-featured and easily customizable JS tools for project management. DHTMLX released a JavaScript Kanban Board designed to help project managers with workflow visualization. The great thing about this tool is that it can be easily integrated with DHTMLX Gantt and Scheduler components in a single app for covering most of project management needs.

The State of Project Management 2021 annual report conducted by Wellingtone says that businesses often suffer from poor resource management. Creating advanced functionalities from scratch to deal with management challenges is a painstaking and time-consuming task. Meanwhile, JavaScript components provide a wide range of useful built-in features such as task assignment, resource allocation, progress tracking, work time estimation, reporting, and much more. There are even specialized libraries like a JavaScript Scheduler or Gantt chart, which can serve as the foundation for the whole application. Therefore, if you want to save time and avoid unnecessary bugs, you’d better use JavaScript components for such undertakings.

You may improve your Kanban experience and create a comprehensive project management solution by combining several products. Thus, for example, you may consider using DHTMLX Gantt chart or Scheduler event calendar.

DHTMLX JS Scheduler - go to the site This is a Google-like calendar component with 10 views for booking appointments. The demo of the hotel reservation can be seen here. It includes room types filtering, different statuses for the rooms and booking, drag-n-drop. Car rental demo is also shown. The features are similar.

It has a decent compatibility with both Jest and Vitest's APIs (you can track progress here so you can use it as almost a drop-in replacement for either. Just as Node's, it has describe/it, mock, test and others, but with the expect syntax (which I find more readable). For example:

In this third and final article in the series on HTML Streaming, we will explore the practical implementation of the Diff DOM Streaming library in web browsing. This approach will allow any website using web components to retain its state during browsing. We will discuss in detail how to achieve this step by step using VanillaJS and Bun.

At Node Conference 2023, Jarred Sumner (creator of Bun) showed a demo of server components in Bun, so there is at least partial support in that ecosystem. The Bun repo provides bun-plugin-server-components as the official plugin for server components. And while I haven’t looked at it in-depth, Marz claims to be a “React Server Components Framework for Bun”.

Continuously evolving, Bun is currently optimized for MacOS and Linux, with ongoing efforts towards Windows compatibility. Tailored for resource-constrained environments like serverless functions, it emerges as an ideal solution. The Bun team is committed to achieving comprehensive Node.js compatibility and seamless integration with prevalent frameworks. For those intrigued by Bun's potential and want to give it a try, more information is available on its website at https://bun.sh/.

Let’s say you are interested in learning more about Bun and probably give it a try. Bun has a website, where you can learn more about Bun and its features (including all the benchmark data captured in this issue), and here is the link.

Looks like it, it seems the 2% are mostly odd platform specific issues that the authors' did not deem very important (my assumption for the release happening anyway). AFAIK this[1] PR tries to fix them.

[1]: https://github.com/oven-sh/bun/pull/9729

Bun has a solution for it. First of all, it already has a list of trusted dependencies. For them, Bun will execute all necessary scripts by default. Otherwise, you can add it to trustedDependecies in your package.json file. In Bun community usage of trustedDependencies is a hot topic. There are several suggestions on how to improve it.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

I think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2]. But I suspect there's a much better way of detecting and using the different backends.

[0]: https://github.com/waygate-io/fs-js

[1]: https://github.com/waygate-io/http-js

[2]: https://github.com/oven-sh/bun/issues/7057