Julian Cataldo
@juliancataldo.com
Or
"typescript.tsserver.useSyntaxServer": "never",
"editor.foldingStrategy": "auto",
"editor.linkedEditing": true
in a project settings.json, just to try.
"typescript.tsserver.useSyntaxServer": "never",
"editor.foldingStrategy": "auto",
"editor.linkedEditing": true
in a project settings.json, just to try.
August 12, 2025 at 5:16 AM
Or
"typescript.tsserver.useSyntaxServer": "never",
"editor.foldingStrategy": "auto",
"editor.linkedEditing": true
in a project settings.json, just to try.
"typescript.tsserver.useSyntaxServer": "never",
"editor.foldingStrategy": "auto",
"editor.linkedEditing": true
in a project settings.json, just to try.
Maybe this? `editor.experimental.preferTreeSitter`
github.com/microsoft/vs...
github.com/microsoft/vs...
Allow toggling `editor.experimental.preferTreeSitter` at runtime · Issue #227141 · microsoft/vscode
Currently: If it's disabled and I enable it, nothing changes. I must reload the window. If it's enabled and I disable it, all colors are gone. Enabling it back again does nothing. I must reload the...
github.com
August 12, 2025 at 5:15 AM
Maybe this? `editor.experimental.preferTreeSitter`
github.com/microsoft/vs...
github.com/microsoft/vs...
Reposted by Julian Cataldo
Now importNode and cloneNode have the same performance in Chrome: issues.chromium.org/issues/37124...
I'm happy frameworks can get simpler, but also because Lit, which always uses importNode, probably just got faster too.
Filing issues for browser implementation bugs is a good thing for everyone!
I'm happy frameworks can get simpler, but also because Lit, which always uses importNode, probably just got faster too.
Filing issues for browser implementation bugs is a good thing for everyone!
August 9, 2025 at 5:11 PM
Now importNode and cloneNode have the same performance in Chrome: issues.chromium.org/issues/37124...
I'm happy frameworks can get simpler, but also because Lit, which always uses importNode, probably just got faster too.
Filing issues for browser implementation bugs is a good thing for everyone!
I'm happy frameworks can get simpler, but also because Lit, which always uses importNode, probably just got faster too.
Filing issues for browser implementation bugs is a good thing for everyone!
The ported project:
github.com/JulianCatald...
github.com/JulianCatald...
GitHub - JulianCataldo/remark-lint-frontmatter-schema: Validate your Markdown frontmatter data against a JSON schema — remark-lint rule plugin
Validate your Markdown frontmatter data against a JSON schema — remark-lint rule plugin - JulianCataldo/remark-lint-frontmatter-schema
github.com
July 25, 2025 at 9:46 PM
The ported project:
github.com/JulianCatald...
github.com/JulianCatald...
You’re right. It’s all about choices! In my case, light mode in high luminosity environments, and dark when it’s not. Otherwise it’s blindening 😎
Thanks for the reading
Thanks for the reading
December 22, 2024 at 2:35 PM
You’re right. It’s all about choices! In my case, light mode in high luminosity environments, and dark when it’s not. Otherwise it’s blindening 😎
Thanks for the reading
Thanks for the reading
Same thing with Dark Mode.
It was an accessibility must for a long time, then it became some sort of "cool trend", but somehow a dispensable bonus.
It was an accessibility must for a long time, then it became some sort of "cool trend", but somehow a dispensable bonus.
December 22, 2024 at 1:17 PM
Same thing with Dark Mode.
It was an accessibility must for a long time, then it became some sort of "cool trend", but somehow a dispensable bonus.
It was an accessibility must for a long time, then it became some sort of "cool trend", but somehow a dispensable bonus.
I forgot one thing that had bitten me in the past : Syntax highlighting, in VSCode, is more prone to break on huge, complicated files. Breaking them up can help pinpoint oddities.
Often I don't get what's triggering colours weirdness.
Often I don't get what's triggering colours weirdness.
December 22, 2024 at 1:14 PM
I forgot one thing that had bitten me in the past : Syntax highlighting, in VSCode, is more prone to break on huge, complicated files. Breaking them up can help pinpoint oddities.
Often I don't get what's triggering colours weirdness.
Often I don't get what's triggering colours weirdness.
ESLint, Prettier, the TS LSP, etc. are going bananas on huge files :p GH won't even display it. Splitting eases the work on the IDE.
It's more about DX, I admit ^^.
It's more about DX, I admit ^^.
December 22, 2024 at 12:57 PM
ESLint, Prettier, the TS LSP, etc. are going bananas on huge files :p GH won't even display it. Splitting eases the work on the IDE.
It's more about DX, I admit ^^.
It's more about DX, I admit ^^.
All this popups are going more and more insane with each major macOS upgrades.
Sometimes, it feels like a maze. Huge productivity killer IMO. I don't want a Windows Vista computing experience 😒
Sometimes, it feels like a maze. Huge productivity killer IMO. I don't want a Windows Vista computing experience 😒
December 22, 2024 at 12:53 PM
All this popups are going more and more insane with each major macOS upgrades.
Sometimes, it feels like a maze. Huge productivity killer IMO. I don't want a Windows Vista computing experience 😒
Sometimes, it feels like a maze. Huge productivity killer IMO. I don't want a Windows Vista computing experience 😒