Nessie – The Loch Ness Monster of Programming Languages

A new programming language has been sighted, it goes by the affectionate name “nessie” and it claims to be the loch ness monster of programming languages.

the main trait of nessie it borrows from python: indenting.
the main difference to python: it is typed, something that python developers
are now considering for python 3.

ever since i started using python myself i have to agree, indenting is one of
the best ideas in the evolution of the syntax of programming languages that has
been made in a long time. indenting is a must for readable code anyways and
anyone who thinks that indenting is a problem is either writing sloppy code or
has simply never tried python.

i like concise and explicit syntax without redundancy. and that’s something
that nessie promises to offer. the syntax should serve both the user and the
compiler. the compiler should not try to guess what the user wants to do, but
it should also not force the user to be overly verbose.

nessie offers a number of interesting things that python does not (yet) have.
one of them is static typing. this topic has always raised a controversy in the
python community. nessie may be the way out for those that do like static
typing without forcing their opinion onto the rest of the python community.

there is also the very compact use of operators on all kinds of data
operations, like splitting a string: instead of s.split(" ") nessie uses s/" "
you divide the string at the spaces. the reverse of course also works:
arr*" " joins an array to a string.

there are many more operators and they can all be applied to almost any type.

there is a well evolved runtime library that offers an astonishing set of
features from image manipulation, a calendar module that supports any kind of
date manipulation you have ever dreamed of, support for most internet
protocols, xml, database access, you name it, it’s there.

like python nessie is object oriented, but it offers class member protection
that allows to add security features to your application that are simply not
possible in python.

one interesting feature here is nessies class syntax. you don’t need to mark a
class with a keyword, but just but the contents of your class into a file. the
filename becomes the class name. instantiate or inherit the file elsewhere and
you are done.

a bit more about types:
nessie is statically typed but it does not make you go out of your way to make
things work like java does. there is a mixed type which will hold anything, and
brings you back to the same dynamic typing flexibility that python offers.
you may also combine any types as you like: string|int|float.
incidentially a similar syntax for types is being discussed for python.

container types may be specified generic: array (which is really
array(mixed)) or more detailed:

mapping(string:array(array(int(0..359))). the latter is a dictionary
with keys of type string and 2-dimensional arrays with integers ranged from 0
to 359 as values. as you can see the typing is very flexible, you may be as
specific as you want and as generic as you need.

let’s have a look at nessie itself:

void main()
  write("hello world!n")

void main()
  write("hello world!n");

print "hello world!"

nessie is more explicit than python but less redundant than pike.

apart from the indenting syntax, nessie is essentially a dialect of pike.
it uses the pike runtime which brings with it a great amount of features that
have been evolving since the late 80ties. the features described above are
really all just inherited from pike. nessie actually just adds the indenting.
a minor difference, that may have a large impact on those that don’t like

python and pike are both great languages, and so is nessie.
it’s time for some change.

Nessie and


  1. 2005-04-01 12:54 am
  2. 2005-04-01 1:08 am
  3. 2005-04-01 1:17 am
  4. 2005-04-01 1:21 am
  5. 2005-04-01 1:24 am
  6. 2005-04-01 1:34 am
  7. 2005-04-01 1:39 am
  8. 2005-04-01 1:47 am
  9. 2005-04-01 1:52 am
  10. 2005-04-01 1:55 am
  11. 2005-04-01 2:05 am
  12. 2005-04-01 2:05 am
  13. 2005-04-01 2:09 am
  14. 2005-04-01 2:16 am
  15. 2005-04-01 2:30 am
  16. 2005-04-01 2:35 am
  17. 2005-04-01 2:40 am
  18. 2005-04-01 5:02 am
  19. 2005-04-01 5:45 am
  20. 2005-04-01 5:48 am
  21. 2005-04-01 5:51 am
  22. 2005-04-01 6:00 am
  23. 2005-04-01 6:16 am
  24. 2005-04-01 6:36 am
  25. 2005-04-01 6:47 am
  26. 2005-04-01 7:56 am
  27. 2005-04-01 8:44 am
  28. 2005-04-01 8:46 am
  29. 2005-04-01 9:14 am
  30. 2005-04-01 1:32 pm
  31. 2005-04-01 2:14 pm
  32. 2005-04-01 2:40 pm
  33. 2005-04-01 2:45 pm
  34. 2005-04-01 3:53 pm
  35. 2005-04-01 5:24 pm
  36. 2005-04-01 5:31 pm
  37. 2005-04-01 5:35 pm
  38. 2005-04-01 6:30 pm
  39. 2005-04-01 11:40 pm
  40. 2005-04-02 4:14 am
  41. 2005-04-02 8:32 am
  42. 2005-04-02 8:45 am
  43. 2005-04-02 8:50 am
  44. 2005-04-02 7:25 pm
  45. 2005-04-02 9:01 pm
  46. 2005-04-03 10:41 am
  47. 2005-04-03 5:13 pm
  48. 2005-04-03 9:54 pm
  49. 2005-04-04 12:58 pm
  50. 2005-04-04 1:12 pm