Bro your point make sense eh but we only disagreed with you calling Ruby old school, no one is trying to undermine your opinion about programming languages and feel like we’ve gone from A to Zbbdhudw but yh @M.O.O you clearly know your shit
First github,gitlab, airbnb, shopify and a host of other web apps uses rails extensively and it servers more than a million users and I don’t see no performance issues.
For a serious web dev company. I think the knowledge of php and ruby are just enough. It now depends on the developer the way he decides to optimize his code and the tools he uses for that. besides PHP 7 is significantly faster than it’s predecessors so you might want to benchmark it again against the previous result of other languages.
Agreed you might run into issues pretty fast if you don’t develop your code knowing following the specified guidelines for which-ever paradigm you are following.
However speed is not the only thing you consider when you are developing apps, other things comes into play like productivity. Ruby has been known as programmers joy for a long time now because of the ease with which the developer can get up and running in no time especially with rails. It allows you to build up a spotless and battle tested MVP in no time. much like with python or any other MVC for that matter.
Also I can decide to use SLIM/Silex/Rails to serve an api to whichever js front-end framework am willing to use. just like node
Ruby is also a handy language outside the web domain. heard of metasploits payload?
Yes javascript is event based that runs on a single thread. This means that once you are running a cpu intensive task your app get significantly slower. as it’s wait for the execution of a stack frame before running the next. even though it would like you to call it’s callback as being async. it’s still a sync process I think this was the reason why go-lang comes in as an option. again here fast is relative.
Right about now the only place C# is that useful is using it with any .Net technologies.(I will pick it over Java any day though). Using Xamarin for seirous IOS apps is a pain. You still have to go to xcode to build your UI with .xlb and know the native api well enough to be able to work with it. This is like a 2 step process that in my opinion building it with it’s seperate platform is better. For more universal feel I’ll rather go with react-native or nativescript
The fact that a tool has been around for a long time doesn’t mean it’s no longer in demand as long as it get the job done.
A sizeable number of developers still uses smalltalk
What am trying to say is as someone has said here before… “A tool is only as good as the man using it”. no need of calling it outdated or whatever…