iMessage between iMessage users is akin to Whatsapp/messenger -- not actually SMS/MMS. Those are only sent when, say, messaging an Android user or if an iMessage failed to deliver.
How will commenters submit their comments? Would they be required to enter their email? Or are you implying an email address would be generated for them to associate with their activity/comment chain?
He was comparing coolness, an "unmeasured and a dangerous motivation", to curiosity, which is similarly unmeasured and dangerous. ie, both are unreliable motivators and yet the industry idolizes both.
What is the frame rate like when you do this, though? A buddy had an original run Chromecast and I remember being excited about that feature back in the day, but the framerate for tab streaming was so inconsistent it wasn't watchable.
Bingo. Having one language for your front end, back end, build tools, database schema... It simplifies life a lot.
You can reuse code / modules.
You Don't suffer from context switching inherent with jumping between languages.
Also, people act like JavaScript is a bad language purely because it is not strictly typed. It's an incredibly fast and robust language with a vibrant ecosystem -- something I'd argue is more important than pure technical bullet points.
Because in a lot of ways those practices don't further the end goal or bottom line of the business. They don't meet business needs. As a developer, I think we both can agree that these things make our (developer) lives easier, but they often don't help the bottom line of the company. I know some dev will retort this, but if I was wrong then companies would be mandating these practices top down.