jjames's comments

I believe this refers to the Entity Component System.

"To the members of the Budget Council" --Dijkstra

https://www.cs.utexas.edu/users/EWD/transcriptions/OtherDocs...

yes, please. Much appreciated. Address in about.

I'd personally suggest looking at Python as a first language. Others here will suggest Ruby (esp with the mention of LISP) or Perl. Of course there are many others to suggest but that trio has a good enough balance of power, complexity and understandability to get you up and running without throwing up too many barriers.

You can't go wrong with really any language to get your feet wet. It's really a matter of finding documentation, books and a community you resonate with to keep your attention and get you excited about all of the possibilities.

Same here. Like many things in python, the unconventional hack is made just inconvenient enough to persuade most people to rethink their strategy.

You are right. Publisher and "The company behind" do not necessarily equal "maker of". Perhaps I should have instead posted the Reuters article titled "Electronic Arts to buy Chillingo for $20 mln".

http://www.reuters.com/article/idCNN2022096920101020?rpc=44

I read the "early" as pre-release and thought someone was trying to re-implement clojure in CL. I'm relieved.

What's the backstory on this, fogus? I've not read about a CL Clojure pre-dating the JVM implementation. Was this just a prototype or was there a plan to platform on CL at some point?

It really depends on what type of vim user you are. I used vi/m for 10 years before starting with emacs. Emacs works better for me. I know people for whom vim works better for them. It would be a shame not to find out for yourself.

It may not be interesting tech news but it is tech news relevant to the interests of those paying attention to the activities of startups.

I have to question your reasons for making a stand just now on the re-implementation of standard website features throughout the proliferation of diverse web publishing systems. It's been quite a ride since the first CMSs decades ago but the scenery has been much the same, you must admit.

You can claim that the release of standard CMS features by one company or another is not newsworthy (which is why we have the little arrow over there by the link) but I'd then submit that most developments by technology companies (large and small) are less then entirely novel. If those developments are deemed not-news-worthy, HN will have even less to do with the activities of entrepreneurial operations.

I believe he was referring to those who built and those who currently maintain Wikipedia. It is likely that those individuals set out not motivated by money but for some ideology, a "dent" in the universe.

I would assume the NSA releases their Linux kernel because the license compels them to. I could be wrong. Maybe it is a trap.

Most open source and free culture advocates are _self_ motivated by a drive to give their stuff away to other people. The entire talk is about self interest, completely the other side of the planet from altruism. It sounds like you actually agree with what he is saying but are entangling entangling money and self-interest in precisely the common way this talk seeks to dismiss.

I don't believe the man in this story had any idea what he wanted apart from escape, escape from her, his kids, his job, perhaps his mortality. He could be described as a victim of his emotions. I think she was right to identify this as negative, as hopelessness and directionless self destruction. That doesn't make it any less real for him or any less painful for everyone involved but it does make it possible to see her as a patient and dedicated support. We all go through trials. Sometimes those trials work to destroy our lives, relationships and the people we love. We would all be lucky to have someone stick around while we take them for grant and self-immolate for 6 months.

Regardless, he always had the option to leave. If he had a better plan, he'd have rolled with it. If he was self-actualizing greater destiny, I would agree with you but this guy sounds like he was under water.

It is possible that the rhetoric is part of the brand.

They won't have to learn C or much of memory management or anything about pointers because of that other Smalltalk influenced language full of fancy abstractions.

That dragging things around in Interface Builder and copy/pasting TableCell code off the web is more hardcore than a typical Ruby on Rails website is unfortunately not a realistic argument. That's why we have so many "haha, I farted" type apps.

Loved flipping through all the memories. Not sure how I'll interact with it now that I've put most of my history in. I've sent it to all my co-workers and I can definitely see it making for good conversation for the next few days. I wonder what jtauber has planned for future interactions.

The Full Disclojure videos have helped me understand some of the features new to clojure in 1.1.

http://www.vimeo.com/channels/fulldisclojure

I found some context for this after searching around a bit.

A potential new Perl programmer goes to #perl and is told that Perl 6 isn't Perl then goes to #perl6 and is told Perl 6 is the new Perl but if they want to Get Things Done they should use old Perl.

http://use.perl.org/~masak/journal/39861

The F--- Perl 6 post is more directed at a Perl 5 audience. This companion blog post for the Perl 6 audience. These are both bridge building attempts.

http://use.perl.org/~masak/journal/39912

That's interesting. It actually illustrates the sometimes massive difference between "configurable" and "extensible".

"may be useful for learning the basis of the Lisp language".

* "checkout" is a destructive command

Most VCSs have a destructive command. If one doesn't expect the destruction from the command, they will no doubt be perturbed.

* You can’t merge upstream changes into your local, uncommitted modifications

Commit.

* Git’s merge conflict resolution workflow is unintuitive

Subjective but I'm curious which VCS has an intuitive merge conflict resolution workflow. I assume this means that without previous experience with the VCS a developer can (immediately?) intuit the workflow.

* Interface for working with the index almost universally confusing

Three switches for a single command. If you want to operate in a business as usual DWIM manner you can just remember --hard.

All that said, I do believe git reuses some commands in a semantically elastic way, sometimes to the confusion of new users.