71–80 of 93 posts
Earlier quoted context omitted.
Maybe he considers emacs part of 'modern tools'?
I'd rephrase it and say: "You can be much more productive with mature tools.". Which Emacs and vi, ofcourse, are.
[ keep in mind that 'mature' != 'old' ]
> I'd like it if the Air was about half the size. [...] > I'd like it if the HD display was bigger and much lighter and didn't have such a massive octopus of cables attached to it. Looks like Apple agreed. The more recent Apple displays are bigger and have mostly eliminated the “octopus of cables” (when LightPeak hits this should even further improve), and the new Air is substantially smaller.
> I'd like it if the Air was about half the size. [...] > I'd like it if the HD display was bigger and much lighter and didn't have such a massive octopus of cables attached to it. Looks like Apple agreed. The more recent Apple displays are bigger and have mostly eliminated the “octopus of cables” (when LightPeak hits this should even further improve), and the new Air is substantially smaller.
I'm thinking about getting a new Macbook Air, but I'm concerned about his desire for unlimited fast CPU: the new Airs have pointedly lacking CPU resources.
I just finished reading "Coders at Work". An I 'used' this would make an interesting site as well. Especially if there were pics of some of those old machines. I borrowed a unix book from a friend and he had been using an old punchcard as a bookmark. Neat little find.
Why can't I create my own usesthis page? Who decides who's important or interesting enough to get "interviewed"?
Why can't I create my own usesthis page? Who decides who's important or interesting enough to get "interviewed"?
Earlier quoted context omitted.
Another Windows sighting! http://jakob.nielsen.usesthis.com/
http://jason.rohrer.usesthis.com/ Another windows sighting. And the most fascinating of the interviews I've read.
Earlier quoted context omitted.
I'd rephrase it and say: "You can be much more productive with mature tools.". Which Emacs and vi, ofcourse, are.
Is 'vi' mature? Or are you talking about Vim? vi has been around a long time, but the functionality is rather limited compared to Vim. When was the last development on vanilla vi (not Vim in compatibility mode)? [ keep in mind that 'mature' != 'old' ]
Earlier quoted context omitted.
I know this isn't a popular POV, but I've always thought that developers should work on last gen hardware. Getting good performance out of last gen hardware ensures great performance for the typical user. (okay, let's be reasonable, the build machine should be stupid fast so nobody is sitting around for half a day while the repository builds).
I think that would be true for testing, but not for actual development. When I'm working I want to marginalize anything that might slow me down. You did mention the build machine should be fast - but don't most people build locally first before pushing out? I guess it also depends on what you're building. I mostly work on stuff that isn't used by a consumer. It's going to run as a service on a machine or network of m…
Earlier quoted context omitted.
In the Unix culture the people who claim to use vi actually use vi + shell + hundreds of little software tools. If it have worked for 30 years perhaps you should give it a try.
That's not a very good argument. Horse-drawn buggies worked for well over 30 years.
I can't see how this is a good counter-argument either. They still do work, they run on renewable fuel, growing the fuel can be enhanced by the waste products of the horse. They're relatively low maintenance, the motor can be interchanged and easily used to drive other machines. Certainly at city driving speeds the buggy is going to compete quite well.
Yes a car or other automobile is going to outperform a horse & buggy in many situations but there are other aspects that are wins for the horse & buggy.
I'd be interested to see a running cost and efficiency comparison, shoeing horses is probably quite expensive nowadays with the dearth of blacksmiths/farriers.