jQuery no longer being a default dependency is great! been waiting for that for a while
still miss prototype js...
Ruby on Rails 5.1
21–30 of 35 posts
Re: Ruby on Rails 5.1
#22jQuery no longer being a default dependency is great! been waiting for that for a while
Poor jQuery. You truly made the web a better place, but we have moved on. My feelings towards jQuery are almost exactly how I view my childhood dog. It was good while it lasted, but I really had no idea what I was doing back then.
If it's any consolation, your doggie didn't mind. That's what makes them such great companions.
edit: r/care/mind
Re: Ruby on Rails 5.1
#23jQuery no longer being a default dependency is great! been waiting for that for a while
Poor jQuery. You truly made the web a better place, but we have moved on. My feelings towards jQuery are almost exactly how I view my childhood dog. It was good while it lasted, but I really had no idea what I was doing back then.
jQuery's still great if you don't want to use all these cheesy new-school JS frameworks. I have yet to find it lacking
Re: Ruby on Rails 5.1
#24Earlier quoted context omitted.
Poor jQuery. You truly made the web a better place, but we have moved on. My feelings towards jQuery are almost exactly how I view my childhood dog. It was good while it lasted, but I really had no idea what I was doing back then.
jQuery's still great if you don't want to use all these cheesy new-school JS frameworks. I have yet to find it lacking
Well, I would argue that the main purpose of jQuery was to help cover all the strange DOM edge cases of the browsers of that time. In that case, it really isn't needed anymore as most browsers behave the same on like 90% of the things now. (It's just that people used it as if it was a Framework, not a library which caused a bunch of problems.)
I am with you that if I'm doing something lightweight I don't use any of the new fancy JS frameworks, I just write vanilla JS.
Re: Ruby on Rails 5.1
#25Earlier quoted context omitted.
Poor jQuery. You truly made the web a better place, but we have moved on. My feelings towards jQuery are almost exactly how I view my childhood dog. It was good while it lasted, but I really had no idea what I was doing back then.
jQuery's still great if you don't want to use all these cheesy new-school JS frameworks. I have yet to find it lacking
The new school frameworks' purpose is pretty much entirely orthogonal to that of jQuery's, although their features do overlap, which is I think why people mistakenly say what you just said so often.
Angular, Ember, etc. are frameworks for coding routing, components, state, etc. Barely any of this was the concern of jQuery, which the main purpose of jQuery was to provide a lingua franca for interacting with browsers that were inconsistent in their implementation of javascript.
Re: Ruby on Rails 5.1
#26Yarn and Webpack integration is already changing my life (for the better). Documentation on both still sucks however. In particular the inclusion of yarn and webpack represent a significant change in development workflows that they've not really outlined yet.
I haven't really been following yarn or web pack. Can you give an example of how it changed your life?
Using npm alone is like using bundler without a Gemfile.lock. If one person does `npm install` today, and a new teammate does `npm install` in a month, the new teammate will install different versions. With yarn, there is a yarn.lock to make sure everyone gets the same versions when they run `yarn install`.
Also, yarn is way faster.
Re: Ruby on Rails 5.1
#27Earlier quoted context omitted.
Imagine wanting to quickly scan which attributes are required and which ones aren't. It used to be easy, find the "null" option with your eyes then scan downwards. Plus it just looks more messy now.
Sure, but I still wasn't a fan of the diffs that it produced—and like poorman said, if you really need that then use the annotate gem which lets you check the model file for that info instead of digging through a giant schema file.
Not what I want. No syntax highlighting, and annoying when I don't need it. Plus I always read the migration file for the db/schema diff anyway. Also, sometimes I want one place to quickly hop around in to remind myself how one area of the codebase snaps together. I never intentionally write code that is harder to read to produce readable diffs, and I don't know why generating schema.rb should be any different.
Re: Ruby on Rails 5.1
#28Wow, the yarn and webpack support is awesome! I've been using the react_on_rails gem, and I didn't like how the webpack stuff felt "tacked on", and I had to run a whole bunch of different stuff using guard. Hopefully they can work with these changes and let me get back to a single "rails server" command.
"System tests" look great, too. It's great that they've brought this in as a convention, since every Rails project I've worked on has configured capybara for integration tests.
Re: Ruby on Rails 5.1
#29Earlier quoted context omitted.
Poor jQuery. You truly made the web a better place, but we have moved on. My feelings towards jQuery are almost exactly how I view my childhood dog. It was good while it lasted, but I really had no idea what I was doing back then.
jQuery's still great if you don't want to use all these cheesy new-school JS frameworks. I have yet to find it lacking
jquery + vue.js on rails is pretty sweet
and no npm dependency BS!
Re: Ruby on Rails 5.1
#30The new form_with is bugging me. It doesn't generate id's on inputs anymore, so you have to manually add `id: 'field_id'` so that clicking labels focuses on the input. Not having the id attribute has also broken Capybara's `fill_in 'Label text'` for me.