Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

This Week in Rails: jQuery no longer part of Rails, and more

weblog.rubyonrails.org

Post reply on HN
Print view View original

51–60 of 143 posts

Re: This Week in Rails: jQuery no longer part of Rails, and more

#51

Post by jayajay »

dang wrote: post #48
reitanqild wrote: post #47

Earlier quoted context omitted.

I don't think you really got it jayajay: You are talking down a tool that saved thousands of engineering hours and helped level the playing field between the browsers. And then it seems you try to lie your way out of it. (The first comment looks nothing like a joke.) Recommendation: own your mistake, be more careful next time. Oh, and skip unnecessary profanities.

> And then it seems you try to lie your way out of it. Please be charitable and give others the benefit of the doubt when commenting here.

Are you a mod? I'd like to apologize for crashing this jQuery funeral.

Re: This Week in Rails: jQuery no longer part of Rails, and more

#52

Post by dispose13432 »

500carrots wrote: post #43
dispose13432 wrote: post #31

Earlier quoted context omitted.

>PHP made web development accessible to the masses. Because PHP is embedded in the HTML itself, it is way easier to work with than Perl or Java, especially in the context of The Web In 1999. PHP didn't make it easy. It made it possible. Until fairly recently, getting a VPS was insanely expensive, so any learner, hobby, startup went to shared hosting. As a result, any tech which required starting servers or elevated p…

No. You could give CGIs any filename, in any directory, on many shared hosting environments in the 90s. I know because I did it. Some shared hosting providers allowed persistent processes. Also, in the 90s, many small businesses self-hosted on tower PCs connected by fractional T1s. Many hobbyists self-hosted on dorm Ethernet (which had publically routed static IPs then) or got a corporate network administrator buddy…

>PHP was successful because it was embedded in the HTML which lowered the barrier of entry. That's the only reason.

JSP also allowed Java code in HTML (The new syntax came later). Yet, it never took off (though being a memory hog back then definitely didn't help it).

Re: This Week in Rails: jQuery no longer part of Rails, and more

#53

Post by [deleted] »

jayajay wrote: post #50
reitanqild wrote: post #47

Earlier quoted context omitted.

I don't think you really got it jayajay: You are talking down a tool that saved thousands of engineering hours and helped level the playing field between the browsers. And then it seems you try to lie your way out of it. (The first comment looks nothing like a joke.) Recommendation: own your mistake, be more careful next time. Oh, and skip unnecessary profanities.

If making a black joke at an all-black wedding isn't funny, I don't know what is.

[deleted]

Re: This Week in Rails: jQuery no longer part of Rails, and more

#54

Post by [deleted] »

mythz wrote: post #28

Pour one out for jQuery! jQuery was a major productivity boost when first released but it didn't scale well and encouraged creation of tightly coupled glue code. It's decline being the result of evergreen browsers maintaining good parity where "vanilla JS" is now a feasible option and from it no longer being needed in the premier JS SPA frameworks which scales better and allows for the creation of better componentize…

[deleted]

Re: This Week in Rails: jQuery no longer part of Rails, and more

#55

Post by MrBra »

mythz wrote: post #28

Pour one out for jQuery! jQuery was a major productivity boost when first released but it didn't scale well and encouraged creation of tightly coupled glue code. It's decline being the result of evergreen browsers maintaining good parity where "vanilla JS" is now a feasible option and from it no longer being needed in the premier JS SPA frameworks which scales better and allows for the creation of better componentize…

> minimal complexity

compared to?

Re: This Week in Rails: jQuery no longer part of Rails, and more

#56

Post by grzm »

jayajay wrote: post #50
reitanqild wrote: post #47

Earlier quoted context omitted.

I don't think you really got it jayajay: You are talking down a tool that saved thousands of engineering hours and helped level the playing field between the browsers. And then it seems you try to lie your way out of it. (The first comment looks nothing like a joke.) Recommendation: own your mistake, be more careful next time. Oh, and skip unnecessary profanities.

If making a black joke at an all-black wedding isn't funny, I don't know what is.

This is completely uncalled for. Two people have already commented on your posts today in this thread. Please take extra care to post civil and constructive comments here.

Re: This Week in Rails: jQuery no longer part of Rails, and more

#57

Post by ralmidani »

I use Ember on the client-side. Inside components, jQuery is still very relevant for things like form input masks, Bootstrap plugins, etc.

jQuery continues to save countless hours over using vanilla JS. And it's even better when you use it with CoffeeScript.

Re: This Week in Rails: jQuery no longer part of Rails, and more

#58

Post by jayajay »

grzm wrote: post #56
jayajay wrote: post #50

Earlier quoted context omitted.

If making a black joke at an all-black wedding isn't funny, I don't know what is.

This is completely uncalled for. Two people have already commented on your posts today in this thread. Please take extra care to post civil and constructive comments here.

The occasional phase-shifting surface in an echo chamber isn't completely uncalled for.

Re: This Week in Rails: jQuery no longer part of Rails, and more

#59

Post by somecallitblues »

I will personally continue to use jQuery for many years to come. It's a lot of power in few concise lines of code and it really makes sense. And it comes at the cost of a single request. For the small amount of JS my sites use its perfect. I don't know why everyone in thread is saying goodbye to jQuery. Are that many people coding in vanilla JS?
Post reply on HN