News for hackers. Stuff that matters.
Re:Taking PHP Seriously by cakeinblue on Thursday October 13, 2016 @11:21PM (#12705945)
After I use both php and ruby for the same employer over more than a year. I would rather say Ruby is more like a garbage language -- 1) twist syntax to allow people write the same function into different ways is not a cool feature, it is disaster feature which causes more for a team to sync. 2) Duck typing is not interface, don't kidding yourself. they are totally two different thing. 3) ruby attract a lot of master level people try to make the community better, however, the whole community filled with mediocre developers who cannot even understand Rail != Ruby, and also they believe ActiveRecord is the only persistence layer they can use, and stop learning write native database query script.

Finally, good luck with writing a unit test against an API not created by you because, you have to go through deep into the source code just for figuring out what data structure return and give.

Re:Taking PHP Seriously by mastazi on Thursday October 13, 2016 @11:28PM (#12705961)
I have worked on both (among many other languages) and I too prefer PHP, but I guess my opinion on Ruby is unfairly distorted by Rails, which I dislike a lot. I hear that Sinatra is nice, for example.
Re:Taking PHP Seriously by mrmondo on Friday October 14, 2016 @06:19AM (#12707130)
Could not agree with your statement enough, just like Django really is a heavy burden for python when you could use flask etc... for most things.
Re:Taking PHP Seriously by mastazi on Monday October 17, 2016 @05:37PM (#12730021)
Yes, Django is in some ways similar to Rails but, at least, in Django I know how to exclude some parts of the framework (e.g. if I don't want to use Django forms, I'll just go on and use vanilla HTML forms, if I need raw SQL, I'll go for that rather than Django queries). I suspect that the same kind of thing is, at least to a certain degree, possible in Rails as well, however it seems harder to achieve because in Rails the components that make up the framework seem very tightly coupled. Obviously the opinion that I have formed may be distorted by the fact that I know Django/Python quite well, whereas I know little about Rails/Ruby.

EDIT: obviously I agree with you that, if you want more freedom and if you are not using many of the features that Django offers, then it would make more sense to use something light-weight like Flask, which is a very nice framework.

Re:Taking PHP Seriously by cakeinblue on Friday October 14, 2016 @10:13AM (#12708177)
Sinatra is good, in the last few months, I use grape a lot.
Re:Taking PHP Seriously by swat535 on Friday October 14, 2016 @11:34AM (#12708761)
I think you are expressing some legitimate opinions about what kind of languages you like. Ruby, like Perl, embraces more than one way to do it. Some people like that, others find it irritating. Neither reaction is wrong. I think the same thing goes for your reaction to Ruby's lack of explicit interfaces. I find it liberating, you may not.

However what I find incorrect is the claim that Ruby is a garbage language. Then again, maybe that is best treated as hyperbole, as an exaggerated expression of your dislike for it.

Re:Taking PHP Seriously by tluyben2 on Thursday October 13, 2016 @11:40PM (#12705994)
I agree with this as well, although this is about Rails. I still have a legacy project to maintain in Rails (a big project) but that is (hopefully) the last I see of it up close in my life time.
Re:Taking PHP Seriously by regularfry on Friday October 14, 2016 @05:13AM (#12706917)
> good luck with writing a unit test against an API not created by you

Is that a good idea?

Re:Taking PHP Seriously by nsomaru on Friday October 14, 2016 @08:05AM (#12707523)
why not, if the function is untested and plays an important role in your application?