You are mistaken in seeing iOS frameworks as a limitation. It is an advantage! It is the natural fit for the eye tracking and hand gestures because those apps will work flawlessly with no change.
You are also mistaken in thinking Mac OS can't work with Vision Pro, because it can. Apple has put a trojan horse in Vision Pro by giving us any number of screens we want to use with our Macs. In the future Apple will bundle Mac OS and iOS in Vision Pro. It is the ultimate evolution of computing. This is my prediction. Vision Pro will replace both the iPhone/iPad and Mac. All of it can coexist perfectly in Vision Pro.
This is what you should do. Copy Apple. Make your headset work with Android. Allow Linux and Windows to also be able to work through the headset with existing computers, by providing virtual screens. In the future you can offer a version of your headset with either Linux or Windows, but Android must definitely be in the first version of your headset. This is the only chance you have.
You are mistaken in seeing iOS frameworks as a limitation. It is an advantage! It is the natural fit for the eye tracking and hand gestures because those apps will work flawlessly with no change.
You are also mistaken in thinking Mac OS can't work with Vision Pro, because it can. Apple has put a trojan horse in Vision Pro by giving us any number of screens we want to use with our Macs. In the future Apple will bundle Mac OS and iOS in Vision Pro. It is the ultimate evolution of computing. This is my prediction. Vision Pro will replace both the iPhone/iPad and Mac. All of it can coexist perfectly in Vision Pro.
This is what you should do. Copy Apple. Make your headset work with Android. Allow Linux and Windows to also be able to work through the headset with existing computers, by providing virtual screens. In the future you can offer a version of your headset with either Linux or Windows, but Android must definitely be in the first version of your headset. This is the only chance you have.
You need to establish some rules to make Slack work for most teams without overload.
1) People should avoid DMing each other when talking about work, use threads instead (see 3) to discuss topics in team channels (see 2).
2) Keep channels to a minimum.
Every person shouldn't have more than 2/3 channels they need to pay attention to. A private team communication channel (eg #dream-team) and a private work channel (eg #dream-team-engineering) is enough for most teams.
All team members are in the private team communication channel.
A work channel is specific to a domain, such as engineering. Example you don't want engineering work banter to distract those working on other stuff.
3) Use threads religiously!
This is super important as it helps declutter the Slack experience and keep conversations heavily organized.
I really wish Slack would let users / channel-moderators move messages. Push them into the thread they belong on, copy-to-room for ones that need broader visibility, send question X to team Y's channel, etc.
Instead, what's done is done, and it can lead to rapid degradation in communal rooms that have a lot of newcomers.
Then two years ago, whatever. I wasn't referring to used phones, anyway. There have been "cheap" iPhone options for a long time, and a decent, brand-new Android phone didn't really pop up until the Moto X, which was something like 2012.
But that doesn't answer any of the (very valid) points raised in the article?
Go is interesting as a replacement for a scripting language, perhaps. But it seems very lacking in many other areas. All of the points in the article, plus what libraries are available.
I think some of it could be explained by it being a young language, but if that's the case, why is it getting the adoption it has so far? Just because it came from Google?
Because it has allowed so many of us to significantly raise the ratio "Amount of time I care about my project"/"Amount of time I care about something other than my project (typically, the language itself)".
Go is the poster child for Worse is Better. It's ugly, inconsistent, feels naughty at times (all those copy-pastes ! It's so un-DRY !) but it gets shit done.
This is what you should do. Copy Apple. Make your headset work with Android. Allow Linux and Windows to also be able to work through the headset with existing computers, by providing virtual screens. In the future you can offer a version of your headset with either Linux or Windows, but Android must definitely be in the first version of your headset. This is the only chance you have.