#VSCode is NOT Visual Studio... And my #PineTime @PINE64 tutorials are Fully FOSS-Friendly... Here's why... https://gist.github.com/lupyuen/08e383845d68d3337747e8eb59d0f624

@lupyuen

All valid points. But it is stll microsoft, ick! I can understand the reason. If I see someone using VSStudio in a video or tool I dont tend to give it much attention just because I have an aversion to anything microsoft.

@PINE64

@freemo I would love a nitpicky brainy debate about this :-) But tell me which part of VSCode still smells icky like Microsoft? I must tell the #VSCode Community to change the darned branding! The #PineTime Community @PINE64 might even consider adopting it as #PineCode ;-)

@lupyuen

To me this is a perfect example of a monopolistic corporation using OSS improve its image, attract the community to do free work and marketing for them, while keeping key components of the system(in areas where they have and wish to maintain their monopoly, which for MS very much is C# and C++ dev tooling) proprietary. VSCodium supports VSCode, unless it actually forks and does sizeable amount work under a GPL like license.

Also it being based on the abomination that is electron, I just can't see how someone doing embedded dev or even just rust in general can like it, even purely on the technical level. Your only excuse is "I like shiny, and I don't care"... which is a valid excuse I guess.

@freemo @PINE64

@namark

I agree that is microsofts intent. I have nothing wrong with that intent. Its a wonderful step in the right direction for them and a brilliant business move overall. It simply isnt a tactic that works for me as I do not have microsoft in high regard in terms of fostering quality dev communities or products, so I stay away.

Despite my distaste for Microsoft I have no issue with them going open source, I applaud it

@lupyuen @PINE64

@freemo @namark @PINE64 OK maybe let's bring the discussion back from Microsoft back to VSCode (or whatever *Code that we can choose to name it)... Had a quick discussion with the Awesome #PineTime Community...

We would like to have a GUI tool (in addition to the existing command-line tool) because it's a matter of Choice and Inclusiveness. Some folks may find GUI IDEs more comfortable (probably younger+older coders). Also I suspect that Asians prefer a GUI IDE that's culturally agnostic. (Easier to communicate too. Any other Asians here who can validate this?)

Is it going to be based on VSCode or Electron or whatever? Not sure yet. But seems the VSCode Community has done such a great job, we should consider them.

Erm maybe I get a tad offended when people say I should use the command line and GUIs rot my brain... But my brain really works better with GUI.

And since command line tools like gdb are extremely well documented, I thought I might chip in a viable FOSS GUI alternative. Remember that All Monopolies Are Bad... Even Command-Line Monopolies 😉

So my plea to all Command-Line Fans... Please cut us GUI Folks some slack... Let's all solve problems with the tools that work best for each of us. Thanks! 🙏

@lupyuen

I think you should use whatever you enjoy using. I dont like to rely too much on my mouse it slows me down and obscures me from the internals and limits my ability to be productive when I read the limits of that GUI.

I find the argument for using a GUI is only one, a smaller learning curve. You can open it up and start working, no need to memorize key bindings or commands or look at man pages.

While there is nothing wrong with that I do find that when we talk about the whole of a community (not the individuals which can always deviate from the norm) this has consequences. When I deal with other GUI users (windows users who are programmers) I often find they have far less skill than command line users. I cant tell you how many times I said to a windows user "Can you please rebase your commit and squash and reorganize your commits" and they had No idea what I was saying, all they ever knew how to do was hit a few buttons, even though this should be the norm for most commits.

My aversion to the GUI world is mostly just that, that I find the communities that build up around them seem to be poorly skilled.

Now to bring that back to VS code, well that point was really just one of the points I listed. The microsoft association and how they used microsoft idology to make that GUI made the consequences worse.

Take Emacs, my prefered IDE. It has a GUI, there is a menu bar, you can open files with a mouse click, multiple tabs for different files, the whole none yards. However it is designed like a GUI for console programmers. You can use it entirely via hot key without ever needing a mouse (in fact that is the primary use) and you tend to have full access to the commands you issue on the command line (with built in shells or building out your own hot keys or whatever way you want to use it). So the userbase that uses it doesnt seem to have the issues I mentioned before where the skill level is inadequate.

But like I said, you use a GUI, it speaks to you, you like it, there is no issue. There are plenty of people who use GUIs who are amazing programmers too. Like I said the "average" doesnt mean it represents you, so those arent judgements about you.

You wanted to know why I, and others, are bias against VSCode so I thought I'd share

@namark @PINE64