I saw one in the form of a wiki awhile back. schemers cookbook maybe. The venerable (lambda-the-ultimate) and readscheme still excellent. We can always use more lisp and scheme oriented sites.
71 karma · joined February 22, 2013
Great books which do not need registration based shilling techniques for your hacking careers:
https://mitpress.mit.edu/sicp/full-text/book/book.html
http://www.paulgraham.com/onlisp.html
https://gustavus.edu/+max/concrete-abstractions.html
https://www.cs.cmu.edu/~dst/LispBook/
Open and Free FTW!
When the datamining show is over let me know. I'm in need of a well paying position and interested in moving out to california. I can teach shell automation, programming paradigms and productive workflow to eager learners new to the UNIX programming environment, hacking and building their own tools.
In my early days when first learning the system I used ee, a HP public domain pico clone which is distributed on *BSD systems for new users.
The original Berkeley UNIX had a modded vi named edit which was aliased to ee and while normal vi operation was aliased to e. I'm assuming ee stood for easyeditor back then.
The video you linked states in its about section that nvi is not customizable. This is simply not true. It's just as easy to script as ed and ex.
Though Bostic never included lisp support like the Joy's editor for extending vi with the shell has always been the main UNIX way of doing it. The classic tutorial to show someone how to extend nvi is to have them do external spell checking with one of the many spell programs.
Though I agree that avid learners new to programming concepts may experience anxiety or euphoria depending on the problems which they are working on defeating. I wouldn't necessarily call it an addiction; no more than I would suggest that a musician is addicted to playing their instrument or writer is addicted to creating prose.
The art of programming in which begins with exploring computational programming models and processes ultimately ends with the craft in which itself is as fluid as a master composer composing whom subsequently is also a master musician.
Though it's that "Teach Yourself Programming in Ten Years" which may be what TFA is referring. Not everyone programs inside skinner's box, even in their early years of programming. There is better research on the subject than this generalized blog post which is far from aphoristic of the effects of computer programming on the brain.
Agreed. The Debian developers should feel proud of the accomplishment.
The editors have had major impact on our languages mainly because regular expressions, called regular sets at the time, where implemented in Thompson's ed which was based on an earlier line editor implementation called qed used on ctss and multics.
One can follow the evolution almost in dialect fairly well.
ed -> grep -> sed -> awk
ed -> em -> ex -> vi
awk -> perl -> ruby
so
ed -> grep -> sed -> awk -> perl -> ruby
The right tool for the right job when all you know is a chainsaw everything looks like a hammer unix process are cheap and all that yada yada philosophical paradigmy finite state automata pipelines vs pointers vs classes vs recursive enumeration iterative parenthesis backtick mind expansions expression logic =P
I use awk more as a anonymous function at the end of a pipeline nowadays and mainly for small stuff where I'm too lazy to use cut or when grep sed and tr may not be sufficient for complex filtering.
Surprised there isn't more of a response here on this site. Even users that don't use awk directly use a language which has been directly influenced by it like ruby and of course the original chainsaw perl.
BSD has the almquist shell as it's /bin/sh and tcsh as it's /bin/csh. Various commercial vendors licensed the korn shell from bell labs. The korn shell is public domain and open for 13 years now. The default sh on most UNIX boxes are either ash or a hard link to ksh which emulates the POSIX definition of sh. zsh and bash also provide the option to hard or soft link so depending on your distro you may have /bin/sh linked to bash.
Debian at one point repackaged the BSD almquist shell as their system sh calling it dash mainly for speed and stability. I believe they removed it as their programmers apparently couldn't program system level scripts without their non portable bashisms or maybe just one of the NIH moments where everything must live under a single mono-cultural license and identity.
Happy hacking =)
for example:
Offending key in /home/user/.ssh/known_hosts:12
ed .ssh/known_hosts
12d
w
q
diff that against this one:
http://www.onlamp.com/pub/a/onlamp/2001/01/25/lamp.html
I love the obvious later edit:
"Of course, there are plenty of excellent open source variants for any of the pieces of LAMP. Let the L stand for Linux, FreeBSD, NetBSD, OpenBSD, and Darwin/Mac OS X, all of which are open source operating systems and all but the latter have open source GUI layers. Let the M stand for MySQL and PostGreSQL. Let the P stand for PHP, Perl, Python, and Ruby."
also reading the ed man page will help as well for newbies.
--------------------------
IEEE Std 1003.1-2008 :
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/ed...
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/ex...
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/se...