361–370 of 1001 posts
I was ready to be unsympathetic - too bad for the company - but then I read TFA and it's a rug pull on a nonprofit teaching coding to kids.... https://hackclub.com/ (They do help clubs sell things, taking "7% of income", so they do have a revenue stream, but the money that Slack wants would pay a veritable army of student interns.)
[flagged]
I was ready to be unsympathetic - too bad for the company - but then I read TFA and it's a rug pull on a nonprofit teaching coding to kids.... https://hackclub.com/ (They do help clubs sell things, taking "7% of income", so they do have a revenue stream, but the money that Slack wants would pay a veritable army of student interns.)
[flagged]
Classic Salesforce. The exact same thing happened with our org and Heroku. Zero empathy, just pony up or we trash your company.
Yeah they fucked Heroku hard. I used to love Heroku. Can’t imagine there’s many people still left using it now.
Sounds about right, sad to hear that it caused so much strife though.
Meanwhile, did a bit of a test drive in my org with Mattermost, devs were mostly okay with it, but it was decided from top down to go with Teams instead. Wonder how that will work out in the next decade.
I was ready to be unsympathetic - too bad for the company - but then I read TFA and it's a rug pull on a nonprofit teaching coding to kids.... https://hackclub.com/ (They do help clubs sell things, taking "7% of income", so they do have a revenue stream, but the money that Slack wants would pay a veritable army of student interns.)
[flagged]
(the comment you made surprised me)
[flagged]
And Kübler-Ross did not describe a linear progression of grief. It was meant to be enough of a framework to start conversations, to put experiences in perspective, to help reflect. And plenty of times, life still has to go on even with devastation -- no time to grieve and reflect until crises has passed.
The wording of the co-founder's comment and the post did not strike me as grief. They are calling out enshittification without trying to burn bridges and requesting help.
That's a 40x increase all at once with a very short grace period, it's bait-and-switch territory. If only 2.5% of targets pay the ransom, Slack breaks even on this racket, so in absence of any protection this strategy is most likely profitable for Slack. This is something you pull if you want to squeeze in the short term, and don't mind losing customers.
Was not obvious before but these days it is: choosing VC-backed service is very risky.
Now you can argue choosing a Salesforce product is not a good idea and that I agree with.
Slack has been a down hill project for the past 5 years and has become incredibly bad. Unfortunately,this should be the sentiment with all SaaS projects. When a platform, like in this case, is inherent to the value proposition and can not easily be exchanged (building programs around it), one should consider self hosting.
This type of app isn't supposed to hold data. At least in my opinion, Slack is more for instant messaging and e-mail for tracing.
[flagged]