arms

I've been using LightTable, but plan on switching to Emacs soon. The only reason I haven't done so already is learning Clojure is challenging enough without also coming to grips with a new editor :)

I just finished a long coding session (it's 3AM here), and was about to go to sleep before I saw this. Looks like I won't be going to bed for awhile longer... :)

I agree that most of the authentication belongs on the backend, but there's still the question of how best to handle/recognize authenticated users and authorized requests on the frontend. Should I be using JSON web tokens, or cookies? What's the best way to protect routes for users with varying degrees of access? If anything, I'd like to see pros and cons of each strategy, assuming a backend implementation is already in place.

I would love to see a section on authentication and authorization best practices. From my research, it doesn't seem like this is covered as well as it should be in various Angular resources. This isn't a knock against the OP - just something I'd like to see.

So I'm about half way through it now. I'm really impressed with how much information it's conveying in a succinct form. I'm going through Clojure for the Brave and True, and think this supplements it nicely.

There are a few typos, but the most glaring one was the incomplete python code underneath the "Code Structure" heading:

l = [1, 2, 3, 4, 5]

for i in l i = i*i

for i in l if (i mod 2 == 0)

print l

I assume the author wanted to show how the list was mutated. And those conditionals need trailing colons :)

Good to know! I started with emacs, but decided to use Light Table for now. Nothing against emacs, but I don't want to make things harder by learning a new language and a new editor at the same time. Aside from Light Table (and presumably Leiningen) do you have any other tooling recommendations?

I'm currently learning Clojure. For all the "aha!" moments, there are plenty of "WTFs?", too. Not that it's a fault of the language, it's just that it requires a different way of looking at things. I've only skimmed this article, but look forward to reading it in depth later. Thanks!

I'd be interested if anyone has some similar pieces to share.

None taken. I got the impression from comments on HN and elsewhere. To be fair, those comments might've been from Node advocates, so they could've been skewed. Is one of the (main) problems that the registry is often unavailable?

Why do you think NPM is "the most unreliable package manager"? I don't use Node, but I thought the general consensus was that it's one of the best out there. I'm genuinely curious.

Wow - perfect timing. My copy of Clojure Programming should be delivered tomorrow, and this looks like a nice way to complement my learning. Plus, I love Tetris :)

Good for Adam. These patent trolls are reprehensible. It's hilarious that they want to pull out now that they stand a chance of losing.

I definitely see how this would be useful for automated tasks. I have some python scripts doing a fair bit of automated data munging that would probably benefit from being written in Erlang/Elixir.

Slight tangent - people often say learning Haskell is worth it for the eye opening experience it provides, regardless of whether you get to use it day-to-day. Would you say the same of Erlang and Elixir?

I love the concept of Elixir, but is it used out in the wild much? A language's popularity, or lack thereof, has little influence on whether I'll learn it or not, but I'm always curious about this.

"you have to be even more careful that you're not just copying patterns from one app to another" Absolutely. I hope my post didn't convey the opposite. The way I see it is that the designers of the language know more than the (new) developers using it, so it pays to rewrite existing applications in the way in which the language designers intended.

To the author's points of committing and staying idiomatic, I'd recommend rewriting an existing application in your new language of choice. It doesn't need to be a 1:1 port, but by porting over the basic/foundational pieces, you really learn a lot about a new language and its idioms. For me, it's a much more concrete way of learning a new language.

I'm curious why you think Golang doesn't support concurrency properly.

Very cool! I think detailed examples like this are much more conducive to getting a feel for a language when you're just starting out than the typical "sift through the official docs then build a Hello World example." I'm going to set aside some time to work through this (and then go through the official docs.)

Kudos for the Simpson's references; that's one of my favorite episodes :) I look forward to more of these.

I was tasked with using ExtJS for a large project, without having prior experience with it. It was both a dream and a nightmare for me (OK, that's a bit dramatic, but it was a mixed bag.)

In the end, I was able to do what I needed to, albeit not on mobile due to performance issues, but I wouldn't choose to use it again if it was up to me. It just felt too bloated, and I'd much rather work with various smaller libraries, and fill in the gaps as needed.

I'd be very interested to know what flexibility you think javascript provides that python doesn't. I have nothing against JS (I usually enjoy writing JS), but IMO it doesn't begin to offer anywhere near the functionality or beauty that python does.

I'm not interested in language wars, just genuinely curious about your statement.

Such as?

This is one of the better Haskell videos I've seen - it's nice to see use cases in a high speed environment like the NYT.

Thank you, I found this very helpful. I'm being selfish, but I'd love some more examples like this where you compare the basics in Haskell against more mainstream, imperative languages - it makes it easier to digest.

It's common to use SQLAlchemy with Flask, so the answer depends on how comfortable you are with that ORM.

That being said, you should absolutely at least learn the basics of working directly with databases. ORMs are a leaky abstraction, and you will run into situations where it's easier to drop into raw SQL to get the job done. Think of it like this: using GPS while driving is fine 95% of the time, but when it malfunctions or breaks, you're screwed unless you know how to read a map or ask for directions ;)

I would much sooner introduce someone to Flask than I would to PHP and Laravel (which is, IMO, the best current PHP framework.) Flask has an easier learning curve than Django, and is able to handle small to large applications. Plus, Python is simply a better language than PHP.

This is coming from someone who writes a lot of PHP.

Very cool! I always like seeing when something is built using a typically non-traditional language for the environment. I downloaded the game to see how well it performed, and I gotta say, it's a lot of fun. Great job!

I really like this suggestion. I'm in the process of learning Haskell now, and plan on using this as a practical learning exercise.

Out of curiosity, how difficult did you find this to complete?

405 days ago... ;)

As someone who was obsessed with Lemmings back in the day, this is the best thing I've seen on HN in weeks :) It brings back fond memories.

As someone who's interested in Haskell and missed this the first time around, I'm glad it's back.

I know I would be very interested in this.