News for hackers. Stuff that matters.
Re:Visual Studio Code is designed to fracture by kragen on Sunday September 29, 2024 @11:20PM (#41693232)
that's not my problem. my problem is making sure i don't make my own job skills dependent on microsoft's continued goodwill, because historically that has been a guaranteed path to obsolescence. i don't need their engineering work. i have emacs, vim, clang, gcc, idea, eclipse, firefox, and so on

i'm only interested in microsoft's generous gift of blankets if they come without smallpox

Re:Visual Studio Code is designed to fracture by dumbo-octopus on Sunday September 29, 2024 @11:51PM (#41693381)
You also have vscode. What you don’t have is the various proprietary extensions msft makes to vscode, just as you don’t have every proprietary extension anyone has ever made to those listed platforms.
Re:Visual Studio Code is designed to fracture by toofy on Monday September 30, 2024 @12:40AM (#41693612)
> You also have vscode. What you don’t have is the various proprietary extensions msft makes…

i’m not trying to be confrontational i promise, but i mean, yeah, youre just repeating what we’re discussing…

microsoft bangs its drums chanting “please like us again, look at how open source we are. we’re not the same abusive company we used to be… we’ve changed, really.”

to many of us, the extension ecosystem is the biggest thing separating code from other IDEs in the first place.

this is just more abusive tactics from a company with very very long history of abuse, only this time they try to hide it behind empty “open source community, look how much we love you” rhetoric.

i’ve always recommended to organizations to run fast and far from ms products. basically “if you’re looking at a long timescale, you want agility, you want to be able to easily pivot in various other directions. if you use MS, you never know where they’re going to lock you down. run fast and far from them.” and this is just another example of why.

i think the commenter above nailed it perfectly with, “they keep telling us we should be grateful for microsoft blankets infected with the smallpox.”

Re:Visual Studio Code is designed to fracture by dumbo-octopus on Monday September 30, 2024 @01:14AM (#41693753)
Software engineers have to be the most melodramatic lot in existence. Microsoft: you can use this product for your development work freely, but we have licensing in place that prevents redistribution that cuts out our core product offering because let’s be real here this is really expensive to develop and both us and our employees have bills to pay just like anyone else.

Internet personalities: the closest thing I might compare this to is the deliberate proliferation of smallpox and the resulting deaths of hundreds of thousands of native americans. (a story which, ironically, turns out to be almost entirely fabricated to spread FUD about the us government… https://allthatsinteresting.com/smallpox-blankets)

Re:Visual Studio Code is designed to fracture by shiroiushi on Monday September 30, 2024 @02:18AM (#41694082)
>a story which, ironically, turns out to be almost entirely fabricated

The same is true for the adage about boiling frogs, but it's still a useful analogy.

Re:Visual Studio Code is designed to fracture by delta_p_delta_x on Monday September 30, 2024 @05:06AM (#41695032)
> let’s be real here this is really expensive to develop and both us and our employees have bills to pay just like anyone else

Couldn't put it better. FOSS advocates want everything for free and source code released every time, all the time. Who's paying the bills? The rent? The mortgage?

To be precise, the system sucks, but we have to work within it, and that means profit-driven companies which pay employees liveable salaries so said employees can buy the food and shelter they need to experience a decent life.

I'll bet that 95% of FOSS developers either contribute as part their full-time job, or already have full-time jobs with the salary and flexibility that allows them to also contribute to FOSS projects in their free time. Not everyone has this luxury.

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @07:01AM (#41695744)
i don't care. if you don't want to write free software, that's fine with me. but don't piss on my shoes and tell me it's raining, and don't offer me a gift and then demand payment
Re:Visual Studio Code is designed to fracture by delta_p_delta_x on Monday September 30, 2024 @07:32AM (#41695962)
> but don't piss on my shoes and tell me it's raining, and don't tell me it's a gift and then demand payment

Who's doing this? VS Code is free; Pylance is free, cppdbg is free, the C# suite is free. However the licences are clear; these extensions are closed source.

VS Code's core editor functionality (Monaco, LSP, DAP, etc) is fully open, and has been regularly repurposed and re-branded by several other companies. I sincerely don't see the problem. If someone else wants to write their own extensions, they are free to; these extensions are Microsoft's IP and hence Microsoft is free to do what it wants with its IP.

Re:Visual Studio Code is designed to fracture by CrimsonCape on Monday September 30, 2024 @02:56PM (#41700674)
It's just disingenuous for Microsoft to say, for example, the cpptools extension is MIT licensed, which it is.

https://github.com/microsoft/vscode-cpptools?tab=License-1-o...

In reality, it's a MIT-licensed wrapper. The real license is also included in the repository, just not the top level github license.

https://github.com/microsoft/vscode-cpptools/blob/main/Runti...

The disingenuity is what you are condoning. The repo is superficially organized to appear open-source but is actually a minefield.

Github will sometimes say "found other licenses"; the best Github can do is to "report" on the state of a repository; it's up to the community to decide on stricter tolerances for declaring something to be open-source, because as we see here, even a major corporation is willing to engage in subterfuge/exploitation.

Saying something is "open source" provides material benefit: it creates attention, it attracts users, it creates community. Shouldn't a project be fully in-the-spirit of open source to benefit?

There's plenty of case law around the word "free"; it's just too early for the phrase "open source" to have settled case law.

Re:Visual Studio Code is designed to fracture by dumbo-octopus on Monday September 30, 2024 @03:15PM (#41700883)
Where has microsoft stated the cpp extension is MIT licensed?
Re:Visual Studio Code is designed to fracture by dumbo-octopus on Monday September 30, 2024 @03:16PM (#41700912)
(assuming you haven’t somehow looked at a block of legal text, disregarded the opening paragraph, and assumed the rest of it somehow is to be interpreted in isolation?)
Re:Visual Studio Code is designed to fracture by TheRealDunkirk on Monday September 30, 2024 @10:05AM (#41697234)
> Software engineers have to be the most melodramatic lot in existence.

They have nothing on gamers.

Re:Visual Studio Code is designed to fracture by Capricorn2481 on Tuesday October 01, 2024 @09:34AM (#41708196)
> Internet personalities: the closest thing I might compare this to is the deliberate proliferation of smallpox and the resulting deaths of hundreds of thousands of native americans. (a story which, ironically, turns out to be almost entirely fabricated to spread FUD about the us government

Hmm? I mean maybe some people believe this, but I have never heard of anyone thinking the epidemic that affected hundreds of thousands of Natives was caused by blankets. The Natives I know are well aware that it was a specific event and most Smallpox infections were caused by general contact with Europeans.

In fact, the commenter doesn't even do this, they just referenced the siege and then YOU conflated it with hundreds of thousands of deaths. Officials did intentionally infect Natives and the article confirms that, so I don't think merely referencing that fact is spreading a myth?

But yes, it is melodramatic and tasteless.

Re:Visual Studio Code is designed to fracture by Barrin92 on Monday September 30, 2024 @12:23AM (#41693543)
>because historically that has been a guaranteed path to obsolescence

Has it? If there's one good thing about Microsoft, it's that basically anything, even from the stone age, is still supported. You can fire up some executable from the 1990s on Windows and it works and you can probably just be a .net dev for the next 50 years if you want to. If there's one company in this industry that takes long term support and backwards compatibility seriously it's Microsoft

Re:Visual Studio Code is designed to fracture by 0dayz on Monday September 30, 2024 @02:35AM (#41694172)
You're talking about the most broadest of broad experiences here, what about all the proprietary dev products that have been sunset which usually was design to keep in said developer in the walled garden?
Re:Visual Studio Code is designed to fracture by wvenable on Monday September 30, 2024 @03:17AM (#41694393)
Nobody used them -- except maybe for Silverlight -- but we all know why that model (along with Flash) was retired.
Re:Visual Studio Code is designed to fracture by Mashimo on Monday September 30, 2024 @04:23AM (#41694775)
I honestly don't know, but what are those?
Re:Visual Studio Code is designed to fracture by 0dayz on Monday September 30, 2024 @03:15PM (#41700886)
Pretty much anything pre-Edge in the web world, I'm sure there are some deprecated Sharepoint predecessor and similar.
Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @07:04AM (#41695764)
tell me more about how valuable my knowledge of mfc and visual basic 5 is now

i mean, yes, the code still runs. but it's not useful

Re:Visual Studio Code is designed to fracture by SleepyMyroslav on Monday September 30, 2024 @02:20PM (#41700307)
while I like your point in general you might be wrong on MFC part at least a bit.

Last time I checked one can still choose optional MFC component of desktop development in vs installer and it will let you build old code with latest toolchain and do maintenance. Not that it makes any sense in 2024 but its still there.

ps. I've been hitting F5 every working day in vs for entire career and have no plans to switch to anything else =)

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @02:27PM (#41700371)
Re:Visual Studio Code is designed to fracture by iLemming on Monday September 30, 2024 @11:32AM (#41698354)
> takes long term support and backwards compatibility seriously it's Microsoft

Silverlight, Internet Explorer, Windows Phone, Microsoft Edge (Legacy), Windows Media Center, Microsoft Expression, Hotmail, MSN Messenger, Zune, Kinect, Cortana (on mobile devices), Groove Music, Windows Mobile, FrontPage, ActiveX, Visual Basic 6, Windows XP, Windows 7, Skype for Business (being replaced by Teams), Office Picture Manager, DCOM, Winforms (considered legacy), .NET Remoting (superseded by WCF), WCF itself now considered largely obsolete, Classic ASP.NET (Web Forms), etc.

While Microsoft does offer LTS for core products, they also regularly obsolete technologies, often driven by market changes or strategic shifts. Their rate of obsolescence is comparable to other major tech companies.

Re:Visual Studio Code is designed to fracture by electronbeam on Monday September 30, 2024 @01:36AM (#41693880)
Too many people love smallpox, especially the younger croud who missed the early 2000s
Re:Visual Studio Code is designed to fracture by paulryanrogers on Monday September 30, 2024 @08:12AM (#41696279)
Please elaborate
Re:Visual Studio Code is designed to fracture by pjmlp on Monday September 30, 2024 @02:25AM (#41694122)
Naturally you also generously support emacs, vim, clang, gcc, idea, eclipse, firefox, and so on for them making your livehood possible, selling your skills.
Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @06:34AM (#41695585)
no; i provide some support for some of them, but the nature of software is that it is infinitely replicable, so in general the efforts of a few suffice to satisfy the needs of many

mostly what i offer 'in return' is more free software, which is also how, for example, the vim and gcc teams support each other, for the most part

i'm surprised to see your comment because i thought you were old enough to know this already

Re:Visual Studio Code is designed to fracture by pjmlp on Monday September 30, 2024 @07:16AM (#41695847)
I am old enough to see too many devs abandon open source because it doesn't pay the bills, contrary to the old promises of everyone singing happy songs around the fireplace on a comunity farm kind of ideas.

And also to remember Public Domain and the various flavours of Shareware and Demos, which is what Open Core/Dual Licensing are nowadays, by another name.

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @08:07AM (#41696242)
sure, plenty of people have always abandoned open source for that reason. running a free software business isn't easy

i agree that open-core is little more than shareware. dual-licensing is a different model, one pioneered by peter deutsch in the 90s

Re:Visual Studio Code is designed to fracture by suddenclarity on Monday September 30, 2024 @09:07AM (#41696690)
Which is a can of worms by itself which we saw this year with xz-utils.
Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @09:34AM (#41696917)
yes, and we are going to see a lot more of that, unfortunately. heartbleed was another somewhat similar case, and though the debian openssl hole was probably accidental, nobody will ever be able to prove that conclusively
Re:Visual Studio Code is designed to fracture by talldayo on Monday September 30, 2024 @01:26PM (#41699738)
Most of us are old enough to have seen too many devs abandon iOS and Android for being head-up-ass terrible solutions.

I don't know what solution you're promoting because Free Software still works. The professional for-profit software industry is in the toilet right now - Open Source is destroying it in a certain for-profit purview.

Re:Visual Studio Code is designed to fracture by XajniN on Friday October 04, 2024 @01:14AM (#41738045)
Nice bubble you have there.
Re:Visual Studio Code is designed to fracture by gregmac on Monday September 30, 2024 @03:23AM (#41694427)
It's an IDE. If you need to edit your code somewhere else, there's a billion other IDEs and text editors, as you pointed out.

A guitar doesn't make the musician, and the hammer doesn't make the carpenter.

There's specific skill with being able to use tools well, but that's not what makes a programmer, guitarist or carpenter valuable.

Re:Visual Studio Code is designed to fracture by wiseowise on Monday September 30, 2024 @03:42AM (#41694559)
> A guitar doesn't make the musician, and the hammer doesn't make the carpenter.

Is that why famous guitarists play only on specific expensive brands and professional carpenters have favorite instruments?

Re:Visual Studio Code is designed to fracture by onion2k on Monday September 30, 2024 @04:19AM (#41694752)
There's nothing wrong with having a favorite. That's not the same as only being able to use that specific brand. A good guitarist can play any good instrument well, just as a good developer should be able to write good software in an IDE that isn't their preferred one. The favorite tool just makes them a bit better; it isn't required to do the job.
Re:Visual Studio Code is designed to fracture by bigstrat2003 on Monday September 30, 2024 @03:57AM (#41694635)
> Is that why famous guitarists play only on specific expensive brands...

But that isn't true. Lots of famous guitarists play, and love, the cheap guitar they had before they made it big. Yeah they own lots of expensive guitars (because they like collecting guitars and are rich enough to do it). But they don't only play those.

Re:Visual Studio Code is designed to fracture by KeplerBoy on Monday September 30, 2024 @04:01AM (#41694654)
Sure we all have our favorite tools, but if something happened to code, we could adapt to one of the other options in a fortnight.
Re:Visual Studio Code is designed to fracture by wcrossbow on Monday September 30, 2024 @08:44AM (#41696509)
Famous guitarists mostly only play specific expensive brands because they are endorsed by them. Any professional musician can make the cheapest of instruments sound really good. Maybe a note is missed here or there and the sound is not as good as it could be but it will still be way way better than an average player.

Here is Satriani playing on a terribly setup guitar [1] His only comment at the end? Oh, that was a little painful.

[1] https://www.youtube.com/watch?v=_KZjVZLsU6s&t=20s

Re:Visual Studio Code is designed to fracture by iLemming on Monday September 30, 2024 @11:27AM (#41698284)
Although it is an interesting thought experiment, to a certain degree, I don't think it's right to compare musical instruments and IDEs.

IDEs are usually far more complex due to their vast feature sets and constant evolution. If guitars evolved and increased in complexity at the same rate as IDEs, we would've seen something absurd like James Hetfield wielding a 150-string monster guitar.

IDEs have become incredibly complex tools with features that go far beyond the original concept of text editing, while guitars have remained relatively consistent in their core design and function over decades.

We don't have to keep practicing typing "the quick brown fox jumped over the lazy dog" over and over again to master an IDE, while you have to play same tunes again and again to become a virtuoso. Experienced musicians often have a broader, more adaptable skill set and can change instruments, while IDE users might be more "locked in" to their preferred environment for various reasons.

I agree with your sentiment though - good programmers are good not because they've mastered their tools - they chose to master their tools because they are good programmers.

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @01:01PM (#41699450)
> a 150-string monster guitar

almost all pianos have more strings than that; the bottom octave or so have two strings each and the rest of the keys have three strings each, for a total of somewhere around 250 strings. pipe organs are routinely significantly more complex than that. but a lot of the elaboration in musical instruments doesn't take the form of increasing the number of parts; instead we have things like special varnishes, holes cut in particular shapes, special alloys for strings, tweaked electronic circuit designs, tweaked magnetic pickup designs, etc. i'm not sure it would be easier for a random person to learn how to make a stratocaster-competitive electric guitar than it would be for them to learn how to write an emacs-competitive ide

as for lazy dogs, i think it's common for both programmers and musicians to practice etudes, not just for instrument mastery (which is only a small part of the problem both in programming and in music). a typing class in eighth grade was enormously helpful to me in programming even though, as everyone knows, typing is only rarely the bottleneck in programming. and i think it's pretty common for programmers to spend time on practicing the effective use of one ide feature or another, watch screencasts of other programmers using them, buy books about particular ides, etc. check out https://www.vimgolf.com/challenges/9v0062d0773d000000000225 http://vimcasts.org/ https://www.youtube.com/watch?v=wDIQ17T3sRk https://www.youtube.com/watch?v=uGrBHohIgQY https://www.youtube.com/watch?v=p09i_hoFdd0 etc.

Re:Visual Studio Code is designed to fracture by iLemming on Monday September 30, 2024 @01:44PM (#41699922)
Okay, yeah, I see where you're going with this. I guess, you can compare IDEs and musical instruments, in many aspects, there's more overlap in two areas.
Re:Visual Studio Code is designed to fracture by coliveira on Monday September 30, 2024 @11:28PM (#41704383)
For famous guitar players: they play guitars that pay them (endorsements). They basically don't need to buy anything because guitar brands will offer them customized instruments. It has nothing to do with how much these guitar cost.
Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @06:56AM (#41695702)
much of what you learn programming in an ide is how to program, but some of it is how to use the ide, and it's common for programmers to keep using the same ide for decades as a result

i still have some keybindings in emacs from when i used visual c++ last millennium, and i'm probably using emacs in significant part because i started using lugaru epsilon in about 01989. since then i've also used vi, vim, idea, eclipse, nedit, and the f83 editor, but i keep ending up back in emacs sort of by default. and i think my level of flexibility on this count is far above average

Re:Visual Studio Code is designed to fracture by cruffle_duffle on Monday September 30, 2024 @11:39AM (#41698436)
> A guitar doesn't make the musician, and the hammer doesn't make the carpenter.

A good guitar player or a good carpenter sure as shit know a good tool from a bad tool. Good tools are force multipliers and can can make somebody much better than without the tool.

Plus bad tools can actively keep people away from learning new things. A shitty soldering iron can absolutely convince somebody they suck at soldering. Sure a pro can make use of a shitty soldering iron but they won’t do it willingly and their output will be subpar. Same with cooking and bad knives. Same with anything.

The argument that “tools don’t make somebody good” is pretty silly. They absolutely do.

Re:Visual Studio Code is designed to fracture by CrimsonCape on Monday September 30, 2024 @02:10PM (#41700195)
Remember folks, when Apple says that a video they present is "shot on iPhone" it comes with many many many disclaimers.
Re:Visual Studio Code is designed to fracture by gregmac on Monday September 30, 2024 @02:35PM (#41700456)
> The argument that “tools don’t make somebody good” is pretty silly. They absolutely do.

I disagree, but only because I'd rephrase what you're saying as "good tools are force multipliers for skilled people". You can give a beginner musician the most expensive guitar rig, and they'll still sound like a beginner.

I also never said what you're arguing against. The GP was essentially complaining that using vscode would hamstring their career because their skill would be in something Microsoft could take away. What I was trying to say is the reason programmers get paid isn't because they're good at using their IDE, it's because they're good at programming. I believe the GP's concern is misplaced.

Consider: Do you go to a restaurant because their chef uses expensive high-end knives, or because they have good food?

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @03:02PM (#41700759)
that is not what i was complaining about, essentially or otherwise; you can resolve your unfortunate confusion by reading https://news.ycombinator.com/item?id=41695702, https://news.ycombinator.com/item?id=41699450, https://news.ycombinator.com/item?id=41695744, https://news.ycombinator.com/item?id=41696512, or https://news.ycombinator.com/item?id=41695764, all of which i posted before your comment above in which you baselessly attribute to me the most brain-damaged knuckle-dragging strawman viewpoint possible

i wrote one of those comments specifically in response to your comment, in order to correct your misreading of mine, so you really have no excuse whatsoever for not having read it

Re:Visual Studio Code is designed to fracture by fennecfoxy on Tuesday October 01, 2024 @09:56AM (#41708494)
That's a ridiculous statement imo, there's a reason that AI researcher from meta was all like "come back to me when you have 10,000 H100 GPUs".

Oh, I'm sorry. The tools don't matter.

Re:Visual Studio Code is designed to fracture by dark-star on Monday September 30, 2024 @08:24AM (#41696358)
Your skills as a developer are never dependent on the tools, APIs or platforms you use. You can always abstract over that. But yes, effectively using your skills will always be somewhat dependent on some company's goodwill. If a product, platform or feature you use goes away, you need to switch. That doesn't only happen for development IDEs. It's a process of learning that happens (or should happen) continuously in any line of work, and especially in software development.

As a developer you should already be used to having to switch stuff to something else. Going from DX12 to Vulcan, from x86 to RISC-V, from Linux to FreeBSD, from XCode to EMACS, from Perl to Python, from Angular to Flask, whatever.

Re:Visual Studio Code is designed to fracture by kragen on Monday September 30, 2024 @08:44AM (#41696512)
yes! always be learning! and learning how to think and create, not just how to operate tools

however, see https://news.ycombinator.com/item?id=41695702

inevitably some of your learning efforts are sunk into the tools, apis, and platforms you use. those can compound over time, making you more effective for the rest of your life, or simply be a pleasant memory. spending time on tools, apis, and platforms that are not dependent on some company's goodwill is helpful here; none of vulkan, x86, risc-v, linux, freebsd, emacs, perl, python, angular, or flask is dependent on any single company

(x86? yes, without amd, x86 would have died around 02000 like most other 80s architectures did, killed by intel's itanic blunder.)

in the 90s i invested time learning a lot of different tools and platforms. most of them are no longer useful to me because they were dependent on some company or other: vax, vax/vms, informix, netapp, mfc, sunos 4, purify, clearcase, pv-wave idl, erdas imagine, khoros cantata, irix, windows nt 3.51, cde. but, for the most part, those that were open standards (or, better still, free software) remain useful to me to this day: diff and patch, shellutils (now coreutils), tcp/ip, perl, netbsd, emacs, python, html, css, the i386 architecture, bash, vim, c, c++, sql, gcc, gdb, samba, ssh, postscript, tcl, tk, etc.

admittedly x.25, smtp, ftp, perl, tcl, twm, and fvwm are not as useful these days, and visual c++ and win32 are still somewhat useful. so it's not 100% black and white. but the longevity difference is extremely striking

Re:Visual Studio Code is designed to fracture by gosub100 on Monday September 30, 2024 @11:28AM (#41698308)
I didn't read the article but I could absolutely see MS doing something shady to promote their AI racket: beginning next year, VSCode Basic edition will remain free, but to use Premium AI Cloud additions will cost just $6/month for a basic plan. (Then shoehorn intellisense and a bunch of other features that used to work fine into the "AI" paywall, because it's 2024 and words don't mean anything anymore).

Or more likely, "the free version will now contain ads and mandatory telemetry, pay to upgrade to premium for a more streamlined experience". Just like the Mafia, create the problem then sell your their solution.