deno_std VS KotlinLanguageServer

For reference (for the issues you mentioned): 1. This issue was opened almost immediately to solve the weird .only function not working https://github.com/denoland/deno_std/issues/2979 2. That looks weird to me, will get back to you on this one since it should work I think 3. Generally polluting the global namespace isn't great, but because we're only polluting the namespace of a module (and we choose what parts to import), I personally find it quite freeing. I entirely understand how that might feel awkward. 4. you CAN specifying only writing to certain directories! --allow-write=/path/to/dir would allow that!

At least for the ones related to trees, it's just a renaming. Below is a link to the PR. When I initially implemented these trees, I chose the names BSTree and RBTree to keep the names short. I'm guessing the person that proposed renaming them did so to make it more obvious what they are.

https://github.com/denoland/deno_std/pull/2400

The standard library is separate from the runtime. It wouldn't break backward compatibility if you were to update. For example, if you were importing RBTree and upgraded Deno to the latest release, it would keep working just fine. You would only really need to switch to using RedBlackTree instead if there was a change made to it that you wanted.

I think the only time you would need to update your standard module imports to be able to use newer versions of the Deno runtime if the standard module were depending on runtime APIs that have a breaking change.

It is like Demo deprecating fs.exists().[1]

[1]https://github.com/denoland/deno_std/discussions/2102

This was fun to read through.

I would need to profile the code, but the startup time being bad for Deno seems like maybe a combination of the code in here being unoptimized:

https://github.com/denoland/deno_std/blob/0ce558fec1a1beeda3...

(Ex. Lots of temporaries)

And usage of the readFileSync+TextDecoder API instead of readTextFile (which is also a docs issue since it's suggests the first one). It seems the code loads the 100MB into memory, then converts to another 100MB of utf8, then parses with that inefficient csv decoder. The rust and go versions look to be doing stream/incremental processing instead.

But it there's some talk to reconsider it

Sorry to hear that. I want to provide expect API in deno_std in the future: https://github.com/denoland/deno_std/issues/1779

I just migrated the module to Deno and rewrote the test cases using the Deno test runner. Also contributed a bug fix to the test runner that I encountered during the migration. An npm version is still available and automatically generated from the Deno code via a small bash script (rewriting imports, adding an index.ts, etc.).

Much of Node.js is written in C, yet it's still called Node.js.

Deno has some JavaScript/TypeScript in it. On GitHub https://github.com/denoland/deno is 22.8% JavaScript and 13.2% TypeScript, and https://github.com/denoland/deno_std is 68.2% JavaScript and 31.6% TypeScript.

So to me it's misleading about the name, but not about what Deno is written in.

There's a community-made one, but of course as much effort as has been put into it it's not as featureful as JetBrains's own stuff.

Kotlin is probably the worst case for Neovim. While there is a language server for Kotlin, it's not very advanced and does not look like it's actively developed.

Hi, if you are going to do Kotlin the easiest choice is android studio with Kotlin plugin. Using Vscode is more tricky because Jetbrains does not want to support lsp for Kotlin so you only have https://github.com/fwcd/kotlin-language-server available to write Kotlin on Vscode.

Kotlin Language Server puts a warning on this code, because the bar inside the lambda shadows the function argument bar. Flow typing solves this problem by eliminating the need to redefine bar as a new non-nullable variable in the branch where we've verified it's non-nullable.

You want to change something about that? Go and help over at the kotin lsp server. It's maintained, and welcomes contributions. I sometimes use it in my day job (writing Kotlin backend code)

There is https://github.com/fwcd/kotlin-language-server, but I wouldn't expect something more official from a company that refuse to support LSP in their IDEs. JetBrains is the Apple of the IDE world.

Oddly enough, we use mostly the same languages. However, I would advise against using neovim with Kotlin: its language server has an excessive memory usage and its debugger is cumbersome with neovim (I haven't managed to get it working, and currently it also lacks an entry in nvim-dap's wiki).

I'll bring up the Kotlin LSP[0] every time I see Kotlin on HN because I really hope the LSP takes off (which would make it viable to use Kotlin with a non-IntelliJ editor).

Kotlin as a language looks really cool, but I don't want to give up terminal-based, modal editing (which I'd have to in order to use IntelliJ).

Along those lines, I once tried diving into using Gradle outside IntelliJ, and I couldn't find any good resources to help with that. If folks have hints/links-to-blog-posts with regards to that as well, that'd be great!

[0] https://github.com/fwcd/kotlin-language-server#this-reposito...

I've tried [this Kotlin LSP](https://github.com/fwcd/kotlin-language-server) and it isn't perfect. It's not complete, but it does some of the basic things.

I've downloaded kotlin language server from here: https://github.com/fwcd/kotlin-language-server