HN user

johnwalker

304 karma
Posts4
Comments32
View on HN

We need both! In the meantime, I like the idea of ending subsidies for fossil fuels since it incentivizes building a moonshot technology that everyone can adopt, and curbing our reliance on them so that we have time to build better technology.

I can definitely understand why a team could dissolve. But there are really only upsides for employees to understand why they're being paid X and to be able to model their behavior after the person that gets paid Y.

A friend told me about their big company's interview process for interns from Ivy Leagues, which was getting flown out to a party and then getting an internship. The candidates weren't asked any technical questions, since they were assumed to be smart enough to learn how to code in bootcamp. It made me feel confused about myself for a while, since I didn't have a job or much experience and it was hard enough getting a phone screen.

Did you come up with a solution for recompiling the clojurescript files only when cljs and cljc files were changed? The watch task fires whenever a file in the resources or src directories changes.

Beyond Light Table 12 years ago

I retract the statement that Rich uses Cursive. I misinterpreted a tweet a while ago, and hope that I didn't cause too much harm. Instead, I'd like to say that Cursive is extremely nice and that you shouldn't let Emacs scare you away from Clojure.

The S in Rest 12 years ago

Coming up with names for groups of data that you want to be atomic isn't that useful, though.

Goodbye Gmail 12 years ago

I'm also interested in any answers to this. I haven't come across anything as easy and usable as Thunderbird.

kmail for KDE seems OK. It's not my favorite, but it feels lighter to me.

Considering using Emacs.

Although this project renames functions, that isn't all that it does. Accomodating new users is very necessary for adoption of any language, library or project, especially by having reasonable defaults. All working professional programmers were once beginners. Of course, it's another argument that this project succeeds at any of these.

Yep! It's necessary to modify slime (or light table? I've been interested in making a CL plugin for it) to take advantage of this syntax, but the absense of sane reader macros in the spec has always driven me nuts.

The functions are basically inconsistent in both name and argument order. I think that's one of the problems they're working on correcting (a generic elt/getf), and more obvious ways of creating and using non-list data structures.

I'll have to defer to this paper. It mentions that the core persistent vectors are cache-friendly, but I would suspect that the llvm will always be an upper-bound for the jvm.

infoscience.epfl.ch/record/169879/files/RMTrees.pdf‎

I'm very interested in better answers to this question, though.

Some time ago, hypirion wrote about how persistent vectors are implemented in Clojure.

http://hypirion.com/musings/understanding-persistent-vector-...

There are actually several different implementations of the core data structures:

https://github.com/clojure/data.finger-tree

https://github.com/clojure/core.rrb-vector

Of course, the short answer is that Clojure isn't using classic linked lists, and that regular Java collections can be used and created pretty easily. [0] [1]

[0] https://stackoverflow.com/questions/4313505/converting-cloju...

[1] http://blog.raek.se/2011/01/24/executors-in-clojure/

I actually agree with this article. It's a lot more trouble to wait for the web to standardize than it is to support a couple different versions of an app, which usually has potential to offer a better user experience anyway. (More developer jobs, too!) This really shouldn't be troubling to anyone.