Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Qualcomm cancels Windows dev kit PC
Date: 19 Oct 2024 01:43:51 GMT
Lines: 76
Message-ID: <lngh6nFrkgdU1@mid.individual.net>
References: <lne5rqFh2g9U3@mid.individual.net> <vesq10$35da7$1@dont-email.me>
	<lne969Fh72qU5@mid.individual.net> <vesrvb$35nh1$1@dont-email.me>
	<lnfq59Fog9vU1@mid.individual.net> <veue38$3eg7f$6@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net gY36WvwIeYCk3vm7ZtB2tQqDu/dQQogrCHuf8nxxbqAyDqG0kH
Cancel-Lock: sha1:g5En2BVdyT+PdHe89EUcwa9Kfvo= sha256:remeMMMoPOO1nnmHwyfDFvaxjVEvyLVKt0aeSCaZrnM=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 4362

On Fri, 18 Oct 2024 15:48:40 -0400, Chris Ahlstrom wrote:

> Is that a lowest-common-denominator IDE or programmer's editor?
> 
> I've used Visual Studio a fair amount, Eclipse a little, and NetBeans a
> little.
> Oh, Qt Creator to lay out dialogs and, in Windows, to do some debugging.
> Still, most of my work is done using a terminal, vim/gvim, automake or
> meson, and cgdb (gdb wrapper).

There is a vim extension so if I hit <Esc>:wall I don't leave pecker 
tracks in the code. :) Searching, saving and pasting buffers including "*p 
for the clipboard work as expected. There are one or two things that 
weren't implemented the last time I tried to use them but it's being 
enhanced all the time.

There are extensions for almost everything so I would say an IDE. I 
started using it on a large Angular project so that was TypeScript, css, 
and html. If you've ever worked with Angular you wind up with a directory 
structure from hell. Having the visual tree and search capabilities helps.

I also use it for .NET programming with C#. It works well with Python. 
Purists object because it's proprietary but Pylance works well.

https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-
rich-language-support-for-python-in-visual-studio-code/

For working with MicroPython on the Pico there is a MicroPico extension.

https://randomnerdtutorials.com/raspberry-pi-pico-vs-code-micropython/

After MicroPython is installed on the Pico it comes up as /dev/ttyACMxx. 
The extension finds the device and enables copying the program. Code has a 
console where debugging information appears. Thonny is the easiest IDE for 
MicroPython but in the long run Code and the extension is more flexible.

For C++ Pico programming there is a Raspberry Pi Pico extension. It 
handles the SDK for the project. Transferring the executable is a little 
more complex. If you hold down the BOOTSEL button on the Pico when 
plugging in the USB it comes up in the file system and you can copy it 
directly out of the build directory. Plugging/unplugging gets old fast so 
you can also use the debug interface. That requires GPIO pins on the RPi 
or for a straight Linux box you can use another Pico.

Then there is the Swiss army knife PlatformIO

https://marketplace.visualstudio.com/items?itemName=platformio.platformio-
ide

I use that with Arduino C++ code. That and VS Code are much better than 
the Arduino IDEs. v2 improves on the original but is still lacking. 

Oh, yeah Code works with Jupyter Notebooks.

That's only what I use. There are many more extensions for langiages. How 
it performs does depend somewhat in the extension but the overall 
experience doesn't change Versus learning the Arduino, Thonny, PyCharm, 
Visual Studio, etc IDEs. 

I do like Visual Studio for starting a dotnet project. You can do it all 
with 'dotnet' on the command line but that means remembering all the 
dotnet commands instead of filling in the blanks of a handy template.

 
> I don't need no funking Intellisense.

See above about remembering commands. Expand that to remembering stuff for 
several different languages. Half the time I have to run 'man read' and 
'man fread' to remember the correct order.

size_t fread(void *ptr, size_t size, size_t nmemb, FILE *stream);
ssize_t read(int fd, void *buf, size_t count);

All these years and I haven't figured out why they stuck the file 
descriptor and stream pointer on opposite ends.