miniblog.

← Back to all posts
Dec 20, 2018 at 15:34
Microsoft's Edge moving to Chromium will reduce browser diversity. However, Safari/WebKit has forked from Chromium. Presumably they'll diverge over time? Browser vendors influence *new* standards, and both Apple and Google will need to do implementation work.

Related Posts

Jun 24, 2026 at 10:49
3
TIL that LSP 3.18 was released this month! Several APIs now support richer content, such as tooltips or docs on code action kinds. Signature help continues to improve too, allowing you see more about a function at its call site.
Specification
This document describes the current 3.18.x version of the language server protocol and is under development. An implementation for node of the 3.18.x version...
Dec 4, 2025 at 10:37
71
Delighted to see that Typescript 7 is moving to conventional LSP for its IDE services!
Progress on TypeScript 7 - December 2025 - TypeScript
Progress on TypeScript 7 - December 2025 - TypeScript
Earlier this year, the TypeScript team announced that we’ve been porting the compiler and language service to native code to take advantage of better raw performance, memory usage, and parallelism. This effort (codenamed “Project Corsa”, and soon “TypeScript 7.0”) has been a significant undertaking, but we’ve made big strides in the past few months. We’re […]
Feb 15, 2025 at 23:12
In LSP, a position is represented as a line number and a column offset (in Unicode code units): https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position This is pretty elegant. You'll get the correct line regardless of encoding bugs, and the editor already knows the line number so it's cheap to compute.
Specification
This document describes the 3.17.x version of the language server protocol. An implementation for node of the 3.17.x version of the protocol can be found here.