Almost identical to NickFitz’s answer: var str = [“” ,”line 1″ ,”line 2″ ,”line 3″ ].join(“”); // str will contain “line1line2line3” The difference, the code is slightly more maintainable because the lines can be re-ordered without regard to where the commas are. No syntax errors.
As Einstein said: Make everything as simple as possible, but not simpler. It applies to code as well as to physics. Use your judgement – will it get easier to maintain? Often by reducing large if/else messes into something smaller you remove corner cases that didn’t need to be there, preventing bugs that may have …
The theoretically optimal values are: Maintainability index: 100. Higher values indicate better maintainability. Cyclomatic complexity: 1. The number of different paths that code can take. Depth of inheritance: 1. The number of class definitions above this one in the inheritance tree, not including interfaces. Class coupling: 0. Number of other entities this entity is dependent …
I did a talk on this topic at Yahoo last year.
I’d play to the strengths of each system. Aggregating, joining and filtering logic obviously belongs on the data layer. It’s faster, not only because most DB engines have 10+ years of optimisation for doing just that, but you minimise the data shifted between your DB and web server. On the other hand, most DB platforms …
This is a totally subjective question. There might be many other points, but let me point out a few below: JSON based approach: If I am not wrong then this will be implemented using Map on server side. Advantage: In JavaScript you can directly use users.id1, users.id2, i.e. no need of iteration Disadvantage: On the …
I have written portable replacement for time.h (currently just localtime(), gmtime(), mktime() and timegm()) which uses 64 bit time even on 32 bit machines. It is intended to be dropped into C projects as a replacement for time.h. It is being used in Perl and I intend to fix Ruby and Python’s 2038 problems with …
It depends on your needs. If you use http://api.example.com it makes your API a subdomain. Basically, this URL pattern is good if your REST service is to be consumed by multiple clients, but if only one client is connected to your API then the pattern http://example.com/api/v1 is good. However, if you want to add more …