Hmmmmmmm - part 391 VS Code suspicious amounts of memory
-
Sort of like this?
The fact that ACPI was designed by a group of monkeys high on LSD, and is some of the worst designs in the industry [...]
If any Intel people are listening to this and you had anything to do with ACPI, shoot yourself now, before you reproduce.
-
@Applied-Mediocrity Oh, there's some good quotes there.
If Microsoft ever does applications for Linux it means I've won.
See thread topic.
-
@Tsaukpaetra said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
The fuck???! How come nobody told me Visual Studio supported Python? The most recommended "IDE" still mostly amounted to a plain text editor with keyword coloring and brace matching!
Well, only since VS-2010..... Perhaps you are still using VS-2008??????
-
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@pie_flavor said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
No GUI builder
Visual C++ doesn't have that either.
It doesn't? It did the last time I used it (2005 or 2008 or something)
Mostly because it doesn't have dedicated support for any particular GUI flavor, so including one makes no sense.
Was Win32 IIRC, maybe with some MFC crap on top.
-
@topspin said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@pie_flavor said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
No GUI builder
Visual C++ doesn't have that either.
It doesn't? It did the last time I used it (2005 or 2008 or something)
It still does. But our .rc file is so hacked together, we have to manually edit it. Opening it in the RC editor will cause git-hell - pretty much every single line will get rewritten. I blame it on cargo-cultism-the-editor-is-broken mentality.
-
@pie_flavor said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Applied-Mediocrity Oh, there's some good quotes there.
If Microsoft ever does applications for Linux it means I've won.
See thread topic.
-
@dcon said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Opening it in the RC editor
That thing is a pile of dung and feels like it hasn't been maintained since 1972. My attitude towards it is "avoid at all cost, and if you are unfortunate enough to accidentally open it, pray the RC file is still open in some other editor so it refuses to touch it, or it will shit all over the file". Never much used it for any GUI stuff, though.
Filed under: Then again, maybe after all these years I'm just still bitter about the demise of ResEdit
-
@Tsaukpaetra said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Think about this, Visual studio has had support for JS, TS and Python from way back
The fuck???! How come nobody told me Visual Studio supported Python? The most recommended "IDE" still mostly amounted to a plain text editor with keyword coloring and brace matching!
Python devs deserve to suffer.
-
@Kian said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Tsaukpaetra said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Think about this, Visual studio has had support for JS, TS and Python from way back
The fuck???! How come nobody told me Visual Studio supported Python? The most recommended "IDE" still mostly amounted to a plain text editor with keyword coloring and brace matching!
Python devs deserve to suffer.
Unlike JS devs, who make the rest of the world suffer.