Sounds like he's referring to "image persistence", which is similar in appearance to burn-in, but a different mechanism.
Burn-in is more likely to be found on CRTs and can take a long time to occur. Image persistence can happen in seconds or minutes and is what is seen on LCDs. It's usually temporary or reversible. (And plasma owners can experience both, yay! :)
Looks like Sublime Text 2 meets his requirements. Goto Line is simply Ctrl-G, and up pops a simple input line, similar to hitting ":" in vim.
As an added bonus, the input line disappears if you press Ctrl-G again, hit <esc>, or press enter without entering anything. So, fast and easy to get into, fast and easy to get out of.
Hah, nice. My first thought was: what's the big deal? Someone installed Pow, though I wouldn't expose my dev machine to the public like that. Oh, wait....
Hey, you and me both, brother! Some of the most fun I've had programming was writing an assembly TSR that would scrape the screen buffer of the PAL BBS game Flash Attack (I think that was name of it, anyway) to calculate the firing angles for me.
I also tied into the keyboard hooks so that I could build an entire decoy base with a single key press (just some simple buffer stuffing) along with a cool little "death blossom" attack.
It's also interesting to note that in the U.S., companies are thought of as a standalone entity, and referred to in the singular, rather as a group of people.
So, it'd be "BankSimple is based in...", instead of "BankSimple are based in...".
When I first started reading things from the UK, I initially thought the writers simply used poor grammar :)
So what are the frameworks or tools that you recommend? Serious question from someone that has so litte Java experience, you might as well call it "none."
All of the XML config stuff was, to some extent, what turned me away from Java so many years ago.
If I were to start over today, what kind of frameworks would be the wiser choices for desktop apps (gui frameworks) or web apps (web frameworks, maybe an ORM)?
What point am I supposed to be getting here? Yup, it's a benchmark. F# was consistently slower than Java, but, consistently used less memory and fewer lines of code.
Burn-in is more likely to be found on CRTs and can take a long time to occur. Image persistence can happen in seconds or minutes and is what is seen on LCDs. It's usually temporary or reversible. (And plasma owners can experience both, yay! :)