McUsr

It seems like a well written tutorial, not to worded, not to terse, and should be a good introduction, that gives a broad overview of Unix. -And not Unix on OsX, which saddens me, all the time the author has made it on a Mac. C'mon, just a short piece on the open command, please…. :)

PopcornTime is performing badly on my machine, I actually have to shut down the browser to use it, I usally have 50+ tabs open in it, -that I use.

The short definition would be: "node.js is something that eats up my browsers latency", something along those lines, and as far as I am concerned, that is everything I have to know about it. Node.js is a no stop for me.

That may be so, but when I run something with Node.js in my browser, then I may have to close other things. So, wherever it runs, it really uses too much resources, and therefore I find it as a bad idea from the consumer perspective. It shouldn't be so, that somebody else, should dictate the content of your browser.

I haven't tried Mongo.db, but Node.js takes up a lot of resources in a browser, Node.js apps feels a bit like the widest book strategy in the bookstore, you have to shove other stuff out of your browser, in order to use stuff that uses Node.js, and I feel that as a rather arrogant approach to deliver software, especially, when the functionality of Node.js apps doesn't really dictate the necessity.

AS for Javscript, there are worser languages out there, and the debuggers are good enough now, so it can be perceived as a "normal" language.

You should really consider something other than LaTeX as a publishing platform, or make it look better, when taking it from draft format to publishing format.

This doesn't communicate that algorithms are fun. An algorithm book, should be like a Magicians show, really. With fun problems to apply the algorithms on.

I also note that there aren't any links for backreferences to topics, and that at least one topic is missing, heaps.

I am actually very fond of Robert M. Sedgewicks books (Second Edition), and Donald E. Knuths monumental accomplishment. Those books are fun, most books concerning algorithms are not as fun as they should be.

I am picky I guess, I want fun excercises, or presentations, but also accurate details, and minituous explanations.

This was really a fascinating read, well written, and the information was levelled correctly, for someone not involved in the subject.

Interesting.

Debuggex worked best for me, dabbling with PCRE. I just wish the fonts was somehow bettter on a mac.

The first part doesn't intrigue me at all, because I can easily import an objective C-class into an AppleScriptObjectC app.

I guess something like that works for Swift as well.

AppleScript in itself, can't do that, but I can call everything that is in Say Foundation, and the other frameworks (AppleScript version 2.3), and AppleScript is quite SmallTalkish. ;)

I advise everybody to not mess with any secrets setting that is listed with a red font.

I advise everybody to not mess with anything written in red.

I concur. The emotions the imagery invoked in me was a rare experience, technology hasn't invoked such feelings for years. So not sure if it is feeling associated with art, but still, it made me happy, and I do acknowledge the work as art.

If this interests somebody, then I suggest they'd read "The Unix Programming Environment" By B.W Kernighan, and Rob. Pike. It gives you the concepts, and learns you tools like yacc, that lets you off a lot of tedious tasks when writing an interpreter of sorts. Then follow up with at least "Advanced Unix Programming" By Stevens.

The universe of commandline tools is still not completed, and this kind of programming is fun! fun! fun!

Personally I miss the Plan-9's plumb utility. :)

It is a great fun to compute Planetary positions. You should really read a book named "Astronomical Algorithms" by Jean Meeus. That is the ultimate source for those computations, for hobby use. (There is a really nice chapter in there, about accuracy, and interpolation of values). You'll find various implementations of the algorithms on the net.

I agree totally. The level of violence for instance in your society, may be something you are used to, but others may not be inclined to make the move into such an environment.

What I got out of this essay, which I found to be good, is that you should investigate your hunches, more deliberately before dismissing them. That is hindsightly (From my hindsights :) )a great wisdom from Paul Graham.

This is an insightful thread on Macscripter.net, about how bad the javascript implementation on OS X really is.

The dev team that implements JavaScript on OS X have even been provided with a reference implementation that does stuff the right way but no . . .

This is an insightful thread on Macscripter.net, about how bad the javascript implementation on OS X really is.

The dev team has even been provided with a reference implementation that does stuff the right way, but no . . .

If you are on a mac, then you can really do all this with Apple Script, which also is a bit small talk alike, and that by Maverick, can let you create libraries quite easy.

