Would there also be interest paid for time lost in traffic? New York roads are tight and always busy, something the public transit system is supposed to workaround.
Public transport is supposed to alleviate congestion on the road. That there exists those unwilling or unable to make use of it is irrelevant, so long as a sufficient percentage of the driving population can and do use it over driving themselves.
There is no reason to imagine that compensating those not using it (for any reason, be it disability or in a niche area in the city, or simply unwilling) would be a part of the goal of providing public transportation.
It is not a gift to the people from bottom of the government's heart, that they would try to offer an alternative gift to those unable or unwilling to partake in this wonderful service.
I think free fare and door to door service would be pretty good already.
Paying them for time lost in traffic seems like it's going too far. After all, its not the taxpayers fault they are in a wheelchair. We don't need to compensate them.
There are many legitimate uses of calling methods and functions using reflection. Expecting to hit all of them in a short review process is comically optimistic for anything but the simplistic of apps.
Your suggestion of enforcing this also makes no sense from performance or privacy standpoint.
You don't need to have your work communication on your private phone. If you want to do that, you can still temporarily disconnect them before leaving for holidays...
That statement makes a few assumptions. I don't have more than one device for this stuff. My business and clients all emergency numbers (which would include that person number if it existed). I also have a painfully small amount of self control and have in the past nipped off to check my emails for "10 minutes".
A holiday can be a good opportunity to disconnect completely.
I didn't the last time I went on vacation in Europe. My cell phone carrier also is atrocious and charges usurious international roaming charges, so that was a contributing factor, but it's really nice to unplug and go off the grid on vacation. You just have to do things the old fashioned way - print out your reservations and itinerary, get some maps.
20? I recall going to Europe for two weeks in 2006 (BMW European Delivery). Didn't bother bringing my dumb-phone. Just had a camera. I drove 2000 miles around Western Europe, 6 countries, had zero hotel reservations before I left, and had no problems whatsoever. This was in April so just popping into a hotel and finding a vacancy was not a problem.
Is it the best tool in the world? No. Is it the only actual tool to communicate bugs and enhancement requests to Apple? Almost. We've all used issue tracking software to add to backlog ("Open a Jira and I'll take a look when I have time"). Doesn't mean it's not being looked at.
That bus entails both good and bad, and everyone should be familiar with the risks of developing in a language in this state.
Personally, I wouldn't take any job application that only lists "Swift developer" seriously. Anyone serious enough about iOS development should know that you always need both. Also, not a big fan of telling people what technology to use forcefully.
There are a lot more challenges than just ABI and 32 bit. Swift is not dynamic, lacks many of the features the ObjC runtime provides - so most of Apple's frameworks cannot actually be implemented in the same way with Swift. Basic stuff like KVC, KVO, responder chain, etc. go out of the window. And many of Apple engineers are not convinced throwing these technologies out of the window for some imaginary benefit from Swift is the right direction.
