Revision as of 16:32, 28 September 2022 editOvinus (talk | contribs)Extended confirmed users, New page reviewers, Pending changes reviewers6,895 edits →Formatting function names: new sectionTags: Mobile edit Mobile web edit← Previous edit | Revision as of 14:21, 1 October 2022 edit undoKvng (talk | contribs)Extended confirmed users, New page reviewers108,221 edits →Formatting function names: ReplyTag: ReplyNext edit → | ||
Line 71: | Line 71: | ||
There’s of course an argument for (2)—not treating functions any differently than other nouns, considering the monospacing is somewhat of a specialist style—but I think (3) is cleanest and easiest to read, by how it unobtrusively differentiates from prose. Thoughts? ] (]) 16:32, 28 September 2022 (UTC) | There’s of course an argument for (2)—not treating functions any differently than other nouns, considering the monospacing is somewhat of a specialist style—but I think (3) is cleanest and easiest to read, by how it unobtrusively differentiates from prose. Thoughts? ] (]) 16:32, 28 September 2022 (UTC) | ||
:Consistency is probably the most important consideration. Consistency within an article is paramount. Consistency between articles, less so. So my suggestion would be to choose <nowiki><code></nowiki> or {{tl|mono}} in the lead dependent on what's already used elsewhere in the article. Be aware that a campaign to create consistency between articles has the potential to be mildly controversial (e.g. ]), but I agree that the third option looks the cleanest. ~] (]) 14:21, 1 October 2022 (UTC) |
Revision as of 14:21, 1 October 2022
This is the talk page for discussing WikiProject Computer science and anything related to its purposes and tasks. |
|
Archives: Index, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11Auto-archiving period: 3 months |
Computer science Project‑class | ||||||||||||||
|
Misplaced Pages:Misplaced Pages Signpost/WikiProject used
State Machine Replication a subtopic of Replication but does not reference it
Add a link from replication (computing) to state machine replication. The other direction is covered. This is also an opportunity to improve consistency between these two related articles.
Curating the top-importance list
I've been doing some work to curate the list at Category:Top-importance Computer science articles and welcome any participation and feedback! Pinging Kvng (talk · contribs)
The list was in a pretty inconsistent state initially. Notes so far:
- Lots of cryptography articles unnecessarily rated as top I think due to a quirk of template:WikiProject Cryptography, which I think I've fixed now.
- Regarding language articles, HTML, CSS, JavaScript, and COBOL were included, but I think we should only include these if we also include C, C++, Python, and Java. Currently I'm including none of these based on some pushback at moving the others to top. My hunch is that "high" is correct for all of these.
- In general the list is still pretty theory-biased. We should include a few key systems articles and not unilaterally exclude them -- suggestions for which are welcome. For instance, I nominate Embedded system for top.
- It may also be useful to reference the list of most popular CS articles. Not sure how much popularity/views factor into importance for computer science specifically.
Obviously, top articles should be those with a strong consensus for such, and I believe that many decisions about what to include are likely to get political (i.e., which fields of computer science are important or not), so I'll try not to get too invested in any particular inclusion. Caleb Stanford (talk) 19:43, 23 June 2022 (UTC)
- Thanks for this. I demoted Dining philosophers problem, Cellular automaton, and Lambda calculus. I still see a couple of articles listed that may be top for crypto but not CS (e.g. Transport Layer Security). Embedded system seems like a fine choice for top (in my department it's one of the major faculty research groupings). Another candidate that I think is currently much lower prioritized than it should be is middleware (currently low for computing, not even listed for computer science). —David Eppstein (talk) 19:51, 23 June 2022 (UTC)
- I try not to quibble about importance or quality assessments that are one bracket away from where I'd place them but I have not exactly stuck to that for this round of assessments. Sorry about that but I hope the discussion gets us on the same page. I don't see a description of the importance categories on this wikiproject so I assume we're using the ones at Misplaced Pages:WikiProject_Computing/Assessment#Importance.
- Programming language is and should be Top importance. Individual programming languages may be popular but are any actually essential? I would be inclined to rate them at High or below.
- I question a Top rating for Embedded system because I see it as an computer engineering topic, not so much of a computer science one so Top for Computing, High for Computer science. I seem to have an inclination to only give a Top rating to one wikiproject on each article but maybe that's misguided. ~Kvng (talk) 20:29, 23 June 2022 (UTC)
- I would personally vote for top for Embedded system and lambda calculus. Caleb Stanford (talk) 18:22, 30 June 2022 (UTC)
- I changed Embedded system to Top for this project as that is acceptable to me and seems to be the rough consensus. ~Kvng (talk) 15:10, 3 July 2022 (UTC)
- Thanks! I just changed it (in case you forgot). Caleb Stanford (talk) 16:08, 3 July 2022 (UTC)
- Yes, I must have gotten interrupted and then forgotten. Thanks! ~Kvng (talk) 15:57, 6 July 2022 (UTC)
- Thanks! I just changed it (in case you forgot). Caleb Stanford (talk) 16:08, 3 July 2022 (UTC)
- I changed Embedded system to Top for this project as that is acceptable to me and seems to be the rough consensus. ~Kvng (talk) 15:10, 3 July 2022 (UTC)
- I would personally vote for top for Embedded system and lambda calculus. Caleb Stanford (talk) 18:22, 30 June 2022 (UTC)
Draft:Martin Hamilton
Hello, WikiProject,
I just delayed deletion of this stale draft for another 6 months. I have no knowledge of the history of computer science but I think this person might be considered notable enough to be included in Misplaced Pages. I don't think it would take a lot to improve this draft to get it approved but the page creator has been gone for over a year so it is unlikely that they will be spending any more time on it. So, I thought I'd bring it here in case a WikiProject member was inspired to take it on and get it improved enough for main space. Thank you for considering my request. Liz 02:56, 19 September 2022 (UTC)
- I don't see anything in the draft that screams notable. I haven't reviewed the sources but Nightenbelle has and found them lacking. ~Kvng (talk) 14:47, 21 September 2022 (UTC)
Weak supervision
There's a long-standing merge proposal between Weak supervision and Semi-supervised learning that could do with some expert views at Talk:Semi-supervised learning. I work on merges, but am not a subject expert; so, some help at that talk page would be appreciated. Klbrain (talk) 08:18, 25 September 2022 (UTC)
Formatting function names
I’m working on harmonizing and cleaning up the C standard library articles, and noticed a stylistic inconsistency for which I’d like broader input before changing. For standard functions like malloc, it’s customary to display them in monospace font (at least when talking about it as a specific function, rather than, say, memory allocation as a whole), and this is usually done with code tags, but I find them unsightly in inline text. I think it looks nicer with {{mono}}. Compare the following:
In computing,
mmap(2)
is a POSIX-compliant Unix system call that maps files or devices into memory. When no longer in use, memory-mapped pointers should be unmapped withmunmap(2)
. Somemalloc
implementations usemmap
internally.In computing, mmap(2) is a POSIX-compliant Unix system call that maps files or devices into memory. When no longer in use, memory-mapped pointers should be unmapped with munmap(2). Some malloc implementations use mmap internally.
In computing, mmap(2) is a POSIX-compliant Unix system call that maps files or devices into memory. When no longer in use, memory-mapped pointers should be unmapped with munmap(2). Some malloc implementations use mmap internally.
There’s of course an argument for (2)—not treating functions any differently than other nouns, considering the monospacing is somewhat of a specialist style—but I think (3) is cleanest and easiest to read, by how it unobtrusively differentiates from prose. Thoughts? Ovinus (talk) 16:32, 28 September 2022 (UTC)
- Consistency is probably the most important consideration. Consistency within an article is paramount. Consistency between articles, less so. So my suggestion would be to choose <code> or {{mono}} in the lead dependent on what's already used elsewhere in the article. Be aware that a campaign to create consistency between articles has the potential to be mildly controversial (e.g. WP:ENGVAR), but I agree that the third option looks the cleanest. ~Kvng (talk) 14:21, 1 October 2022 (UTC)