Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Microsoft Programming

As VS Code Gains in Popularity, Microsoft Praises 'Inner Source' Development (zdnet.com) 169

It's been estimated that there are 24 million developers in the world. 14 million of them now use Microsoft's Visual Studio Code (VS Code) as their IDE, reports ZDNet, with five million new users arriving in 2020.

Julia Liuson, corporate vice president of Microsoft's developer division, tells them why: "The strategy for VS Code is really to support our any, any, any strategy. You can be a developer working with any programming language, working on any operating system and develop any kind of software." VS Code runs on macOS, Windows 10, and multiple distributions of Linux, it supports Arm64 on Linux, and runs on Raspberry Pi and Chromebooks. It's also available in preview form
Part of VS Code's popularity is the breadth of language extensions for C++, C#, Python and various Python libraries for data scientists, Java, and JavaScript/Typescript... "We have almost two million Python developers using VS Code and well over a million C++ developers using VS Code," said Liuson. "And even our Java usage is approaching one million...."

Liuson also talked about Microsoft's inner source approach to software development. The company doubled down on inner source in 2019, and recently highlighted its inner-source approach as a factor that mitigated the threat of the SolarWinds hackers accessing its source code. Microsoft didn't make up the term inner source and the approach means taking open-source development practices and applying them inside a single organization. GitHub and GitHub's Enterprise Server fits snuggly with this approach to help organizations collaborate but do so in private.

"Inner source means if you have private IP, but you're inviting other teams within the company to collaborate with you. That's the fundamental difference between open source and inner source. Today, it's very common in large enterprise..."

This discussion has been archived. No new comments can be posted.

As VS Code Gains in Popularity, Microsoft Praises 'Inner Source' Development

