DEV Community

Top 5 Frontend and Backend Technologies Used by Developers in 2024

Dhruv Joshi on June 30, 2023

Frontend developers and backend developers must stay updated with the trend of technologies and frameworks and which one to use for efficient and f...

Read full post

Marcin • Jul 2 '23

Top 5 backend and no Laravel, really ?

Dhruv Joshi • Jul 2 '23

thanks to notify, will add it too.

Dhruv Joshi • Oct 16 '23

medium.com/@ermawinter08/top-front...

JoelBonetR 🥇 • Jul 3 '23 • Edited

A great amount of cons listed here are about the people abusing of a given pattern/workaround or misunderstanding the tech, instead issues of the tech itself, e.g. it's not Node's fault that you code a callback hell or that you try to process heavy computation tasks "as is" on it, Node is just a RE for Javascript 😅😂

Following the example, you could well design your app in a shape that uses callbacks when strictly necessary or even that doesn't use callbacks at all (e.g. making good use of promises).

The same way you may split heavy computational tasks into smaller ones and process them async whenever possible (even if you need to do X after Y, you can use events to trigger following steps asynchronously instead locking the thread on a single long, heavy task).

Even if you definitely can't, you may as well face the same issue in most of the languages (Python, PHP, Ruby... even Java or C# may bottleneck in some tasks), and the workaround is quite simple and widely used: code those heavy tasks in C++ and call those programs from Node by using the available InterOperability features.

Best regards 😁

motimash • Jul 3 '23 • Edited

Thank you for the article. I think you are a little confused between technology languages, and libraries.
Libraries and languages are not technology. Although node.js can be called a technology as it is an engine that build to compile application.

I just found it a confusing article for young developers.