samora

Thanks for the reminder. I forgot to take my creatine today.

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.

This is great! I think Facebook Lite already uses something like this. Great work.

https://engineering.fb.com/2016/03/09/android/how-we-built-f...

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.

GitHub Pages

There are a lot of people who won't buy a used phone. And last year's model is not $249 brand new.

I think a lot of us miss the Go point.

There is nothing special about Go. It's simple and just works.

Every time I used Go for a project it just worked. No fuss. With very little effort. And that's the point.

How to create a mind - Ray Kurzweil

Rich Dad, Poor Dad - Robert Kiyosaki

This is kind of sad. Balanced Payments is one of the companies I look up to. Very sad when you lose a role model.

Is it Google's no CAPTCHA reCAPTCHA? A custom implementation? I am quite curious to know.