Thanks for the link! I hadn't seen that one before. While I think I'm already thinking in expressions, Erlang's placement of punctuation never really made a lot of sense to me. Maybe that explanation will finally clear up my confusion.
So far, I agree with the note about 0/1-based indexing. It's just not used a lot. However, I find it pretty calming that indexes will work the way I expect them to, should I ever need to use them.
Now that I think about it, these two points (syntax and indexes) are somewhat petty things to point out about the Erlang : Elixir relationship, and I feel a bit bad for repeating them in the blog post. Things like protocols are way more interesting (and hopefully, are what drives you to try out Elixir). (-:
Thanks! Please let me know if you have any questions about it or run into problems. If you write a filter set and you can share the script that generated it for the examples, that would be pretty super, too (-:
You can't see a date on it, but that page is now 10 years old (I wrote my entry when I was 20 years old, 30 now). Still loving Common Lisp (and clojure and Elixir and all the many other cool things that came out since then), so no harm done; just... beware (-:
Did you consider SSL client auth? I'm not sure you will get all the properties you want out of it (ease of logging out, especially); but having used it a bit now, it is a really pretty nice way to do SSO. Plus, it forces you to keep your internal services on HTTPS which is just a good idea anyway (-:
Congratulations - that is a seriously useful utility. At first I thought that holding down the mouse button wasn't that bad - but your browser tab demo absolutely convinced me (-:
Thanks for making this - anything that improves my Mac's drag&drop and copy&paste functionality is worth at least $5.
That's pretty amazing. I had the privilege of demoing repraps to a Vienna UT researcher a while ago, and he reciprocated by giving me and my friends a tour of the 3D printers at their institute. The 2-photon printing facility was already in place (and oh my is it impressive), but it hadn't made a lot of interesting stuff at the time - I think they were focusing on fabbing organic molecules at the time. I'm pretty sure it wasn't as fast as this - 4 minutes for a sculpture of that size, at that level of detail is pretty great.
That was about 2 years ago now. Very glad to see they made such great progress in the meantime (-:
I love the postrock/space-y sound it makes when you pause. Rotating around the frozen cat then feels like the space scenes in a bizarre rendition of "2001".
Hah, This is the first time I hears about Foreman (been away from Rails for 1.5 years), but I'm so glad to see process management for development has gotten fixed! In the past, I even wrote an OS X application for managing the running processes, watching stdout, etc. - but as homemade things go, it never was 100% perfect, kept dropping state, forgot how to scroll nicely (one of the problems you face there is that you end up reimplementing a tty).
Foreman seems quite smart, as complete as (if not better than) my old app - and it's configurable, too! Goodbye Soupsie.app, hello foreman (-:
I can't help feeling that he's barking up the wrong tree: If people criticize your new language for imaginary shortcomings, then maybe the available documentation isn't communicating its purpose/idioms/concepts clearly enough.
Not saying that a new language needs to launch with impeccable documentation and a crystal-clear understanding of what problem it tries to solve at all, but those "I can't imagine ..." criticisms can also be a (not-so-greatly worded) way of saying "I don't understand" - an opportunity to learn how to talk about the language better.
I'm sure a lot of people here have already learned this lesson the hard way, but: If you're blaming your product's users for not reading the docs (or for not trying it out), you're missing out on a great opportunity to improve it.
That's a pretty neat article! I'm glad you wrote that up! (Didn't even notice the EVAL in there, until I saw wes-exp's comment: You can avoid it (if you want, seeing as this is example code) by not using a SPECS variable, and putting all-specs in the loop directly.
I've known quite a few people who moved somewhere, made big commitments, only to find out that they just couldn't deal with the new place after a year.
IME, it's best to first live there (rent!) for a year, figure out if it's right for you still, and then go for it (-:
This announcement reminded me too of when Linus commented (upon the integration of virtual memory into Linux) that Linux had become the Emacs of terminal emulators.
Pretty funny that by integrating a Terminal emulator, Chrome becomes the Emacs of web browsers.