applications made with node js (or javascript) are like pyramids made of playing cards. one mistake can ruin everything. the problem is that finding that mistake can lead you to an eternity. Making an application with javascripts is like installing electricity in a building. Javascript is for technicians. Making an application with ruby is like working on a regular electronic circuit. ruby is for engineers.
Ok can you explain further? What does ruby excel at that JavaScript struggle with? And can you use ruby on both the front end and back end without using JavaScript?
Nodejs is a platform - Ruby on Rails is a framework. This is one of the most misleading comparisons I have seen. Why not compare Photoshop to OpenGL in your next video?
This is a good point about Node.js and Ruby on Rails. Comparing them is not easy, however, it does make sense. We often choose topics based on most typical questions we receive from our clients. And this one apparently needs to be discussed and clarified.
Jelvix Ok. If the client asks which one is better - Ruby on Rails or NodeJS - the answer should be: “Ruby on Rails is an web application framework and NodeJS is a JavaScript runtime.” If the client asks that question it shows that they should be kept as far away as possible from any tech-related choices and rely on the developers to choose the best solution based on their knowledge. The less they know, the happier they will be.
@@johanandre5338 and how would a developer choose a particular technology on the basis of clients request? For example if I want to improve my traveling agency and I ask for a website which technology will you choose and how?
You know damn well what they mean. Node.js users may apply express.js and other frameworks for handling common tasks in web apps. People can code up their own frameworks for the sort of web apps they provide. The comparison of Rails vs Node.js is not being based on _how much coding_ you have to do with them: it's being done on the basis of (1) how performant each tech is for a given type of web app; (2) how long it takes to acquire the skills; (3) how quickly a minimum viable product (MVP) can be coded up using each tech; (4) how scalable and/or adaptable the final app will be and so on.
The guy narrating doesn't even know how to pronounce "asynchronous". Point of correction at 5:39 Ruby language cannot be used for frontend scripting work. Only JavaScript and things that compile to JS like CoffeeScript and TypeScript will substitute. RoR has one or two async APIs that give it some help when working with many database intensive code. Node.js allows one to create separate threads for CPU intensive tasks that would hold up execution of database/file/network calls. So today even the traditional weaknesses of RoR and Node.js can be remedied to some degree. Coder familiarity and proficiency with these frameworks is important to make the best decision here.
I agree. You can build really good applications with both, but should try to get proficient in one or the other. If you are proficient in Rails, then no big reason to switch to Node.
We have a great review of PHP frameworks - ua-cam.com/video/-XIO2Ve0iCE/v-deo.html As for language comparisons, we'll definitely include PHP in the future.
I worked with php for 15 years, it is a very boring language. you work without pleasure, it makes you feel more like a construction worker than a programmer. most of the time you have to hold your right hand with your left ear!!! while solving problems. in languages like ruby and python you don't face such problems because it takes seconds to write another virtual hand to hold your right ear. the only problem is that with php you can write hundreds of lines of code for everything, whereas with languages like python and ruby you have to be very clever and solve it with minimum lines of code. so, php doesn't require intelligence... you can hold your right hand with your left ear :D but you have to write clever code because others know that would be retarded behavior. that's where the joy and ego of making software starts.
Ruby on Rails vs Node.js - which would you choose for your project? Drop a comment and let us know... 🦾
Ruby and ROR is the best and lovely ♥
applications made with node js (or javascript) are like pyramids made of playing cards. one mistake can ruin everything. the problem is that finding that mistake can lead you to an eternity.
Making an application with javascripts is like installing electricity in a building. Javascript is for technicians.
Making an application with ruby is like working on a regular electronic circuit. ruby is for engineers.
Ok can you explain further? What does ruby excel at that JavaScript struggle with? And can you use ruby on both the front end and back end without using JavaScript?
@@OfoeNelson I would also like to know
This is very telling. Thanks for this insight!
Then does TS fill up that disadvantage?
love nodejs...its really amazing
Nodejs is a platform - Ruby on Rails is a framework. This is one of the most misleading comparisons I have seen.
Why not compare Photoshop to OpenGL in your next video?
This is a good point about Node.js and Ruby on Rails. Comparing them is not easy, however, it does make sense. We often choose topics based on most typical questions we receive from our clients. And this one apparently needs to be discussed and clarified.
Jelvix Ok. If the client asks which one is better - Ruby on Rails or NodeJS - the answer should be: “Ruby on Rails is an web application framework and NodeJS is a JavaScript runtime.”
If the client asks that question it shows that they should be kept as far away as possible from any tech-related choices and rely on the developers to choose the best solution based on their knowledge.
The less they know, the happier they will be.
@@johanandre5338 and how would a developer choose a particular technology on the basis of clients request? For example if I want to improve my traveling agency and I ask for a website which technology will you choose and how?
You know damn well what they mean.
Node.js users may apply express.js and other frameworks for handling common tasks in web apps. People can code up their own frameworks for the sort of web apps they provide.
The comparison of Rails vs Node.js is not being based on _how much coding_ you have to do with them: it's being done on the basis of (1) how performant each tech is for a given type of web app; (2) how long it takes to acquire the skills; (3) how quickly a minimum viable product (MVP) can be coded up using each tech; (4) how scalable and/or adaptable the final app will be and so on.
Does Jelvix develops on RoR or node?
We use both of them :)
The guy narrating doesn't even know how to pronounce "asynchronous".
Point of correction at 5:39 Ruby language cannot be used for frontend scripting work. Only JavaScript and things that compile to JS like CoffeeScript and TypeScript will substitute.
RoR has one or two async APIs that give it some help when working with many database intensive code.
Node.js allows one to create separate threads for CPU intensive tasks that would hold up execution of database/file/network calls. So today even the traditional weaknesses of RoR and Node.js can be remedied to some degree.
Coder familiarity and proficiency with these frameworks is important to make the best decision here.
They probably just hired a voice actor
I agree. You can build really good applications with both, but should try to get proficient in one or the other. If you are proficient in Rails, then no big reason to switch to Node.
What about php?
We have a great review of PHP frameworks - ua-cam.com/video/-XIO2Ve0iCE/v-deo.html
As for language comparisons, we'll definitely include PHP in the future.
I worked with php for 15 years, it is a very boring language. you work without pleasure, it makes you feel more like a construction worker than a programmer.
most of the time you have to hold your right hand with your left ear!!! while solving problems. in languages like ruby and python you don't face such problems because it takes seconds to write another virtual hand to hold your right ear.
the only problem is that with php you can write hundreds of lines of code for everything, whereas with languages like python and ruby you have to be very clever and solve it with minimum lines of code. so, php doesn't require intelligence... you can hold your right hand with your left ear :D but you have to write clever code because others know that would be retarded behavior. that's where the joy and ego of making software starts.
Thanks for making this video!
To be fair I do not think anyone should pick NodeJS or Ruby on Rails if "speed" is one of you main concerns
What's for speed then?
Development speed or runtime speed or what?
Hulu now use NextJS, AirBnB now migrate from Ruby and Twitch soon
Fullstack or frontend only?
Fake info
NextJS is front end only. You can run Rails on the back, and NextJS on the front
@@andrewng9950 Nextjs is not a frontend only .It's a full stack framework .It's is both backend and frontend .It's API folder is the backend
great video as always
a-sin-crow-nus
its incredibly distracting watching people fake work. they barely move their fingers when they fake type