Hmmmmmmm - part 391 VS Code suspicious amounts of memory
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I saw how you changed "You could not be more vague" to "Was anything I said not true?"
Well, I could've said both. You both couldn't be more vague, and haven't debunked anything I said.
You get vague replies when you spout vague bullshit.
What's vague about "both Visual Studio and VSCode are IDEs with first-class support for C++, C#, Python, Javascript, and Typescript"? I can't imagine how I could be more direct and precise than that.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I have used both (for different things, but still).
Then you don't know shit.
Maybe I don't. But you not telling me what I'm missing doesn't help me with knowing more.
You should not comment on things you don't know shit about.
I know what IDE is. I know they're both IDEs for same languages. That's enough to tell they're direct competition.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
"Stacks"? They're just IDEs.
No they're not.
Yes they are. .NET, Node.JS, C++ and Python ecosystems all exist independently of either Visual Studio or VSCode - and you can switch between VS and VSC without changing even a single line of code. Stacks are stacks, IDEs are IDEs.
Unless you're just trying out tutorials in both, they are nowhere close to same.
I'm not saying they're the same. I'm saying they're competition. They're both products that are used for the same thing. Tesla and Lexus are also very different but they're still direct competition - they both make semi-luxury cars.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Then tell us - what is the truth?
I have. see up thread.
So far, you've only said what isn't true. Still waiting for you to say what is true. What makes VS and VSC not a competition for each other?
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
What makes them not a competition despite them both being IDEs for same programming languages with very similar feature sets?
Severely retarded way to look at this. VS Code is not the competition for Visual studio. Visual studio code is not going to replace Visual studio.
Linux isn't going to replace Windows either, but they're still considered to be competition. It doesn't matter VS isn't going away anywhere soon - what matters is that VSC has reimplemented most of the features of VS so you can ditch it and switch to VSC at any moment for your C++, C#, Python, JS and TS projects.
Do your fucking homework once in a while instead of typing something retarded and doing the same repeatedly.
I did my homework. In the meantime, you've just been yelling that I'm wrong, but not specifying what is wrong with what I'm saying (except this "it's stack not IDE" thing which is just plain bullshit).
-
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
and haven't debunked anything I said
Why would I try doing that. I know you lose the capacity to listen when someone says you're wrong. Debunk my ass.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I know what IDE is. I know they're both IDEs for same languages. That's enough to tell they're direct competition.
Like I said, extremely retarded way to look at it.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Tesla and Lexus are also very different but they're still direct competition - they both make semi-luxury cars.
How you conveniently chose the wrong example. Your argument has been the same company has been making two competing products just because most of their functionality overlaps. That's like saying Ford makes a sedan and a SUV and you think they compete against each other because omgaaaad both have seats both have wheels both get you from point A to point B omgaaad what a stupid idea.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
VS so you can ditch it and switch to VSC at any moment for your C++, C#, Python, JS and TS projects
This tells me you have absolutely no experience trying to use these two for development using the same languages in production.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
In the meantime, you've just been yelling that I'm wrong, but not specifying what is wrong with what I'm saying
I have. You're just too dense.
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
and haven't debunked anything I said
Why would I try doing that.
To justify using words like "retarded" and "bullshit" to describe what I said? If it's all true, it's hardly retarded or bullshit. And if it's not, show it.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I know what IDE is. I know they're both IDEs for same languages. That's enough to tell they're direct competition.
Like I said, extremely retarded way to look at it.
Like I said, you're being extremely vague, so much that you could've said nothing at all and it would be just as informative.
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Tesla and Lexus are also very different but they're still direct competition - they both make semi-luxury cars.
How you conveniently chose the wrong example. Your argument has been the same company has been making two competing products just because most of their functionality overlaps.
No, my argument is that two products with the same purpose are competition - regardless of whether they're from the same company or not.
That's like saying Ford makes a sedan and a SUV and you think they compete against each other because omgaaaad both have seats both have wheels both get you from point A to point B omgaaad what a stupid idea.
Sedan and SUV have different purposes. VS and VSC don't, as far as I can tell. And if they do, then tell me - what's the difference in their purpose (for the five languages they both have first-class support for)?
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
VS so you can ditch it and switch to VSC at any moment for your C++, C#, Python, JS and TS projects
This tells me you have absolutely no experience trying to use these two for development using the same languages in production.
No I don't. But I've used a dozen different IDEs and non-IDE editors for C++. VS, Netbeans, Eclipse, Emacs, and several others, including Notepad clone whose only IDE-like features were syntax highlighting and keeping indentation. Switching between them has always been a very fast and painless process. It's just a tool.
I can see there might be problems if you use a build system that's highly integrated with your IDE. But for most project, setting up the build system from scratch is relatively simple and fast. Definitely easier than actually changing stacks - say, going from WinForms to WPF.
Am I missing something? If so, please tell me what I'm missing. What exactly makes switching from VS to VSC or vice versa so hard? And don't tell me I don't know shit about switching between them. I already know that. Tell me something I don't know, like what it is that makes switching hard.
-
@Gąska I'm not gonna bother anymore. It's the same shit with you in every other thread.
-
@WhatYouSay said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@marczellm said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@dkf said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Fucking 700MB what in the everloving name of fuck is this.
You've got how much memory in a current developer machine? 8GB? 16GB? More? Why are we bitching about using less than 10% of that to be the environment that people literally do their paying work in?
Sorry but what about poor companies in poor countries, or poor freelance developers, or disadvantaged minority people, that have to stick to older machines?
I’m surprised we haven’t heard an outcry from the usual suspects over the fact that literally all the hippest libraries and tools are built first and foremost for Mac users and Linux users. After all, that is exclusionary to PoC and Transfolk who are too oppressed to afford a fruit box and don’t have enough privilege points to understand how to run a Mint install.
The garage is that way .
-
@Gąska I use both of them myself, and I wouldn't necessarily put them as direct competitors. For anything that requires (for example) a UI or a persistent database connection/ORM, VS is your go-to. Same with anything that needs heavy profiling. VS Code is much better for light-weight, cross-platform interpreted tasks (faster start-up, faster running, direct shell access, available everywhere).
They're definitely in the same basic field but they serve different parts of the market. Just like Whole
PaycheckFoods and Walmart's Neighborhood Market are in the same market but have basically no overlap in customer draw. Market segmentation is a thing, as is different tools for different purposes.
-
@loopback0 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
It is very uncommon to see people using laptops with SSDs around here. Anything that comes with an SSD but with all other things being equal costs about $120 more than the HDD version.
But it'd be considerably quicker, so in theory the $120 pays for itself in extra productivity fairly soon.
That would be true except that when you say it in rupees, the kind of things that you can get for that much money vastly overshadows an SSD. You could buy a real nice full HD monitor a mouse and a keyboard if you give up an SSD. It's still a luxury here.
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska I'm not gonna bother anymore. It's the same shit with you in every other thread.
I probably should make a new account with different username - so when I ask why people think I'm wrong, they actually tell me why I'm wrong, instead of referring me to my past discussions where people also refused to tell me why I'm wrong.
Edit: though until now, it was only about garage-worthy topics, so I didn't care much. But now it's impacting my ability to discuss technical topics, and that sucks.
-
@Benjamin-Hall said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska I use both of them myself, and I wouldn't necessarily put them as direct competitors. For anything that requires (for example) a UI or a persistent database connection/ORM, VS is your go-to. Same with anything that needs heavy profiling. VS Code is much better for light-weight, cross-platform interpreted tasks (faster start-up, faster running, direct shell access, available everywhere).
They're definitely in the same basic field but they serve different parts of the market. Just like Whole
PaycheckFoods and Walmart's Neighborhood Market are in the same market but have basically no overlap in customer draw. Market segmentation is a thing, as is different tools for different purposes.See Ben Hall just took everything Stillwater doesn't have the intelligence to explain and instead just saying, you're retarded without giving reasons why.
Thank you Ben for actually showing why these are not in competition. Market segments is the reason, VS and VSCode do the same thing, but are targeted to different audiences, just like an SUV and luxury car.
Stillwater has no idea how to argue a point, Gaska is purely asking questions and not just hurling insults, if that's how you feel about Gaska from this example, the problem is you.
-
@KattMan I've never had anyone stand in defence of my arguing style before. That's... nice.
-
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@KattMan I've never had anyone stand in defence of my arguing style before. That's... nice.
Only because here, in this case, you haven't dropped to a single insult, only asked questions for which insults where given.
I can't speak for others, or other arguments you have been in.
-
@Benjamin-Hall said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska I use both of them myself, and I wouldn't necessarily put them as direct competitors. For anything that requires (for example) a UI or a persistent database connection/ORM, VS is your go-to. Same with anything that needs heavy profiling. VS Code is much better for light-weight, cross-platform interpreted tasks (faster start-up, faster running, direct shell access, available everywhere).
Usually, people don't take it as a sign of products not being competition. They take it as a sign that one competing product is better at some task than the other competing product. See cloud providers. As far as I know, there are things you can do with AWS that you can't with Azure, and things you can do with Azure but not with AWS. And they're still considered competing products.
They're definitely in the same basic field but they serve different parts of the market. Just like Whole
PaycheckFoods and Walmart's Neighborhood Market are in the same market but have basically no overlap in customer draw. Market segmentation is a thing, as is different tools for different purposes.Yeah, maybe. My autistic results-oriented mind with near zero people skills just cannot comprehend how two companies selling the same products in the same area might not be considered competition. It's just illogical.
-
I can't stand VS Code and don't understand why would I want to use it instead of VS.
-
@Gąska I stand by what I said but I apologise profusely for the insults. Way out of line.
-
@stillwater I don't care about insults. But that you know that I'm wrong, you know exactly why I'm wrong, but you refuse to share with me why I'm wrong - that's quite annoying.
-
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I can't stand VS Code and don't understand why would I want to use it instead of VS.
If you're doing anything Angular + TS, VS code feels really nice to use but with full blown VS something funky happens with the TS to JS transpiling frequently. I'm not sure where from the config it's coming from but with VS Code out of the box angular 2 development and setting up is clean. We ve used Visual studio for ASP.NET API and VS Code for Angular all the time.
-
@Gąska Point taken.
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
If you're doing anything Angular + TS
Ah, no. Never did, never will.
-
@MrL Well, it's literally 100x smaller than Visual Studio so there's that.
-
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
If you're doing anything Angular + TS
Ah, no. Never did, never will.
Trade places in life? Best if you also have a predisposition to Indian cuisine
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@MrL Well, it's literally 100x smaller than Visual Studio so there's that.
And takes as much RAM.
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@MrL Well, it's literally 100x smaller than Visual Studio so there's that.
Notepad is also a lot smaller than EditPad Pro, so...
It would be a concern if I could run out of disk space. But I can't.@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
If you're doing anything Angular + TS
Ah, no. Never did, never will.
Trade places in life? Best if you also have a predisposition to Indian cuisine
Uh, no. But you can send me some cuisine.
-
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Benjamin-Hall said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska I use both of them myself, and I wouldn't necessarily put them as direct competitors. For anything that requires (for example) a UI or a persistent database connection/ORM, VS is your go-to. Same with anything that needs heavy profiling. VS Code is much better for light-weight, cross-platform interpreted tasks (faster start-up, faster running, direct shell access, available everywhere).
Usually, people don't take it as a sign of products not being competition. They take it as a sign that one competing product is better at some task than the other competing product. See cloud providers. As far as I know, there are things you can do with AWS that you can't with Azure, and things you can do with Azure but not with AWS. And they're still considered competing products.
They're definitely in the same basic field but they serve different parts of the market. Just like Whole
PaycheckFoods and Walmart's Neighborhood Market are in the same market but have basically no overlap in customer draw. Market segmentation is a thing, as is different tools for different purposes.Yeah, maybe. My autistic results-oriented mind with near zero people skills just cannot comprehend how two companies selling the same products in the same area might not be considered competition. It's just illogical.
There's a difference between theoretical competitors and practical competitors. This comes up when looking at pay quite a bit--Walmart and Costco (to name two giants of retail) are theoretically competing for the same employees, but their business model is so different (and their customer base is so different) as to make them practically in different markets.
For computers, it's the difference between the high-end workstation PCs and the cheapo Best Buy laptops. They're both theoretically capable of doing the same thing, but what you buy one for, the other will fail at miserably.
Even with feature overlap, things have different strengths. Doesn't make one overall better, just different. I have both VS and VSC installed on my home PC. Both are useful side-by-side. Doing JS/HTML/CSS work (without the ASP core) in VS is a pain. Doing C# (and especially GUI) work in VSC is a pain. Different tools for different tasks.
-
@Benjamin-Hall said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
For computers, it's the difference between the high-end workstation PCs and the cheapo Best Buy laptops. They're both theoretically capable of doing the same thing, but what you buy one for, the other will fail at miserably.
That's not a good analogy. VSC isn't a cheaper, objectively worse version of VS. They're different products with different strengths.
Even with feature overlap, things have different strengths. Doesn't make one overall better, just different. I have both VS and VSC installed on my home PC. Both are useful side-by-side. Doing JS/HTML/CSS work (without the ASP core) in VS is a pain. Doing C# (and especially GUI) work in VSC is a pain. Different tools for different tasks.
Agreed - though there's no universal agreement as of which tools are best for which tasks.
-
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
It would be a concern if I could run out of disk space. But I can't.
More than disk space, it's about download and install time. Which is easily >1h in a less modern system.
Obviously not a problem if you intend to use it regularly, but a major issue if you just want to build a goddamn WPF app with 3 buttons.
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
It would be a concern if I could run out of disk space. But I can't.
More than disk space, it's about download and install time. Which is easily >1h in a less modern system.
How many times per year do you install VS on a single computer?
Obviously not a problem if you intend to use it regularly, but a major issue if you just want to build a goddamn WPF app with 3 buttons.
If you want to build a goddamn WPF app with 3 buttons, "good" isn't something you care about in your tools - but for everything else, it's the deciding factor.
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
It would be a concern if I could run out of disk space. But I can't.
More than disk space, it's about download and install time. Which is easily >1h in a less modern system.
Obviously not a problem if you intend to use it regularly, but a major issue if you just want to build a goddamn WPF app with 3 buttons.
Hmm. I install VS on my workstation(s) as one of essential tools. So I'm never in need to suddenly install some IDE.
If I go to work with a client I take my work laptop with me - same situation.Using some random not-developer computer and suddenly needing to compile something just doesn't happen. For me I mean, is that a common scenario?
-
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Using some random not-developer computer and suddenly needing to compile something just doesn't happen. For me I mean, is that a common scenario?
Nothing WPF specific but I've had it happen a few times. Sometimes the sales or business guys give demos and pitches and they need last minute changes and only their laptops around, then it is an instant login to aws, generate a key and then ssh + vi scenario but even that is a pain. Development machine or not I install VS on every damn computer around the house.
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Make Visual Studio lighter? Nah, we'll make Visual Studio Code.
Seems like they failed to make it lighter
-
Can you create and/or build Win32, .NET (WinForms, WPF) and/or UWP projects from VS Code?
-
@marczellm said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Can you create and/or build Win32, .NET (WinForms, WPF) and/or UWP projects from VS Code?
In principle, yes. In practice? No. No GUI builders, requiring manual configuration of dependencies (something VS does a whole lot better) including the core pieces.
VS Code has a debugger, a compiler, and other basic toolchain support. It's missing all the profiling, dependency management, etc pieces that VS has.
And @Gąska, if you need something portable, a BB laptop is going to fit the bill much better than a workstation. Especially if you're trying to use it on an airplane. So one is not "objectively better" unless you only look at certain uses.
-
@Benjamin-Hall said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
And @Gąska, if you need something portable, a BB laptop is going to fit the bill much better than a workstation. Especially if you're trying to use it on an airplane. So one is not "objectively better" unless you only look at certain uses.
I think you know what my point is, but just don't want to admit you said something stupid so instead you're pushing this pointless argument forward just so you get the last word. If you said "desktop and laptop", I'd agree (though laptop with same spec is objectively better than equivalent desktop in every way - except they're not the same price tag then, and the high-end desktop specs really have no equivalent laptops). But you said high-end workstation PC and cheapo laptop, which sounds like stating the simple truth of life that more money gets you better spec.
-
@Deadfast said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@dkf The developer machine wouldn't need
1632GB of RAM if every bloody application didn't feel like it's entitled to a gigabyte of it.But then I need to run a VM while I'm compiling sometimes...
-
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater both are IDEs. Both have first-class support for C++, C#, JavaScript, TypeScript and Python. Both have very similar feature sets - code completion, static analysis, refactoring, debugging, dependency management. They are direct competition in every way.
VSC is not an IDE. VSC is a glorified text editor.
-
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Make Visual Studio lighter? Nah, we'll make Visual Studio Code.
(probably 'd, but ) I thought the biggest "selling" point for VSC was that it's cross platform?
-
@dcon said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
But then I need to run a VM while I'm compiling sometimes...
What other weird fetishes do you have?
-
@Zecc said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@anonymous234 said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
this weird mindworm where instead of improving existing products, they make a new version from scratch
I can relate.
Sigh
Yeah, that's why I'm now job hunting. I don't want to work on Electron.
Give me C++ or give me death! (I figure I have another 10 years before retirement...)
-
@dcon said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
(probably 'd, but ) I thought the biggest "selling" point for VSC was that it's cross platform?
Yes. Also makes the OSS crowd less anxious when using an MS Tool.
-
@pie_flavor said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater both are IDEs. Both have first-class support for C++, C#, JavaScript, TypeScript and Python. Both have very similar feature sets - code completion, static analysis, refactoring, debugging, dependency management. They are direct competition in every way.
VSC is not an IDE. VSC is a glorified text editor.
At what point a text editor stops being a text editor and becomes an IDE? As far as I can tell, VSC checks all the boxes.
-
@dcon said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I don't want to work on Electron
A PM went "we should start using electron and provide an improved UX for the users". The WPF app he wants to replace has been running for about 7 years without a single problem. Electron is cooooool!
-
@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:
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater both are IDEs. Both have first-class support for C++, C#, JavaScript, TypeScript and Python. Both have very similar feature sets - code completion, static analysis, refactoring, debugging, dependency management. They are direct competition in every way.
VSC is not an IDE. VSC is a glorified text editor.
At what point a text editor stops being a text editor and becomes an IDE? As far as I can tell, VSC checks all the boxes.
Once it starts using over 750MB of RAM? Come to think of it, that would make Chrome the most popular IDE out there.
-
@MrL said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I can't stand VS Code and don't understand why would I want to use it instead of VS.
Because you don't want to debug your C++ code?
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
Also makes the OSS crowd less anxious when using an MS Tool.
I have no issue with using an MS tool when it's a good tool.
I tried VS Code and ran into the issue of it using WAY too much memory while only having ONE file opened.
Fuck that shit
-
@TimeBandit said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I have no issue with using an MS tool when it's a good tool.
You re not doing "being an oss developer" right.
-
@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:
@Gąska said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@stillwater both are IDEs. Both have first-class support for C++, C#, JavaScript, TypeScript and Python. Both have very similar feature sets - code completion, static analysis, refactoring, debugging, dependency management. They are direct competition in every way.
VSC is not an IDE. VSC is a glorified text editor.
At what point a text editor stops being a text editor and becomes an IDE? As far as I can tell, VSC checks all the boxes.
At the point that it starts having actual integrations with its tools. VSC has half decent Git support, but aside from that, doing anything involves a box so similar to a shell that it's got a > in front of it. No GUI builder, no build tool integration, no dependency management, etc.
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
What other weird fetishes do you have?
In the post right below yours! (C++)
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
You re not doing "being an oss developer" right.
Toby Fair: I didn't release any OSS prog. I only contributed to some libraries I was using.
Looks like I'm not an OSS developer, just a user
-
@TimeBandit said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I only contributed to some libraries I was using.
Boom. OSS! Oh god this term has morphed so much even I don't know what it meant originally anymore.
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
@dcon said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
I don't want to work on Electron
A PM went "we should start using electron and provide an improved UX for the users". The WPF app he wants to replace has been running for about 7 years without a single problem. Electron is cooooool!
Ours are basically: we want to consolidate the 5 independent code bases into one so we can improve release velocity. (Win, Mac, web, various phones/etc) (don't get me wrong, our desktop apps do have some issues!)
-
@stillwater said in Hmmmmmmm - part 391 VS Code suspicious amounts of memory:
You re not doing "being an oss developer" right.
That's called
vim
.