Comments Filter:
  • by therealprologic ( 2118298 ) on Sunday February 07, 2021 @08:46PM (#61038550) Homepage
    Seemt to me like this so-caleld "inner-source" is just justification for "closed source" and "propriatery" software.
    • You may find part of the reason for it's Python popularity is some python IDEs are costly.

      https://www.reddit.com/r/humbl... [reddit.com]
      https://www.jetbrains.com/pych... [jetbrains.com]

      • Re: (Score:2, Interesting)

        You may find part of the reason for it's Python popularity is some python IDEs are costly.

        https://www.reddit.com/r/humbl... [reddit.com]
        https://www.jetbrains.com/pych... [jetbrains.com]

        IDE with python? What's wrong with a text editor and command line.
        It never cost me a penny and I've never felt wanting for debugging crutches.

        • by sodul ( 833177 ) on Monday February 08, 2021 @01:28AM (#61039138) Homepage

          I had been using TextMate since 2007 for all my Python development and was quite satisfied with it. That was until We started using type annotation with Python 3 a couple of years ago and this has been a significant boost in both productivity and quality.

          Thanks to IDEs that actually use the typing information I no longer have to guess the spelling if every single method or argument that I need to call. It makes refactoring a lot more reliable since all the instances of a class in a project are actually understood by the IDE.

          Sure you can run mypy on the side, and you should, but regular text editors are not capable to have the understanding of what type you are currently using while an IDE like PyCharm can. I did try VsCode and it had too many glitches on our larger project. PyCharm does get slow, but that can be tuned, but it does understand your code base quite well.

          Just download and try the free community edition for yourself, point it to the python environment you use for the given project and how nice it is.

          It is not perfect for sure, I still use TextMate since I find the multi line editing, the global search and replace to be much better.

          • My programming doesn't tend to be 'large projects'. I develop algorithms for data analysis and processing. That usually stretches to a reading one or more files, doing stuff, writing it out again and dealing with command line arguments. The clever bit is the bit in the middle that fafs around with data.

            So python is fine when the computational complexity is not terrible, C when it is, C++ when I have to use mpfr and a better algorithm if its still too slow.

            As a result, type annotation doesn't really benefit

        • I have started using vscode for a professional project in python. I have never used an IDE before (except for idle), but I have to say I find it really handy. The function hover over display of the help text, nice integration with git, and other conveniences make the coding experience easier and more pleasant.
        • A year or two ago, I would have agreed with you. But I've been using VSC since then (switching from another very good text editor that I won't name here, which I used for ten or more years), and I have found at least one aspect of VSC very helpful: the Python plugin has a built-in lint that flags many of my errors before I even try to run the program. Much easier (and sometimes much faster) than waiting for Python to throw a runtime error.

          There are probably lots of other things I should be doing that VSC

      • by DrXym ( 126579 )
        Same for most languages. Either the IDEs are non existent or cost money. I also think it is popular for web development simply because there are so many tools and ways of doing stuff it is chaotic and not really suited to an IDE.

        That said, I don't quite understand why VS Code became popular when the likes of Brackets & Atom didn't because they're basically the same thing and came much earlier. Atom in particular though because it was open source.

    • by Vairon ( 17314 ) on Sunday February 07, 2021 @09:22PM (#61038664)

      Inner-source or Inner-sourcing is about using open-source code, open-collaboration and similar principles inside a company or organization. It was coined by Tim O'reilly in 2000. You can read the original coining of the phrase here: https://web.archive.org/web/20... [archive.org]
      Also check https://en.wikipedia.org/wiki/... [wikipedia.org] for more details about the concept.

      It is not closed-source or proprietary, it's the exact opposite of that.

      • > It is not closed-source or proprietary, it's the exact opposite of that. How? How is taking a bunch of evolutionary software development processes from open source culture into your organization make your software development suddenly open source? If you have not released your software's source code to a public in some feely available (free as in beer) way where one can inspect the source code, modify it, etc, that is the very definition of "closed source".
        • ? If you have not released your software's source code to a public in some feely available

          it is available on GitHub under an MIT license. Do whatever you want with it (except for releasing under the same name for trademark reasons.)

          • I don't think we're talking about the same thing. We're talking about this thing apparently called "inner source".
            • We are taking about the same thing. Inner source means releasing the code under an permissive license on github, but calling it something other than open source so that corporate managers say okay. I think it also means only accepting pull requests from inside the company.
              • by Vairon ( 17314 )

                You can look through the commit history of vscode and see examples of them accepting PRs from individuals that do not work for Microsoft.

        • If you have not released your software's source code to a public in some feely available (free as in beer) way where one can inspect the source code, modify it, etc, that is the very definition of "closed source".

          Visual Studio Code source code is on GitHub.

          "This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product. Not only do we work on code and issues here, we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license."
          https://github.com/microsoft/v... [github.com]

        • by Vairon ( 17314 )

          Inner-sourcing is about a company or organization making its internal code open-source to all of its employees, contractors and depending on the license that may include the public at large as well. It's also about using open source practices such as open collaboration and communication to develop open-source code inside that company.

          In my experience, a company that only uses closed-source or proprietary software is more likely to depend on outside closed-source vendors for their software. If they do develo

      • Literally the first sentence after the term definition in that Wikipedia article says that the software is proprietary.

        "Closed" or "proprietary" are always in relation to the world, i.e. the public at large. Intra-corporation term fiddling doesn't change anything.

        • by AmiMoJo ( 196126 ) on Monday February 08, 2021 @07:35AM (#61039626) Homepage Journal

          No it doesn't. It says:

          "The organization may still develop proprietary software, but internally opens up its development."

          Note the word "may". It is saying that it is possible to use this technique for proprietary software, not that it is mandatory.

          Sure enough, Visual Studio Code is open source.

          • Context is key. As far as "inner-source" is concerned, Wikipedia's "may" basically means that it's prorietary. If it was open, there'd be no need to call it "inner", they'd call it "open".

            You don't call Linux, or Emacs, or Gnome "inner-source software", though they technically fulfill all the requirements. You call them F/OSS, because they fulfill a superset of "inner" which qualifies for "open" and for "free". The're open to anyone.

            As soon as you choose to call something "inner-source", that's because you

            • Re: (Score:2, Informative)

              by AmiMoJo ( 196126 )

              Linux and EMACS don't meet the requirements. You don't seem to know what inner source is.

              All it means is organizing your commercial development like an open source project, rather than like a typical engineering group. And as I pointed out, the product they are discussing this in relation to is Visual Studio Code, which is open source.

              • Organizing it like open source such that you don't pay the developers, or only pay them when they come up with a change on their own, with no management involvement, that meets the goals of the project and company?

            • Comment removed based on user account deletion
              • Open source development styles... Not even sure what that is. Is there an Open Source Development Standard such that all the projects develop products the same way? I don't think so. If "inner source" means you have a guy named Linus at the top who occasionally throws tantrums then it's not much different from a lot of corporations :-) But if it means that when a project is dumped because the developers got bored and then someone else comes along and revives it, then how's that work in a commercial wor

              • No, they're not, but this doesn't matter here. Again, context is key.

                Free Software is software that respects the 4 freedoms (GNU).

                OpenSource is a little more tricky because different people assume different things, but if you adhere to the Open Source Initiative (and FSF), it's in large parts and for most purposes similar to Free, but not exactly the same thing. But nuances are subtle, and RMS himself states that "the differences in extension of the category are small: nearly all free software is open sourc

      • What's the point though? Open source development is done the way it is because it is forced to; the developers may have never met each other, and any random bozo is allowed to look a the code and try to submit changes. This means you need a gatekeeper, or a set of gatekeepers. And if the guys submitting don't like that they're rejected then you may get forks. Maybe the fork is good, maybe it's bad, but from the standpoint of trying to manage an actual product, which is what a company needs to do, it's a

    • And it is, but at least they're not giving it a confusing name.

      Inner source still makes it sound like closed source, which it is. Inner invokes "internal".

  • Also you can take vi (well I use Vim) and ed (which vi is based on) out of my cold dead hands :D Never used an IDE full-time and not about to start!
  • by Tough Love ( 215404 ) on Sunday February 07, 2021 @08:59PM (#61038582)

    Javascript inside. You have been warned.

  • This doesn't sound like good news.

    Monocultures are usually not good things as they introduce massive weak points.. You wouldn't want every tree to be the same species. If a blight arose you're screwed.

    You wouldn't want the majority of the world's coding environments to be vulnerable to a devastating bug or security issue occurring in a single IDE and/or deployment system.
  • by account_deleted ( 4530225 ) on Sunday February 07, 2021 @09:38PM (#61038718)
    Comment removed based on user account deletion
    • I'm partial to WebStorm for JavaScript projects. Most of my team uses VSCode and when I observe them they seem to be missing refactoring and code inspection features that I take for granted and couldn't live without, though I've been told there are plugins for VSCode that can add those.

    • by PPH ( 736903 )

      I'll use whatever tool I find is best for the job.

      Acording to TFS, "inner source" refers to collaborative projects between teams within a company. So yeah. You can use this if it works for you. But I suspect that if its a "team" project, you will have to use the tools that the team selects. Particularly if the collaboration hooks are tightly bound to VS Code.

      Where I used to work, we'd always have one weak-willed dev that got invited to Microsoft workshops. And he'd come back with some new tool suite that they'd foist on him. And then if we didn't all swit

  • Microsoft didn't make up the term inner source and the approach means taking open-source development practices and applying them inside a single organization. GitHub and GitHub's Enterprise Server fits snuggly with this approach to help organizations collaborate but do so in private.

    This is not anything new. Proprietary code is sometimes made available under binary licenses or source licenses. Under the latter you may only distribute binaries, the source may NOT be distributed, but you are free to modify it and ship your modified binary. This is vital as it allows the licensee of this code to control their own fate and not be dependent upon the original developer. Sharing changes, usually bug fixes, upstream was common.

    "Inner source means if you have private IP, but you're inviting other teams within the company to collaborate with you. That's the fundamental difference between open source and inner source. Today, it's very common in large enterprise..."

    No, that is mistaken, note that inner source allows collaboration w

  • Look - when you have the skills to see an issue and the experience to know how to overcome it, then this is not really a problem.

    If GitHub gets in the way it will be replaced. Git is after all open source.

    If VSCode / VSCodium starts to be annoying, likewise. Screw it. You could try Eclipse?

    Same with TypeScript. It will just fork if there is a problem. This is the way of open source code.

    Learn JavaScript. Learn your favorite basic editor. (vi, vim, ex, ed, nano, emacs, whatever) You are safe for some time.

    Do

  • by Locutus ( 9039 ) on Monday February 08, 2021 @01:29AM (#61039140)
    It seems there are so many developers using MS VS Code that the Raspberry Pi org decided every rPi needs to phone home to Microsoft no matter if you installed MS VS Code or not. They have quietly added the Microsoft repository to the apt sources list. Just look in /etc/apt/sources.list.d and you'll find the vscode.list file.

    And it's even been done to the rPiOS server version.

    It never ceases to amaze me at how naive corporations and organizations become when the MS MiB come to visit and promise wonderful things as long as you give up your soul. And the souls of all your customers too.

    LoB
  • Are Slashdot "editorials" just paid ads for MS. It looks like that to me.
  • "Inner Source" are just WEASEL WORDS.

  • by matushorvath ( 972424 ) on Monday February 08, 2021 @06:26AM (#61039492)

    Funny how so many people completely missed the concept of inner source. Yes it's not open source, but nobody says it is. It's using open source project management methods to develop proprietary software.

    If you ever worked in a large software corporation, I think you will understand. Often there are silos of people working on various software products, and you as a developer within one team, you have no access to code of other teams, even though you are forced to use their software. That's frustrating as hell, you find yourself using software with bugs that would be trivial to fix if only you could see the source.

    Inner source is just an answer to that. As a developer within the corporation, you can see all the source code, even for software you don't officially work on, and you can create PRs and contribute to the source just as if it was open source software.

    It's nothing more, nothing less. It's still proprietary software, so yeah that's not ideal. But for us who work in a corporation because they like to eat food, it does two things:
    1. You can finally fix those annoying bugs you had to workaround for years. This improves software quality for everyone, similarly to how open source improves software quality for everyone.
    2. It teaches the tie-wearing MBAs that closely guarding the source code is not necessary, in fact that making something more open basically gives you free resources to work on your project (that's how they tend to think about it).

    This is just the result of developers used to working with open source software slowly transforming the corporations from inside. I see it as a good thing. Yes, it could go faster, yes, it's just one step on the way. Still better than no step.

  • After getting my 3D printer last year I had to download VS Code, the free version at least, in order to update the firmware of my printer. I'm not doing any development with it. If I add something to my printer or want to update the firmware I compile the firmware and send it to the printer with VS Code.

    So how many of those 5M new people last year were just people that got 3D printers. I was one of them.

Anyone can make an omelet with eggs. The trick is to make one with none.

Working...