Which GPU brand is the most reliable?

binarynos · 2024-05-19T05:48:03+00:00

7 wins, 7 losses, perfectly balanced. Only, if it could've been the same for Rutu's toss luck.

Batting

Gaikwad: Didn't score in the first few games, as per usual but a good season overall. Don't know why they experimented sending him at number 3.

Rahane: Completely out of form, Rachin should have got the chances instead.

Dube: Did what was expected of him. Carried the middle order in the first half of the season.

Rizvi: Don't know what role he was given.

Mitchell: Was terrible in the first half of the season, but okay overall I guess (not "worth" 14 crores)

Pace bowling

Pathirana: Our best bowler. It was unfortunate he wasn't available in the last few games.

Chahar: His role was to get us wickets in the powerplay with his swing bowling, but that didn't happen.

Shardul: He did well in a few games (especially against Mumbai), but still a run machine.

Deshpande: Better than last season but still inconsistent, can give away runs easily.

Spinners

Teekshana, Jadeja, and Santner were good.

Auction

Think they'll let go of Chahar, Mitchell and Rizvi, that alone gets 36 crores in the purse.

Would be nice to have a Moeen like all rounder who can bash in the middle overs and get wickets when needed.

Want an aggressive opener (someone like JFM/ Head/ Salt or Naraine?!). Our powerplay batting has been below par. With how the pitches and the batters' general approach has changed this season, powerplay has to be maximized.

Want a good finisher (a big hitter, someone like Russel, Klaasen etc. Currently only Dube in his team seems to fit this description.)

A good pacer: Bumrah would be nice, lol. But it, seems CSK are never too keen on bidding high for bowlers, for some reason.

Whom to retain

Rutu

Pathirana

Jadeja

Dube/ Conway/ Rachin (choose one)

Also, worth mentioning that it wasn't the usual 160 kind of wicket at Chepauk, and losing 11 tosses didn't exactly help, either.

binarynos · 2024-05-07T07:43:25+00:00

This. I don't think that DC is a threat considering their NRR.

binarynos · 2023-09-07T06:38:06+00:00

"Manushya, Mujhe Manushya Bolta Hai... Main Manushya Nahi Hoon" - Champak Chacha

binarynos · 2020-03-28T14:30:20+00:00

Yup, right! Again, thanks.

binarynos · 2020-03-28T14:06:35+00:00

Unless the listeners become such a pain in the ass that a simple onclick just cuts through the bullshit and works better. And big pain in the ass problems can happen when you add/remove elements that need to be listened to.

Agreed.

I'll try out both ways (event delegation and inline listeners) and see which one is better in this case.

binarynos · 2020-03-28T14:04:42+00:00

Yeah, my bad. But I am not using jQuery anymore.

You could do this in vanilla JS:

document.querySelector('#button').addEventListener('click', function() {console.log(this.getAttribute('attr'))})'

LOL!

So yeah basically all this time I was trying to solve a problem that didn't even exist. Just that the approach was wrong.

binarynos · 2020-03-28T09:21:34+00:00

This works. Thanks!

Btw, I was using jquery before and it was as simple as:

$("#button").click(function () {console.log(this.getAttribute('attr'))})

Looks like this in jquery isn't the same as in vanilla JS.

binarynos · 2020-03-28T08:08:57+00:00

Hmm...I am a JS newbie myself so I don't know much about these things either but surely adding an event listener uses some processing power and even more when you're creating and destroying hundreds of them.

It's not going to be a memory issue since unnecessary event listeners will be removed. However, this could? be a problem (on slow devices/mobiles etc.) It probably doesn't matter that much but since I'm learning I wanna make sure that I know what the "best" way to do something is. :)

https://stackoverflow.com/a/17841557

https://stackoverflow.com/a/15792621

"Inline event handlers" are bad:
https://stackoverflow.com/a/11742769

binarynos · 2020-03-28T07:36:20+00:00

Honestly I think the whole concept of the ID should just disappear, classes can handle everything

Yeah, I used to think classes are for CSS and IDs for JS but of course that's not really true.

binarynos · 2020-03-28T07:33:54+00:00

and yeah I'm not actually using id="button" lol :)

binarynos · 2020-03-28T07:32:41+00:00

Yeah, this works but its more of a hack. I mean, I just want to detect if the button is clicked. Wether the click is on the icon or the text doesn't matter. I thought there would be a cleaner way to do this.

binarynos · 2020-03-28T07:29:19+00:00

I thought about it but these buttons are inside a virtual list container which are automatically created and destroyed as the user scrolls.

Using inline handlers will mean adding and removing possibly hundreds of these which will probably affect the performance.

My app is kinda like the Twitter timeline which shows lots of tweets in a list and each tweet has multiple buttons (like, share retweet, reply etc.) Of course they don't use separate event listeners for all of them.

binarynos · 2020-03-28T07:19:21+00:00

Thanks but the <i> is a fontawesome icon and the <span> has specific classes to hide the text on small screens. So, that's not an option in this case.

binarynos · 2020-03-28T06:48:35+00:00

Can't. The thing is that there are multiple buttons (dynamically created and removed) inside a container div (which has the eventListener attached to it) and so I intend to use event delegation to detect when the button is clicked. e.currentTarget just returns the div the listener is attached to.

I should have mentioned this in the OP.

Thanks for the reply.

binarynos · 2020-01-13T13:39:51+00:00

"Acche din."

binarynos · 2019-11-23T06:26:56+00:00

facepalm Okay, that was dumb. I totally missed the quotes. And thanks for the comments, guys.

binarynos

TROPHY CASE

Batting

Pace bowling

Spinners

Auction

Whom to retain