924 karma · joined May 18, 2011
So if you want speed, I'd go for those two out of your list. Go and node.js are still infants in the game, so I don't think there is enough serious software out there built with these to properly judge their effective speeds.
Does anyone know how hard it would be to integrate AngularJS with Fay as described? Sounds like it would be a great way to build large client-side applications entirely in Haskell (Fay).
You can see the different styles for yourself for a very basic web application (and try to extrapolate what it would look like for large ones): http://addyosmani.github.com/todomvc/
Our opposite experiences just goes to show that UI qualities are subjective, and until someone releases scientific studies (none of this "many users" crap) that go against Microsoft's own user testing, I don't see why they should ditch their Metro experiment.
Here are some examples of non-button rectangles:
http://www.windowsphone.com/en-us/store/app/weather-clock/ec...
http://www.windowsphone.com/en-us/store/app/weather/171f3a75...
The differetiators here seems to be that 1) the rectangle is not a square 2) the rectangle has rounded corners
edit: and I guess 3) the rectangle is not "flat", it has a gradient, 4) it's not colored, it's transparent grey, unlike any clickable rectangle in the system. .... (basically, it's fairly easy to differentiate between a clickable square tile and a pure informational rectangle)
http://developer.apple.com/library/ios/#documentation/userex...
Really? Where is this problem? I know the tiles on my phone can all be tapped, without any exception (WP7).
Furthermore, the author talks about affordances and how Metro has none. This is false. Anything that can be touched on the screen reacts to your touch. For example, if you're scrolling down the main menu and your finger happens to press down on a tile, the tile will be "pushed inwards" at the point of contact (even if you haven't released your finger). It's very subtle, but it definitely lets your subconscious know that in the future, if you would want to press that thing, you can. Now it's not an immediate affordance like a door knob, but a touch screen in itself is an affordance for touching, and once you touch then the other affordances reveal themselves.
That is incredibly selfish. Sometimes the person doing the lifting is the one being "brought down", so you're essentially depending on the fact that people are less selfish than you for this to work. Like anything taken to the extreme, this extreme individualism can only be harmful.
[1] http://www.qnx.com/products/neutrino-rtos/safe-kernel.html
edit: that doesn't detract your point however that C is used nowadays on "robust systems"... in terms of popular robust kernels though you'll want to look at something like L4 or QNX Neutrino. There's a kernel that is actually formally verified (seL4) that was first written in Haskell, then verified, then translated to C (for speed).
see: https://blog.mozilla.org/futurereleases/2012/07/06/bringing-...
(edit: the feed cutting was probably just me, just saying it was an unfortunate time for it to do so)
edit 2: They just said that the problem is specifically for the visor (to prevent fogging and icing), not the whole helmet... They still haven't found out what's wrong.
What are you worried about, exactly?