2019-07-15
1898
#node
Paige Niedringhaus
3791
Jul 15, 2019 ⋅ 6 min read

Node.js 12: The future of server-side JavaScript

Paige Niedringhaus Digital marketer turned fullstack software engineer. JavaScript is my language of choice, but I enjoy learning new things in new languages.

Recent posts:

docker exec command

How to use docker exec to interact with running containers

Read up on how to interact with running containers using the docker exec command, and discover the difference between exec and attach.

Paul Akinyemi
Mar 25, 2025 ⋅ 4 min read
array filter method javascript

How to use the array filter() method in JavaScript

Learn about the array filter() method, from its basic syntax and use cases to more advanced techniques like chaining with map() and reduce().

Abiola Farounbi
Mar 24, 2025 ⋅ 5 min read
css vertical alignment

CSS vertical alignment: Best practices and examples

CSS has come a long way, making vertical alignment easier than ever. Learn about this concept and explore some of the best CSS vertical alignment techniques.

Facundo Corradini
Mar 23, 2025 ⋅ 8 min read
How to win clients with a Flutter web demo that feels real

How to win clients with a Flutter web demo that feels real

Use Flutter to build browser-based app demos that help clients visualize the product, speed up buy-in, and close deals faster.

Lewis Cianci
Mar 21, 2025 ⋅ 5 min read
View all posts

7 Replies to "Node.js 12: The future of server-side JavaScript"

  1. Clarification towards the end… Node is *NOT* single-threaded. The main JS runs in an event loop on a single thread. Async I/O (and often other compiled modules) run within a thread pool. Node doesn’t run server and browser, but the code can run on both.

    1. Clarification, not all async events are using thread pool, many of them use low level underlying OS functionality, but not separate thread polling. Http module is the best example.

  2. Also, node doesn’t have to “produce dynamic web content”. It does any type of server-side (or even command line) work. It can power a websocket server, PDF export service, host an event/message system or do any other work not related to rendering web pages.

Leave a Reply