Not all questions that are tagged with optimization is about performance, there have been many other kinds of questions tagged with optimization as well. (optimizing code length, optimizing cyclomatic complexity, all other things that can possibly be included in the way-too-broad "optimization" tag)
Merging these tags would make it appear that they ...
Since the tag wiki states that these are community challenges, I suggest that the tag to be renamed to community-challenge. This doesn't sound the same as programming-challenge, and it's less-likely to be confused with anything else.
Questions about optimizing execution time should use the tag: performance.
Questions about minimizing memory should use the tag: memory-optimization.
I like the idea of speed-optimization and memory-optimization.
These two have obvious benefits. I think speed-optimization is more clear than performance (to me, memory is part of performance...), and making ...
I agree with this, and it should be done. I started the process by creating the raku tag, but then ran out of privileges to complete it (I don't have enough perl6 tag-rep to complete the synonym.
The tag should be created raku and then existing perl6 questions should be merged in to raku, and then perl6 should be synonym-linked to raku. This will likely ...
Why does performance have to equal speed improvement?
You have a performance increase when you optimise your design to use less resources. So then time is just a resource and optimizing to use less time is increasing the speed performance. Optimizing to use less memory is increasing the memory performance?
.: Increase in cow performance should be a result ...
I prefer the status quo.
Implementing sorting algorithms is a rite of passage for all true programmers, and we sure get our share of such questions on this site. It would be beneficial to keep a few tags to help users find similar previous questions.
In practice, there are just a few commonly used sorting algorithms that are simple and fast (O(n log n)). ...
I would agree with the merging of the two tags, however, I would merge network-programming into networking.
Why? This is Code Review. The "programming" part of the first tag is redundant, because you have to program in order to produce code.
Just my two cents.
(Note: Mast and I discussed this in chat this is a complete write up of my POV from this)
Salesforce's Developer Tools
I think that Salesforce has three major sections to their developer tools.
A language - Apex [W] [S]
REST APIs [S]
B2C Commerce Developer Sandbox API's
Einstein Prediction Service Scoring API
Einstein Vision and Einstein ...
I'm not quite sure about this one. After comparing the questions, I can see some differences:
Questions tagged as asking-questions mostly involve asking about whether or not a certain question can be asked here.
Questions tagged as questions involve things such as feature requests or anything else about existing questions (which are also not about specific-...
I propose renaming programming-challenge to online-judge. Many of those problems have similar characteristics:
Accept one line on standard input telling your program how many test cases follow. Each subsequent line of input, with space-delimited fields, represents one test case. Your program should read each line and print the corresponding answer.
I'm not so sure.
From tags (emphasized by me)
A tag is a keyword or label that categorizes your question with other, similar questions. Using the right tags makes it easier for others to find and answer your question.
If I would like to see how other people implemented the mergesort, then I would look at the merge-sort tag. There is a huge difference ...
If you take a list of sorting algorithms, you will see that it is quite extensive. Merging those two sorting tags now will prevent us from having a ton of different sorting tags later, and instead have one tag that encapsulates them all.
I like this thought from @200_success a lot.
To force some thought, I believe you should have to choose between speed-optimization, code-size-optimization, or memory-optimization.
The tough part though, would then be initially parsing out the different categories of optimization from the massively overused optimization and stay on top of it consistently ...
I recommend adding "review" in there somehow. In fact, review-challenge works to disassociate it with any other competition I know of, and identifies it at least partially with the site.
Alternatively, how about cr-challenge ?
As far as I can see those questions are about ERB templating.
A combination of text with <% %> <%= %> <% -%> <%# %> and Ruby inside those delimiters.
This is a far cry from NSString and I think the erb tag should be left alone.
Of course, I am in the TPL*, so I am hardly objective ;)
* Tag Proliferation League
I agree. The actionscript tag should be removed from all questions currently using it.
There are currently seven questions, and they all are tagged actionscript-3 as well. There are twenty-two actionscript-3 questions that are not tagged actionscript. This seems quite feasible and the lowest cost way to proceed.
I was just looking around our site tags and checking if I could clean anything up. Noticed we didn't have a socket.io tag, I think we should have one.
The reason being, I just started to use the library myself, and really, it's too distant from WebSockets (websocket, however, the library is built off this) for Socket.io questions to be lumped in that tag. ...
It looks like they were all created by the same user, too. SO's tag wikis seem to suggest that coldfusion and cfml are not quite similar. If they are, then someone else can change them. For now, I've retagged the coldfusion-10 question with coldfusion, and the former will die soon.
UPDATE: That question has been retagged by the OP with this reason.