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:

Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Gemini CLI tutorial — Will it replace Windsurf and Cursor?

Discover how to use Gemini CLI, Google’s new open-source AI agent that brings Gemini directly to your terminal.

Chizaram Ken
Jul 10, 2025 ⋅ 8 min read
React & TypeScript: 10 Patterns For Writing Better Code

React & TypeScript: 10 patterns for writing better code

This article explores several proven patterns for writing safer, cleaner, and more readable code in React and TypeScript.

Peter Aideloje
Jul 10, 2025 ⋅ 11 min read
A Guide To Wrapper Vs. Container Classes In CSS

A guide to wrapper vs. container classes in CSS

A breakdown of the wrapper and container CSS classes, how they’re used in real-world code, and when it makes sense to use one over the other.

Temitope Oyedele
Jul 7, 2025 ⋅ 10 min read
Stagehand and Gemini logos on a gradient background symbolizing AI web automation

How to build a web-based AI agent with Stagehand and Gemini

This guide walks you through creating a web UI for an AI agent that browses, clicks, and extracts info from websites powered by Stagehand and Gemini.

Elijah Asaolu
Jul 4, 2025 ⋅ 8 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