I don't want to sound like a douche, but It looks to me that you did it to prove you eat your own dogfood. If you were so unhappy with Tumblr, why didn't you just use another blogging platform or software? There are many alternatives in almost every language known to man.
Because of the reasons in the post, but mainly our design team. I didn't want to set up a WordPress instance and make them learn the intricacies of php and WP theme system. They already understand the Rails folder structure, Sass, Haml and all the other tools we use.
I'm going to agree on your point as well. Designing with things like WordPress, Tumblr, etc become a major pain quickly. Especially considering the speed at which you can design with a bare rails app.
Moving away from the X86 instruction set 5 years after the move PowerPC is NOT going to happen, period. ARM is fine for the iPad, but for high performance work it doesn't cut it.
ARM tech & Intel have proven that they can scale, but only Intel has the performance advantage for years to come.
And come on! Fragment the Mac market in laptops with ARM and workstations with Intel chips is a really bad move. The only laptop that would have an ARM chip would be an iPad with a keyboard.
I think ARM is developing fine for high performance work. Nvidia's Denver is probably going to be half GPU anyway, so parallel workloads will thrive on their ARM chip.
I also think a RISC instruction set is starting to look pretty nice, since (as I understand it) x86 chips break CISC instructions down to RISC-like micro-ops anyway. Why not move that process off the die (where space, power and thermal requirements are strict) into the compiler.
The transition away from PowerPC wasn't that tough in reality. If anything, it told Apple that such a change is very possible. With Windows 8 coming to ARM, it's not that big of a deal for Apple to follow suit.
Yes, most implementations of x86 translate opcodes into equivalent RISC-like micro-ops.
But this was necessary to achieve any kind of real performance with x86. It's a terribly-designed architecture where all of the instructions are scattered all over the map. There's no unifying design, and most operations that should be simple to implement require scads of silicon. Much of the power wasted on x86 chips is in that instruction decode hardware. It's terribly inefficient. (It's also a horrible instruction set to deal with.)
Call me skeptical, but I've never trusted Compete's numbers.
Their service gives stats without citing sources, so I don't know what kind of magic or data interpolation they use.
Without Google Analytics to do a 1-1 comparison, any metric will be suspect. Alexa will suffer from its standard bias of only counting people with the Alexa toolbar installed, which won't be many for either site. Compete's metrics are compiled from a variety of sources [1], including a toolbar, none of which seem particularly definitive.
I don't know.
I saw your site and I find it is not easy to use. The first page doesn't tell you what is a virtual bet about. It also gives you to calls to action that are equally important. I would only highlight one of them.
The How to Play page is boring to read. I would replace everything with a form that fills in a Twitter post for you (for which you don't need permissions from Twitter).
I began programming when I've got my first computer, an Atari 600XL (what a pos for 1992). I learnt BASIC from a collection of science magazines from the 80s that my older brothers had and from an Atari BASIC manual.
Unfortunately I never had a diskette drive nor some assembler books :(
Only if Sony doesn't do a thing to lock the software up. Maybe they could add SPUs to the phone, or something that would lock the software to the platform.
