silon

I'm only running Windows on my VMware machine.

Along with browser page history. I really get annoyed if I reload while site/network has a problem and can't go back to previous version.

Note also that code of average architectural quality will require about 1 maintenance day per year per 80 LoC just by virtue (vice?) of existing. (Paul Graham: a full-time maintenance engineer can own 20,000 lines of code.)

This is true in my personal observation. I mostly wrote two pieces of software rougly 50,000 lines each, and it's my limit of manageability. Will need splitting up and modularizing if it needs to get larger.

They must understand that user can (and should be able to) change (just the) font size, if not their designs are often useless.

Ratio display needs to be fixed:

99k -> 71k is not usefully presented as 1.4x, but better as ~30%

>But you can forbid it to access other memory areas for security

Not in C/++ in any standard definition of "thread".

Zoom text only (showstopper, IMO).

For me, I could learn git no problem, write wrapper scripts for some things, etc... But I'm not explaining it's idiosyncrasies to other people on my team.

Git is not wrong by itself, there's just an impedance mismatch between it's model and a usable interface model. For most purposes, the index should completely hidden.

LOL. Yesterday, I restarted firefox because it ate 13GB of virtual memory and started to get really unusable.

Ceylon looks to be much better C-like language than Go. Go simply has too divergent syntax.

This needs a framework to write distributed / sync based offline applications.

Perhaps it's time to upgrade my HTC Hero (rooted, of course)

Must download location bar add-on.

I found that Apache jmeter works well for me. Easier to use than Grinder, but much more useful than the MS tool.

Slower query using indexes is better than randomly using table scans depending on statistics, ...

At least for interactive apps, NoSQL wins.

I wish there was an SQL option to cause a fatal error if it needs to do a table scan. This would be very useful on test systems, at least.

NoSQL forces discipline which is a good thing, preventing "late" performance optimization when in production.

I mostly stopped too. I still read the mailing list occasionally, but haven't bothered to download any snapshots.

-1 to Automatic semicolon insertion (seriously).

Complete with non working backspace, just like in Linux early days.

In subversion, it's best to rebase the branch after you have merged it back. Just like git rebase, you lost history.