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.
-
4What's with the 99999999 links?DeadMG– DeadMG2012-06-04 04:11:18 +00:00Commented Jun 4, 2012 at 4:11
-
1I thought this might be good for the community wiki, (if it gets good replies); so I thought it would make sense to have well-defined question content.A T– A T2012-06-04 04:12:42 +00:00Commented Jun 4, 2012 at 4:12
-
4@AT That's not how Community Wiki works... You posted on Programmers, the crowd here is expected to understand what a search engine is, no need to link to the Wikipedia article. Your question isn't really well defined, you aren't telling us anything about the actual project and how it works, other than some vague buzzwords.yannis– yannis2012-06-04 07:10:54 +00:00Commented Jun 4, 2012 at 7:10
-
It's a general question. The vague buzzwords have been disambiguated through references. I also included my use-case for having a decoupled client, i.e.; same codebase for mobile apps and website. My question is very well defined and applicable to a wide audience.A T– A T2012-06-04 07:27:53 +00:00Commented Jun 4, 2012 at 7:27
-
3@AT The problem with the buzzwords is not that they are vague themselves, but you are not telling us absolutely anything on how exactly you implement the various technologies. Linking to a reference sites for extremely common buzzwords is completely pointless, we know what the technologies are and how they are used, what we don't know is how you use them in your project. Also the one bit of information you actually give us, "decoupled client", is quite idiomatic and means absolutely nothing by itself.yannis– yannis2012-06-04 15:37:27 +00:00Commented Jun 4, 2012 at 15:37
|
Show 1 more 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