The reason irccloud is popular is that it is simple to set up and there is a really great mobile client. No one really needs another web based client, even if it is free; there are plenty of alternatives for that such as ircanywhere[1] or Convos[2].
I'm really not sure who this is for.
Komanda: IRC Client For Developers
31–40 of 68 posts
Re: Komanda: IRC Client For Developers
#32I keep an IRC client (Colloquy for OSX) open everyday when I get home from work. However, it crashes a few times a day and I think it's about time to switch. Is this a suitable replacement for Colloquy? Any recommendations on a better IRC client to use, web-based or OSX, are much appreciated. Thanks!
irssi, textual, or IRCCloud (if you care about a mobile client as well) would be good. Textual over Limechat because it is a forked version of Limechat and is much improved in terms of functionality.
Re: Komanda: IRC Client For Developers
#33Earlier quoted context omitted.
A big part of the appeal for IRC to me is the not so low barrier to entry with tools like irrsi
Which is wonderful if you're an old hat who enjoys having new people get frustrated and leave before they have a chance to contribute to the ecosystem.
yes precisely and people who use tech buzzwords like ecosystem
Re: Komanda: IRC Client For Developers
#34The reason irccloud is popular is that it is simple to set up and there is a really great mobile client. No one really needs another web based client, even if it is free; there are plenty of alternatives for that such as ircanywhere[1] or Convos[2]. I'm really not sure who this is for. [1] http://ircanywhere.com/ [2] https://github.com/Nordaaker/convos
O_o what are you talking about. This is an irc client.
Re: Komanda: IRC Client For Developers
#35It's worth noting that despite the "ZNC bounce" stuff on http://komanda.io/ this is actually just an IRC client.
It seems to run on all my systems because it's webkit based; it's quite pretty. Had a bit of trouble with the setup which resulted in "USER Not enough parameters"; pretty rubbish first experience using it.
I don't see any 'developer features' that make it worth bothering with over any other irc client, but I appreciate the idea that it's javascript based and I could download and customize it if I wanted to.
Cute project; yet another 'uses webkit for desktop app'. For better or worse, that seems to be flavor of the month at the moment.
Re: Komanda: IRC Client For Developers
#36The reason irccloud is popular is that it is simple to set up and there is a really great mobile client. No one really needs another web based client, even if it is free; there are plenty of alternatives for that such as ircanywhere[1] or Convos[2]. I'm really not sure who this is for. [1] http://ircanywhere.com/ [2] https://github.com/Nordaaker/convos
O_o what are you talking about. This is an irc client.
Yes, it is an irc client but on the front page
>With a ZNC bounce
which implies that they want you to connect to a bouncer. In which case, those two I linked to are clients as well, just it having a bouncer built in.
Re: Komanda: IRC Client For Developers
#37So "people who write code" now equals "web developers". Sad ...
Re: Komanda: IRC Client For Developers
#38Can this be run as a web app rather than with nodewebkit somehow? I'm not familiar enough with node/npm to figure it out.
Re: Komanda: IRC Client For Developers
#39It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someone would build a desktop app with these technologies is that they cbf to learn to use the correct tools for the job.
As for "the best client for developers" -- I'll stick with irssi, thanks.
Re: Komanda: IRC Client For Developers
#40It's beyond me why anyone would write a desktop application in JS, CSS, and HTML, and require node as a dependency. These technologies are already bastard children of the 'just make it work' mentality. Using them for an environment they were never designed for, when there is decades of existing infrastructure purpose-built (and far easier to use), makes no sense. The only reason that I can come up with for why someon…
What does "cbf" mean, in this context?