Language: Namespace polluting by creating a large footprint of variables in the global context. Binding event handlers in the form ‘foo.onclick = myFunc’ (inextensible, should be using attachEvent/addEventListener). Using eval in almost any non-JSON context Almost every use of document.write (use the DOM methods like document.createElement) Prototyping against the Object object (BOOM!) A small one … Read more
Setting aside the argument of whether or not implementing the singleton pattern is a good idea, here’s a possible implementation: package singleton type single struct { O interface{}; } var instantiated *single = nil func New() *single { if instantiated == nil { instantiated = new(single); } return instantiated; } single and instantiated are private, … Read more
Every time innerHTML is set, the HTML has to be parsed, a DOM constructed, and inserted into the document. This takes time. For example, if elm.innerHTML has thousands of divs, tables, lists, images, etc, then calling .innerHTML += … is going to cause the parser to re-parse all that stuff over again. This could also … Read more
I am the author of the quote in the question, which came from a previous answer. Jason is right to be suspicious of brief statements such as mine, and to ask for an explanation. Of course, if I fully explained everything in that answer, I would need to have written a book. Mike is also … Read more
It’s OK for small applications and allegedly “one-off” scripts, especially with the vars enhancement mentioned by @kaizer.se and the .format version mentioned by @RedGlyph. However, for large applications with a long maintenance life and many maintainers this practice can lead to maintenance headaches, and I think that’s where @S.Lott’s answer is coming from. Let me … Read more
Warning: Long scary post ahead I’ve written about one application I’ve worked on before here and here. To put it simply, my company inherited 130,000 lines of garbage from India. The application was written in C#; it was a teller app, the same kind of software tellers use behind the counter whenever you go to … Read more
Take a look at onBeforeUnload. It wont force someone to stay but it will prompt them asking them whether they really want to leave, which is probably the best cross browser solution you can manage. (Similar to this site if you attempt to leave mid-answer.) <script language=”JavaScript”> window.onbeforeunload = confirmExit; function confirmExit() { return “You … Read more
To help with answering, here is more about the anti-pattern comment: it is overused, introduces unnecessary restrictions in situations where a sole instance of a class is not actually required, and introduces global state into an application From: http://en.wikipedia.org/wiki/Singleton_pattern For more on this you can look at: https://www.michaelsafyan.com/tech/design/patterns/singleton Here is a great ending to the … Read more
I assume the answer is largely because why are you catching it if you can’t handle it? Why not let whomever can handle it (or whomever is left with no choice but to handle it) log it, if they feel that it is log-worthy? If you catch it and log it and rethrow it, then … Read more
Patterns are complex All design patterns should be used with care. In my opinion you should refactor towards patterns when there is a valid reason to do so instead of implementing a pattern right away. The general problem with using patterns is that they add complexity. Overuse of patterns makes a given application or system … Read more