91–100 of 110 posts
Earlier quoted context omitted.
Instead of using open you can just run the binary inside Slack.app directory: SLACK_DEVELOPER_MENU=true /Applications/Slack.app/Contents/MacOS/Slack
That's not a great idea. If you don't use open, the app won't show up in the Finder app switcher.
Small nitpick, though. The dock is what runs the app switcher, not the Finder.
Earlier quoted context omitted.
> You can include native code in Electron apps. I am not sure it is actually needed in any of the messaging Electron apps (Slack, Discord), but the capability is there. Discord has options for streaming your game to others, identifying running processes to display games as your status, downloading and launching games, and displaying a chat overlay on top of external game processes. Some of those can be accomplished i…
That is all available in WebRTC.
Seriously? I thought it was just a networking protocol. Can you please provide some examples so I can dig in further?
* streaming your game to others - I know that there are window capture APIs in browsers now, or at least in WebExtensions[0]. Then you stream the result over WebRTC, makes perfect sense to me.
* identifying running processes to display games as your status - Does WebRTC really have access to inspect running processes? That's horrifying.
* downloading and launching games - By downloading here I meant managing your installed games like an app store. They had everything from 2D games like Hollow Knight to open world 3D games that require a decent amount of horsepower like Saints Row. It looks like they've actually killed this feature, but either way I'm not really sure how WebRTC helps manage installed applications.
* displaying a chat overlay on top of external game processes - I can imagine how you'd accomplish this via WebRTC for games that expose an API to enable it, but rendering on top of an arbitrary game doesn't seem like something WebRTC allows.
[0]: https://chrome.google.com/webstore/detail/chrome-remote-desk...
Earlier quoted context omitted.
I tried using a quote first, but the fact that you need to double-space between paragraphs, even when using the > symbol broke the formatting. To avoid spending too much time figuring it out, I switched to blockquote. Sorry!
Good use case for a WYSIWYG editor!
Earlier quoted context omitted.
See, Steve Jobs could get away with this because he was exceptionally good at making the right choices, at least in the later part of his life. When others try to emulate him, it doesn't go as well.
Yes. For instance, Apple's spent the last couple of years emulating his visionary design decisions, focused specifically on "get thinner and thinner until you can't actually do your job anymore".
We'll never actually know unless someone finds a way to raise the dead, but I personally believe that Jobs would never have allowed those butterfly keyboards out the door.
I don't use slack so the issue isn't on my radar, but if this has made it to the top of HN.... I guess Slack reeeealy effed up.
It’s a tempest in a teapot. Yes, the new editor is horrible. But at best it is a minor annoyance, and most users learn to work around it.
I've been struggling with the new editor for the past week or so. I finally sent this feedback to Slack today: Hi there, when the WYSIWYG editor rolled out, I was pleased to see it could be disabled with the "Aa" button in the bottom right. I quickly realized it's not disabled, the toolbar is just hidden. Here are the problems I run into: 1. Typing ``` and then pasting and typing it again (force of habit from *every…
Slack is extremely hostile towards user feedback. I sent them comments on what I believe to be a terrible feature and they also told me it will never be changed.
And they are far from the first consumer-facing company to deal with user backlash when a new feature came out. Facebook notoriously got an onslaught of negative opinions and sometimes press when a feature in the UI changed. The UI never caused any significant migration away from Facebook, only the privacy/surveillance concerns, vitriol, and the "embarrassed by my parents" un-cooling of the platform caused users to leave.
From what I read here and elsewhere about feedback from customer service, I suspect there is a push from management down to product to hit certain targets (I don't have visibility into Slack's internal metrics, but this is exactly how it presented in my previous company).
Earlier quoted context omitted.
Maybe if they start getting enough emails/tweets they will reconsider this...emailing them now...
Slack is an enterprise product. You aren't the guy who buys it, so what you think is irrelevant. They don't care anymore, user experience won't affect their bottom line unless it somehow becomes a Powerpoint bullet vs. some other enterprise competitor, which by definition is equally unconcerned about end-user opinions for the same reasons. Atlassian is the same way now, providing any kind of feedback to them is equiv…
If Slack thinks this, they are only 2-3 years from getting overtaken by a disruptor. I don't think they do.
How much sway angry emails have over actual usage is a different question. Facebook notoriously used analytics and A/B tests to decide if feature changes stayed, not angry complaint messages.
I don't use slack so the issue isn't on my radar, but if this has made it to the top of HN.... I guess Slack reeeealy effed up.
It’s a tempest in a teapot. Yes, the new editor is horrible. But at best it is a minor annoyance, and most users learn to work around it.
What a time to be alive.
>We really appreciate your feedback, and we hear your frustration. We're sorry for the impact this is having on your ability to communicate with your team and on your overall productivity. We made a mistake by forcing everyone into this feature without providing an opt-out for customers like you: people for whom the existing behavior was working just fine.
>We've started working on a preference that will let you return to the previous message composer. We don't have a specific release date to share right now — it's this team's top and only priority, however, and we expect to have it available on the desktop within a couple of weeks, with Android following shortly thereafter.
>We will follow up with another note when this option is available to you, and we'll include instructions on how to enable it.
>Again, we're sorry for the disruption and we're grateful for the feedback. We missed the mark on this feature! We will do our best to learn from this and avoid similar mistakes in the future.