> What do you mean under term older technologies? For the first couple of programming jobs I had I literally had physical wyse60 and vt100 terminals sitting on my desk, connected up via 9600 baud (or 19200 if I was lucky) serial lines.
I have an interest in lexing and parsing and tended to like writing utility programs to help manage our code base (ie. show me all the functions defined in, and all the external functions called from, this particular source file). One company where I worked was not prepared to pay for a C compiler so I ended writing some basic parsers in awk. Back then with programming languages you pretty much started with a clean slate, a primitive library giving you basic OS services, and not much else. It was up to you to implement anything beyond that and you had complete control to do it as you wished. These days software development is all just plugging together frameworks and libraries with 'nuget this' and 'maven that'. When it works, great. But usually it doesn't. I think this quote from StackOverflow pretty much sums up my experiences with this... > After several hours of following dead ends, installing Maven, customizing > environment variables and chasing down dependencies, I eventually found > that... Also once upon a time I tried Ruby but got stuck in a situation where Gems (or something) needed a version of Ruby > some specific version, but the library I needed to use for my project required a version of Ruby < that specific version, so it couldn't be made to work and in the end I just gave up. Sorry, this has turned into a bit of a longish rant, but so far my experience with Nim has been that (apart from needing to download a lib for iup) everything has pretty much just worked out of the box.
