Topic: 2021 New LISP Editor

[w64bit]

AutoCAD 2021 is bringing new LISP editor: VS Code and the AutoCAD AutoLISP Extension.
The Visual LISP (VL) IDE has been retired and will be removed in a future release.

Do you think that this replacement is a good thing for LISP editing?
VS Code for AutoCAD it's better than BLADE (the equivalent for Bricscad)?
Thank you

[JohnK]

VS Code will be better but AutoLisp developers will need to learn to adopt new practices such as the use of version control, and debuggers.

I wrote down some of my initial thoughts/concepts on the use of VS Code here:
https://www.theswamp.org/index.php?topic=55696.msg598040#msg598040

[MickD]

I think it's pretty hard to get a better IDE than a purpose built one embedded into the host application but VLIDE is showing its age. BLADE will be pretty hard to beat for BricsCAD though.

I like working with VS Code (I spend 90% of my time there) and for AutoCAD at least it will become the better alternative as long as the plugin maintainers keep improving it.
It also comes down to workflow I guess.

[It's Alive!]

I’m still using LispLink lol, I wish BLADE had a dark theme..  VS Code looks really nice, I think I’ll give it a whirl since its easier on the eyes

[kdub_nz]

I was told a few years ago that the guys at AutoDesk didn't know enough about the IDE or Vital Lisp to make changes to it.
Looks like they took the easy way out.
 
I'm pleased I'm done with them.

[gile]

Looks like they took the easy way out.

ZWCAD already did this some years ago.

Otherwise, it seems that the support of Unicode characters also brings some compatibility issues (see here)...

[Augusto]

The fact is that every change takes us out of the comfort zone. I particularly like it very much when that happens.

But some changes that Autodesk is making in relation to its business model, more specifically saying, software leasing model, has caused a certain discomfort in the people with whom I talk.
Many are already considering purchasing software with a lifetime license, such as BricsCAD.

But going back to the main issue that is IDE, I think the following:
Instead of changing the IDE, why not change the way that autoCAD processes autolisp?
There are routines here in my work that in autoCAD take almost 60 seconds, but the same routine in BrisCAD takes less than 5 seconds. 

But please understand, this is just a thought that came to mind. I know this could be a very long conversation.

I already made my decision.
Despite being passionate about autolisp, although I don't know much, I will face my discomfort and go to the .net platform. 

Wish me luck. 

[MP]

I believe my fondness for LISP is well known (after all we were born the same year). That said, I wish Autodesk / Bricsys would natively support Python.

On IDEs -- due to the lameness of VLIDE I adopted Ultra Edit (UE) eons ago. While Blade is truly awesome -- and I have tested and customized it a fair amount (the DCL viewer is very convenient) -- my productivity is far higher with UE. I typically pound out over 5K lines of LISP a month so an IDE I'm productive with -- not fatigued by -- and the same regardless the platform I'm supporting -- is essential.

tl;dr: Not abandoning UE any time soon.

[gile]

Due to the support of Unicode, StripMtext requires the LISPSYS sysvar to be set to 0 to work with A2021 (iow, keep the VLIDE as default IDE).

[framednlv]

I’m still using LispLink lol, I wish BLADE had a dark theme..  VS Code looks really nice, I think I’ll give it a whirl since its easier on the eyes

I wish I still had LispLink.

[Atook]

.. I typically pound out over 5K lines of LISP a month...

 

That's incredible!

[MP]

That's incredible!

[It's Alive!]

.. I typically pound out over 5K lines of LISP a month...

 

That's incredible!

And that's only LISP