Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tell HN: Slack decides to close down IRC and XMPP gateways

news.ycombinator.com

Post reply on HN
Print view View original

211–220 of 624 posts

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#211

Post by bringtheaction »

bringtheaction wrote: post #210
amarkov wrote: post #200

Earlier quoted context omitted.

These are not unrelated observations! The same people who expressed disbelief that your UI is temperamental will react the same way if Slack releases a temperamental UI. The difference is that they don't work in the same office as Slack. They'll never hear about all the important, completely justified reasons Slack decided to release a bad UI. They'll just notice it happened, and conclude that Slack must hire incompe…

What is a temperamental UI? It must have something with UX to do I am sure but can’t find anything on the first page of Google about it aside from one page that mention avoiding UIs to be temperamental but firstly that was all that was said it seems and secondly the forum is was posted on was, ironically, completely broken on mobile such that the text could not be seen. The page had a mobile navigation bar and the zo…

PS: Here is the link https://www.lean.org/FuseTalk/Forum/messageview.cfm?catid=49...

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#212

Post by beavis2 »

saagarjha wrote: post #133
dblohm7 wrote: post #113

Earlier quoted context omitted.

Those APIs will probably be deprecated soon enough.

I doubt it. Many companies depend on Slack's APIs to do things like post build failures or provide custom commands.

Same could be said about their IRC gateway.

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#213

Post by snuxoll »

BukhariH wrote: post #206
snuxoll wrote: post #187

Earlier quoted context omitted.

And? I am absolutely tired of companies taking a giant dump on the experience of desktop applications. If you're going to make a desktop app make a damned desktop app, stop making everybody accept a terrible electron app because "oh no, I have to do extra work" - give me a break. How many companies still maintain native iOS and Android apps? Lots. Qt even feels (mostly) native on GNOME desktops these days, if you can…

Honestly, I don't think you can point to any actual business reason for a native client. Slack makes majority of their revenue from large organisations buying thousands of seats in one go and a native desktop client is sadly not a huge selling point for the sales team. At the end of the day Slack has to optimize for growth and there's a huge list of features that will bring more ROI than native clients which will req…

Fine, if they don't have any business reason for a native client they should just can the slack desktop app because it provides 0 benefits over the web app then.

If you're going to do something do it right or don't do it at all.

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#214

Post by jeena »

Viper007Bond wrote: post #207
dennisdamenace wrote: post #105

Earlier quoted context omitted.

Why is it a bad idea? And I doubt _any_ business has centralized their communications with Slack. I’m sure they are still using phones, and email and face to face communication.

The ~600 person distributed company I work for doesn't use phone or email and obviously doesn't do anything face to face. We relied on IRC for years before switching to Slack so yes, all of our real-time communication is via Slack. We have internal blogs for threaded important async discussion though, but Slack is where our high bandwidth talk done.

How come you don't use Rocket.Chat or Mattermost or Matrix?

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#215

Post by dethos »

It is a shame. People with older computers will have a harder time, also people with their own work-flow and clients.

Deep down, we knew that the Gateways were just a temporary thing, to help people enter the walled garden and also to shut down who might complain about the move to slack.

Even though your company might use it (you can't do much there), you should resist when communities choose this system to their chat, there are open alternatives that fit better the use case.

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#216

Post by keyle »

FooBarWidget wrote: post #46

Everybody here is disappointed at Slack, and I like open protocols and open platforms just like everybody else, but I still have a contrarian view. Instead of blaming Slack, why not accept that the open protocols indeed suck? IRC does not specify encoding, netsplits are a common issue, file sending sucks, etc. XMPP also has file sending problems, does not play nice with mobile, is fragmented (not every client impleme…

Why don't you evolve slack into open protocols? Oh that's right, that's your IP. That is the reason you walk away from protocols and implement 'safer', 'reliable', 'augmented' closed source options..

Your time could be spent on open source, so don't claim that open source walked away from you, when you're the one doing it.

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#219

Post by clintonb »

snuxoll wrote: post #187
panopticon wrote: post #175

Earlier quoted context omitted.

The web-based implementation means you only have one codebase for both Slack in the browser and Slack in Electron. So adding Qt in addition to their browser client means they have two disparate clients instead of one client (plus Electron glue code).

And? I am absolutely tired of companies taking a giant dump on the experience of desktop applications. If you're going to make a desktop app make a damned desktop app, stop making everybody accept a terrible electron app because "oh no, I have to do extra work" - give me a break. How many companies still maintain native iOS and Android apps? Lots. Qt even feels (mostly) native on GNOME desktops these days, if you can…

I keep hearing bad things about Electron, and have only now bothered to look it up. As a user of Slack, and whatever other applications I happen to use that are based on Electron, I don't care that the application isn't native. Electron is "good enough." I would imagine that 99% of users feel the same way.

Feel free to articulate your issues with such apps. So far, no one has really done that in the various comments online disparaging Electron.

Re: Tell HN: Slack decides to close down IRC and XMPP gateways

#220

Post by dman »

BukhariH wrote: post #206
snuxoll wrote: post #187

Earlier quoted context omitted.

And? I am absolutely tired of companies taking a giant dump on the experience of desktop applications. If you're going to make a desktop app make a damned desktop app, stop making everybody accept a terrible electron app because "oh no, I have to do extra work" - give me a break. How many companies still maintain native iOS and Android apps? Lots. Qt even feels (mostly) native on GNOME desktops these days, if you can…

Honestly, I don't think you can point to any actual business reason for a native client. Slack makes majority of their revenue from large organisations buying thousands of seats in one go and a native desktop client is sadly not a huge selling point for the sales team. At the end of the day Slack has to optimize for growth and there's a huge list of features that will bring more ROI than native clients which will req…

Killing battery life of their users isnt a business reason?
Post reply on HN