The "first" main stream hi-res display? I have some Sony Trinitron CRTs in my basement that would like to talk to you.

Thousand times this. I still own a 22'' Trinitron (20'' working area) that beats any `FullHD' hands down, by resolution and by any other measure as well -- from lag to colorspace -- and it wasn't even top of the line back then. Heck, it even starts up faster than many LCDs.

I refused to let go of it for so long exactly because there was no LCD that would be an upgrade, with the sole exception of the expensive T221. Guess now's the time :-)

Sorry, didn't really clarify what I meant by mainstream: easily available to purchase, by non-techie consumers, from a high-street shop.

Sony multiscan trinitrons weren't exotic - you could purchase them in any reasonable electronics store. I have several that go up to 2048x1536 @ 75hz. Viewsonic had monitors that did the same. While I look forward to higher resolution LCDs becoming a standard option, LCD's set us back resolution wise for quite a long time. LCD does have other advantages over CRT of course.

I had and loved a similar NEC CRT. But 2048x1536 on a 22" display is ~116ppi. Apple's non-retina laptops have been higher than that for years (with the MacBook Air being highest, at ~135ppi), and Sony, at least, has offered configurable 1080p displays in 13" laptops (~165ppi) for some time.

It was pretty nice a decade ago, when everyone was moving to LCD monitors that were vastly inferior in every measure beyond size or weight, but, at least in terms of ppi (and on consumer grade equipment), display technology eclipsed the CRT quite a while ago.

edit: I'd forgotten that CRTs were measured with the bezel included, so at 20" viewable, the display is 128ppi. So closer, but still pretty far behind.

Viewsonic had a 19" display (with 18" viewable) that did 2048x1536. I think that was the smallest size that the 2048x1536 CRT's came in.

So, you obviously never worked at Twitter, where they moved from Ruby to Java.

1. The only moved the search 2. A lot of code is in scala not java

1. I never said they moved the entire code base. What would be the point of moving the entire code base anyway? The reason why they moved search to Java is simply because Java scales better than Ruby when faced with heavy traffic.

2. AFAIK, only the message-queue backend is in Scala?

Just wanted to point it out for people who did not know that.

2. Not sure.