I use it a lot as a calculator, when I don't use it for autmating the UI. It is great, IMO, the best thing about a Mac.

I have no problems with getting emails by a search warrant from an overseas server. Drug trafficking is global, so should the law enforcement be. I know, I am addressing this particular case, I am not saying "go" on a general basis. But I cases like this, with a search warrant, that turns up during an ongoing investigation, I really have no problem.

By the way, in Norway, blood samples are taken from murderers. 23% of all murderers had thc in their veins.

I have read a great book covering TTY program on ux machines, it is also great for getting an understanding on how it all works. The book title is : "Advanced Programming in the Unix Environment" By W. Richard Stevens and Stephen A. Rago

It gives a thorough walk through of the ttys and pty's, IMHO it is a must read for anybody wanting do to TTY programming, and it is also a great source for understanding how the streams works in connection with the tty's/pty's.

I'm not saying that it is a 'cure all', but actually make -n lets you dry run, and test out your rules before you actually use them (with "touch"), and in most cases I'm sure that that is faster than both reading the manual, and writing a python library for replicating the functionality (reinvent the wheel).

Now, this approach depends of course how well you know make to begin with. But there are a lot of examples out there, and the man pages of GNU make are quite good. It is quite true to the old make facility, so even older book examples should work with it.

Me too.

I use make together with a markdown compiler, and the m4 preprocessor, to keep devdocs up to date, in one huge document, where everything is included, and the various sections as stand-alone docs. The markdown version of the section files is almost uncluttered from m4 and html. I link from any external doc to any other via links in the toc in the main doc index.html, to keep everything as simple as possible. It's sweet.

At the moment you can't even drag and drop a url from the browser.

I think I'll stick with the somewhat mediocre Notes.app that are included with OS X for the moment. If we take away all the gloss, and the fact that you can't have multiple Notebooks, and sharing, and .. and .. then we are left with basically the same. :) Another objection is the max password length of sixteen, that may be long enough but...

Hello. Thanks for sharing! I also found the BBedit plugin, so that I can edit it from the TaskPaper link above. Here is a simple AppleScript to install it, when you don't have administrative rights on your user account:

   do shell script "cd ~/Downloads/doing-master; gem install doing" with administrator privileges

Since I'm an adult, I' wont reply to this by saying: "emacs has more likely fucked you over."

OS X is on the other hand sexy, since you can build emacs-keybindings into the OS and every app that uses the Cocoa Text System, you can even get an "extra clipboard" with the kill-ring.

As for programming, when it is more convenient with an editor as the "control-center" for the endeavour, or real small things that makes a simple editor feasible, then I must say I prefer Vim.

I liked most of the generalizations in the blog post,I think that if he isn't 100% right, then at least he is really on to something.

The place I balked, is where he said that design patterns are almost dead. I find design pattersn to be invaluable, and so does at Apple Computer and with them millions of developers, so the death of design patterns is a bit premature.

Me too, I use source-code-pro almost everwhere (I have problems making it stick with AppleScript because I use different editors I believe). I love it.

It was a long thread but it was worth it. It was very interesting and thought provoking to read so many peoples biases, and insights. I am ready to start implementing tests, and I think that as was stated above, tautological unit tests has no value, unless something inside it may be suspectible to change. When you write a unit test, then you add cohesiveness, so you have to update the unit test when your interface change. In other words. You don't write any regression test before your interface is stable. -On the other hand, you may use that same test as a test driven development test up to that point, and let the test be the manifesto of the specification. For simpler cases, it is often best to use assertions, that you can annhilate when you ship anyway. Apple says that Unit tests are for the model more than the view, but may be used in the controller, so those places I am inclined to use NSAssert. I don't have to throw away unit tests that takes a long time to run in Xcode either, as I can just disable them.

I must also say that I am reluctant to write large tests, and "mock objects" to provider large environments for the code to run in, as that may introduce new bugs and more work.

I guess (hope) the correct stratagems for when to implement tests, and when not comes with experience!

I agree totally. I must say, that I have seen typeless declarations in code, but I do find them to be a nuisance. Adding (id) to a declaration isn't really that hard, and makes the code a lot more radable. Why raise the treshold for the ability to read Objective-C?