Not sure what you mean about immediate results though... if I search for, say, "10C in F" I get "10 Celsius = 50 Fahrenheit" at the top of the page. And "time in mumbai" gives me "7:37 AM" plus the offset from UTC and the date. Also "weather in chicago".
Same for conversions of lb/kg, mph/kmh, and some other units I just tried, as well as currencies. But either it doesn't do mpg<->L/100km or I'm formatting the search wrong.
It also doesn't answer "hello in french" with an immediate translation like !g does. But I'm ok with missing translations because languages that I want to look up are in wordreference, are easy to make shortcuts for, and generally have better translations and more thorough info.
When I do have to use google directly I sometimes find it _harder_ to get results because it doesn't just show some links and summaries, it seems to want to try to give me "solutions" which aren't always quite what I want. I've been told the results get better the more you use it (ie. the more info you feed to the machine, it learns what you want) but I almost always get what I need on the first attempt searching with ddg and usually within the first few results. If it's not there, my experience has been that I'm not going to find it with !g either. (Usually something to do with really obscure programming problems or error messages.)
Most of it could even be done offline.
$ units
You have: 37817.55 per second You want: per day * 3.2674363e+09 / 3.0605034e-10
Or 3,267,436,320 requests per day.
I was profiling redis performance, and I got approximately 37817 requests per second for MSET on 8x terminal windows when running redis-benchmark -P 2000 -c 6 -s /var/run/redis/redis-server.sock