Live data from Hacker News

Dear Skype/Microsoft: Problems with Linux client

nickforall.nl

241–250 of 483 posts

Re: Dear Skype/Microsoft: Problems with Linux client

#241
post #229

Earlier quoted context omitted.

they both break library compatibility and break their environment (like when kde removed the widget toolbar and a whole lot of app suddenly stopped working) sure you can have bunch of ifdef in the code, and an autoconf, and make sure you support a wide set of options, but that is basically the whole point, it makes for a painful experience and costlier, slower development (for closed source application that comes pre…

I feel like you do not understand the concept of static linking, because the entire point is that you don't need a bunch of ifdefs, since you target exactly the version you develop against and ship with it.

the example I gave is exactly how stuff has broken in projects. static linked on a kde library that had widget, new one doesn't have that nor a fallback, application crashes.

or just go get some old static compiled stuff run on your modern distro and see yourself. like, mindrover the europa project port.

Re: Dear Skype/Microsoft: Problems with Linux client

#242
post #181

Earlier quoted context omitted.

As someone who works in the VoIP mobile client area for 7 years (though not for Skype) I have to be fair and say that this is unlikely to be Skypes fault. They are known to use state of the art codecs so most likely the issue lies in the PSTN network that you are calling into. For the out calling feature they are relying on Carriers all around the world for the VoIP -> PSTN functionality. It would be another thing if…

That's the thing. VoIP -> VoIP is perfect. They really need to choose better PSTNs in that case.

If the destination number is in the t-mobile network then they can't chose that the call doesn't go into t-mobiles network.

They can control one part of it, the point where their VoIP is transcoded and switched into the network, here could lie the issue. But the issue could also come from the destination end of the network.

I generally believe that US and EU carriers are solid enough that calling there shouldn't cause issues, but who knows whom the parent is calling.

Could be Afghanistan for all I know and I am not as confident here that there wont be any issues that are definitely out of control for Skype.

In some cases the carrier might even wilfully degrade the quality because they want to earn more. They earn less if Skype routes a caller from the US to Afghanistan via IP and lets him call from a Afghan to Afghan number.

Re: Dear Skype/Microsoft: Problems with Linux client

#243
post #154

Earlier quoted context omitted.

Skype is shit, but Hangouts is not even a contender * No desktop client * Connected to your google account meaning I'll need to juggle several google accounts to keep my personal and business chats separate Just the fact it doesn't have a native desktop client makes it unusable. I know there are workarounds I can use like nativefier but it's still not as smooth as a desktop app. Running in the browser: - Gets grouped…

> No desktop client Seeing the level of shitty ported Linux programs I see this as a pro. > Connected to your google account meaning I'll need to juggle several google accounts to keep my personal and business chats separate This would be easier with Skype if you have 2 Skype accounts? When using Chrome: > - Gets grouped with my other browser windows in my taskbar, making it hard to find Menu -> More tools -> Add to…

>> No desktop client

> Seeing the level of shitty ported Linux programs I see this as a pro.

Well, google manages to make a shitty Linux port of the plugin, so they've got their bases covered there.

https://bugs.chromium.org/p/chromium/issues/detail?id=363358

Re: Dear Skype/Microsoft: Problems with Linux client

#244

Skype worked far, far better 10 years ago than it does today. From all indications I've seen, Skype is getting dramatically worse all the time. From a personal standpoint, it crashes for me multiple times a day and I can rarely get group calls working on the first try. Often Skype requires a force-quit and then it crashes twice more when it is being restarted. This is on Mac and Android. Fun fact: I have a friend who…

The android client is also a bit random. Notifications pops when they feel like it. Some upgrades change for different kind of wrong.

Usually updates fix the problem. But I loved how the last update failed with a very clear "Error $SomeNumber". I just love Microsoft's style.

...

Re: Dear Skype/Microsoft: Problems with Linux client

#245
post #194

Earlier quoted context omitted.

>Fun fact: I have a friend who worked for Skype in Prague. He said the codebase is a true horror, an extreme mess, and that soon it would "reach a singularity" Being a developer, I read this and think, what developer thinks any existing codebase is NOT a mess. It's the number one developer complaint ever. They (we?) all think we know a better way.

I've worked on plenty of good codebases. I think the key is continuous improvement. The code from 5 years ago is always going to be worse than today's code, but as long as you're able to improve code as you work on it it doesn't get too bad.

Once when I was interviewing for a job, I was given and offer and I accepted it conditionally. I asked to sit with a senior developer for 30 minutes and browse the code. Turns out it was in great shape and the person that gave me the walkthrough was one of the greatest programmers I've ever had the pleasure to work with.

Re: Dear Skype/Microsoft: Problems with Linux client

#246
post #173
post #162

46 active contacts and 12 blocked account in my Skype 4.3.0.37 (2014 Skype and/or Microsoft Patents Pending) Family: Wife (mac), Mom(ubuntu) and Sister(win) All - Family = work or business (i can safely say that 90% are OS from MS). Do I want all those contacts in my slack ? No i don't. Do I want to change to another very powerful chat system? Well, sometimes connect sqlite3 to find a conversation is not really what…

What if there was a free, interoperable protocol that could connect anything to anything? That's what we are trying to achieve with Matrix ( https://matrix.org ) - making apps connect either natively or via gateways/bridges. We already have bridges to IRC, Slack, and libpurple! Ideally we would connect all services to each other, but obvs we can only do so for those who offer an API. In Matrix, you can set up a WebRT…

thanks for the reply.

will look at that but still, in this moment and with the current api of skype, an instance of it must run in background somewhere.

Re: Dear Skype/Microsoft: Problems with Linux client

#247
post #229

Earlier quoted context omitted.

I feel like you do not understand the concept of static linking, because the entire point is that you don't need a bunch of ifdefs, since you target exactly the version you develop against and ship with it.

the example I gave is exactly how stuff has broken in projects. static linked on a kde library that had widget, new one doesn't have that nor a fallback, application crashes. or just go get some old static compiled stuff run on your modern distro and see yourself. like, mindrover the europa project port.

This will be my last reply.

> static linked on a kde library that had widget, new one doesn't have that nor a fallback, application crashes.

As I said before, please read up on what static linking means.

> like, mindrover the europa project port.

    $ file Mindrover\ The\ Europa\ Project\ DEMO\ r1-lgp-x86.run 
    Mindrover The Europa Project DEMO r1-lgp-x86.run: ELF 32-bit LSB executable,
    Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2,
    for GNU/Linux 2.6.15, BuildID[sha1]=fe926b7ea13be61d05cdd605e313f50042040153, stripped
...version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2...

    $ ldd Mindrover\ The\ Europa\ Project\ DEMO\ r1-lgp-x86.run 
	linux-gate.so.1 =>  (0xf7722000)
	libglib-2.0.so.0 => not found
	libz.so.1 => not found
	libfuse.so.2 => not found
	librt.so.1 => /lib32/librt.so.1 (0xf7700000)
	libdl.so.2 => /lib32/libdl.so.2 (0xf76fb000)
	libpthread.so.0 => /lib32/libpthread.so.0 (0xf76dd000)
	libc.so.6 => /lib32/libc.so.6 (0xf7525000)
	/lib/ld-linux.so.2 (0x5660a000)
Clearly not a statically linked binary.

Re: Dear Skype/Microsoft: Problems with Linux client

#248

I've been educating as many people (especially Management and Business people) as I can to switch over from Skype to any other alternative (like Hangouts). Because Skype is: * A memory hog * A bandwidth hog (its really inefficient about network usage, and uses a lot of bandwidth even when idle) * Has much lower call quality (a consequence of the above), just try having a call in Hangouts or Skype and notice that Hang…

You read my mind, while we are 99% an open source organisation we have a couple of managers that are strangely MS centric, if it has their stamp on it - it has to be 'enterprise grade' and there for the only serious option for them.

But Skype is a consumer offering. The "enterprise-grade" product is Skype for Business (formerly Lync), which is a completely different product and codebase (and thus, presumably, with completely different bugs and annoyances).

Re: Dear Skype/Microsoft: Problems with Linux client

#249

Skype worked far, far better 10 years ago than it does today. From all indications I've seen, Skype is getting dramatically worse all the time. From a personal standpoint, it crashes for me multiple times a day and I can rarely get group calls working on the first try. Often Skype requires a force-quit and then it crashes twice more when it is being restarted. This is on Mac and Android. Fun fact: I have a friend who…

Most things worked far, far better 10 years ago than today. Apparently this is progress. Social everything means we can't visit a website today without calls to a billion external domains. Phones are doing the same as they're mini-tablets that suck at actual phone calls. Operating systems have taken on mobile centric (and the hideous flatten everything) design that is broken paradigm for a 15" laptop or 24" desktop s…

>Firefox was a stripped down, light browser so it stayed fast - now they include more useless garbage than Netscape Communicator ever did.

Sorry, I don't think Pocket and Hello surpasses the junk bundled with Communicator, which came with a custom mail client. Mozilla's mail client is not only not installed with Firefox, but it's also pretty much dead now, in fact.

Re: Dear Skype/Microsoft: Problems with Linux client

#250
post #229

Earlier quoted context omitted.

they both break library compatibility and break their environment (like when kde removed the widget toolbar and a whole lot of app suddenly stopped working) sure you can have bunch of ifdef in the code, and an autoconf, and make sure you support a wide set of options, but that is basically the whole point, it makes for a painful experience and costlier, slower development (for closed source application that comes pre…

I feel like you do not understand the concept of static linking, because the entire point is that you don't need a bunch of ifdefs, since you target exactly the version you develop against and ship with it.

The problem is services and non-ABI/non-library APIs. The way I suspect that this is set up is that there is precisely one KDE widget displayer service at any given time, running as part of the desktop environment and presenting an IPC interface that widgets talk to to get themselves added to the widget display area that the window manager maintains. You can link statically to the KDE widget client libraries all you want; if the KDE widget server decides to change the language it speaks, your widgets are hosed unless you included a not-a-widget mode that makes it a normal window. Seeing as how widgets tend to have special build systems (or, worse, the widget server is actually an interpreter for a declaration-heavy widget definition language that's not strictly plaintext), I don't think I've ever seen a widget with a non-widget mode supported.

"Breaking userspace" probably is a misnomer, if only because userspace has a precise technical definition. This is more like changing an interpreted language without maintaining backwards compatibility (python3, anybody?) or changing a json API.

Post reply on HN