The problem with meteor (and similar frameworks): curl -s https://www.meteor.com/blog/2014/08/26/meteor-090-new-packaging-system \ | sed -e '/[ ]/,/[ ]/ d' If you want someone to read your article, actually sending that article would be useful. If that article has advanced features that require javascript, flash, or video/audio, you should probably give me a reason to whitelist the page. Sending and empty body tag, o…
> js is whitelist only You're not representative of the majority of online users. Not even close, by an enormous margin (95% of people don't know what JavaScript is, let alone how to disable it; out of the remaining 5% that do know, 4.999% don't care). Given that you're in an extreme minority and wield no power in the marketplace, could you give them a reason as to why they should dedicate development time to making…
> 95% of people don't know what Javascript is
Indeed. So you take every opportunity to exploit that ignorance, instead of educating them that there might be risks associated with running unknown code?
This is a perfect example of one of the larger problems in the tech industry. Your product could be something that helps them, despite their ignorance of the alphabet soup of technologies. Instead, you choose to make something that requires the client to take risks. Was there some technical reason this was necessary? No. Was here some huge benefit to speed or availability that wasn't available with other technologies? No. The benefit was personal convenience ("development time").
The next time you see someone annoyed at technology they don't understand, remember that YOU (and people like you) were the source of that frustration.
//i'm sure this will be downvoted as well, given how selfishly narrow-minded this crowd can be at times