Slashdot Mirror


Microsoft Releases Skype As a Snap For Linux (betanews.com)

BrianFagioli writes: While Microsoft has long been viewed as an enemy of the Linux community -- and it still is by some -- the company has actually transformed into an open source champion. One of Microsoft's biggest Linux contributions, however, is Skype -- the wildly popular communication software. By offering that program to desktop Linux users, Microsoft enables them to easily communicate with friends and family that aren't on Linux, thanks to its cross-platform support. Today, Microsoft further embraces Linux by releasing Skype as a Snap. This comes after two other very popular apps became available in Snap form -- Spotify and Slack.

"Skype is used by millions of users globally to make free video and voice calls, send files, video and instant messages and to share both special occasions and everyday moments with the people who matter most. Skype has turned to snaps to ensure its users on Linux, are automatically delivered to its latest versionupon release. And with snaps' roll-back feature, whereby applications can revert back to the previous working version in the event of a bug, Skype's developers can ensure a seamless user experience," says Canonical.

88 of 166 comments (clear)

  1. Don't copy that floppy! by Anonymous Coward · · Score: 1

    Don't install that snap!

  2. I've been out of the Linux loop for a few years. by aussersterne · · Score: 2

    What is a "snap"? Has the distro-packaging problem finally been solved?

    --
    STOP . AMERICA . NOW
  3. what is it? by fluffernutter · · Score: 1

    Is it a real application, or is it a slimmed down web browser with the sucky HTML version of Skype?

    --
    Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
    1. Re:what is it? by Hal_Porter · · Score: 1

      MS recently rewrote Skype to run on ReactXP.

      https://microsoft.github.io/re...

      What's that? It's MS's fork of React Native.

      https://microsoft.github.io/re...

      ReactXP was designed to be a thin, lightweight cross-platform abstraction layer on top of React and React Native. It implements a dozen or so foundational components that can be used to build more complex components. It also implements a collection of API namespaces that are required by most applications.

      ReactXP currently supports the following platforms: web (React JS), iOS (React Native), Android (React Native) and Windows UWP (React Native). Windows UWP is still a work in progress, and some components and APIs are not yet complete.

      The ReactXP version of Skype runs on Windows 10, iOS, Android and macOS. What about Linux? Well it seems like they support it via web wrapper, like Windows 7 and macOS

      https://microsoft.github.io/re...

      ReactXP currently supports the following platforms:

      iOS (React Native)
      Android (React Native)
      Web (React)
      Windows 10 â" UWP (React Native) - in progress
      Other platforms such as Windows 7 & 8, MacOS, and Linux can be targeted using a web wrapper solution like Electron.

      So I think the answer is probably "the latter". Though I use Skype on my Windows 7 and macOS machines and it's ... OK despite being the web wrapper version. I prefer the old native app, but it does the job.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    2. Re:what is it? by WallyL · · Score: 1

      MS recently rewrote Skype to run on ReactXP.

      https://microsoft.github.io/re...

      ReactXP? That sounds cool. Maybe that's a variant of ReactOS that targets Windows XP.

      What's that? It's MS's fork of React Native.

      https://microsoft.github.io/re...

      Rats. Well, it was a good thought.

  4. How this sounds to me: appy snaps! by ToTheStars · · Score: 2, Funny

    LUDDITE Linux can now run snappy app Skype snap! Appy snap apps! Skypes! Snaps!

  5. Re:I've been out of the Linux loop for a few years by Anonymous Coward · · Score: 4, Informative

    Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.

    https://snapcraft.io/

  6. Irresponsible Word Choice by scunc · · Score: 5, Insightful

    Skype is a "wildly popular communication software" in the same way that chlamydia is a "wildly popular" STI. Sometimes numbers alone don't tell the whole story ...
    ---
    "Think of how stupid the average person is, and realize half of them are stupider than that." -- George Carlin

    1. Re:Irresponsible Word Choice by thegarbz · · Score: 1, Interesting

      Sure. If every other person also has chlamydia then your comparison would be accurate. On the desktop Skype is the single most popular video chatting app. What you personally think about it doesn't change that fact or doesn't change the fact the word choice is perfectly fine.

    2. Re:Irresponsible Word Choice by enjar · · Score: 2

      My company uses Linux, Windows and Mac across the enterprise. All of our email/calendar/messaging comes from Exchange/Outlook/Skype. Now if MS would release Outlook in this same format I could happily jettison the Windows VM I run Windows/Outlook/Skype on and not have to put up with its endless bullshit. Mac already has a client for all the MS stuff that people use.

      It's about 6 steps above my pay grade to do anything about this choice, so the chances of swapping out the company's messaging platform for some open source thing, or switching everyone to Linux isn't going to happen because I open my mouth. Our customer base uses all platforms so it's not like we could drop one platform and stay solvent.

    3. Re:Irresponsible Word Choice by Anonymous Coward · · Score: 1

      According to the Center for Disease Control, "Chlamydia is the most commonly reported STD in the United States".
      https://www.cdc.gov/std/chlamydia/stats.htm

    4. Re:Irresponsible Word Choice by ArhcAngel · · Score: 4, Informative

      Skype for Business != Skype

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    5. Re:Irresponsible Word Choice by Rakarra · · Score: 1

      Skype is not super-popular in the home market as it once was.
      I used to have tons of friends on Skype, now the only people on it are a couple of die-hard holdouts. Everyone else, one by one, said they were sick of the Skype client being a resource hog, how finicky and buggy it was, and how "skype sucked" for the last several years. They pretty much all went to either Discord or Telegram.

      I never noticed too much; I always ran a skype plugin for Pidgin. I have no use for video calls, just messaging my friends, so all I ever needed was the instant messenger part of it. I added them with Discord and Telegram plugins for Pidgin, so I still chat with the same interface. But I noticed this trend over and over again. "ICQ sucks now, I'm switching to Yahoo Chat." "Yahoo blows, they fucked up their client, so I'm switching to AIM." "AIM is fucking up my computer, I'm moving to Skype, join me there!" "Skype blows since MS bought them. It slows down my computer. You can find me on Discord now." It sucks that everyone wants to use the official client from the chat networks. The client always sucks, does things that you don't want it to do (like refuse to support logging, spying on you, serving you ads, slows down your PC), and they just jump from network to network every 1-2 years. The networks should be open (like AIM and IRC were) to third-party clients, and should be multi-network as well so you don't have to fun five different clients to keep in touch with everyone.

    6. Re:Irresponsible Word Choice by rtb61 · · Score: 2

      So just use something else https://askubuntu.com/question.... Just because it is popular does not make it good, which is why the disease reference. Just because it is wide spread, does not mean you don't want to get rid of it. In this case M$ has a terrible reputation for invasion of privacy, corrupt practices, a willingness to install software they know you don't want. So a communications app, ask one question, do you think M$ will listen in or not, now or some time in the future based upon past and current practices, you can lie if you wish but you know the real answer, of course they will.

      --
      Chaos - everything, everywhere, everywhen
  7. Oh hurray... by Junta · · Score: 4, Interesting

    Now when a security update comes for a core library, now I get to update every single snap instead of just updating the system library...

    Yay for static linking, I mean containers....

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re: Oh hurray... by Anonymous Coward · · Score: 1

      Not only that but, with most distros, maybe at most you have 3-4 versions of some libraries/packages just for supporting random Apps. You can logistically keep track of that in case bugs come out and you can also be quite sure that the supplied libraries have been unmodified.

      With Snaps, if you have 120 installed Snap Apps, you literally could have up to 120 different copies of that library and all could be different versions and those versions could be modified within updates thus making even more unique different versions with potentially more bugs. Try logically keeping track of that if bugs come out.

      The only reason it's "safer" is because bugs shouldn't be able to break out of the App container, but if Snap apps go un-patched over time, maybe you'll have dozens of old libraries and insecure files in all of these containers.

      Packaging everything together is cool but once you switch you can't go back, really. Because now generally a distro has version x.y of a library and the apps simply must support those stable/secure versions--period.

      Once everything becomes a snap, now each single App is going to be using their own bizarre concoction of different versions of every library/framework/dependency etc. If they all need to coexist again it's just going to be a train-wreck or like "dependency hell" back in the day when you had to manage your 20+ Slackware floppy disks and programs.

    2. Re:Oh hurray... by rnturn · · Score: 1

      Well, Micron execs probably love static linking, containers, et al.

      --
      CUR ALLOC 20195.....5804M
    3. Re:Oh hurray... by StormReaver · · Score: 1

      ...instead of just updating the system library...

      Snaps are useful for sampling pre-release software. I was curious about the current state of Kdenlive, as the last version I used was horribly unstable, and saw that they offered a Snap. I downloaded the Snap and ran it, and got to test drive Kdenlive without having to install (and potentially uninstall) the program.

      But that's about the extent to which I like Snaps.

    4. Re:Oh hurray... by Khyber · · Score: 1

      "Now when a security update comes for a core library, now I get to update every single snap instead of just updating the system library..."

      Oh fucking please, as if the goddamned program didn't need a recompiling or update anyways to keep up with the changes caused by the newer library versions either obsoleting or entirely removing functions in favor of newer ones, since nobody these days knows a fucking thing about slow and stable and reliably-present features.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    5. Re:Oh hurray... by Junta · · Score: 1

      The last several decades or so of software ecosystem shows that yes, indeed bugfix and security updates to libraries happen all the time without requiring dependent applications to rebuilt.

      At least for mainstays of C and C++ application development. People breaking any semblance of compatibility is generally not tolerated in C/C++ (though there are exceptions) and even in the broader software market, people *tend* to be mindful of compatibility (though in the worlds of gems, pypi, npm, et al, yes there are a larger proportion of broken libraries. If you stick to your distro and pick a distro that cares, you can have a solid 8 years of updates that won't break existing applications.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  8. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  9. Wow! by nospam007 · · Score: 2, Insightful

    "While Microsoft has long been viewed as an enemy of the Linux community -- and it still is by some -- the company has actually transformed into an open source champion."

    Wow! Is that straight from the MS marketing slime?

    1. Re:Wow! by thegarbz · · Score: 1

      Well I guess the first "by some" has shown himself.

    2. Re:Wow! by gfxguy · · Score: 4, Insightful

      I've been using Linux since slackware c. 1994. I actually have come to appreciate some of the things MS has done w.r.t. Linux - running a development web server under WSL makes my life a lot easier when I have to use Windows for most things anyway. Their development tools are actually really nice, too; the .Net system of being able to write interchangeably between different languages is not perfect, but works really well for most of my Windows development.

      Yet, the marketing speak is absurd.

      --
      Stupid sexy Flanders.
    3. Re:Wow! by KozmoStevnNaut · · Score: 1

      MS is partially responsible for the debacle that is UEFI and (at least for a while) making it really shitty and annoying to put a non-MS OS on your newly purchased PC.

      Not to mention the raft of new Windows-based "faux Chromebooks", which have all kinds of shitty hardware with absolutely no driver documentation.

      --
      Eat the rich.
  10. Re:I've been out of the Linux loop for a few years by Anonymous Coward · · Score: 1

    It's like flatpak, except just works on ubuntu, because not invented here. Basically.

  11. Re:I've been out of the Linux loop for a few years by 110010001000 · · Score: 4, Insightful

    What makes them "safe to run"? Is the software that they run in the container open source and can be inspected? If not, how do you know it is "safe to run"?

  12. Tried using Skype on Linux by QuietLagoon · · Score: 2

    Debian to be specific. It would not work with my friends who use the Windows version of Skype. Skype would connect, but no video, no audio. And no error message of any kind.

    1. Re:Tried using Skype on Linux by Trailer+Trash · · Score: 4, Funny

      Debian to be specific. It would not work with my friends who use the Windows version of Skype.

      You have friends who..... use Windows?

    2. Re:Tried using Skype on Linux by blindseer · · Score: 1

      Friends don't let friends use Windows.

      I don't have friends that use Windows, I've left those that could not leave Windows. Family members still use Windows and I can't abandon family. I can only support them as best I can until they see daylight.

      --
      I am armed because I am free. I am free because I am armed.
    3. Re:Tried using Skype on Linux by David_Hart · · Score: 2

      Friends don't let friends use Windows.

      I don't have friends that use Windows, I've left those that could not leave Windows. Family members still use Windows and I can't abandon family. I can only support them as best I can until they see daylight.

      True friends do not let an OS choice affect their friendship unless one of them is in a cult... (grin)

    4. Re:Tried using Skype on Linux by HyperQuantum · · Score: 1

      You..... have friends?

      FTFY

      --
      I am not really here right now.
  13. skype or Skype for Business? by Joe_Dragon · · Score: 1

    skype or Skype for Business?

  14. Champion? by Anonymous Coward · · Score: 5, Informative

    " the company has actually transformed into an open source champion"

    Really? So Skype is being released as an open source app? No. Windows is being released as an open source OS? No. Microsoft has agreed to stop using patents and fear mongering to extract money from companies using open source software? No.

    So Microsoft is actively working against open source companies and is not releasing its software under open source licenses. How exactly is Microsoft an open source champion?

    1. Re: Champion? by liefer · · Score: 1

      Even if they did completely open source windows, office, azure and everything else, gave all their money to Linux and became nonprofit, I'm sure the slashdot crowd would find a way to see it as not being enough

    2. Re:Champion? by raddan · · Score: 1

      All of .NET is open source.

      Numerous languages are open. Even the compiler is open source.

      You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

      In short, you are living under a rock.

    3. Re: Champion? by liefer · · Score: 1

      I do, yes. Thanks for noticing :)

  15. Re:true champions of open source by xvan · · Score: 1

    Just not true. Linux support was stalled for years until Microsoft bought them and released an updated version. It receives frequent updates since then.

  16. A shitty replacement for static linking? by Anonymous Coward · · Score: 3, Interesting

    In the early days of microcomputing, we used static linking when creating an application binary. The code we wrote would be linked against any third-party libraries, and a single binary containing the application code and the library code would be the result. Life was easy.

    Then there was this huge push toward dynamic linking, with its proponents going on about how it's supposed to use less memory, it's supposed to use less disk space, and it's supposed to allow libraries to be updated easily, and so on and so forth.

    But then we experienced "DLL hell" or the "shared object shitshow", which turned out to be far worse than anything we experienced with static linking.

    So workarounds, like the various Linux package managers, were created to try to handle the complex dependencies between applications and their shared libraries. This is effectively a complex form of static linking, done by keeping shared library versions consistent with the installed applications.

    When that proved to be problematic, such as when there were different applications that depended on different versions of the same shared library, we started seeing a move toward this "containerization" nonsense. There are different approaches used, but again they all have one thing in common: they're a complex way of imitating static linking.

    I hope that someday soon the industry at large wakes up to the fact that static linking is just the most sensible thing to do. Yes, the binaries might be slightly larger, but that's well worth it if it means we can avoid "DLL hell" or the "shared object shitshow", and if we can avoid complex package managers, and most important of all, if we can avoid this goddamn "containerization" bullshit.

    Now there may be problems when it comes to certain libraries, because they use highly restrictive licenses like the LGPL that effectively force the use of dynamic linking if you don't want your code to be infected by a viral license. The solution to this is simple: don't use poorly licensed libraries. Stick with libraries that use static-linking-friendly licenses like the MIT or BSD licenses, for example.

    A whole lot of problems would be solved if we stopped with all of this dynamic stupidity and just went back to static linking.

    1. Re: A shitty replacement for static linking? by gustavojralves · · Score: 2, Insightful

      Exacly what I'm feel about all those new package systems.

    2. Re:A shitty replacement for static linking? by Anonymous Coward · · Score: 1

      Why can't we just compile everything from source? That would be perfect for stuff like Skype, where trustworthy crypto is a must.

    3. Re:A shitty replacement for static linking? by ArtemaOne · · Score: 1

      This makes so much sense. Back when RAM and storage space were relatively scarce it seemed the way to go without a doubt. I observed the advantages, but we have since outgrown the scarcity of resources available on modern systems, and a self contained program does seem to make far more sense in this age of computing.

    4. Re:A shitty replacement for static linking? by tlhIngan · · Score: 5, Interesting

      When that proved to be problematic, such as when there were different applications that depended on different versions of the same shared library, we started seeing a move toward this "containerization" nonsense. There are different approaches used, but again they all have one thing in common: they're a complex way of imitating static linking.

      I hope that someday soon the industry at large wakes up to the fact that static linking is just the most sensible thing to do. Yes, the binaries might be slightly larger, but that's well worth it if it means we can avoid "DLL hell" or the "shared object shitshow", and if we can avoid complex package managers, and most important of all, if we can avoid this goddamn "containerization" bullshit.

      Now there may be problems when it comes to certain libraries, because they use highly restrictive licenses like the LGPL that effectively force the use of dynamic linking if you don't want your code to be infected by a viral license. The solution to this is simple: don't use poorly licensed libraries. Stick with libraries that use static-linking-friendly licenses like the MIT or BSD licenses, for example.

      A whole lot of problems would be solved if we stopped with all of this dynamic stupidity and just went back to static linking.

      No, because dynamic linking, even with non-shared shared libraries is still better. Static linking hides important information like library versions which may be important.

      With dynamic libraries, even inside containers, you can still validate the library version to see if it's a vulnerable library. You can run tests against the library to determine if it's vulnerable (just because it's inside a container doesn't mean you can't extract it and test it). This way when a vulnerability happens, you can verify whether or not the copies of the libraries you have are vulnerable since a scanner can go inside containers and check. Users can then either not use the app until it gets an update with a fixed library, try to fix it themselves by replacing the library, use the app understanding its vulnerable, etc.

      When you static link, you lose those benefits - for what? Just to have one file? That's not going ot happen ever - it's why we have containers to begin with.

    5. Re:A shitty replacement for static linking? by Etcetera · · Score: 1

      This makes so much sense. Back when RAM and storage space were relatively scarce it seemed the way to go without a doubt. I observed the advantages, but we have since outgrown the scarcity of resources available on modern systems, and a self contained program does seem to make far more sense in this age of computing.

      Lolwut?

      Not when my phone keeps running out of space.
      Not when some glorified IRC chat program (Stride) requires 400MB of resident memory to run.
      Not when some idiot replaced perfect good shell scripts with a compiled monstrosity that's 10 times larger in an attempt to shave 5 seconds off a reboot that never happens.

      People are making all sorts of dumb decisions because they think resources are limitless again. They're not. Resources are always limited. The only time things change are when the actual underlying technology changes. (E.g., moving from spindles to SSD means I/O performance has improved drastically for some use cases.)

    6. Re:A shitty replacement for static linking? by Etcetera · · Score: 2, Insightful

      So workarounds, like the various Linux package managers, were created to try to handle the complex dependencies between applications and their shared libraries. This is effectively a complex form of static linking, done by keeping shared library versions consistent with the installed applications.

      When that proved to be problematic, such as when there were different applications that depended on different versions of the same shared library, we started seeing a move toward this "containerization" nonsense. There are different approaches used, but again they all have one thing in common: they're a complex way of imitating static linking.

      Here's the thing though... That wasn't problematic. We have perfectly good Linux distros that provide perfectly good platforms using dynamic linking. We have them at varying levels of stability and long term support: RHEL and its derivatives if you need Enterprise ABI guarantees so that you *don't* ever have a chance of shared library incompatibilities on the platform, and Fedora if you want more frequent updates, although with ABI stability mostly guaranteed within a given annual OS release.

      These two OS's work fine. Yes, there were dependency problems initially, but yum and apt-get solved resolution issues DECADES ago. The only people who complain about dependency hell nowadays are those who don't understand that some things change and some things stay the same, and that you ideally will recompile for a new OS release.

      In short, the people who don't understand this are Windows Developers and Java Developers.

      They have no idea how shared libraries work on Linux, have little or no understanding of package management generally (Literally the only people who complain about 'dependency hell' are those trying to use RPM/dpkg to do YUM/apt-get's job.), or are trying to iterate with ABI breakage every 3 weeks like a generic Silicon Valley d-bag.

      Statically compiling everything, adding three layers of virtualization nonsense, putting out 500MB .jar files, or live-including left-pad npm, because you don't know how packaging works is the epitome of the current industry approach. And it sucks for everyone else trying to keep some sanity in the mix.

    7. Re:A shitty replacement for static linking? by ArtemaOne · · Score: 1

      Good points. I have not had these issues, but they clearly still exist.

    8. Re: A shitty replacement for static linking? by Anonymous Coward · · Score: 1

      Static linking means a vulnerability in a widely used library means re-compiling every executable and/or waiting for each developer to release a fixed binary only executable, assuming they do.

      Those weren't fun days.

    9. Re:A shitty replacement for static linking? by JabrTheHut · · Score: 1

      I’m afraid you’re confusing idea with implementation. Dynamic linking is great and works well on every major Unix platform as well as a few bygone ones. The Linux implementation is rubbish and it’s the implementation that causes the headaches.

      --
      Work like no one is watching. Dance like you've never been hurt. Make love like you don't need the money.
    10. Re:A shitty replacement for static linking? by Kickasso · · Score: 1

      Magic!

      Posted from my Gentoo box.

  17. No "champion" at all. by l2718 · · Score: 4, Insightful
    From TFA:

    [Microsoft] has actually transformed into an open source champion

    Really? So shere is the source code for this "snap"? In fact:

    1. Compiling your software for GNU/Linux doesn't make you a "champion of open source" just because GNU (and Linux) are open-source (and, more importantly, also Free Software). Releasing your source code makes you open-source.
    2. "Snaps" are the opposite of the Unix philosophy of dynmically linking against system libraries – they are basically statically linked binaries (except that the binary comes in pieces). Instead of the "open-source" philosophy of clean interfaces and interoperability, they embrace a philosophy of tailored interfaces and closed gardens.

    In fact, to the extent Microsoft champions "open source", this open-source is about taking advantage of source code released by others without Microsoft releasing any of its own. When I see Microsoft releasing source code under a free license (say BSD) for a significant program originally created by Microsoft (Skype, their web browser) I will believe them.

    1. Re:No "champion" at all. by Doctor+Memory · · Score: 1

      When I see Microsoft releasing source code under a free license (say BSD) for a significant program originally created by Microsoft (Skype, their web browser) I will believe them.

      Microsoft bought Skype, they didn't write it. The one they did write (Lync, nee Office Communicator, now Microsoft Teams) is completely different.

      --
      Just junk food for thought...
    2. Re:No "champion" at all. by sad_ · · Score: 2

      "Snaps" are the opposite of the Unix philosophy of dynmically linking against system libraries – they are basically statically linked binaries (except that the binary comes in pieces). Instead of the "open-source" philosophy of clean interfaces and interoperability, they embrace a philosophy of tailored interfaces and closed gardens.

      Great comment, now i finally see the point of snaps. They only exist to facilitate closed source software. If you use open source software there is no need as you can easily make it to run on your system.

      --
      On a long enough timeline, the survival rate for everyone drops to zero.
  18. Re:I've been out of the Linux loop for a few years by ArhcAngel · · Score: 1

    I believe each snap is sandboxed by default.

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
  19. Re:I've been out of the Linux loop for a few years by duckintheface · · Score: 5, Informative

    This particular snap install is NOT safe to run. When you run "snap install skype" in a terminal you get a warning that skype is packaged using "classical" isolation and may escape the sandbox and make unrelated system changes. In order to install, you have to add the --classic flag to indicate you understand the risks. I did not install skype.

    --
    "He took a duck in the face at 250 knots." -- William Gibson, Pattern Recognition
  20. Sabotage by Gavagai80 · · Score: 4, Informative

    As someone who actually uses Skype for Linux, I can say definitively that it's a torture device meant to make Linux users experience excruciatingly unpleasant interfaces, Windows ME stability, Windows Vista levels of bugs, and pointless slowness for what is actually no more than a frame around a website. The Skype for Linux from before MS bought it was a far better, more feature-full and reliable product... since the MS purchase it has only been progressively sabotaged. The several years it went without an update were nice, but ever since updates resumed it gets more painful in each release.

    --
    This space intentionally left blank
  21. "Fully embraces linux"?? by l2718 · · Score: 3, Insightful

    In fact, this is Microsoft trying to support a dangerous undercurrent in the Linux world of walled gardens and insecure vendor-controlled installations.

    If something is wrong in libc, libm, or libgtk Microsoft should get it fixed upstream, not ship their own incompatible version. Do you really trust them to backport every future bugfix after their fork?

    1. Re:"Fully embraces linux"?? by l2718 · · Score: 1

      BSD has non-GPL version of libc and libm; in any case you only have to offer the source code, not to directly contribute it to the upstream project.

    2. Re:"Fully embraces linux"?? by jouassou · · Score: 1

      Agreed. Let them use their libc, and run their software in a sandbox like Firejail, and hopefully they can't do anything except what you let them do. (Which is to monitor you via webcam and microphone, and upload it to the internet.)

  22. Re:Alternatives? by Hal_Porter · · Score: 1

    What is the address of these turtles? I'd be glad to sent my assistants Mr R Steady and Mr B Bop round and to take care of them

    Yours,

    Oroku Saki

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  23. Just What I'm Looking For by NicknameUnavailable · · Score: 3, Interesting

    An IM client which spies on me and logs all my conversations for Microsoft without so much as a decent search function for me to view my own archives. There's no reason to use Skype outside of a business environment where you have to do so, there are plenty of open source alternatives and there are plenty of more popular things if you can't get your friends to switch.

  24. Re:I've been out of the Linux loop for a few years by Anonymous Coward · · Score: 1

    What makes them "safe to run"? Is the software that they run in the container open source and can be inspected? If not, how do you know it is "safe to run"?

    They think it's safe to run because Microsoft said so. You know, just like they said their "operating system" (hahaha) is "safe to run". There's no real reason to believe a word out of the mouth of anyone who works or worked for Microsoft. Also, you know how Skype is used by "millions of users" to make "free" calls? Yeah, well, if you're not paying for a service, you're not the customer, you're the PRODUCT. In the case of Free/Libre Open Source Software, the motivation is generally altruistic. The ability to legally fork software if the owner/maintainer ever gets greedy prevents malfeasance of the type Microsoft routinely practices.

  25. Does this one work? by GameboyRMH · · Score: 2

    I wonder if they've fixed the White Screen of Death that the latest version of Skype for Linux in the repos suffers with (start program, receive white screen with basic window controls and nothing else). I've rolled back to an older version and blocked updates for the package to work around it.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
    1. Re:Does this one work? by GameboyRMH · · Score: 1

      Does this white screen of death take down the whole system or can you at least SSH into a terminal and kill X?

      It just freezes up the Skype window, you can easily kill it.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Does this one work? by GameboyRMH · · Score: 1

      Possibly, but it would be a lot of work to set up the X environment. You'd probably have an easier time with andLinux.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  26. Was already available as Flatpak, same as Spotify by buchanmilne · · Score: 2

    And Skype was already available as a Flatpak available on flathub (and easily installable from the gnome-software GUI).

    The summary could have mentiomed that (and, of course, that Slack and Spotify are also available as Flatpak's from Flathub)

  27. Re:Open source champion? by Anonymous Coward · · Score: 4, Interesting

    MS has been one of the largest contributors of open source projects and applications over the past few years. MS has been positioning themselves to transforming their flagship OS and related applications to a true cross platform solution. Think about all those people and companies that cannot move to a Linux platform due to the lack of Linux application support. No think of signing into your computer and being able to start a Windows session or Linux session without any intervening VM. Think about a version of .NET that is open source and cross platform. The number one rule in capturing a large market share is to make it easy for developers to create applications. It's a lesson the Linux fateful have never really understood. MS has always catered to the developers. MS VB was probably the one product that pushed MS to the top. VB allowed almost anyone to become a developer. VB was certainly not a perfect development tool but it was easy compared to C\C++ or any other native languages that the average person could not use. VB allowed the rapid creation of applications that ran on the MS application stack. (VB had a lot of faults. People created a bunch a sup-par applications. These two characteristics didn't stop the adoption of VB and all the subsequent adoption of a pure MS application stack.)

  28. Helping friends with switching obstacles by tepples · · Score: 1

    "I tried $linux_distro on my laptop, but it couldn't find my audio or Wi-Fi, and when I took it out of suspend, it stayed on a black screen. Others on forums mentioned the same problem without a solution." What's your next course of action for a friend who tried and failed to defenestrate his laptop?

    1. Re:Helping friends with switching obstacles by blindseer · · Score: 1

      What's your next course of action for a friend who tried and failed to defenestrate his laptop?

      Buy an Apple.

      If funding limitations prevent buying a new computer then install VirtualBox and the Linux distro of your choosing in a virtual machine. Make the virtual machine as big as possible on RAM and drive space allocations. Run everything in the virtual machine, with the full screen option. The laptop will simply appear in most every case to be running Linux on the metal. That way Windows is not much more than a hardware abstraction layer.

      Another possible solution, assuming the problems are limited to lacking sound, WiFi, and perhaps some other hardware issues, is install Linux on the metal and purchase some USB peripherals that Linux supports. I did this with one of my laptops. The machine had four USB-A ports and I put these tiny little USB adapters for Bluetooth and WiFi into two of those ports. They are so small that they almost disappear in the port. This still left a port for a mouse and another for whatever else I wanted to plug in, such as occasional use of a flash drive, a cell phone, or an optical drive. If the $50 or so to buy these USB adapters and "defenestrate" your laptop... {ahem} I mean "your friend's laptop", is too much then see above and run Linux in a virtual machine.

      What should your friend do if he cannot afford a new Apple laptop? And, has a laptop that cannot run Linux? Or, not enough memory to run Linux in a Windows VM? And, cannot afford a memory upgrade? Or, Linux will run but there are some issues with sound and networking? And, your friend cannot afford some USB adapters to address those hardware shortcomings? Or, using up USB ports is impractical for some reason? Well, then maybe your friend needs to cut back on the trips to the coffee shop and brew at home to save some money to get some hardware.

      Assuming your friend is dedicated to leaving Windows then this is a problem that will come to resolution eventually. At some point that laptop will need to be replaced. It could be broken, stolen, worn out, or just deemed too outdated to be useful. Tell your friend to put up with Windows for now but just don't buy another computer with Windows on it in the future. In the mean time suggest to him that he install as much "Linux-like" software to do what he needs to make the future switch to Linux as smooth as possible.

      Also, I don't believe for a second that you are "just asking for a friend".

      --
      I am armed because I am free. I am free because I am armed.
  29. The direct link by Midnight+Thunder · · Score: 1, Informative

    To save people trying to find the link to the official page, here it is: https://snapcraft.io/skype/

    --
    Jumpstart the tartan drive.
  30. Latest version? by HalAtWork · · Score: 2

    "Skype has turned to snaps to ensure its users on Linux, are automatically delivered to its latest version upon release."

    Are they also going to release a new snap any time one of the static linked dependencies are updated as well?

    "And with snaps' roll-back feature, whereby applications can revert back to the previous working version in the event of a bug" ...and also previous unpatched versions of static linked dependencies as well.

    I think I like normal packages with shared libraries I can ensure are up to date whenever any app or utility relies on them to run.

    1. Re:Latest version? by HalAtWork · · Score: 1

      I'd rather update the distribution at that point. I guess I've been doing so at such a pace where I don't have any problems running the apps and versions that I want, even though I wait enough time to upgrade for issues to be worked out. I'd rather do that than have possible unpatched dependencies. For older systems where updating to a new version impacts performance detrimentally then it would be an option. But how often does that happen?

    2. Re:Latest version? by HalAtWork · · Score: 1

      It's not a burden. Your statement that suggests the desire for up to date software means that you wouldn't have to update your entire system to get the latest app, you'd already have an up to date system.

      For third party developers nearly every project has ABI compatibility, the only reason they'd have to create different versions is if their project depends on esoteric functions and routines that were never previously available. This is rare given the normal "do one thing and do it well" nature of Linux dependencies.

  31. Doesn't sound safe to me by HalAtWork · · Score: 2

    The fact that they bundle dependencies are what makes me feel they're unsafe. I can't rely on snap packages to have up to date dependencies.

  32. Re:Alternatives? by jimtheowl · · Score: 1

    Why do you want full duplex audio? Its not like the turtles can talk back.

    Instead of trying to find something that does things exactly the way they used to be (whether you need that feature or not), you should start with something that works and build on it. It requires more time and effort, but you are less likely to find yourself in the situation you are right now.. a web site with a live cam first perhaps.

    As for SIP alternatives, I have had good luck with mumble, but have not yet tested it on ARM.

  33. Re: Mod parent up! by Type44Q · · Score: 1

    ideals

    Ideas??Ideologies?! ideal what??

  34. Re:I've been out of the Linux loop for a few years by BlueStrat · · Score: 1

    Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.

    https://snapcraft.io/ [snapcraft.io]

    Ah, so they've recreated PC-BSD .PBI packages for Linux!

    Imitation is the sincerest form of flattery! :)

    Strat

    --
    Progressivism (aka US 'Liberalism'): Ideas so good they need a police/surveillance-state to enforce.
  35. Surrender Privacy to ... MICROSOFT! by bwanagary · · Score: 1

    They won't do anything bad with your data. Promise.  Yeah, right! I don't want MS storing all my personal and contacts' information anywhere - they are the least secure mainstream OS in the world.   I was a long time Skype user on LINUX.  Recent versions want access to all kinds of private data on my system so I have purged Skype from my main computer (LINUX) and my MACs as well.  There are plenty of other free, secure, multi-platform and unobtrusive alternatives out there, many of them browser-based so you don't need to install anything at all.

  36. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  37. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  38. Re:Mod parent how you will by Insanity+Defense · · Score: 1

    How DARE you mod down this post for merely disagreeing with ideals. Slashdot is an OPEN FORUM where every man is allowed to express his opinion.

    Amen.

    So you claim the right to express your opinion but wish to deny those who moderate the right to express theirs? Hypocrite.

  39. Re:Open source champion? by Insanity+Defense · · Score: 1

    MS has been one of the largest contributors of open source projects and applications over the past few years. MS has been positioning themselves to transforming their flagship OS and related applications to a true cross platform solution. Think about all those people and companies that cannot move to a Linux platform due to the lack of Linux application support. No think of signing into your computer and being able to start a Windows session or Linux session without any intervening VM. Think about a version of .NET that is open source and cross platform. The number one rule in capturing a large market share is to make it easy for developers to create applications. It's a lesson the Linux fateful have never really understood. MS has always catered to the developers. MS VB was probably the one product that pushed MS to the top. VB allowed almost anyone to become a developer. VB was certainly not a perfect development tool but it was easy compared to C\C++ or any other native languages that the average person could not use. VB allowed the rapid creation of applications that ran on the MS application stack. (VB had a lot of faults. People created a bunch a sup-par applications. These two characteristics didn't stop the adoption of VB and all the subsequent adoption of a pure MS application stack.)

    I'm waiting for the public apology from the executives who have used their position in Microsoft, its wealth and its power to publicly attack Linux in particular and open source in general. Not to mention spending as much money on promoting Linux and open source as they did to fighting it. Where are the apologies for calling open source/Linux Communist, unAmerican and viral? How about all the public claims of patent violation but total unwillingness to say what patents so the violation (if it even existed) could be removed?

    Also I'm waiting for Microsoft and many other big corporations to comprehend that the novel 1984 was not a HOW-TO manual and STOP the big brother aspects of their software and hardware.

    It will take at LEAST as many years of being a GOOD CORPORATE CITIZEN as they have spent being vile to earn trust, respect and forgiveness. Still waiting for them to start.

  40. I see the good folk an MS by BrookSmith · · Score: 1

    I see the good folk an MS have provided a marketing spin to publish straight onto /. "open source champion", "wildly popular" hardly an independent or realistic view of MS or Skype - there's just a little bit to much hype going on there, maybe now farcebook isn't accepting fake news they thought they could dump some on /.

  41. Re:Open source champion? by Insanity+Defense · · Score: 1

    Corporations don't care about your hurt feelings and you'll never get anywhere if you're going to sit around and "wait for an apology". The fact that you suffer hurt feelings and feel you are in need of an apology on the back of criticism of Linux at all is quite lame. Grow up snowflake.

    Tell it to the snowflakes who tell us "Microsoft doesn't do that stuff now so stop being mean to them/us". They tell us to forgive Microsoft and the execs and to trust them when they haven't shown they DESERVE trust. Tell those snowflakes that Microsoft has to earn what they forfeited by their loooong history of horrible corporate behavior.

  42. Re: Open source champion? by brunes69 · · Score: 1

    Just use the web app... Problem solved.

    I literally NEVER use the desktop version of office now. Using it in your browser is much more convenient and works on any modern browser.

  43. Is this a press release from Microsoft? by hughbar · · Score: 1

    'actually transformed into an open source champion', 'wildly popular' etc. etc. No. Microsoft has stopped throwing chairs, issuing Halloween memos and is now burrowing into open source with a view to subverting it since open source is a threat to revenue and shareholder value.

    You have to ask yourself, each time, there's some breathy announcement, followed by the shill commentary below it, 'Do I trust Microsoft? For me, the answer is and will remain, 'no'.

    --
    On y va, qui mal y pense!
  44. Horrible program by NorthWay · · Score: 1

    So I finally went through a major hoopla to upgrade my system so I could run a more recent version of Skype (so mom could keep calling me and get her remote support).
    There was absolutely no reason to update (ok, a system update is never wrong) as the old version of Skype worked just _fine_ (well, after a lot of tweaking) and the only reason it stopped working was M$ throwing all the toys out of the pram and refusing to let the old version keep running.

    The new Skype wont take my camera (Cheese likes it plenty fine) and the incoming sound is so scratchy and choppy that I have major trouble understanding peoples' speech.
    First up against the wall etc...

  45. Re:Awesome Naming by Microsoft, too. by KozmoStevnNaut · · Score: 1

    It's better than 'Lync'.

    "Hey, can you send me the Lync link?"

    --
    Eat the rich.
  46. Open source sells software non-freedom. Again. by jbn-o · · Score: 1

    Sometimes people don't want to see how the older free software movement (a social movement which advocates for the freedom to run, inspect, share, and modify published computer software) and the younger open source development methodology are philosophically different (1, 2) and that philosophical difference leads to radical differences on the ground. Objections to raising this difference tend to take the form of trying to make it look like any reminder of software freedom (which open source enthusiasts don't like because their philosophy was founded to reject software freedom) is being somehow rude. But time after time we see this difference in action and this article promoting Skype is no different.

    Here a proprietary (non-free, user subjugating) program—Skype—is being advertised for use on what might be a free software system (unfairly referred to as a "Linux" system). No reminder of anything to do with software freedom except in a place where the proprietor thinks they can benefit from the conflation the open source philosophy was designed to achieve: "While Microsoft has long been viewed as an enemy of the Linux community -- and it still is by some -- the company has actually transformed into an open source champion." tries to get you to think of "open source" but not to the extent that one would wonder if even that group's weaker philosophy is going to be available to Skype's users by running Skype. No mention of GNU as in a GNU/Linux operating system; any mention of GNU is far too strong a reminder of the software freedom you're not getting with Skype. Better to stick to distracting technocratic details that are irrelevant compared with the profound problems of running Skype, details like the software's packaging. And to reinforce the notion that open source advocates will often abandon their own developmental philosophy if it gets in the way of a powerful proprietor, we get a quote from Canonical, an open source supporting company, further encouraging users to install the non-free communications software.

    Nowhere will you find a reminder that not only is Skype non-free software (and that this alone carries horrible implications) but Microsoft is an NSA partner, and Microsoft changed Skype specifically for spying. Apparently the "seamless user experience" Canonical championed and the "high quality experience" Microsoft talked about doesn't include respecting a user's software freedom, their privacy, or the security of their computer.