7

Didn't realise (ruby) sass was becoming deprecated :(

Comments
  • 1
    Yup, its a native c module now.
  • 0
    @nblackburn and Dart Sass!
  • 1
    @itsdaniel0 ...It's a native c module now.
  • 1
    Thank god there are rubyists here too. I was starting to give up the hope of seeing a meaningful rant.
  • 0
    @fuckinghipsters Ruby is great just not for stuff that needs to perform well.
  • 1
    @nblackburn Ruby 3 will be 3x fast
  • 0
    @jcserracampos Which is good but proportionate to other languages doesn't equate to much.
  • 0
    @nblackburn ever heard of the concept of premature optimization? ;) I've seen so many upstarts run out of money to get their MVP just because of the statement "Ruby is slow" and jumped onto the Java/c#/node.js train.

    So I'd like to turn your argument around, "Ruby is slow if you're using it for the wrong purpose"
  • 0
    @fuckinghipsters I have but have to respectively disagree because it's slower regardless of what you use it for.

    If you are not worried about performance and want a nice language then it's a great fit.
  • 0
    @nblackburn duly noted but I still disagree, regardless of the speed of your program you're going to have to rely on cache for heavy loaded systems, last time I checked the speed of reading a key in redis is the same regardless what language you used to generate it. So sure if you have an infinite budget you can base your choices on factors like speed of a language, but usually the client cares more about the speed of achieving results, e.g. development speed, I'd dare say Ruby wins that race tenfold.
    Sure next goal might be too optimise speed in order to increase profits, then of course you should start porting chunks of code to some thing else, but that's still step 2 in my book.

    Just look at all the big successful companies who sell you the idea of a faster language,(linked in, Twitter, github) they all started with rails and changed technology _after_ they matured.
  • 0
    @fuckinghipsters @nblackburn This wasn't the sass I was referring too 😉
  • 1
    @fuckinghipsters Ruby is a beautiful language I agree and is largely the reason it gets used but that beauty comes at the cost of speed.

    Sure you get things done quick but ultimately fall short when our hit that threshold rather than keep going. It's not about speed of development it's about choosing the right tool for the job (not necessarily what gets you there quickest).

    Going back to the original before we got de-railed (pun intended) Ruby is not a good choice for Sass.
  • 0
    @fuckinghipsters I know we disagree but that is because I think about foundation from the get go instead of an afterthought.
  • 1
    @nblackburn I understand you, and I stress that there will be no room for afterthought if to much focus is poured into the foundation. Fail cheap, minimize risk.

    But you sound like a sensible chap so let's not derail this thread and continue this discussion another time/another place. Cheers
  • 0
    @fuckinghipsters I agree, there is a balance to everything and we both make valid points.
Add Comment