3 ms·
> Well guess what. A lot of stuff poses security issues. But you have to balance that out with the features and usability you want to give to the user Just ima
by superasn 14y ago
> Well guess what. A lot of stuff poses security issues. But you have to balance that out with the features and usability you want to give to the user
Just imagine if Microsoft had done the same starting with Windows 3.1. How much innovation would it have killed?
I recently tried using Adobe AIR to make something, but unlike C# the AIR API is severely sandboxed and limited that even simple things like GetDC or CreateShortcut are just near impossible to implement. End result is I never really completed my app.. something which would have taken me an hour at most to do in C#.
This new trend of technology where everything is being sandboxed and scrutinized for approval in the name of security is really very sad for hacker culture.
- taligent 14y agoAll we are talking about here is a loss of performance in Javascript benchmarks. In every day usage you simply don't notice a difference between Chrome and Safari. So I think you have the volume turned to 11 on the idea of it killing innovation.
- superasn 14y agoWell my reply was to the above poster wrt to Apple's inane policies in the name of security that kills innovations and and hacker culture. For example: The most important app for me is iBlacklist for iPhone. It prevents nearly 20 spam text messages for me daily, which directly translates into less annoyance and added productivity daily. Yet, Apple will never approve this app for general public. Same for Microsoft's on{x}, which is a genius innovation imo but because of the recent inane app store policies trend, even Microsoft had to release it for Android only.