heynk

Incredible.

The biggest downside is that it looks like you can only use a single display from your Mac. If I could run 3+ screens from my mac, this would become a no-brainer.

Understandable - my point is that it's a turing incomplete language.

As a non-paying user, this seems to be mostly fair. I used to do pretty remote trail running, and the route building feature was great for putting together a route and exporting it to my watch. If I get back into that type of running, then I'd probably be willing to pay just for that feature.

Hiding the "friends only" leaderboard seems like a bad idea on their part. That feature definitely drove engagement and friendly rivalries. It's not the same if it's only amongst your paid subscriber friends, which is not many.

I appreciate them doing more to get users to pay. I've never paid for Strava, despite having been a very active user in the past. I generally like them as a network, and wouldn't want them to go away.

The immediately breaking API changes are pretty bad. I wonder what the impetus was behind that move. Too complicated to have it act as a transition? Maybe they could have announced these changes, but have them start in 30 days, with a small discount for users if you subscribe before then.

While it is harder to actually do something, node helped me understand how web development "really" works. I started with Rails - I could put a simple app together, but I had no idea how it worked. It wasn't until I worked with node, where I had to do my own routing, controllers, models, database connections, etc, until I finally could understand what was happening under the hood in Rails.

No, it's not tied to a specific device. You can of course log back in, and keys are not "destroyed". We ask users to store a 12-word seed phrase, from which all other keys are derived from.

I'm an engineer at a platform that makes it easier to build privacy-friendly apps. This means that all apps on our platform have app-specific private keys stored on the client side (in localStorage), and they never touch a server.

With this change, you're essentially "logged out" after 7 days of inactivity.

This is pretty a bad user experience. I honestly am not sure how to mitigate this. MacOS Safari might not be a massive market, but iOS Safari is.

Any thoughts about how we should address this change?

When I was starting my engineering career, it was right around when the first DARPA challenges had started. The hype was beginning, and my optimism towards technology was strong. I thought the predictions and timelines would be correct, and I still feel strongly that self-driving will be safer than humans in the long term.

Recently, I bought a newer Subaru, with EyeSight. It has adaptive cruise and lane keep assist. The LKA is fine - it'll beep if you sway outside of a lane, and automatically adjusts the steering, but it won't keep you centered. It's more of a safety thing, and it works well from that perspective.

The adaptive cruise is really good. It's camera based, and I have had zero problems with it. It works well at night and in pouring rain. It'll even stay pretty close to the car ahead of you if you turn the "tolerance" all the way down. I'm always impressed.

Since I've had this car, I've thought a lot more about the practical implementation details of actual self-driving. I more often notice situations when driving that are seriously complex.

The more I think about it while I'm driving, the more I realize how fucking hard self-driving would be.