** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD ** - Page 1187 - Computer Technical Help

Two Plus Two Forums Other Topics Computer and Technical Help

** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **

Post Reply Subscribe

...

Page 1187 of 1603

First

187 687 987 1087 1137 1167 1177 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1197 1207 1237 1287 1387

Last

Page 1187 of 1603

First

187 687 987 1087 1137 1167 1177 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1197 1207 1237 1287 1387

Last

09-07-2017 , 01:32 AM

#29651

suzzer99

Save the Cheerleader, Save the World

Join Date: Nov 2005 Posts: 101,163

Dude.

Quote

$25m Guaranteed WPM on CoinPoker

Join the action now

Daily Rewards • Splash Pots • CoinRaces

09-07-2017 , 10:22 AM

#29652

Larry Legend

Celtic Pride

Join Date: Jul 2009 Posts: 42,243

Was completely unable to reproduce a tester's bug with our app not loading in ie11. Check their screenshots closely and see compatibility mode is turned on. Well then..

Quote

09-07-2017 , 01:49 PM

#29653

suzzer99

Save the Cheerleader, Save the World

Join Date: Nov 2005 Posts: 101,163

Boom shaka laka. You gotta think that emailing the other employees is what made this happen. 95% chance anyway. Being nice never pays.

Quote

09-07-2017 , 02:11 PM

#29654

blackize5

old hand

Join Date: Sep 2012 Posts: 1,358

Nice! Glad you got paid. Once that clears I'd let the other employees know that while you did get paid it was a huge pain dragged out over weeks and you have doubts about solvency going forward.

Quote

09-07-2017 , 02:12 PM

#29655

well named

poorly undertitled

Join Date: Jun 2007 Posts: 78,085

Gj suzzer

Quote

09-07-2017 , 02:20 PM

#29656

suzzer99

Save the Cheerleader, Save the World

Join Date: Nov 2005 Posts: 101,163

Quote:

Originally Posted by blackize5

Nice! Glad you got paid. Once that clears I'd let the other employees know that while you did get paid it was a huge pain dragged out over weeks and you have doubts about solvency going forward.

I've promised them no more mass emails. The employees know how long it dragged out. If any of them reach out to me I will reply.

Quote

09-07-2017 , 02:20 PM

#29657

iversonian

Carpal \'Tunnel

Join Date: Sep 2003 Posts: 21,447

Quote

09-07-2017 , 02:42 PM

#29658

goofyballer

Carpal \'Tunnel

Join Date: Jun 2005 Posts: 70,719

Regarding my earlier performance issues - here is a jsfiddle that does something kinda similar to what my page is doing. When switching from the smaller list to the larger one, you'll notice the browser chug a little. This is a little faster than my page, I'd guess due to a couple things I removed for demonstration purposes (e.g. not using Linkify because things are still slow w/o it), but still quite slow. For the web devs here...
- is the slowness an inevitable issue of "rendering 300 things at once on a state change"?
- anything in particular that would improve the performance of this page as-is?
- what strategies (lazy loading? is offloading rendering to a background thread while you show a spinner or something a thing people do?) would you employ to work around issues like this?

Quote

09-07-2017 , 03:34 PM

#29659

Larry Legend

Celtic Pride

Join Date: Jul 2009 Posts: 42,243

Nice one suzzer

Quote

09-07-2017 , 04:29 PM

#29660

Grue

Pooh-Bah

Join Date: Mar 2004 Posts: 5,667

@gb 2 things jump out

a) don't extend react.component unless you're using state or lifecycle events and
b) your react is out of date by a lot. Try using the most recent version, see if that changes things, and then try v16-alpha and see again how that looks.

Quote

09-07-2017 , 05:20 PM

#29661

goofyballer

Carpal \'Tunnel

Join Date: Jun 2005 Posts: 70,719

Quote:

Originally Posted by Grue

a) don't extend react.component unless you're using state or lifecycle events

More reading on this? Can I make a React element out of something that isn't a component? I thought everything should be a component.

