Mislav Marohnić

Polyfills: Are those jQuery polyfills? If not, did giving up jQuery's chaining hurt code's readability?

Giving up chaining actually *improved* readability, even if it would lead to more verbose code. More explicit code often communicates intent better.

The claim's interesting, but isn't evident enough. Twitter's a bad place to hold meaningful conversations. Can you write a detailed write-up somewhere beyond 140 chars? I'd love to follow through.

So custom elements, but nothing else from web components then? Would love to see a blog post about this.

We would like to jump on the Shadow DOM train but for now, the polyfill incurs performance penalty for regular DOM lookups

I wanted to ask if you’re going to start using Shadow DOM once it ships in Firefox later this year, or if you’re going to wait a few more years for Edge to ship it, but then I remembered that Microsoft bought GitHub…

Good one hahaha.

How long did it take?

End of a era. It’s cool to think the foundation jQuery provided, and how poor cross browser support once was. Now it still isn’t perfect, but it’s gotten so much better and jQuery itself is part of why stuff got better. For example the ease of using querySelector all

Oh boy! How many times I saw someone picking jQuery when the task only required to write some vanilla JS code.

... and how many Apps I have seen broken by a faulty, home made, event delegation system just because jQuery felt to be "too much" :)

OK, now what are the downsides? Do not tell me there aren't any? And why did u choose to remove jquery and not to use any popular fw in the first place

Unnecessary dependencies become part of technical debt. jQuery simply wasn’t as needed as it was 10 years ago to normalize browser behavior; regular DOM APIs do just fine and lend themselves better to static analysis.

Someone at GitHub: "Need a file upload? No poblemo, let's use that shiny Fetch thingy! I'll just show a nice progress bar aaand… well, crap."

Haha we’d simply use good ol XHR for that. But I don’t think we show progress bars on uploads anyway

Wow!!! I didn't think people actually still used XHR

What's wrong with XHR?

I like to promisify them to prevent having callbacks in my code. Other than that, I don't mind XHR at all.

You can make an XHR request resolve to a promise quite easily

So to answer the question "what's wrong with XHR": it's ugly, nobody can or should memorize it and everyone should use an abstraction if they want to live. I'm just saying what we're all thinking.

Don't call a subset of developers as "all", you are not even close to "all". Being ugly or not XHR is a powerful tool and it's childish easy to wrap it with promise/observable or even use it as is. Can't memorize it? Too bad, I did.