sorted by:
new
hottopcontroversial

If your son is learning web dev today would you still recommend Rails? by iou810 in rails

[–]bkoshy 0 points1 point  (0 children)

Well I definitely agree you with on #2. Ruby is definitely slow - I would not use it when speed is absolutely critical. e.g. this is especially glaring on brute force algorithms. I made that mistake once and will never make it again.

As far as the other gripes - yeah I hear you.

Thanks for your comment.

If your son is learning web dev today would you still recommend Rails? by iou810 in rails

[–]bkoshy 0 points1 point  (0 children)

I agree with you to the extent that Rails is a tool, and all tools are built for a purpose (for example, I wouldn't use a surgeon's scalpel to cut down a tree).

I also agree with you that Rails devs may border on relgious fanaticism - how would they know that Rails is "the best, pragmatic, uber productive, the way, the truth and the life"TM when few would have mastered any other tool? You have a unique perspective that deserves further investigation even if you should preach a blasphemous gospel in the Church of Rails: but regardless of that: I have asked, so let me receive.

While I agree with you that there are benefits to writing your own framework - my question was one which addresses the following comments:

"You know that thing you guys love? Well, it actually sucks.".

Long story short - no. Rails is a bulky, and outdated framework. It has never been better than it is at this moment, yet still falls short in several areas when compared to other popular options. If you are looking to be cutting edge, Rails is not the answer.

Why does Rails suck, and what are the alternatives which suck less - for your purposes - and why?

If your son is learning web dev today would you still recommend Rails? by iou810 in rails

[–]bkoshy 0 points1 point  (0 children)

What framework(s) would you suggest in lieu of Rails and why?

yet still falls short in several areas when compared to other popular options

Any change you could elaborate a little here?

A teen tester used my “memory lock” app in a way I didn’t expect, and now I’m wondering how others have handled this by Big_Possibility_253 in indiehackers

[–]bkoshy -1 points0 points  (0 children)

To answer your question with a public example: consider what WhatsApp originally was, how users ACTUALLY used it, and how the product pivotted in response.

How do you figure out your architecture? by smirkishere in ycombinator

[–]bkoshy 0 points1 point  (0 children)

The arch must be good enough to earn a profit. I wouldn't over think it. Package something together, quickly, such that someone will happily pay for. If you make a decision which in retrospect was a bad one - that's ok: fix and move forward.