<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/16/24 5:29 PM, Hairy Pixels via
fpc-pascal wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGsUGtk0za1PA06KUHRudvVEA=4q0+uxPPqGB+Kv43Hm633eFQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Oct 16, 2024 at 9:18:01 PM,
Nikolay Nikolov via fpc-pascal <<a
href="mailto:fpc-pascal@lists.freepascal.org"
moz-do-not-send="true" class="moz-txt-link-freetext">fpc-pascal@lists.freepascal.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"
type="cite"> I also have some experience from my day job on
making a VS Code extension for the Nim language (you can see
my commits in the Nim language server here <a
href="https://github.com/nim-lang/langserver/graphs/contributors"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/nim-lang/langserver/graphs/contributors</a>
and for the Nim VS code extension here <a
href="https://github.com/nim-lang/vscode-nim"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/nim-lang/vscode-nim</a>)
and I can definitely say VS Code is horrible crap. It's buggy
as hell, new versions break API compatibility all the time and
it makes it look like it's your language extension's fault.<br>
<br>
</blockquote>
</div>
<br>
<div dir="ltr">Not my experience. I prefer the editor in Sublime
Text but VSCode is a good debugger which works with LLDB and
Pascal. VSCode is wildly popular as well so FPC is missing out
on new users by not having this as option. Maybe some packages
you used were the culprit? They have a monthly update cycle too
so I would think they catch these things.</div>
</blockquote>
<p>I don't know, it could be the Nim to JS compiler, or the fact
that the previous plugin developer didn't use the LSP protocol,
but direct integration instead. But I don't like the whole idea of
an IDE, written in JavaScript. It's horribly bloated and difficult
to debug.</p>
<p>The LSP protocol is fine, though. I like the idea, it allows
integration with many different IDEs and editors. Sublime Text is
just one example, there are many people who use Vim, Neovim,
Emacs, Helix and many others. I also think it's a nice and quick
way to improve the console IDE by adding an LSP client. But I have
a huge backlog of things to do, so I haven't started on this, yet.<br>
</p>
<blockquote type="cite"
cite="mid:CAGsUGtk0za1PA06KUHRudvVEA=4q0+uxPPqGB+Kv43Hm633eFQ@mail.gmail.com">
<div dir="ltr">When I learn a new compiler these days I download
the installer, run it, then check VSCode or Sublime Text for
extensions to install in one click. If that doesn't work I
probably just give up because I idon’t have time to be playing
around and there’s myriad of new languages to play around with
these days.</div>
</blockquote>
<p>Yeah, it's tempting with its store of extensions. Too bad most of
it is crap. And it's not fully open source. Sorry, I use it at
work, and just don't like it. Anyhow, there's nothing wrong in
developing an VS Code plugin for Pascal. Anybody interested can
try to do that. Most of the work is probably fixing the LSP
server, as it does most of the work. This way, the extension
itself can be kept minimal.<br>
</p>
<p>Best regards,</p>
<p>Nikolay<br>
</p>
</body>
</html>