djfrodo's recent activity

  1. Comment on Web developers - What is your stack? in ~comp

    djfrodo
    Link Parent
    The "magic" you're referring to is Rails, not Ruby. After a while that "magic" fades and you'll know what's actually going on. I'd learn Ruby first. Many of the coding academies that cranked out...

    but the "magic" has always intimidated me

    The "magic" you're referring to is Rails, not Ruby. After a while that "magic" fades and you'll know what's actually going on. I'd learn Ruby first. Many of the coding academies that cranked out Rails developers a few years ago cranked out Rails developers that didn't know where Ruby ended and Rails began.

    2 votes

  2. Comment on Recommended two-player board games under sixty minutes in ~games.tabletop

    djfrodo
    Link
    Backgammon or Pente. Both are great - Pente takes about 10 minutes max, while Backgammon will take 15-20.

    Backgammon or Pente. Both are great - Pente takes about 10 minutes max, while Backgammon will take 15-20.

  3. Comment on Web developers - What is your stack? in ~comp

    djfrodo
    Link Parent
    On the ruby/rails vs python/django question...I think python will win due to its adoption in universities. Ruby/rails was/is loved by startups who want to get to market as fast as possible. The...

    On the ruby/rails vs python/django question...I think python will win due to its adoption in universities. Ruby/rails was/is loved by startups who want to get to market as fast as possible.

    The great and terrible thing about rails is all of the magic/behind the scenes stuff it can do. Basically you get so much power "out of the box" that you feel as though you can do anything without knowing how it works. There are also usually 3 different ways to do the same thing.

    Django is the opposite. You need to know exactly what you're doing. There's one way to do it, that's it.

    When things go wrong in rails...good luck. When thing go wrong in Django you can probably figure out what's happening.

    With that said, ruby is much more fun to write.

    3 votes

  4. Comment on Web developers - What is your stack? in ~comp

    djfrodo
    Link
    For front end stuff on a non complex site I can't see how meghan's choice isn't the best - just HTML, SCSS (or sass), and Vanilla JS. I actually still use JQuery with simple css, and to be honest...

    For front end stuff on a non complex site I can't see how meghan's choice isn't the best - just HTML, SCSS (or sass), and Vanilla JS.

    I actually still use JQuery with simple css, and to be honest it's great.

    For the back end, weirdly, I'd probably go with Rails. It's got all the ORM and migration stuff you need and the language is fun as hell to write.

    I learned how to program using PHP, and it's great, but I certainly wouldn't want to go back to it.

    I'd stay away from Java unless you're really going to get complex or need high scale.

    Personally if I were starting and could give myself advice I would say "stay the fuck away from node" - there are too many frameworks, dependencies, build chains, package managers, etc.

    But it's what the kids like today.

    Do what tildes.net did - skip the "cool" new frameworks and go for a simple MVC server side framework (Django, Rails, Laravel, etc) with a lot of javascript for the UI. Keep the database stuff as simple as possible.

    Hope that helps.

    p.s. I made a version of reddit/tildes in rails: headcycle.com with basically the above advice.

    3 votes