You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1Isn't that pure imagination? You will possibly have to change your server-side stuff when clients change, as you wont get round generating HTML/JS/CSS at some point.Bruno Schäpper– Bruno Schäpper2012-08-24 07:07:53 +00:00Commented Aug 24, 2012 at 7:07
- 1One more thing, 'Client-side web development is strongly coupled with web browsers' - Web-technologies are official standards, as long as you stick with it you are implementing a standard, not coupling your application to a browser. While not too long ago this was not really true, it seems to be at the moment.Bruno Schäpper– Bruno Schäpper2012-08-24 07:12:32 +00:00Commented Aug 24, 2012 at 7:12
- First of all read how some browsers just don't follow the standards (Internet Explorer for example). SOme things have changed over time, but even with IE7 I had horrible problems due to its own way of interpreting what I wrote. Also read a few articles about cross-browser compatibilities. This issue would not exist if every web browser vendor would follow the standards. Second of all if the data set changes, you have to change your business logic, that's obvious.But when new IE gets shipped and you have to rewrite around 30% of code just to make the code work on new browser - something's wrongAndrzej Bobak– Andrzej Bobak2012-08-24 07:16:58 +00:00Commented Aug 24, 2012 at 7:16
- Of course I know how painful it is and was to make everything work in every browser. But this work has to be done regardless server- or client-side (as you have to use a browser in the end anyway). I certainly agree on your second point. However, I don't see 30% to be rewritten. Some alterations possibly are needed, but I doubt it is as bad as in the old days. On the other hand you have to redo everything based on the service layer, if you want to replace your server-side stack. So you are VERY tightly coupled to your server side implementation. Possibly from the top of the UI to the model.Bruno Schäpper– Bruno Schäpper2012-08-24 07:43:59 +00:00Commented Aug 24, 2012 at 7:43
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-js