Interesting. I'm afraid if my boss saw me trying those out at work, he'd ask me why I'm two weeks behind, and if I told him it was the drawbacks of SQL which are holding me back and this is exactly what I needed to get back on track, he's say "you are two weeks behind because you are always getting distracted by stuff like this."
Sucks but honestly, how could I blame him for thinking that way? He--like practically every other boss on the planet-- so utterly lacks any capacity to understand what datalog brings to the table, that really, on what basis could he even make the call?
And you can't even blame him for not taking two weeks off to investigate it--new gee-whiz techniques and methodologies appear every day, most of which promise more than they can possibly deliver. If he spent all his time studying them, he'd get nothing else done.
So why should this be any different? Besides, everybody else on the planet manages to get their shit done with SQL, so just shut up and get with the program.
Your boss either doesn't pay as much attention as you think or you should consider getting a new boss if possible. Life is too short to not indulge on curiosity.
Aye, but these days, with all the layoffs, you are either not that thrilled about rocking the boat, or you are already involuntarily looking for a new boss ;-( With not that much hope that the new one would be better.
And again, it's hard to blame the boss, he's just as scared about it as everybody else. Why should he take a chance and rock the boat?
Especially for something like datalog. No iteration, just recursion? What's with this bizarre syntax? Why are the variables write-once??? Not everybody is just going to be able to take all that in and see how all these weird little pieces add up to a superior solution.
