I enjoyed this. But reading the claim that the iPhone was bad compared to other phones of the day makes me question it all. That's so incredibly backwards. It _was_ a much better internet in your pocket. If you couldn't see that, it says something about you, not phones.
I think a lot of this type of problem goes away with immutable data and being more careful with side effects (for example, firing them all at once at the end rather than dispersed through the calculation)
I think there have been and will continue to be UX improvements to programmer tools. GitHub is one example.
You think tools that stagnate will continue to see the same levels of adoption in new generations of programmers? It's an empirical question, I guess I just don't see it, and I say that as someone who loves vim & emacs.
I use and love emacs, but pointing to it as an example of how to evolve UX over time is indicative of your perspective. iOS/Windows/Android are used by the majority of people on the planet, emacs is not.
Which UX do you think young people today and in the future will most understand? iOS/Android or emacs? Why is that?
Maybe the system was different back then, but now Avoid will only avoid the player as a teammate, they can still be on the enemy team. So if someone is too good, there's no incentive to avoid them.
We're working on task management + email, I kept your comment [1] from awhile ago. I don't see any way to contact you in your profile, are you interested in trying an alpha? Email me at garrett at twobird.com
I think we should do everything we can to give/push them into treatment, but at the very least they don't get to make streets unsafe and unclean for others, they have to go elsewhere
In Our Time is a wonderful podcast, always interesting content! Also, as an American, the pace of the show and way of speaking is itself interesting to me.
This brings back thoughts I've had that we should be working with normalized data in code, rather than thick objects. I think the main reason we don't is because there's a lack of tooling around it in our languages. I think a system/language/library designed around this could solve some of the problems in the article as well. First class support for having only one value for a given domain specific id, relations, declaratively describing constraints, and strong querying seem like they would be very helpful to lots of programming problems in complex apps.
This is the right answer and I wish more languages would make this dramatically more ergonomic to do. Store the most basic normalized truth and query/derive what you need.