New to Harikavach >> Harikavach Introduction The Challange The challange in Harikavach is that it is a HandCryption technique. This implies that it must be humanly possible to encode/encrypt the message and decode/decrypt the message, without using a computer and in a reasonable time with minimal effort. Computers can be used to compromise the message. Computers can use Brute force technique to break the code. In Brute force technique the computer can try all the possible keys ( or a highly probable set ) on the message to compromise it. With increasing computing power, it is easy for a computer to try millions of key combinations within a reasonable period of time. This is the problem with level 4 . There are fixed number of keys that can be generated using Scramble Clock . Let us consider that we place all the possible keys in a Set. Then this set is the Key Set ( Key Space ). The Key Set is finite for Scramble Clock and also finite for Harikavac...
B ackground Last month I had asked a Java related question to all my students on a facebook post . Why is it that in Java, Objects are always to be allocated on heap? Why is dynamic allocation the only option in the toolbox of a Java developer while creating objects? It was a very interesting discussion on facebook. Many participants, my students and otherwise gave good arguments in defense of the Java Language Design. One of the arguments that came out shining, was that of the possibility of unsafe allocations on Stack Frame. Special thanks to Ted Lum, Chetan Parmar, Nishant Verma, Vaibhav Desai, Tusharkumar Thomar, Vimal Sakhiya, Clair Roma Henry, Subham Gadi, Makarand Bhosle, Prasad Kowli and Nirav Kothari for their participation and valuable arguments. Let me now, put forward my perception on why Java Language Designers would have taken such a decision. The following content in this article assumes that the reader is aware of memory models and lif...
(This post is an old article I wrote on Google Knol. I have shifted it here... Witness the power of Extension Methods) My meeting with Dalpat ... I happened to meet a Ruby Language enthusiast (Mr. Dalpat) recently. He was showing me some cool programming tricks in Ruby Language. He was bullish about power of Ruby and lamented over limitations of C# and Java. "C#(especially after version 3.0) has a bigger toolbox of idioms than Java , but Ruby is far better" he said. Ruby being dynamic and capable of supporting internal DSL's( Domain Specific Language) has always had my due respect. However, I wanted to know what made this Ruby evangelist so strongly opinionated. One of the things that came up in his praise for Ruby was that even literals in Ruby were objects. So one could very naturally write something like 5.times{puts "Hello"} and print Hello five times. This he said was possible because the times method had...
Comments