Not really. We already have several different platforms out there catering to "average Joe". I think it's time hackers actually get something tailored to their use instead of having to suffer compromises on other platforms.
Because that doesn't work on the iPhone. iOS has those settings baked in.
I ditched my iPhone when I got tired of my tethering options randomly disappearing/reappearing on minor iOS updates without a chance to override that. Even though my carrier allowed and supported tethering, the options would just disappear because the APN settings for the carrier were not present in the phone and couldn't be uploaded on some iOS versions.
I thought we got past regional bullcrap in 21st century as well. But as long as all other digital music stores and streaming services greet me with "Go away, you're not allowed to listen to us from your countrty" I'm happy to give Grooveshark money.
I might be the only sceptic here, but the fact that it seems that Valve has conflict of interest when it comes to Microsoft lately (see Gabe's comments) makes me doubt the authenticity of these results.
I'd love to see real performance improvements when it comes to Linux, but right now I just see a company that (it seems) has something to gain by smearing Microsoft giving out results without any methodology or explanation. They never even said how they avoided the typical pitfall of "FPS" benchmarking - making sure the GPU and the engine is actually drawing the same things (that means making sure all the same shaders are executed, similar extensions are used so that image quality is identical).
Until we get some confirmation in the wild I'll remain highly sceptical towards claims on the blog.
Because in environments where Java is used "switch language your're using" just isn't such a viable option. Especially in the light of an option of just upgrading the language. There's nothing seriously wrong with Java that couldn't be fixed by incremental language updates - like the ones C# has received in last couple of versions.
Um, pretty much all parallelizable CPU number crunching (data mining algorithms, computer vision etc.) which aren't covered in C code. Those are especially problematic, since they're usually coupled with numpy and simillar libraries not supported on other Python implementations - including Jython.
Funny how that exactly mirrors my experiences building a HTML5/JS app on iPad - I've quickly managed to get 90% of the app done and then wasted hours and frustrating hours of hunting WebKit performance issues, bugs without pretty much any help from tools or operating system.
Especially annoying are intermittent bugs that show only in certain minor iOS versions, which are hard to look for and test because of Apple no-downgrade policy on devices :\
Choosing native app was just a better way to keep my sanity.
Yeah, same here in Slovenia - even though FTTH providers have 100/100 available, people usually opt for cheaper 100/10 or 10/10 options because of pricing (100/100 is 100€/mo, 100/10 is 27€/mo, 10/10 is 22€/mo, which is a noticable difference).
Also I noticed there are very rare use cases when I'm able to actually get over ~30Mbit or so downstream, usually the servers I'm downloading from aren't capable of delivering data so fast.
I'm just hoping slimming down memory usage won't go at the expense of speed... my systems have 16GB of RAM - I want Firefox to use as much memory as possible to speed up my experience. So if slimming down FF will make my disk trash more, that's the wrong direction to take.
Yeah this... I've found out that I subconsciously actively avoid refactoring our (old and in parts terrible) codebase because the tools for it are so bad.