-
Nice. I made something like that a while ago - also in Bash, but with more features and only with GitHub support.
-
-
That was the fun part of building it. Everyone should write their own testing library in Bash ;-)
-
-
-
lukaszkorecki
1 year ago
|
link
| on:
What is the oldest (retro) machine that you still use in production?
I have a vintage early 2015 Macbook Pro, you know the ones that still had the Esc key. Tremendous machine.
-
Great read. Also:
As you know, I’m joking on this article, since as we both know, Erlang copied Scala.
found in the comments.
-
It reassures me that a lot of these guys have “boring” desktops. My desktop is mostly Emacs, Firefox and way to many terminals. Definitely not a contender for a ricer setup that people post on /r/unixporn
-
My favorite part is how they’re all apologizing for being boring.
-
You either get stuff done or have a nice looking desktop ;-)
-
-
I can work around this issue, but I find it much more worrisome that their gateways are discontinued entirely. I use Slack through the IRC gateway, because I don’t want to have a CPU & memory gobbling browser tab for every organization I join.
This means that sometime in the not-to-distant future, using the gateways at all won’t be possible.
Yes. It leaves me with the impression that gateways might exist primarily to ease the on-boarding process of new customers by being able to tell them, that they can continue using their IRC or XMPP clients. Once a company becomes a customer, the discussion is effectively finished and individual users will be pressured to use the electron or browser client anyways because Slack is what the company uses now.
So, sadly, there’s little incentive for Slack to support those bridges as long they are good enough to say “yes, we’ve got them” in the beginning.
What if the gateways are still running by chance, and no one dares to touch them because the dev(s) that built it left the company.
Anyway, as you wrote, it doesn’t make sense to spend money enhancing something that most users don’t care about.
That would imply that a not too small company with lots of resources would run totally unmaintained software in production, right? I hope they don’t, and if they do, they could least say so in their documentation and advertisements.
That’s not what I wrote! I meant that there are little incentives for companies who care a lot about profit maximization and less about supporting users with more uncommon needs. But it would of course ‘make sense’ to spend money on such features if one would like to create a good communication platform for a more diverse set of users!
Yes, I’ve seen them mention their XMPP gateway support in advertising material. They certainly don’t mention that it’s broken and entirely unsupported.
Sorry, I didn’t mean to put words in your mouth. Thanks for clarifying. :)
If you’re using Weechat then give wee-slack a go - I believe its lead developer works at Slack. I switched from IRC gateway some months ago because my team insists on using threads and emoji reactions, and I insist on using tools which don’t consume tons of resources. So far it’s been great, it supports most of the features I need (threads, emoji reactions, some slash commands) and I don’t care about others (search, file uploads)
Seconded; wee-slack is a lifesaver.
Where I work they won’t even turn the gateway on, but wee-slack talks directly over the same websocket API that the official client uses. It also lets me SSH into my work computer from my personal machine and keep my login credentials only on my work machine.
A bit like some time in the not-too-distant future, you won’t be able to unlock a new Android/iOS cellphone without something like “Face ID”.
For your convenience and security, of course. Only a terrorist would want a phone without Face ID!
The commonality here is that the masses don’t care about the alternatives, and so, the alternatives end up becoming impractical.