(haven't tried v16 but I updated to 15.6.1, basically the same behavior - think I was using older one because I was having trouble getting jsfiddle to recognize React.addons.Perf and examples I found were using older versions)

Quote

09-07-2017 , 05:32 PM

#29662

suzzer99

Save the Cheerleader, Save the World

Join Date: Nov 2005 Posts: 101,163

Dangit I'll never be a millionaire now. What if I never cash the check?

Quote

09-07-2017 , 05:35 PM

#29663

Grue

Pooh-Bah

Join Date: Mar 2004 Posts: 5,667

Google react stateless components effectively its uh here I'll copy paste one

Code:

import React from 'react'; // eslint-disable-line
import PropTypes from 'prop-types';

const Changelog = props =>
	<section className="changelog">
stuff here
	</section>;

Changelog.propTypes = {
	onLeaveChangelog: PropTypes.func
};

export default Changelog;

Quote

09-07-2017 , 05:51 PM

#29664

lostmypw

centurion

Join Date: Mar 2017 Posts: 103

Quote:

Originally Posted by goofyballer

- is the slowness an inevitable issue of "rendering 300 things at once on a state change"?

the creating of 300 react vdom nodes is probably the bulk of the slowness.

Quote:

Originally Posted by goofyballer

- anything in particular that would improve the performance of this page as-is?
- what strategies (lazy loading? is offloading rendering to a background thread while you show a spinner or something a thing people do?) would you employ to work around issues like this?

showing spinners when doing ajax requests is standard. I don't think it's common to build a big react dom tree in the background but no reason you can't. I messed around with your code and this is probably awful but the basic idea is there. I set it to show 'loading' for a minimum of 300ms because just flashing 'loading' for a few microseconds is more off putting than being forced to wait a split second.

https://jsfiddle.net/ps43p7q6/1/

Last edited by lostmypw; 09-07-2017 at 06:04 PM. Reason: link

Quote

09-07-2017 , 06:15 PM

#29665

goofyballer

Carpal \'Tunnel

Join Date: Jun 2005 Posts: 70,719

Quote:

Originally Posted by Grue

Google react stateless components effectively its uh here I'll copy paste one

Sweet, didn't know you could also just provide a function that turns props -> JSX.

Quote:

Originally Posted by lostmypw

I messed around with your code and this is probably awful but the basic idea is there.

So basically, the rendered list is part of the state? *mind blown* Awesome!

Thanks for the help.

Quote

09-07-2017 , 06:34 PM

#29666

Larry Legend

Celtic Pride

Join Date: Jul 2009 Posts: 42,243

That loading for a minimum makes me think.

Is it common/good to use loading messages like that?

I don't like them when the request should be really quick, but I feel like maybe I'm missing how common it is for small waits?

Quote

09-07-2017 , 06:44 PM

#29667

lostmypw

centurion

Join Date: Mar 2017 Posts: 103

Quote:

Originally Posted by lostmypw

the creating of 300 react vdom nodes is probably the bulk of the slowness.

For the record, I'm wrong about this. In the example the list method only takes 8ms or so to run so it's react messing with the actual dom that is slow. Either way, updating the dom right away to show something is loading seems like an okay option.

Quote

09-07-2017 , 07:02 PM

#29668

lostmypw

centurion

Join Date: Mar 2017 Posts: 103

Quote:

Originally Posted by Larry Legend

https://www.nngroup.com/articles/pow...-scales-in-ux/

Supposedly if it takes longer than 0.1 seconds to update in response to some user interaction, the user will experience the delay as laggy and get annoyed. In that case it's probably better to let the user know something is happening behind the scenes.

In this example it would probably be better to continue showing the first list and just toggle a spinner somewhere in view instead of immediately removing the first list. Twitter and youtube do something similar to this with their routing changes.

Quote

09-07-2017 , 07:40 PM

#29669

RustyBrooks

Carpal \'Tunnel

Join Date: Feb 2006 Posts: 24,646

I was having an email exchange with a coworker today about the evils of dates and timezones - he was complaining about a code base where the database tables had mixed date types and meanings, I was complaining that python is somewhat inconsistent in regards to "unix timestamps" (i.e. seconds since the unix epoch)

Along the way I mentioned that you should never do this

Code:

d = datetime(2017, 1, 1, tzinfo=pytz.timezone('US/Central'))

And then explained why. His next message was "I think I probably need to re-review all the code I wrote today"

(btw the above problem is a doozy and it's caught me many times)

Quote

09-07-2017 , 09:36 PM

#29670

jjshabado

Carpal Tunnel

Join Date: Jul 2006 Posts: 22,732

Suzzer, nice job. I never thought you'd get paid.

I don't think not cashing the check will work for you.

Quote

09-07-2017 , 09:50 PM

#29671

RustyBrooks

Carpal \'Tunnel

Join Date: Feb 2006 Posts: 24,646

I think you should blow the money on something you wouldn't normally allow yourself to get. It's basically like 8 grand you found on the street.

Quote

09-08-2017 , 06:59 AM

#29672

adios

Carpal \'Tunnel

Join Date: Sep 2002 Posts: 22,558

Quote:

Originally Posted by suzzer99

Boom shaka laka. You gotta think that emailing the other employees is what made this happen. 95% chance anyway. Being nice never pays.

Glad you got paid and glad your strategy worked.

Quote

09-08-2017 , 11:40 AM

#29673

suzzer99

Save the Cheerleader, Save the World

Join Date: Nov 2005 Posts: 101,163

Quote:

Originally Posted by RustyBrooks

I think you should blow the money on something you wouldn't normally allow yourself to get. It's basically like 8 grand you found on the street.

Well what $3k of it is going to taxes? So that's $5500 for hookers and blow. See you in a couple weeks!

Quote

09-08-2017 , 05:11 PM

#29674

Craggoo

banned

Join Date: Sep 2006 Posts: 12,645

Quote:

Originally Posted by suzzer99

Well what $3k of it is going to taxes? So that's $5500 for hookers and blow. See you in a couple hours!

Like a boss

Quote

09-08-2017 , 05:14 PM

#29675

daveT

S.A.G.E. Master

Join Date: Jun 2005 Posts: 23,955

Okay, so I have an interview question I know I struggle with.

Q: "What is the worst bug you've ever dealt with" or "what is the hardest query you ever wrote" or some variation like that.

A: Is there really good enough code bases that questions like this are relevant? **

Sarcasm aside, I really wouldn't know how to answer this. It is like asking a musician the hardest piece they know. There really doesn't seem to be an answer that isn't relative to the time I worked on it, and even so, it's nothing I lose sleep over or think about much. Patterns emerge, I learn them, then I move on with my life.

** in the context of what I normally do, I'm not really sure if people who think they have the worst ever code (tm) realizes there is zero chance I haven't seen worse.