Times changed, people don't
Btw, if you do code for a living what Arndt sad take preference.
Anyway, fast typing...when is more likely to make mistake in your code, when you try "speed" writing or when you put more effort in understanding what you actually type(assuming you don't do something trivial)? Otherwise I'm really fan of GUI tools, especially for code organization, in the same time I don't underestimate bash.
P({})
Exactly! They can't run my code until I've written it, so the faster I get it written the sooner they can use it and solve their problem!
While I understand that 'it must be fast' could a technical specification, almost all the bottlenecks today are in I/O of some sort, or - if they are complex - dependent on the library you are using (unless you REALLY suck at programming and adopt a 'not coded here' approach).
Science is open source religion
Nice. I was suspecting that you could get close to SymbolicWeb using some kind of J2EE-ORM-whatever-flexible-clientside-solution. However, you can't integrate it as nicely to an "application writing language" as Lisp can, unfortunately -- J2EE thingies are very very verbose as you well know.
@akvino, I don't want this to be a ******* contest either. I just am sometimes a bit annoyed by the attitude of the low-level crowd that automatically assumes that my (or other high-level-language programmers') preferences are due incompetence, while it is not apparent to me that they actually understand what non-C-languages actually do, and why, and why that is interesting. For example the coder of SymbolicWeb beats pants off, on low level too, of any programmer I know, and he's a fanatical Lisper exactly because of that. And most of Lisp critics would totally suck at "formulating programs" against him in any language...
Last edited by CptPicard; November 27th, 2009 at 08:36 PM.
LambdaGrok. | #ubuntu-programming on FreeNode
Bookmarks