spacesword's comments

spacesword | 7 years ago | on: App Analysis: Air Canada

I think you should have a discussion section where you talk about potential implications (possible password leaks via S3).

spacesword | 7 years ago | on: Rails, still?

“And Phoenix would be the Rails to Erlang's Ruby (Elixir). The learning curve is steep, you will need to learn OTP. Which is probably why adoption lags."

The author has no idea what they are talking when it comes to the alternatives.

I was making simple CRUD apps in Phoenix (the types of apps I would normally use rails for) for a year before I even looked at OTP. You can become productive in elixir and Phoenix very quickly especially if you come from a ruby/rails background.

I recall a blog post by dockyard where they said they had new hires making commits within the first week.

spacesword | 8 years ago | on: Exploring ReasonML and functional programming

Agreed, I love Elm but the lack of documentation was a pretty big hurdle for me. Especially because I came from using elixir/phoenix on the backend which I found had excellent guides and docs (for language, framework and most packages).

spacesword | 8 years ago | on: MacBook Pro? No

I personally love the keyboard. Also, I don’t mind it being a little thicker but I love the current weight.

spacesword | 9 years ago | on: Rails 5.0.0.rc1

Phoenix and Elixir are trucking along nicely. Elixir 1.3 is on release candidate, as is Ecto 2.0 and Phoenix 1.2.

The big feature of Phoenix 1.2 is channel presence: https://dockyard.com/blog/2016/03/25/what-makes-phoenix-pres...

Whats coming in elixir 1.3: http://tuvistavie.com/2016/elixir-1-3/

Ecto 2.0: http://blog.plataformatec.com.br/2016/02/ecto-2-0-0-beta-0-i...

Other than that the community is growing at a healthy pace. Hex packages have gone from 1000 to over 2000 in the last 6 months.

spacesword | 11 years ago | on: X to close

They mention X and O on the PS controller but usually in games O is for no and X is for yes. Completely opposite of the batsu/maru, incorrent/correct they were discussing.
page 1