3 ms·
I remember learning about Pike nearly twenty years ago. It made some decisions that seemed odd then but which seem rather modern in retrospect. First of all, it
by jhbadger 7y ago
I remember learning about Pike nearly twenty years ago. It made some decisions that seemed odd then but which seem rather modern in retrospect. First of all, it was a scripting language that had typed arguments. And second of all it allowed multiple types as arguments and returns -- for example you could define a function int|float sq(int|float x) {return x*x;} that would do the right thing for ints and floats but still error out on strings.
- em-bee 7y agocoming from C pike felt rather natural, and i felt pike was ahead of its time when people elsewhere argued about typing and python, ruby and javascript (typescript) started adding optional types. pike had them all along. pike attracted me because it was the first language i came across that allowed me to recompile classes at runtime. i also love its deceptively simple class model. each file of code IS a class. there is no need to declare the class inside (as java has you do), but you open the file and put functions inside. done. elsewhere you inherit the class by referring to the filename: "inherit foo.pike". pike was the start of my career as a software developer and i am still using pike for all my websites to this day. the difference now is that i write the frontend in javascript and the backend is a BAAS platform with a REST API in pike.