965 karma · joined March 12, 2009
pr@prlambert.com prlambert@learndot.com
If you haven’t trashed your computer while doing something questionable, then you’re not a computer scientist – you’re just an arts grad who didn’t get laid
A CompSci grad is supposed to be able to do difficult things that arts grads simply can’t understand.
This is exactly the type of biased, negative, and unproductive criticism that the HN community works hard to prevent and has been recently vocal in admonishing.
I may be a little sensitive - I have both a double major BA and a Bachelors in Computer Science and my CS friends look insanely ignorant when they presume they know anything about the benefits/lacks of an Arts degree. Arts "teaches you to think" in ways that CS/Engineering students are never even exposed to (except for by some token arts requirements) - it teaches you have to think about people and the human condition. I would much rather have a CS grad help me start a company, but equally rather have an Arts grad run it (See Warren Bennis' On becoming a leader for a much better investigation into why Arts students make the best leaders [of human beings]).
I'm not saying that Arts is better in any way - I'm just asking for mutual respect. No poli sci student is going around saying they can prove the amortized runtime of a skip list - if you're in CS please don't pretend you've had their education either. Your education also isn't any "harder" in any objective way - ODEs or building an OS in C is not any more difficult than wrapping your head around Aristotle or existentialist phenomenology, it really isn't. It's actually much easier to get an A in CS than Arts, but that's a bit of an aside.
I realize that this was an article not a comment, and I don't intend to start a debate. I just think we need some mutual respect between the disciplines and there seems to be a latent "bash artsies" in some tech writing that really needs to be squashed - it's not helping anyone.
[more to the point of the article: My subjective anecdotal evidence is that arts grads have a MUCH harder time getting hired post-grad (which makes sense considering they chose to learn fundamentals not practical skills) so they go either a) travelling b) to grad school c) to law school. This is a major skew, none of these people should be consider employed, but they don't contribute to the arts grads unemployment rate either]
/* User beware. I don't know javascript. I read mozillas / / reintroduction to javascript, being somewhat familiar with / / actionscript 3, god knows how it ended up working. This code / / is run by tears, wishes and luck. */
That said, writing a programming language sounds a little daunting if you've never been introduced. So here's my recommendation: Work your way through at least the first half of Programming Languages: Application and Interpretation by Shriram Krishnamurthi (free online http://www.cs.brown.edu/~sk/Publications/Books/ProgLangs/). Probably the most influential book of my entire CS degree, not too difficult once you get used to Scheme, and incredibly rewarding (and fun!).
Your experience is mostly OO and procedural. Let's round it out with the functional cannon: In the first half of PLAI you implement the crown jewels of the paradigm: first-class functions, both with dynamic and static scope (aka closures), lazy evaluation ala Haskell, true language-supported continuations, recursion (the Y combinator is in there), mutable vs. immutable variables and more.
The implementation language is Scheme, which is really really easy to grasp the basics of quickly. So as a side effect you will learn an interesting esoteric language just as you wanted. I would think any competent programmer could learn enough Scheme to work through PLAI in under 2 days. Basic Scheme is kinda like "lisp light" compared to CL/Clojure, so it's a great way to start.
It seems this only shifts their heat dissipation problem from having to cool servers to having to cool large quantities of sea water. Perhaps the latter is an easier problem to solve (gigantic outdoor cooling tubs?) but I don't know.
The reason it is difficult is because you can't use any of js tools that leverage a js interpreter - your code isn't valid until it's run through the sproutcore build system (which, as previously mentioned, is pretty slow).
Otherwise, Mozilla Skywriter (http://mozillalabs.com/skywriter/ , previously Bespin) is also sproutcore based.
pros: friendly and helpful community, a number of things that 'just work' and a vocally espoused observers paradigm for wiring up your app that, when it works, is very nice and tidy. Very readable and well documented code base (I've read well over 50% of the codebase now, keep it open in a window all day). Can look very impressive in demos. Deals pretty well with most browsers and platforms (particularly iOS friendly).
cons: Compared to Rails, jQuery, etc... a relatively small community and not a lot of examples to learn from. The wiki is really hit-or-miss and the codebase is pretty much the only reliable source of documentation. Some of the features feel half-baked and like 'some person's pet project'. Some things don't 'just work' and can require a lot of hacking (not in the good way). The build tools are a little slow, which adds 15 seconds or so to every reload (which I do many many times every day, it adds up). Refactoring is a real pain (especially compared to our backend, written in java using eclipse), there just aren't that many tools. That's true of most javascript, but the sproutcore build tools add some 'macros' to javascript (like sc_require();) that really confuse the javascript refactoring tools that do exist.
It's a genuine problem (for me at least) when starting a new project - bitbucket (-) and Mercurial (+) or github (+) and git (-). If anyone from github is reading this - please consider first-class Mercurial support. It would almost definitely be easier for you to do this than for bitbucket to make up the gap.
(I know lots of people prefer git, but Github already has that market pretty cornered. There is an opportunity among those who prefer hg.)
(is that an ad? or some kind of 'social feature'?? Something incredibly ironic about this article if the latter)
It's the most popular language in the world for a reason. There are lots of great things about Java, some a direct result of it's popularity: Fantastic tools, a tonne of very mature and reliable open source libraries, great performance in most situations, and last but not least: A tonne of jobs.
By no means is Java dying. A lot of sexy new technologies are rooted in Java. Here's 3 popular among the HNers: Clojure, Cassandra, and JRuby. You wanna hack on any of these, you better know Java.
Java is far from perfect but it's also very far from horrible. It is most definitely useful. Take the course. You'll learn a lot.
More to the topic: It's much more likely that the motivations are financial.
edit: (unrelated) Have you brought this to the attention of 37signals? You should send them this story, I feel like they may want to keep unsavoury characters like this away from their board in the future.
I am currently working on a drag-and-drop uploading tool, and would really like to use html5 to do it. The new interfaces involved are the drag and drop (http://www.whatwg.org/specs/web-apps/current-work/multipage/...) and File (http://www.w3.org/TR/file-upload/) APIs. Unfortunately, everyone except for Firefox have been slow in implementing the File interface, leaving me with a situation where the only shipping browser where standards-based code runs is Firefox 3.6 (fwiw, it works in Webkit nightly and Chrome 6 dev). In shipping webkit (safari 5, chrome 5), File is implemented (which gives meta data about a native file) but not FileReader (which gives the actual data) (btw if someone knows of a non-standard way to get the data from the File object in shipping webkit please let me know, i just want this to work. FF had a non-standard getAsBinary() method on the File object before FileReader was implemented, for example).
Opera doesn't even have File implemented.
Again, FF is the only shipping browser that native os-to-webapp uploading drags work in a standards compliant way. Give them some credit.
Apple's pretty good at taking old good ideas that never took off because of poor execution and doing them right.