Recent

Author Topic: What VS Code extension do you use?  (Read 4026 times)

anokim

  • Newbie
  • Posts: 3
What VS Code extension do you use?
« on: January 03, 2025, 05:30:11 pm »
I use VS Code for Free Pascal and I tried two extensions:
1) Pascal by Alessandro Fragnani, and
2) OmniPascal by Wosi

With Pascal, code completion is not so good. But it recognizes recent keywords.

OmniPascal seems to be better. Code completion is quite good, but it doesn't recognize some keywords (e.g. generic) and they're underlined in red (see attached file).

Code completion of OmniPascal fails when I want to use a "method" that comes from a type helper. For instance, I import "sysutils", I have a string, and when I type "s.Starts", it doesn't offer "s.StartsWith".

What extension(s) do you use for Pascal development under VS Code? Do you know how to tell OmniPascal to ignore specific warnings?

VisualLab

  • Hero Member
  • *****
  • Posts: 624
Re: What VS Code extension do you use?
« Reply #1 on: January 03, 2025, 08:50:39 pm »
I use VS Code for Free Pascal and I tried two extensions:
1) Pascal by Alessandro Fragnani, and
2) OmniPascal by Wosi

With Pascal, code completion is not so good. But it recognizes recent keywords.

OmniPascal seems to be better. Code completion is quite good, but it doesn't recognize some keywords (e.g. generic) and they're underlined in red (see attached file).

Code completion of OmniPascal fails when I want to use a "method" that comes from a type helper. For instance, I import "sysutils", I have a string, and when I type "s.Starts", it doesn't offer "s.StartsWith".

What extension(s) do you use for Pascal development under VS Code? Do you know how to tell OmniPascal to ignore specific warnings?

I don't use such weird inventions as VSCode at all. It's bloated, heavy, and worst of all, it's really just a bunch of HTML pages, CSS files, and a bunch of JS scripts (a new-fashioned corporate behemoth). It just pretends to be a real program. And it doesn't have a compiler. That's why I use Lazarus. I install, run, and... work. The amount of repetitive and boring operations I have to perform while developing a program is minimized. Apart from that, Lazarus works quite briskly and without any major hiccups on both Windows and Linux. And the source code editor in Lazarus has quite a few convenient features that are used in every decent IDE these days.

BlueIcaro

  • Hero Member
  • *****
  • Posts: 813
    • Blog personal
Re: What VS Code extension do you use?
« Reply #2 on: January 04, 2025, 10:16:17 am »
Hello, Castle Game Engine (A pascal game engine) has a extension https://castle-engine.io/vscode

I used with Castle Game Engine, but never with other projects, but in the documentation explains that you can use it without Castle Game Engine.

/BlueIcaro

Warfley

  • Hero Member
  • *****
  • Posts: 1863
Re: What VS Code extension do you use?
« Reply #3 on: January 04, 2025, 12:46:34 pm »
I don't use such weird inventions as VSCode at all. It's bloated, heavy, and worst of all, it's really just a bunch of HTML pages, CSS files, and a bunch of JS scripts (a new-fashioned corporate behemoth). It just pretends to be a real program. And it doesn't have a compiler. That's why I use Lazarus. I install, run, and... work. The amount of repetitive and boring operations I have to perform while developing a program is minimized. Apart from that, Lazarus works quite briskly and without any major hiccups on both Windows and Linux. And the source code editor in Lazarus has quite a few convenient features that are used in every decent IDE these days.

I find it quite interesting that you call vscode bloated and heavy in a post where you compare it to Lazarus. Just taking raw specs, vscode is a few hundred megabytes, Lazarus is in the order of gigabytes (die to the need for carrying build artifacts). Vscode starts in less than 1 second, Lazarus takes tens of seconds.

I mean sure the reason for this is that vscode and Lazarus are two completely different products, Lazarus is a fat ide with a bunch of libraries while vscode is a slim editor, but especially because of that, if you don't want or need a fat ide, vscode is a great option because it's so lightweight.

When I need to write small test scripts to test some Compiler features, I rarely go through the effort of firing up Lazarus, I just start vscode or vim and do the work in there.

Also things that Lazarus, as good of an Pascal ide it is, simply can't do:
1. working on a remote system via ssh
2. Collaboratively working on the same code in real time
3. Support for additional languages when integrating with other systems (e.g. make, C, bash, etc)
4. Terminal emulator embedded in the IDE
5. Easy to write extensions

Vscode became the most popular editor for a reason. It's slimy lightweight but extremely versatile and easy to extend.

VisualLab

  • Hero Member
  • *****
  • Posts: 624
Re: What VS Code extension do you use?
« Reply #4 on: January 04, 2025, 01:11:20 pm »
I don't use such weird inventions as VSCode at all. It's bloated, heavy, and worst of all, it's really just a bunch of HTML pages, CSS files, and a bunch of JS scripts (a new-fashioned corporate behemoth). It just pretends to be a real program. And it doesn't have a compiler. That's why I use Lazarus. I install, run, and... work. The amount of repetitive and boring operations I have to perform while developing a program is minimized. Apart from that, Lazarus works quite briskly and without any major hiccups on both Windows and Linux. And the source code editor in Lazarus has quite a few convenient features that are used in every decent IDE these days.

I find it quite interesting that you call vscode bloated and heavy in a post where you compare it to Lazarus. Just taking raw specs, vscode is a few hundred megabytes, Lazarus is in the order of gigabytes (die to the need for carrying build artifacts). Vscode starts in less than 1 second, Lazarus takes tens of seconds.

I mean sure the reason for this is that vscode and Lazarus are two completely different products, Lazarus is a fat ide with a bunch of libraries while vscode is a slim editor, but especially because of that, if you don't want or need a fat ide, vscode is a great option because it's so lightweight.

I admit, I exaggerated a bit. Because Lazarus is indeed "big". But that's because it has a lot of tools in it and a lot of library files. Lazarus is not so much an IDE but more of a RAD (i.e. more than an IDE). I paid attention to its functionality. And this one beats VSCode if someone is creating a more complex project. And for editing files I prefer Notepad++.

When I need to write small test scripts to test some Compiler features, I rarely go through the effort of firing up Lazarus, I just start vscode or vim and do the work in there.

Also things that Lazarus, as good of an Pascal ide it is, simply can't do:
1. working on a remote system via ssh
2. Collaboratively working on the same code in real time
3. Support for additional languages when integrating with other systems (e.g. make, C, bash, etc)
4. Terminal emulator embedded in the IDE
5. Easy to write extensions

Vscode became the most popular editor for a reason. It's slimy lightweight but extremely versatile and easy to extend.

My allergy to VSCode stems from the fact that it uses the same "technology" as other "pseudo-desktop applications". Too much JavaScript is not good even on websites, let alone on the desktop. Yes, I know, it's portable between different OSes. But this can be achieved in other ways.

 

TinyPortal © 2005-2018