emiller829
Joined 16 years ago
Joined 16 years ago
Certainly can be worked around, but it's a little annoying.
"Do you need a way to divide your resources across multiple projects[...]"
It's a pet peeve of mine that so many processes and tools use the phrase "resource" in place of person. It may not have been what was meant by "resources" here, but that's how it reads.
How about:
"Do you need a way to manage multiple projects[...]"
or...
"Do you need a way to divide your time between multiple projects[...]"
Syntactically, it's a pleasure to use as a long-time Ruby guy, which I suppose is no surprise given José's presence in the Ruby community.
However, all of this aside, what makes me the most excited about Elixir is José, himself. It's been my experience that when a language/framework has a BDFL, something of that person gets infused into its community. Anyone who's interacted with José will tell you he's an incredibly friendly, humble, and downright thankful person.
Elixir is set up for success in so many ways, but the community aspect is the one we just can't afford to ignore.
I posted about it then (http://erniemiller.org/2013/06/19/my-happiness-formula-me-js..., but the thought at the time had been that it would be nice if prospective employees published something along the lines of things that contributed to their contentment with work.
This was eventually intended to be presented sans ratings in a little browser plugin, for recruiters and the like to score themselves honestly against the criteria, and a little bit of math would yield a compatibility rating on a click.
It wouldn't take long until such a thing evolved into a more full-featured resume such as this. I like the idea.
It still feels a bit DSL-centric from the examples I've seen thus far, and haven't dug into things to see what the generated Ruby looks like -- but if it's anything close to simple, this is something that has a chance to become an important part of the Ruby ecosystem.
If nothing else, it's great to see things like this because they provide concrete example code for discussions that (IMHO) need to happen.