291–300 of 303 posts
Earlier quoted context omitted.
>Agree with him, VSCode is THE IDE. Lol, he said Visual Studio is THE IDE, not VSCode. Compared with VS, VSCode is a toy.
> Compared with VS, VSCode is a toy Is it still true today? I don't really do C++ so I have no use for VS, but I have a hard time imagining not having access to everything to do C++ dev with VSCode
Earlier quoted context omitted.
Installing VS6 on modern Win10 can be annoying. Might actually be easier to make a dedicated Wine prefix on Linux :-P. Anyway, there is an article written on CodeProject[0] a few years ago about installing VS6. It may also work on Win11, however due to the changes over time you need to do some more additional stuff: 1. Do not install the OLE/COM viewer 2. Ensure the installation finished propertly otherwise SP6 wont…
> ideally VB6 should have been able to use VC6 headers or even C sources directly just by making them part of the project You could access compiled DLLs from C and C++ projects within Visual Basic. Not quite the same thing as headers I know but it did at least fill that gap that you described.
Earlier quoted context omitted.
VSCode is based on Electron, a glorified hack/resource hog of Chromium than even Github largely abandoned. It maybe "great" and mildly "popular" here and there, but it's built on a foundation of mud. Build native apps that work and are performant. With enough effort and care, a frictionless experience can be made with a TUI should some "Jetbrains" come along and try to make a commercial product out of it.
> It maybe "great" and mildly "popular" here and there VS Code is not just mildly popular, it's significantly more than twice as popular as any text editor has ever been in the modern era . Source, it's currently used by 74% of programmers ( https://survey.stackoverflow.co/2022/#technology-most-popula... ), the next highest text editor, since the survey started in 2015, was Sublime Text in its prime (2016) at 31%. It…
74% of the respondents to the latest Stack Overflow survey, you mean.
Earlier quoted context omitted.
> ideally VB6 should have been able to use VC6 headers or even C sources directly just by making them part of the project You could access compiled DLLs from C and C++ projects within Visual Basic. Not quite the same thing as headers I know but it did at least fill that gap that you described.
You could do that from pretty much any Windows language, Visual Basic wasn't special in that regard and my point was that since both were MS products and part of the same package they could have much better integration.
You mean “Microsoft” language surely? You couldn’t access DLLs from Perl, PHP, Java, and a bunch other other languages that had been ported to Windows.
And my point wasn’t that VB was special. Just that you could still interface with C++ code albeit only via compiled libraries (you also could access COM objects too).
> my point was that since both were MS products and part of the same package they could have much better integration.
I got that was your point but they weren’t part of the same package. VB didn’t ship with a C++ compiler and nor did Visual Studio support compiling Visual Basic. They were sold as separate products and their IDEs were rather different too. Don’t be fooled into thinking that because they share a similar product name (I mean that makes sense from a marketing perspective) that they were the same package. Having used both, I wouldn’t be at all surprised if the similarities were only skin deep.
Earlier quoted context omitted.
Yeah, half of my coworkers used to be on CLion (for Rust). TBH I couldn't get past the fact that it reminds me of Java IDEs with too many things going on. What's better compared to VSCode?
VSCode is very, very bare bones compared to what JetBrains can offer in terms of refactoring, debugging, and code analysis (for major languages). It's hard to start at anything specific :)
I haven't seen a single person who seriously used both and went back.
Search, VCS, keymapping, defaults, heuristics, refactoring wide of use, AI-based autocompletion - there's simply no real adversary.
Last time I was blasted when copying an old DB to a one in a new DB it correctly guessed the renamed columns based partly on type and size, partly on column names.
Also I love its suggestions so much that when learning a new language I always look at Jetbrains' respective autosuggestions - simply because it makes me a better programmer, faster.
Earlier quoted context omitted.
He was a hero of mine when I was in engineering school but i only see pictures of him mostly at the time and thought of him (probably due to his specs) as an archetypical geek. However, reading about him more and listening to his talks over time has really made me appreciated how well rounded, low drama, and high impact he is.
I'm a 40 years old guy who taught himself and got his first gig last year and he's also my hero. I'll sound "kids nowadays" but it's surprising how many young developers never even heard of Carmack.
Such a joy to listen to Carmack talk about just about anything. Not sure if it's an age thing but there is a particular feeling common to contemporaries of that era, growing up in our formative years as computers grew from their humble beginnings to the incredible machines we have now. At that time, each new improvement brought astounding differences in capability. In the space of 10 years we went from 8k to 64k of m…
Era aside, Carmack is a special guy, he can talk articulately and gently for hours. He did a talk few years ago (quakecon ? .. I forgot), basically a 3h long monologue about thinking while coding, there was only a single 5min pause to sip some water, incredible.
Earlier quoted context omitted.
You could do that from pretty much any Windows language, Visual Basic wasn't special in that regard and my point was that since both were MS products and part of the same package they could have much better integration.
> You could do that from pretty much any Windows language, Visual Basic wasn't special in that regard You mean “Microsoft” language surely? You couldn’t access DLLs from Perl, PHP, Java, and a bunch other other languages that had been ported to Windows. And my point wasn’t that VB was special. Just that you could still interface with C++ code albeit only via compiled libraries (you also could access COM objects too).…
There were languages that weren't able to call such DLLs, but there were also many that could that weren't made by Microsoft - e.g. Borland Delphi, Power BASIC, a bunch of Smalltalk implementations, etc.
> I got that was your point but they weren’t part of the same package. VB didn’t ship with a C++ compiler and nor did Visual Studio support compiling Visual Basic. They were sold as separate products and their IDEs were rather different too.
I know what they were, what i referred to was what they should have been considering that they were (potentially) part of the same package (Visual Studio as a product, not the IDE that hosted Visual C++, though honestly that shouldn't really matter) and made by the same company who had access to the source code, libraries, etc to make these two programs "know" about each other in a more integrated way than what external 3rd party development tools were able to do.
This was about a what could have been, not about what it was (nor about why it was like that either - chances are they were made by largely different teams that competed with each other and only had to deal with their programs "living" in the same CD :-P).
I'm one of the people he talks about who moved from diehard Emacs use slowly to more and more VSCode use largely due to the better UI experience around debugging and integration of a lot of modern tools. His point about features not being used when they're complicated to reach despite people claiming that they'll use them is a true observation in particular. You always can set up a lot of those features in your unix-…
I've used IDEs, but just keep ending up using vim. With fzf, ctags, clangd and YouCompleteMe, it's a very productive tool for C++. The two things I really miss from Visual Studio are the easy project setup - writing cmake by hand isn't very fun and debugging why it isn't generating what you want is a pain ; and the great visual debugger - nothing I have tried on Linux is as comfortable as GDB's TUI, which isn't very…