Timeline for Common Javascript mistakes that severely affect performance? [closed]
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2017 at 16:05 | history | closed |
amon 8bittree Andres F. Bart van Ingen Schenau Thomas Owens♦ |
Needs more focus | |
| Oct 27, 2017 at 4:19 | review | Close votes | |||
| Nov 5, 2017 at 16:05 | |||||
| Jul 13, 2011 at 2:05 | vote | accept | Nic | ||
| Jul 5, 2011 at 17:58 | vote | accept | Nic | ||
| Jul 5, 2011 at 17:58 | |||||
| Jul 1, 2011 at 16:37 | answer | added | It Grunt | timeline score: 1 | |
| Jul 1, 2011 at 16:26 | answer | added | pthesis | timeline score: -1 | |
| Jul 1, 2011 at 15:48 | comment | added | user281377 | Not exactly an answer to your question, so I make it a comment: I've experienced situations where JavaScript did a lot of rendering, and it was actually the rendering engine of the browser that used up the seconds. Therefore, to handle a performance bottleneck, I would look for unnecessary rendering operations first. | |
| Jul 1, 2011 at 15:44 | answer | added | Tyanna | timeline score: 0 | |
| Jul 1, 2011 at 15:03 | answer | added | Raynos | timeline score: 3 | |
| Jul 1, 2011 at 14:55 | answer | added | deadalnix | timeline score: 4 | |
| Jul 1, 2011 at 14:52 | comment | added | Nic | @Adam Crossland you're absolutely right - in that same instance I think I helped a developer with a native app that heavily relied on jQuery as well. | |
| Jul 1, 2011 at 14:51 | history | edited | Nic | CC BY-SA 3.0 |
added 9 characters in body
|
| S Jul 1, 2011 at 14:51 | history | suggested | Michael Mrozek | CC BY-SA 3.0 |
Fixed title
|
| Jul 1, 2011 at 14:50 | comment | added | Adam Crossland | It's getting to be somewhat passe to speak of 'the site' when talking about JavaScript. It's everywhere and being used for everything these days. | |
| Jul 1, 2011 at 14:48 | answer | added | Adam Crossland | timeline score: 8 | |
| Jul 1, 2011 at 14:48 | comment | added | Nic | @delnan that's very true, but it seems like it is a lot more prevalent in JS. Perception maybe? | |
| Jul 1, 2011 at 14:46 | comment | added | user7043 | Likely the same as with every other program: Doing more work than necessary and doing the same work over and over again, often hundreds of times. | |
| Jul 1, 2011 at 14:40 | review | Suggested edits | |||
| S Jul 1, 2011 at 14:51 | |||||
| Jul 1, 2011 at 14:35 | history | asked | Nic | CC BY-SA 3.0 |