The Stack Overflow platform has recently published the results of its popular annual Developer Survey. This year, more than 70,000 developers from all over the world took part in this research project and shared their views on various aspects of a programmer’s life. But we’ll focus on the most intriguing part of the survey - technology rankings.
Angular is still one of the most widely used front-end framework despite a high level of competition in this segment. To maintain developers' interest to the product at a high level, the Angular team regularly updates the framework with new features and improvements. So meet Angular 14.
This major update includes a range of novelties, but two of them deserve our special attention. The first long-awaited feature is the possibility to apply strict typing for Angular Reactive forms. It will help to detect many common errors in TypeScript code. Thus, Angular developers will be able to create much safer forms, especially when dealing with deeply nested complex cases. But bear in mind that this feature is not applicable to template-driven forms.
Another big feature added in v14 is the concept of Angular stand-alone components. Such components will free developers from the necessity to use ngModules. Now they just can add dependencies directly to components rather than modules. This novelty has the potential to significantly simplify the process of building Angular apps, but currently it is in developer preview and may change in future versions. To become familiar with other new things provided in Angular 14, check out this article published in the Angular blog.
DHTMLX To Do List is a simple yet powerful widget that allows implementing a multifunctional to-do list that will function equally well in browsers of desktops and touch devices. This product has a user-friendly interface consisting of two main sections - a toolbar and a list. The first UI element serves for adding projects and conveniently reviewing them, while the second one helps to plan tasks for each project and monitor their completion. There are plenty of useful features for managing tasks. For instance, you can split complex tasks into subtasks, assign tasks to particular employees, specify due dates, categorize tasks with tags, manipulate tasks with the keyboard, use different modes for showing tasks completion, and more. Thanks to a flexible API, it is possible to change the toolbar structure or add custom controls to it and style any part of your to-do list in accordance with any project requirements.
The release of DHTMLX Kanban 1.2, despite its minor status, offers a range of important features designed to facilitate more productive work with large projects containing hundreds of tasks. The most notable changes introduced in v1.2 are built-in and custom sorting settings, lazy rendering, separate scrollbars for Kanban columns, and custom context menus for cards. Moreover, now you can also make use of the enhanced toolbar API and enjoy improved work on mobile devices.
There is also one great feature that is related to both of the DHTMLX products discussed above. The thing is that they can be easily integrated with each other as well as with other popular DHTMLX libraries (Gantt, Scheduler, Suite). Using these components together, you will be able to create a comprehensive business application without any compatibility issues.
If you are still using the Atom editor for working with your code, it is time to start thinking about a worthy substitute for this tool. The thing is that GitHub has announced that its popular editor will be discontinued at the end of the year. This decision is caused by the company’s inclination to concentrate efforts on enhancing the developer experience in the cloud by developing and promoting such technologies as Microsoft Visual Studio Code and GitHub Codespaces.
Interestingly, when Microsoft purchased GitHub in 2018, new owners were interested in keeping the Atom project alive. But priorities have changed and the Atom repository will be archived On December 15, 2022. More details are provided in this post.
Evan You together with his team gives the finishing touches to Vue 2.7 despite the fact that Vue 3 now being the default version of the framework. Why is that? The point is that many developers still cannot migrate to v3.0 because of various bottlenecks such as dependency compatibility, browser support requirements, etc. Therefore, it was decided to help those who still have to use Vue 2.x by backporting some of the key features from Vue 3. As a result, some features from Vue 3 will be available in v2.7 that is currently in beta.
At the same time, it should be noted that v2.7 will be the last release of Vue 2.x. It will be supported for 18 months (by the end of 2023) to give developers enough time for migration to Vue 3. Learn more details about the upcoming release in this post.
When it comes to making up your mind about the architecture type for a web project, developers commonly choose between two popular options - a single-page app (SPA) or a multi-page app (MPA). Although the choice is reduced to two options, it still can be a problem. If you are facing the same dilemma, you should visit the blog of a professional developer Nolan Lawson. Recently, he has posted a series of great articles that will help you to better understand the pros and cons of both approaches.
That’s it for now. Thanks for reading and see you soon.