Chasing Programming Fads
hyperdimensionalrabbit.blogspot.com
Chasing Programming Fads
1–6 of 6 posts
Re: Chasing Programming Fads
#2Ruby vs Javascript is a poor example, that comes across as somewhat scented with sour grapes.
The requirements of the work to be done keep changing as technology grows. Ruby is dying because, right now, it makes more sense to do the work on the front end.
Re: Chasing Programming Fads
#3Ruby vs Javascript is a poor example, that comes across as somewhat scented with sour grapes. The requirements of the work to be done keep changing as technology grows. Ruby is dying because, right now, it makes more sense to do the work on the front end.
You bring up an interesting point with the "front end" comment. Do you see the future of web development as being more heavily geared towards developing Single Page Applications (In JavaScript or otherwise)? From what little I know of it, it just seems to be the way to go, going forward. But would like to hear the opinion of experts.
Re: Chasing Programming Fads
#4Ruby vs Javascript is a poor example, that comes across as somewhat scented with sour grapes. The requirements of the work to be done keep changing as technology grows. Ruby is dying because, right now, it makes more sense to do the work on the front end.
You bring up an interesting point with the "front end" comment. Do you see the future of web development as being more heavily geared towards developing Single Page Applications (In JavaScript or otherwise)? From what little I know of it, it just seems to be the way to go, going forward. But would like to hear the opinion of experts.
It's going to go that way, and then it's going to spin back to the server again when we have the infrastructure in place to deliver full rendered video over the network with reliable sub-100ms network roundtrip and rendering latency, and >everythingEven then, there's a lot that is going to end up staing on the client, for convenience. Just like Ruby isn't going to go away - it's just that delivering JSON to single page apps is an increasing portion of its job.
Re: Chasing Programming Fads
#5Ruby vs Javascript is a poor example, that comes across as somewhat scented with sour grapes. The requirements of the work to be done keep changing as technology grows. Ruby is dying because, right now, it makes more sense to do the work on the front end.
You bring up an interesting point with the "front end" comment. Do you see the future of web development as being more heavily geared towards developing Single Page Applications (In JavaScript or otherwise)? From what little I know of it, it just seems to be the way to go, going forward. But would like to hear the opinion of experts.
SPAs are definitely the future of web development, IMO. End users are growing more sophisticated and expect a web application to function with the same speed and responsiveness as a desktop application. Their tolerance for even the slightest delay is decreasing.
Re: Chasing Programming Fads
#6Earlier quoted context omitted.
You bring up an interesting point with the "front end" comment. Do you see the future of web development as being more heavily geared towards developing Single Page Applications (In JavaScript or otherwise)? From what little I know of it, it just seems to be the way to go, going forward. But would like to hear the opinion of experts.
SPAs are definitely the future of web development, IMO. End users are growing more sophisticated and expect a web application to function with the same speed and responsiveness as a desktop application. Their tolerance for even the slightest delay is decreasing.
They are definitely the future - for now :)