How we made the Deno language server faster
1–10 of 19 posts
Re: How we made the Deno language server faster
#2Easiest way to make something faster, is to start with something very slow.
Working with deno using intellij's deno language server support[0] is extremely frustrating, slow and missing features, compared to it's normal TS/JS support.
Glad to hear that things are improving though, I'll have to give it another go.
Re: How we made the Deno language server faster
#3I have to wonder if maybe writing the whole thing in TypeScript from the start may have been a better choice. It's not clear what they get from Rust and it introduces the binding layer complexity described in the article.
Re: How we made the Deno language server faster
#4[deleted]
Re: How we made the Deno language server faster
#5Glad to see improvements, but hasn't this been an issue since the the introduction of `deno lsp`? My guess is that the Deno team have been a bit overwhelmed and only a paying (and likely enterprise) customer's complaint was able to raise its priority to be high enough for the team to dedicate someone to address it.
Re: How we made the Deno language server faster
#6[deleted]
Re: How we made the Deno language server faster
#7Easiest way to make something faster, is to start with something very slow. Working with deno using intellij's deno language server support[0] is extremely frustrating, slow and missing features, compared to it's normal TS/JS support. Glad to hear that things are improving though, I'll have to give it another go. [0]: https://plugins.jetbrains.com/plugin/14382-deno
[deleted]
Re: How we made the Deno language server faster
#8[deleted]
[deleted]
Re: How we made the Deno language server faster
#9You have to know a lot about Rust to write performant Deno.
Is there a list of language code smells? If the best parts of your language come from another language are you better off skipping the middle layer now instead of later when there's more code to rewrite?
Re: How we made the Deno language server faster
#10You have to know a lot about Rust to write performant Deno. Is there a list of language code smells? If the best parts of your language come from another language are you better off skipping the middle layer now instead of later when there's more code to rewrite?
You don't need to know rust to write performant deno