Slack’s new WYSIWYG input box is terrible

Re:Slack’s new WYSIWYG input box is terrible by joepie91_ on Thursday November 21, 2019 @07:41AM (#21593494)

It being open-source (under your control) or not does make a difference here.

In an open-source thing, with this sort of productivity-harming breakage, you could worst-case just pay a random freelancer to fix it for you. You don't have that option with Slack.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by acdha on Thursday November 21, 2019 @07:48AM (#21593521)

That’s how you end up with critical apps which are full of known security issues because now upgrading requires reverse-engineering and migrating a bunch of one-off customizations. This approach only works if you’re committed to paying regularly to maintain your fork.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by joepie91_ on Thursday November 21, 2019 @08:28AM (#21593750)

I did say "worst-case". And as another commenter suggested, upstream your fixes.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by acdha on Thursday November 21, 2019 @10:57AM (#21595425)

“upstream your fixes” only works if the upstream wants them. If you charge in saying “you're all dummies (per OP); here's a patch which goes against your project direction which I want you to maintain in the future”, that's probably not going to be very successful.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by woodrowbarlow on Thursday November 21, 2019 @08:27AM (#21593742)

or upstream your fixes

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by gizmo686 on Thursday November 21, 2019 @08:54AM (#21593972)

That only works if upstream wants your fixes.

[ Parent | on HN ]

Re:Slack’s new WYSIWYG input box is terrible by eythian on Thursday November 21, 2019 @10:28AM (#21595022)

Then you have the proprietary problem again, only worse as then you can't make the fixes.

[ Parent | on HN ]