User:Diego Moya

__NOINDEX__ http://stats.grok.se/en/latest90/Greater_Bostona.k.a. Dialmove. Protecting SNOWFLAKEs since January 2012.

''Oh shit, they keep the User pages of deceased Wikipedians as a memorial. I'll need to do cleanup one of these days.''

Watching for:

Winter is coming.
 * Category:Proposed draft deletion
 * PrPr course
 * Getting started users from GettingStarted
 * Writing exercises
 * Article_Rescue_Squadron/Rescue_list
 * AfD debates (Web or internet), AfD debates (Fiction and the arts), AfD debates (Science and technology)
 * User:Snotbot/AfD%27s_requiring_attention, Files for deletion
 * Category:Wikipedia files with no non-free use rationale‎, Category:Wikipedia files missing permission‎, Category:Candidates for speedy deletion, Category:Disputed non-free Wikipedia files, User:Wcquidditch/wikideletiontoday
 * Special:NewPagesFeed, Centralized_discussion
 * Testing the Special:FeedbackDashboard and Special:ArticleFeedbackv5
 * VE nowiki log (plus historic documents)
 * Flow sandbox
 * Draft (and some ideas for WP:UNSTABLE / Forkipedia).
 * 2019 Talk pages consultation 2019

Learning New pages patrol.

Inclusion criteria for Lists and Stand-alone lists

Searches

 * - Export articles to Wikia
 * Deletion log


 * Article topic search "articletopic:" (topics)

Proposals

 * User:Diego_Moya/Draft_Talk_RfC, complementary to User:BethNaught/Draft_Flow_RfC

Wikidata

 * Conflictos entre idiomas: https://www.wikidata.org/wiki/Wikidata:Interwiki_conflicts, https://www.wikidata.org/wiki/Help:Merge
 * http://www.wikidata.org/wiki/Wikidata:Glossary
 * http://www.wikidata.org/wiki/Help:FAQ
 * http://www.wikidata.org/wiki/Wikidata:Infoboxes_task_force#Use_cases
 * freenode chat
 * Etiquetas task force
 * - índice de cosas asumidas, mucho más pragmático que una Intro page
 * Notes
 * Primera versión del wikicode necesario para empotrar datos (items, propiedades) en páginas wiki
 * URIs
 * RDF
 * User:Diego Moya/Wikidata shortcomings

Dbpedia

 * Visual Sparql query
 * DBpedia
 * DBpedia overview

Semantic - generic

 * http://www.w3.org/2005/04/fresnel-info/ Fresnel, el lenguaje unificado para mostrar RDF a los humanos
 * Fresnel + javascript: hay una librería que permite implementar GUIs basadas en web semántica
 * Turtle_(syntax)
 * Faviki (blog), el del.icio.us con etiquetas que son categorías Wikipedia
 * Hypernotation, la alternativa
 * pensamientos
 * http://bergie.iki.fi/blog/inspiration-for-fbp-ui/ (not "semantic", but declarative)

Wikidata Tools

 * http://wiki.dbpedia.org/Applications
 * Sztakipedia an Intelligent Assistant for Knowledge Creation
 * http://code.google.com/p/sgvizler/ JavaScript which renders the result of SPARQL SELECT queries into charts or HTML elements.
 * http://www.visualdataweb.org/gfacet.php Graph-based Faceted Exploration of RDF Data

RFCs
Wikipedia_talk:User_pages. Drafts have no expiration date

Essays to write

 * wp:A WikiLink is not an explanation
 * wp:Use the Wiki-against redwalling deleted content-. (yet to write)
 * WP:Three levels of attribution: verifiability, significance, notability - are used by different policies to determine what content to keep and what to remove.
 * verifiability: content can be included in a related article, provided if it doesn't have undue weight.
 * significance: weak form of "encyclopedic", enough to provide "context" from one pov
 * in depth but not neutral (not independent o no multiple)
 * notable: strong form of "encyclopedic", enough to define valid topics.
 * The dark side - policies are created to keep problematic behavior in check - we have issues with inaccuracy, poor fact-checking, relevance, elitism, bias, and trigger-happiness.
 * Wikipedia is finished. The processes that allowed the project to grow are no longer considered acceptable by a majority of the active community. Thus, although the product can still receive small polish and tweaks, the main work for building is mostly frozen by current practices.
 * You Can't Follow All The Rules, All The Time (YCFATRATT, or "fat rat").

Articles I'm interested in
I'm (mostly) proud of my cleanup work in the Monad (functional programming) article (before, after ).

Other articles to which I've significantly contributed:
 * Dialog box, Alert dialog box, Modal window,Mode (computer interface), Game mechanic
 * User_interface,Graphical user interface,Elements of graphical user interfaces, History of the graphical user interface, Direct manipulation interface, Text-based (computing), 3D Interaction
 * Selection (user interface), Lapis (text editor)‎, Pointing device
 * Dolphin Browser
 * Widget toolkit, GUI widget, Widget engine, Web widget
 * Zooming User Interface, Archy
 * Cognitive dimensions, User error, User (computing), End-user development
 * Fina (architecture)‎
 * Deutsch Limit, Brad A. Meyers
 * Gallium3D
 * Tablet computer
 * Programming language, High-level_programming_language, Computer program, Language primitive
 * Declarative programming
 * Solver (computer science), General Problem Solver
 * Chandler (PIM)
 * Storytelling game, Galatea (video game)
 * Benevolent Dictator For Life
 * Hyperlink‎
 * Talk:Recognition vs recall https://en.wikipedia.org/wiki/Talk:Recognition_vs_recall

Improving lead sections
Working hard to make lead sections understandable at least in these articles: Plenty others...
 * 0.999...
 * Abort, Retry, Fail?
 * Stoichiometry
 * Notation
 * Abstraction (computer science)
 * Unification (computer science)
 * Particle swarm optimization
 * Anytime algorithm
 * Aspect (computer programming)
 * Mobile computing
 * Inversion of control, Dependency injection
 * Purely functional, Functional programming
 * Concatenative programming language
 * Service-oriented architecture, Service (systems architecture)
 * Hypostatic abstraction, Reification (computer science)
 * Scripting language, Scope (computer science), Continuation, Trait (computer programming)
 * Local search (optimization), Metaheuristic
 * Gameplay, Kinect
 * Point particle
 * n-gram
 * Subgoal labeling

Community - my own templates
Teoría de juegos-game theoretic analysis of Wikipedia conflict by User:Volunteer_Marek/gt.

Consensus discussions

 * Wikipedia_talk:FFD - screenshots and NFCC#8 ( + Star trek examples )


 * WMF's statement on non-free = Wikipedia_talk:Non-free_content

Zero tolerance 2 newcomers bite
anti-bite templates:

subst:Uw-bite

subst:Uw-npa1

subst:Uw-npa2

subst:Uw-agf2

subst:Uw-notcensored1

subst:Uw-own3

Warning text:

I noticed the message you recently left to a newcomer. Please remember not to bite the newcomers. If you see someone make a common mistake, try to politely point out what they did wrong and how to correct it. If they fail to follow policy, take the extra step to explain how to comply with the rules, and try not to rely only on warning templates; being welcoming to newcomers is mandated by policy.

The first message a new editor should receive is a Welcome notice, not a revert warning. You can use the template, or activate Twinkle at Preferences->gadgets to access the list of pre-populated  welcome templates tailored for problematic editors, that are much less bite-y than the raw templates. Thanks!

Using references
A brief note about inserting references. When adding an external link, please, try to use the "Cite web" template, that properly formats the link and adds it to the References section. You can see how to use the template at the user guide.

Also make sure that the external page you're using is a reliable source; not all pages are valid references.

Essays

 * Autistic, asperger and other non - neurotypical editors: HONEYPOT
 * Obsesive / compulsive wikignomes: WP:OCDeditors, ULTIMATEHOBBY

Wikiproject pages
To create an anchor target without a section heading, you can use a the anchor template or a span:   .

Help:Wikipedia: The Missing Manual

Writing better articles User Warning Templates Map [Mapa Wikipedia España]

***********************
 * WP:NFCC and discussion about people images
 * List of shortcuts
 * Editing policy
 * Upload
 * Help:Picture tutorial - image editing
 * Category:Redirects_with_possibilities
 * Drawing_attention_to_new_pages
 * Help:Footnotes - named references, referencias con nombre
 * WikiProject_Stub_sorting/Stub_types
 * Good_article_criteria - Contains links to important policies and guidelines
 * CITE
 * Cheatsheet
 * Wikipedia:Administrators' noticeboard/Edit warring - Report the Three revert rule 3RR violations
 * Help:Searching/Features

Templates


Boilerplate text


 * non-free no reduce avoid automatic screen resolution reductions;
 * Non-free manual reduce request manual non-bot reduction;
 * subst:orfurrev to remove previous versions
 * Dispute for removed deleted content in a section, discussion at talk page: Content
 * Template:Pdraft - promising draft: hold drafts from being speedily deleted with G13
 * Template_messages
 * Template_messages/Cleanup - maintenance and references
 * Category:Wikipedia template administration
 * efn is used at each footnote, together with notelist above the References section, to create explanatory notes. (Sinking_of_the_RMS_Titanic)
 * Example - Template link is used to display a template name like Example
 * Help:Templates
 * User warning templates
 * : reply other users in their talk pages.
 * quintessential to show wiktionary definition of quintessential
 * Template_messages
 * Welcome_templates
 * Welcome_template_table
 * Top hat hatnote tags examples: hatnote, HATTEST. Ver también la caja plegada que puse arriba de la página
 * Template_messages/General
 * Time-sensitive templates and WP:ASOF
 * Only-two-dabs ( O2d ), Consider disambiguation ( Cdis, Condis ) for two-article DABs


 * mucho texto oculto


 * categorias: cat main para la principal, un espacio en ":category|nombrecat| " para default main article . WP:SORTKEY para ordenar toda la categoría. Ejemplo: Gender representation in video games
 * non-diffusing sub-category subcategories: WP:DUPCAT
 * usuario sin firma: direccion
 * Template messages/User talk namespace - vandalism and other stuff (see also: [|Twinkle] - preferences
 * references - two 2 columns
 * search titles ,
 * template the regulars - useful irony.
 * COI
 * third-party
 * primary, primary sources
 * Reflist, Help:List-defined_references =

Discussion logs in talk pages

 * Delete: y
 * Merge:
 * Categorias:

Preferences
[User:Diego_Moya/vector.js vector javascript page]

Cite bots and search tools
Insert References tools:
 * Best: holek cite-gen
 * Help:Citation_tools
 * User:Citation bot/use
 * User:Smith609/RefTool


 * User:Anomie/linkclassifier - leyenda de coloreado de enlaces con "linkclassifier"
 * Wikichecker - user and article statistics

Old toolserver
 * and search tools from User_talk:Scottywong/Archive_20
 * User:Edward/Find link - to look for an exact sentence in several articles


 * Blame new, [wikipedia.ramselehof.de/wikiblame.php old]

Setup - configuracion

 * User:Diego_Moya/common.css css
 * User:Diego Moya/common.js javascript
 * (antiguo) User:Diego_Moya/vector.js vector javascript page vector javascript


 * Special pages - Customisation. Enlace para apuntar a mi página: Special:MyPage/subpage (En español: Especial:MiPágina/subpágina)

SMS Cheatsheet

 * User:Diego Moya/SMS

Knowledge - links

 * Poe's law about parody indistinguishable from the real thing ("without a clear indicator of the author's intent, parodies of extreme views will be mistaken by some readers or viewers as sincere expressions of the parodied views")

Tools (new)
Tools - todos los enlaces 
 * Administrator_intervention_against_vandalism
 * Global Wikimedia edits
 * Popups navigation
 * OTRS - ticket system for RS reliable sources as mails (see mw:Commons:Permission)
 * Process, summarized: read Donating copyrighted materials and grant permission by submitting an email template to permissions-commons@wikimedia.org. Diego (talk) 10:38, 17 June 2015 (UTC)
 * Spam and linkfarms: WP:BLACKLIST
 * http://reportcard.wmflabs.org (or the more detailed info at http://stats.wikimedia.org/EN/SummaryEN.htm which has *all* the data with no redactions).


 * CatScan - Categories intersections

Tools Labs (Wikimedia foundation) https://tools.wmflabs.org/


 * Reflinks reference fixer - arreglar URLs crudas
 * pageviews

Wiki tools by Alanscottwalker

 * Search through a page's history for edits made by a particular user
 * List changes made recently to pages linked from a specified page
 * List contributors to an article, ranked in order of activity
 * Find images for a given article, using interwiki links
 * Find which Wiki pages link to a particular site
 * What pages have you and another edited?
 * User's across-projects contributions
 * Search Wikipedia's back pages
 * Who wrote that? (Wiki blame)
 * Request page protection
 * Fix bare url reflinks
 * Readability meter
 * X!'s edit count
 * Wikichecker
 * 3RR tool
 * Review
 * Emote
 * Help

Scripts

 * User:Diego_Moya/monobook.js
 * Tools/Navigation_popups

= Half baked = My half baked articles-
 * User:Diego_Moya/Half_baked/GUI
 * User:Diego_Moya/Half_baked/Fina
 * User:Diego_Moya/Half_baked/Sydney Padua
 * User:Diego_Moya/Capacity measurements

Notes to self

 * WP:RSOPINION
 * Rules are only enforced when people agree that they should be enforced.
 * The spirit of the rule trumps the letter of the rule. The common purpose of building a free encyclopedia trumps both. If this common purpose is better served by ignoring the letter of a particular rule, then that rule should be ignored. and Don't follow written instructions mindlessly, but rather, consider how the encyclopedia is improved or damaged by each edit. and WikiLawyering doesn't work
 * A rule-ignorer must justify how their actions improve the encyclopedia if challenged. and Most of the rules are derived from a lot of thoughtful experience and exist for pretty good reasons; they should therefore only be broken for good reasons.
 * If what they are doing helps the encyclopedia, experienced users should be trusted to ignore rules that get in the way of their volunteer work.
 * strict interpretation of a contended guideline and never explained how this removal helps improve Wikipedia.

http://debburn.alioth.debian.org/FORK


 * Having only serious content would imply removing everything about popular culture, which amounts to maybe 80% of Wikipedia content
 * Tilt! How to get bias into a Wikipedia article

Ammunition for disambiguation/move/PRIMARYTOPIC guidelines
What is confusing readers? Disambiguation can be done wrt:
 * How the article is titled - The Big Bang Theory...
 * What would people look for as search term - All That Jazz, Loving You Lovin' You...
 * What the words mean - Big, Nize, Season 2 Season 4, 24 seasons...

NFC bots are out of control

 * File:Original_lorem_ipsum_from_Rackham_edition_of_Cicero%27s_De_finibus.png
 * [[:File:AppleIIGSOS.png]
 * File:Windows 3.1 (customized colour scheme).png
 * File:Windows_3.11_workspace.png
 * File:Windows_95_Desktop_screenshot.png
 * File:Emu running emu.jpg
 * File:NeXTSTEP_desktop.png

To do

 * Archy - integrate third-party sources
 * Pie menu - integrate talk page commentary and references, clean up Pie_menu, and include comparison with other techniques per Talk:Pie_menu.
 * Tablet computer - rewrite History MS-tablets paragraph
 * Modal window - find sources that describe modal windows
 * STARS model and design styles of game design
 * History of video game consoles (eighth generation) - "other systems" section.
 * Wikipedia talk:Article Rescue Squadron - !vote templates.
 * 0.999... infinite
 * Battle of the sexes encyclopedic article
 * Human-machine interaction and man-in-the-loop humans
 * Remove example farm at Pie menu (again)
 * Source old verb-object cut interaction and reference Tesler origin paper
 * Talk:Global_warming_controversy
 * Talk:Scientific_opinion_on_climate_change New summary section for scientific process
 * Scientific opinion on climate change hatnotes - move them in compliance with WP:RELATED
 * Talk:Big Bang Expand article with sources for education and metaphors
 * search
 * "A review of astronomy education research"
 * "Astronomy in the National Science Education Standards"
 * "How Cosmology Became a Science."
 * "Science, Religion, and Education."
 * "The effect of teachers' language on students' conceptions of the nature of science"
 * "Multiple intelligences theory: A framework for personalizing science curricula"
 * "Why science standards are important to a strong science curriculum and how states measure up"
 * Wikipedia_talk:Disambiguation Information forragin disambiguation
 * Wikipedia talk:Deletion guidelines for administrators‎
 * Coverage of Alyssa Bereznak, Anita Sarkeesian and other harassed girl geeks. (Try to keep them WP:BLP-compatible).
 * Discuss having a redirect notice at WP:Redirect.
 * Move Talk:Wolverine_(comics)
 * WP:ATA section called WP:CLEANSLATE based on this. Diego (talk) 09:38, 2 January 2013 (UTC)
 * see also this AfD - probablemente habrá un argumento "empezar de cero" similar.
 * Learn Monoids and Krohn–Rhodes_theorem on how to decompose finite automata into smaller pieces


 * References for Emocapella: http://www.ew.com/ew/article/0,,396755,00.html, http://www.mtv.com/news/articles/1496327/emo-cappella-group-gets-girls.jhtml


 * DYK? Web navigation.
 * Web presence - write stub from academic sources.


 * Alice in wonderland Disney screenshot - Deleted by Fastily


 * Schily COI:, , [Talk:Jörg_Schilling#Incorrect_claims_made_by_laymen],
 * More Cdrtools ,


 * PWCT - Programming Without Coding Technology
 * http://translate.google.es/translate?hl=es&sl=auto&tl=en&u=http%3A%2F%2Fwww.alriyadh.com%2F535735 (Al_Yamamah_(magazine) - reliable?)
 * http://translate.google.es/translate?hl=es&sl=ar&tl=en&u=http%3A%2F%2Fwww.mawhopon.net%2FInnovators-and-researchers%2F3209-%25D8%25A7%25D9%2584%25D8%25A8%25D8%25B1%25D9%2585%25D8%25AC%25D8%25A9-%25D8%25A8%25D8%25AF%25D9%2588%25D9%2586-%25D9%2583%25D9%2588%25D8%25AF-%25EF%25BF%25BD%25D9%2588%25D8%25B1%25D8%25A9-%25D9%2581%25D9%258A-%25D8%25B9%25D8%25A7%25D9%2584%25D9%2585-%25D8%25A7%25D9%2584%25D9%2583%25D9%2585%25D8%25A8%25D9%258A%25D9%2588%25D8%25AA%25D8%25B1.html (mawhopon.net: reliable - not)
 * http://translate.google.es/translate?hl=es&sl=ar&tl=en&u=http%3A%2F%2Fitwadi.com%2Fnode%2F846  itwadi.com: reliable - not


 * [|Xqt bot] breaks redirects
 * Draft:List of Metaheuristics

Feminism & harassment

 * "Gamasutra contrasted the level of criticism that a campaign should reasonably expect with the amount of backlash received from online communities.".
 * A Forbes contributor noted how, while coherent and meaningful arguments against "what she’s doing or how she’s doing it" was legitimate, violent reactions and threats were not.


 * http://geekfeminism.wikia.com/wiki/Timeline_of_incidents
 * http://web.archive.org/web/20130127021031/http://dev.paxsite.com/schedule/panel/ending-harassment-in-gaming


 * “Over the past year we’ve seen a number of cases where high profile women were targeted by a similar backlash including Bioware writer Jennifer Hepler, Aisha Tyler, and Felicia Day.”
 * to populate: Category:Harassment incidents in video games
 * Zoe Quinn
 * 
 * http://www.brightsideofnews.com/2014/08/25/gamers-revolt-another-take-on-the-zoe-quinn-scandal/
 * http://www.escapistmagazine.com/news/view/116360-Jeff-Gerstmann-Explains-His-Departure-From-Gamespot
 * Talk:Zoe_Quinn  (professional blog with an editorial staff)
 * http://www.gamerevolution.com/manifesto/zoe-quinn-between-anger-and-depression-quest-27793
 * http://newmediarockstars.com/2014/08/sex-scandal-involves-female-game-developer-zoe-quinn-kotaku/
 * http://www.gamerheadlines.com/2014/08/kotaku-and-zoe-quinn-accused-of-exchanging-positive-press-for-sex/
 * http://kotaku.com/in-recent-days-ive-been-asked-several-times-about-a-pos-1624707346
 * http://motherboard.vice.com/blog/zoe-quinn-slut-shaming-the-feminist-conspiracy-and-depression-quest
 * The Guardian http://www.theguardian.com/technology/2014/sep/01/how-to-attack-a-woman-who-works-in-video-games

Admin action

 * dialmove keep

PRIMARYTOPIC vs PRIMARYMEANING
-- no threshold -- lacking Wikt stat
 * about readers knowledge wiki structure and customs
 * meaning of common words and idioms sh b taken into account to determine primary topic
 * pageviews adequate to establish Primary (meaning)
 * Proof that base name pageviews are distorted and not in proportion to popularity of the topic: here
 * Brand New has been viewed 121163 times in the last 90 days.
 * Jesse Lacey has been viewed 31078 times in the last 90 days
 * Brand_New_discography has been viewed 9731 times in the last 90 days.
 * Your_Favorite_Weapon has been viewed 18359 times in the last 90 days.
 * Deja_Entendu has been viewed 36532 times in the last 90 days.
 * The_Devil_and_God_Are_Raging_Inside_Me has been viewed 34364 times in the last 90 days.
 * Daisy_(album) has been viewed 18634 times in the last 90 days.

Disambig: add a warning about the validity of page views

it measures the number of people that accessed each page, not the users who wanted to read about it. These may be correlated, but reliable only in these circumstances

base name is a disambiguation page

no English language common idiom or word -> no way to know if readers looked for the topic or the words

no short term rise in popularity recent event anywhere in the world

(only if the event is world-wide and steady it will show a real rise of interest - otherwise it measures the interest of just a small amount of readers)


 * pageviews

Argumentos

 * You ask: " Why would one take VSM for an explanation of why a contestant has an advantage at Q2 when Q2 contains 2 equal weighted members of the 2 Sample Space at that moment in time, at Q2 over any other reason than itself." There are two reasons:
 * 1) it is not true that "Q2 contains 2 equal weighted members of the 2 Sample Space at that moment in time"; because of the way that the two doors have been selected from a set of three doors, the members of the 2 Sample Space are not equally weighted.
 * 2) The VSM answers the question that defines the Monty Hall Problem, and the 1/2 equal weighted probability is an answer to a different question, not to the Monty Hall Problem.


 * It is not true that the solution to the Monty Hall Problem is a false dilemma. The formulation of the problem never assumes that there are only two options, this part of your reasoning is a strawman argument that you set up in order to discredit it, but it is not a flaw in the original solution.


 * The question that defines the Monty Hall Problem is, "is it to your advantage to switch your choice?", which is the same as "Is it better to always switch than any other possible strategy?" This does not imply that "never switch" is the only other possible strategy, that is something that you just made up. It is perfectly possible to compare "always switch" with "switch when a random toss coin says so".


 * In particular, if you compare those options, the problem is equivalent to "Is the probability of always switching higher than the probability of switching after a toss coin?", which means "Is 2/3 > 1/2?". As the first value is indeed higher than the second, the answer to the question formulated in the problem is "yes". I can't possibly fathom what reason has led you to believe that the "always switching" strategy should not be considered as part of the problem, when it is the question that defines the problem itself; nor why you insist that "toss a coin" is the only strategy that should be used, when the problem explicitly asks about a different strategy.


 * Of course if you change the initial conditions, you can reach different conclusions; but then you are not solving the same problem, nor answering the same question. From you reasoning it does not follow that "is it to your advantage to always switch your choice?" should be answered with "no", because along the way you have changed to a different question.

America, ese continente

 * Medios latinoamericanos con ediciones en inglés, tambien
 * Gibraltar: indecisos. Cuando esta claro por contexto que hablan de un continente, claramente usan America. ` 60 dia americano en Asturias
 * the first american pope, vaticano. pope comes from america. America = american continent (and often, America = Latin America)
 * "America" - linguistics (?) uso ,
 * "Redirect": United States of America should have hat note "America redirects here. For the continent, see The Americas"
 * ANOC The Olympic symbols. (Africa, America, Asia, Europe, and Oceania).
 * Waldseemüller map
 * Spanish language official authority - diccionario panhispánico de dudas. EEUU, Norteamérica, América
 * America y NPOV: Neutral_point_of_view/FAQ

documented controversy

 * American_(word)
 * National Geographic
 * http://listverse.com/2012/07/16/top-10-controversial-topics-about-the-us/ (selfpub)

Statistics

 * USA redirect 184644
 * US redirect 23926
 * Americas redirect 6392
 * US country (redirect) 27881


 * United States 1733205
 * The Americas 259154

Ideas for WP:UNSTABLE
-PRODding everything out of view makes sense to keep the main space neat, as this is the showcase of our work ; but the Draft space doesn't have those requirements, so it's in no need of being cleanud up so thoroughly - we can be more lenient, and keep things just in case they may be useful in the future. That's the spirit of Preserve policy and what allows the Wiki way of building content to work. -"Article space is deletionist, Draft space is inclusionist".
 * 1) Create a namespace for draft articles near the main article space (not Incubator, not User pages). First at Article/UNSTABLE (?), later adapt software to support UNSTABLE:Article (prefix U:)?.
 * 2) Treat the content at UNSTABLE with the same rules allowed at Talk - but where the only content is one draft version of the same topic.
 * WP:N, WP:NOT and WP:V (including BURDEN) are desirable, but exempt. The draft works as a collaborative AfC where alternate versions can be developed and kept for a while without risking instant deletion. WP:PRESERVE and WP:IMPERFECT are king.
 * 1) Good ideas found in the draft can be tested for WP mainspace policy compliance, and incorporated into the true article when found notable, verifiable and neutral.
 * 2) Content deleted at AfD could be UNSTABLEd, when previously would have deemed valuable for the Incubator.
 * 3) The problem of the Incubator is not that it was a bad idea, is that it was impossible to find and participate. By making it more visible we could achieve the same goals.
 * 4) Copyright rules (including NFCC) and BLP rules should have full enforcement, at least to the same degree that they are currently enforced at talk pages.


 * Draft RFC for G13 speedy criterion: Wikipedia_talk:Criteria_for_speedy_deletion/Archive_49


 * Draft RFC discussion at Village Pumpt


 * Community-wide |draft discussion against draft expiration in six months ("Unless a userspace draft is unacceptable for Wikipedia for GNG-unrelated reasons (copyright violations, self-promotion, and so on), it does not have an expiration date and does not have to comply with WP:GNG. No-hope drafts should not stick around indefinitely, but drafts with some potential should be allowed to stay.")
 * Previous STALEDRAFT rfc

Ideas art games list
We can follow several non-exclusive approaches to maintain a list, ranging the inclusion criteria, handling growth, and discussion at the talk page. Robust lists that are accepted by community have objective inclusion criteria that are easy to assess, without much place to disagreement, and are strict enough to leave as many items outside is scope as those included.

The lists for art games and games as an art form were originally a single list. It was split to and provide a clearer inclusion criteria for each. They can be split by notable subtopic (genre) or by organizational (year, country). A group of verifiable but not-notable items can be split as a companion list if the group itself has received commentary. This helps to keep the list size manageable, allowing each topic to grow at a different rate without making it unbalanced.
 * robust lists that are accepted by community have objective inclusion criteria that are easy to assess, without much place to disagreement, and are strict enough to leave as many items outside is scope as those included.
 * (At Art games we battled until we've found a balanced criterion with) critics and criticism as RSs for each item. Significant coverage=detailed description by at least one Rs (more than the one bit "belongs/not") . The difference between fancruft and encyclopedic lies in the existence of professional critics reviewing the work.
 * When the list grows, a good criterion for split allows  keep it growing while keeping a useful structure.
 * backlog of candidate (and rejected) entries at talk page
 * requiring that each entry is notable is needed at lists made for navigational purposes (when the list topic itself has not been described as a group or collection), but it's not needed when the topic is notable as a group.

Female VG characters
User:Diego Moya/Female VG characters

**Article_Incubator/List_of_female_video_game_characters_by_role - Incubated
 * Articles_for_deletion/List_of_female_video_game_characters_by_role and Articles_for_deletion/List_of_LGBT_characters_in_video_games - arguments to keep lists - preserved here: User:Diego Moya/female characters without stand-alone articles
 * User:Diego Moya/List of female video game characters by role
 * Categories_for_discussion/Log/2013_October_2

Tropes - direct coverage

 * http://www.nytimes.com/2013/12/15/arts/video-games/chris-suellentrop-on-the-year-in-video-games.html?_r=0
 * http://www.rawstory.com/rs/2013/08/01/anita-sarkeesian-explains-how-nintendo-made-pms-into-a-gameplay-mechanic/
 * http://thinkprogress.org/alyssa/2013/03/08/1690831/anita-sarkeesians-tropes-vs-women-series-is-upand-its-great/
 * http://kotaku.com/indie-games-are-full-of-helpless-women-but-critic-finds-994879878
 * http://www.forbes.com/sites/insertcoin/2013/03/08/damsel-in-distress-anita-sarkeesian-releases-her-first-video-at-last/
 * http://www.dailydot.com/fandom/anita-sarkeesian-tropes-vs-women-ms-male/
 * http://siliconangle.com/blog/2013/11/18/anita-sarkeesians-tropes-vs-women-in-video-games-part-4-looks-at-the-ms-male-character
 * http://www.cinemablend.com/games/Tropes-Women-Video-Games-Part-1-Discusses-Damsels-Distress-53412.html
 * http://blogs.houstonpress.com/artattack/2013/06/last_of_us_anita_sarkeesian.php
 * http://www.nytimes.com/2013/06/14/arts/video-games/in-the-video-game-the-last-of-us-survival-favors-the-man.html?_r=0

Sarkeesian direct coverage

 * http://www.newstatesman.com/helen-lewis/2012/12/anita-sarkeesian-and-gamification-misogyny
 * http://www.escapistmagazine.com/articles/view/editorials/10724-The-Most-Dangerous-Woman-in-Videogames-Anita-Sarkeesian.2
 * http://www.pastemagazine.com/articles/2013/11/hyper-mode-anita-sarkeesian-vs-the-world-level-2.html
 * How to review the reliability of a controversial source
 * Paul Tassi http://yesikareyes.com/2012/04/12/tagw/ http://www.forbes.com/sites/insertcoin/2013/03/12/gears-of-wars-cliff-bleszinski-pushes-back-against-anita-sarkeesian-critics/

TV Tropes NC

 * http://blog.brentlaabs.com/2013/12/the-edge-of-creative-commons.html Brent
 * http://www.projectafterforums.com/index.php?showtopic=2323&st=1640 other forum discussion
 * http://www.metafilter.com/138391/You-are-in-yet-another-maze-of-twisty-little-passages-all-alike metafilter discussion
 * http://tvtropes.org/pmwiki/posts.php?discussion=13769780670A13056100&page=1 tvtropes forum 1
 * http://tvtropes.org/pmwiki/posts.php?discussion=13691430810A90317100&page=0 tvtropes forum 0
 * http://tvtropes.org/pmwiki/pmwiki.php/Administrivia/WhatGoesWhereOnTheWiki TV Tropes classification of content
 * this.

Watches

 * Casio watches User:Diego/List of Guantanamo Bay detainees accused of possessing Casio watches and attribution Seton_Hall_reports

Discussions

 * Village_pump_(proposals)/Archive_87
 * Tablet computer  Some of the problems adduced are that the existing devices were too heavy to be held with one hand on extended periods; they had legacy applications created for desktop interfaces made them not well adapted to the slate format; and the specific software features designed to support usage as a tablet, such as virtual keyboards, digital ink and pie menus were not present in all contexts.
 * Semi-protection level 2 - pending changes RFC https://en.wikipedia.org/wiki/Wikipedia:Pending_changes/Request_for_Comment_2014
 * Two uncomfortable core questions never answered: -how removing the chapters makes the article better?(by itself, with no resort to rules) and -what is the research created (what thought is advanced)?
 * NPOV - [ https://en.wikipedia.org/w/index.php?title=Talk:Zoe_Quinn&diff=626468725&oldid=626468165 ] great criterion about neutrality and keeping sources by Wnt
 * see below Flow architecture by Wil Sinclair

Flow
http://ee-flow.wmflabs.org/wiki/Sandbox


 * This page holds only 18 unique comments! And it's 6997 pixels high. That's 388 pixels per comment. Diego (talk) 21:00, 14 October 2013 (UTC)


 * Lin - 2004 whitespace study
 * No performance improvement, better satisfaction - with whitespace around headers and titles Chaperro, Shaikh, and Baker, 2005 (pdf)


 * Birds-eye view of VG archives


 * whitespace http://boagworld.com/design/why-whitespace-matters/

http://naldzgraphics.net/design-2/11-reasons-why-white-spaces-are-good-in-graphic-design/


 * WP:Flow, Wikipedia talk:Flow


 * http://www.nngroup.com/articles/search-not-enough/ Search Is Not Enough: Synergy Between Navigation and Search

collaborative editing and structure
 * https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=prev&oldid=564887661


 * https://www.mediawiki.org/wiki/Topic:Ty37d0dagims61du "Structured discussions" are the status quo, this here is a step backwards, why this misleading rename?

Lapis parser rule for Wikipedia Talk discussions

 * https://www.mediawiki.org/w/index.php?title=Topic:Ty37d0dagims61du&topic_showPostId=tykxsbzbsaoutrv9#flow-post-tykxsbzbsaoutrv9

Thread indentation model experiment

 * Thread indentation model experiment:   (see original)
 * With images
 * image 2

Flow TOC
TOC & pagination & archiving https://trello.com/c/1Mdiy4Fn/687-table-of-contents-new-draft https://trello.com/c/D07zN08H/334-archiving-pagination

Notifications Wikipedia_talk:Notifications/Archive_5 Village_pump_(idea_lab) https://bugzilla.wikimedia.org/show_bug.cgi?id=56476 Wikipedia_talk:Notifications#Two_kinds_of_notifications

Enchanced scratchpad vs Forum boards
 * https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AFlow&diff=625736118&oldid=625733679
 * https://en.wikipedia.org/w/index.php?title=Wikipedia_talk%3AFlow&diff=625794301&oldid=625779203

Document-oriented workflow
 * https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Flow&diff=626183356&oldid=626179263 Wil Sinclair

My replies to Flow threads
My comments at the portal:


 * Mw:Thread:Talk:Flow Portal/Community consent?/reply (4) Design process a la Google
 * Informed content of users to UX user-centered design and user testing
 * Elephant in the room - no diff.


 * Prioritize content over interaction elements
 * Why news interfaces instead of conversation interfaces?

Wikimedia list
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074376.html
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074389.html
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074408.html

Other people's replies

 * https://www.mediawiki.org/wiki/Topic:S1tp3njjxiiwbu8y#flow-post-s1vpszwbitemgj4x "Community_areas is very powerful for us. If the goal is for Flow to replace article Talk pages then people are going to have very high expectations for Flow as a work space."
 * https://www.mediawiki.org/wiki/Topic:S1xn3muknquhu426 Editing other people's comments - a new angle?

Latest

 * Wikipedia_talk:Flow
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074313.html
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074361.html
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074376.html
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074433.html Erik
 * https://lists.wikimedia.org/pipermail/wikimedia-l/2014-September/074435.html Yo
 * https://en.wikipedia.org/wiki/User:Hhhippo/Flow TOC design

https://trello.com/c/1Mdiy4Fn/687-table-of-contents-new-draft


 * Discusion nueva estructura jerarquía hierarchy Flow - con comentario sobre tests iniciales

Adopted draft

 * User:Diego_Moya/Interactive_Art_and_HCI

Primary? topics

 * Boston
 * Chicago (band)
 * Richmond
 * A Corunha
 * Lorca

* The second article in the Geography category is Greater Boston, with 33785 visits in the last 90 days (aprox. 1/10 the main topic). The name originally came from Boston, Lincolnshire, whose article got 19973 visits (1/16). 

** There's an article linked from the disambiguation page, Deportivo de La Coruña with 61719 visits, but that's commonly referred to as "Depor", not "A coruña".

*** Here we have data of the redirects from users arriving to the disambiguation page by searching for the term "America"

=Knowledge=

Intangible values in Free knowledge
Attention_economy The Edge Article "BETTER THAN FREE" By Kevin Kelly published February 5, 2008


 * 0-Trust.


 * 1) Immediacy - priority access, immediate delivery
 * 2) Personalization - tailored just for you
 * 3) Interpretation - support and guidance
 * 4) Authenticity - how can you be sure it is the real thing?
 * 5) Accessibility - wherever, whenever
 * 6) Embodiment - books, live music
 * 7) Patronage - "paying simply because it feels good",
 * 8) Findability - "When there are millions of books, millions of songs, millions of films, millions of applications, millions f everything requesting our attention — and most of it free — being found is valuable."

Stored value
http://www.nirandfar.com/2012/11/the-network-effect-isnt-good-enough.html

Elements of a viral meme

 * http://www.elmundo.es/elmundo/2013/09/27/navegante/1380275242.html

S.T.U.P.I.D. users!
Or maybe they're just...


 * Stressed
 * Tired
 * Untrained
 * Passive
 * Independent
 * Distracted

Ramblings


56-bit_encryption Alef_(programming_language)

I've been working on a new draft, include the concerns from the opposition to the version in the RfC. I'm trying to emphasize actionable measures and decision criteria over subjective measures (whether a topic "merits" an article or not) that will always be a matter of personal opinion and are prone to produce division. I believe the opening sentence ("having a standalone article on Wikipedia is a matter of style") is safer than the previous proposal ("a standalone page is not required for every topic"), which was geared towards not having the article.

In addition to the previous ideas of when a notable topic should still be merged, I've added a new section with reasons for keeping the standalone article. I hope that these criteria, listed as bullet points, should stimulate direct discussion and thus facilitate agreements and consensus-building.

I'm not sure how to proceed to introduce a new draft now that the previous one is the basis for the RfC, and it's already showing some support (as well as opposition). I think it's common to first refine the new proposal to a sensible middle ground and then start a straw poll for each proposal so that clear preferences can be stated.

Draft 4

 * Standalone pages for notable topics

When a topic satisfies the notability standards, having a standalone article on Wikipedia is a matter of style and how the available information is best presented. A notable subject can be covered better as part of an article for a broader topic, including context that would be lost on a separate page. Conversely, when there is enough information to create a well balanced article, a separate page provides more room to cover the topic in depth. Subject-specific notability guidelines and WikiProject advice pages may provide information on how to make these editorial decisions in particular subject areas.

Notable topics as part of larger articles

A topic can be described in a small part of a wider article when there is not enough content for a start class article. In that situation, redirection pages and disambiguation can be used to direct readers searching for such topics to the appropriate articles and sections within them. The topic should be relevant to the content of the target article.


 * A decision to cover a notable topic only as part of a broader page does not in any way disparage the importance of the topic, as it provides the reader with the wider picture and better explains how the subject relates to the main topic. This is a good solution for topics that are notable but fall under What Wikipedia is not, such as news reports or catalog tables of reasonable size.
 * Examples: Barack Obama presidential campaign, 2012 and Mitt Romney presidential campaign, 2012, for example).


 * Several related notable topics can be collected into a single page, where the relationships between them can be better appreciated than if they were each a separate page (as at Music of the Final Fantasy VII series).


 * A future event may clearly be notable before it happens (such as the 2020 Summer Olympics), but if information is scarce at the time, coverage may instead be better suited to a larger encompassing article (see also WP:CRYSTAL).


 * A subject that is notable, but for which it is unlikely that there ever will be a lot to say, may best not be made a permanent stub.

Notable topics as standalone pages

Deciding whether a separate article is needed is often difficult for a notable topic with few reliable sources, or for which sources provide a small amount of distinct information. There are some cases where covering such topic with a short article is still a good idea:


 * Enough references describing the topic may exist, and the article is short only because the sources have not been included yet. A well placed stub for a topic with potential to be expanded can entice editors to add content and complete the article with the right format and structure, making it easier than creating the article anew.


 * There are cases where many similar notable topics exist and they cannot be collected into a single page, since the resulting article would be too long. A viable option is creating a new list or category for the broad-concept topic and linking the individual articles from it. See Category:Restaurants in New York City for an example.


 * Placing the content of a notable topic under a wider article can provide undue weight to it. That can happen with fringe theories or lesser episodes in a biography, in special for biographies of living persons. In those cases, a standalone article for the notable topic is preferred, as the content is likely to be removed from the main article.


 * Short articles should provide enough context beyond a summary or simple definition in order to explain how the topic has impacted the world, or how it was received by people that wrote about it. The reason for a topic's noteworthiness should be established, or at least introduced, so that a reader with no previous knowledge of the topic can get a rough understanding of it. This can be done including attributed value judgments from experts in the field such as reviews, critiques and academic studies. Focusing on the quality of coverage, rather than its quantity, can help to ensure that the significant content required to write a standalone article is available.


 * Wikipedia is a digital encyclopedia, and the amount of content and details should not be limited by concerns of article size. This means that all the reliable sources can be potentially included as long as they are relevant to a topic. If many independent sources provide a neutral description of the same details, the details are deemed notable and a new spinoff article can be created to hold them. A brief description in summary style can link to it from the main article, providing the same context that would be available if the standalone article didn't exist.

FLOW points of failure
Problems created by creating Wikipedia edit tools that not support a wiki platform:
 * no templates - new templates rebuilt from scratch
 * no transclusion - only the fixed structure of boards
 * no free-flow refactoring, only pre-defined use cases

Talk pages consultation 2019 finally some thoughts in the correct direction

Moya's pyramid of human-computer interaction tools
"Trascendency: thriving on the attainment of far-reaching goals and aspirations; an inherent need to evolve, improve and get better. (Paraphrased from )"

"Human2Human computer-mediated interaction":

"Human-computer interaction"

web tools
http://yeoman.io/about.html http://www.zingdesign.com/bootstrap-3-as-a-web-development-workflow-tool/


 * mmmmh... logarithmic scrollbar

Traffic jam physics

 * The Physics Behind Traffic Jams
 * How traffic actually works - "when there is excess capacity in the road behind you, i.e., the flow rate is below the theoretical maximum and the occupancy is below the critical threshold where people start caring about following distance. You might know whether such a region exists behind you because you just drove through it. So in that situation, it is actually beneficial to try to smooth out the traffic wave by driving slower as you approach it."

To Do

 * 3D agent-based games http://sgda.cs.colorado.edu/arcade/sites/all/modules/drupal_modules/ristretto3d/Ristretto3D/public/hourofcode.html?path=http://sgda.cs.colorado.edu/arcade/sites/default/files/Arcade%20Projects/Hour%20of%20Code3/AgentCubes/Open%20Arcade/0186845d-01c3-4080-99b1-87e16bbb6b2a/currentProject/0186845d-01c3-4080-99b1-87e16bbb6b2a&nid=231733&edit=true&hour_of_code=true&edit=true
 * Update content with animations: medium.com/design-ux

Why revolutions don't work
(prompted by )

That "fight for your lifes" rhetoric is number 1 tool in the dictator's manual to get people fight in their place, either the dictator-in-place or the dictator-wannabe in the opposition. This is the way that leads to war, in which everybody looses except those planning for it and encouraging it in order to make economic benefit from the strife.

Dictators have power because they're at the peak of a wide social network; the way to fight them is to remove their bases. So you don't negotiate with them, you convince their followers so that they drop their support; and you need negotiation to achieve that. Instead, if you simply rise the stakes you make the support from the basis stronger; the end result of a violent revolution is a more solid dictatorship from whomever manages to win the armed conflict.

FRP explained well


And my own take:

Mail 1 - the elevator pitch
The Functional Reactive paradigm provides better abstractions for concurrency than imperative code - futures, promises and observables are at a way higher level than locks and semaphores, and in many cases allow writing complex asynchronous code in a pure functional way. For the rest of cases, you can add explicit state and transform it into an agent-based model, which is essentially OOP parallelism done right.

So yes, I think a high-level paradigm that simplifies synchronization can make complex parallel tasks easier to program and reason about. I've seen some examples in action, of which Espresso Logic is an awesome case. ... That's like saying that building a library for P2P communication is trying to reinvent the TCP/IP protocol. Sometimes you need to look your old tools from a new perspective to adapt it for new, complex use cases that were impossible to tackle from a low level perspective.

Several mayor players as well as multiple small ones are adopting tools from FRP for their libraries and software stacks, and knowledge about the paradigm is spreading through official documentation, MMO courses and the blogosphere - which makes corner cases shallow, and deepens our understanding of the paradigm.

Mail 2 - composition and perspective
Insight: in GUI, observables and composition of streams are to events as OOP inheritance was to GUI layout and structure. The latter allowed to build components (widgets), and the former allows to build behaviors, which are reusable components of interaction ("actlets"?).

http://subbot.org/coursera/reactive/callbacks.png http://subbot.org/coursera/reactive/howtodobetter.png

I have arrived to the following intuitive way to explain why FRP and other dataflow paradigms matter.

Think first of GUIs and object-orientation: class inheritance allows you to create a hierarchy of widgets with more and more specialized behavior, and reuse the parts of code that handle common tasks like layout and redrawing. Now, you could think of this as a very complicated way to draw squares on a canvas, or realize that it breaks the GUI problem in 1) simple encapsulated components plus 2) simple glue code to bind them.

Now, I've come to believe that dataflow programming allows you to do the same thing with distributed computations and asynchronous communication. Change in the system is seen as a stream of values instead of a chain of events, which allows you to create compositions and transformations of events - in the same way that you would build complex dialogs by composing and transforming widgets in a GUI.

This complex composition of events is very difficult to reason about in imperative code, but in FRP it takes the form of reusable "behavior components" that are programmed in a simple way (clasic stateless functional composition). The hardwired inputs and outputs between static widgets and/or dynamic behaviors are automatically updated by the language runtime in the lazy, efficient way you describe above.

Does all of this makes any sense?

The best thing is that, thanks to recent theoretical advances (combined with the ever increasing computational power of new hardware), FRP doesn't seem to be that inefficient any more; and I think that's why it's beginning to spread everywhere you look at. Though it will require a lot of training on old-school developers, that's for sure!

Mail 3 - the engine vs the series of tubes
This morning I've found this list of examples in the Elm language, a FRP language which compiles to HTML+CSS+Javascript:

http://elm-lang.org/Examples.elm

The Intermediate section include a bunch of examples that are considered quite difficult in classic functional programming (video games & animation), but FRP seem to handle those very well.

The Mario and Turtle examples follow a rather intuitive structure - declare your variable structures, then define your methods for behavior (with a very imperative flavor to them - first find the image for the canvas, then rotate it, then place it on its coordinates), and connect the input devices to the model logic.

The trick is that the behaviors don't really destroy the previous value of their variables. You can use a variable as a scalar (e.g. "the x and y coordinates *right now*") but it's often useful to think of them as collections.

Each variable contains an infinite vector with all values that the variable takes during runtime, generated from one stream or a combination of them ("all mouse clicks or keyboard presses"). You can access past and future values or apply filters over the whole collection, and the efficient language VM will make sure that the current value of the stream is propagated to whatever part of the program where it's used (such as updating the screen).

Expressing the same in an imperative language would require building a state machine that keeps track of what has happened before in the sequence of values for the variable, or storing and updating in memory the collection of previous values by yourself. With FRP, those common programming aspects are encapsulated and easy to express in the language.

Of course, the glue code will take a totally different shape; in the imperative paradigm, you think of the language virtual machines as very complex state machines that consume their inputs, update their internal state by destroying the previous one, and spit new generated values by changing the state of the output devices (i.e. changing the world itself). Glue code takes the form of sequential subroutines that give orders to the machine as to what state to go next, and the pass of time is represented by moving to the next instruction in the sequence.

Instead, in dataflow languages, the virtual machine is a spreadsheet-like environment that allows you to draw directed graphs that connect components together (in a spreadsheet you can see the graph by drawing arrows between each cell and all its dependencies). Program execution consists of connecting the inputs to a data storage and waiting for the results to appear at the opposite side, and the pass of time is represented by accessing values that are positioned later and later in their streams.

Criticism

 * "But it's just streams, not a new thing at all"

It depends on perspective. If you see it as a tacked-down library on top of an interactive language, of course it's smallish. But from that perspective, OOP is just high-order functional programming plus cells, so it's not a big thing either, true? It's "just a big name for the concept of state".

The thing with programming paradigms is not that they introduce whole new constructs, it's the way they make you think about them. Any paradigm will reuse the same old basic elements available in all previous programming styles, and explain them in a new way that makes sense.


 * "It can't be used everywhere, so it's not a paradigm" (plus, state machines are the same thing).

But that's the thing, if you program in RFP you *don't have* state machines, it's streams all the way down. If you study RFP as a mathematical way to describe program execution, like PL people do, it's a whole new theoretical construct, with its own set of axioms. The formal semantics of an RFP language will look different than those from an imperative language, which look different than those from a functional or a logic language.

Surely you *can* think of the language implementation as being a program written in a different, old paradigm (which negates any benefit provided by the new, btw), but you don't *need* to; any Turing-complete language can be transformed into any other. I've seen languages for programming micro-controllers based on the lambda calculus, with no notion of state, if that's your thing.

You wouldn't use dataflow programming for calculating a concurrent constraint satisfaction problem (or maybe you would, but it will be more difficult), as you wouldn't use a constraint logic solver to program a platformer game. When you find a paradigm that is well suited to the problem to solve, there's little use in thinking of how that paradigm translates into a different, less adequate paradigm.

See [1] for how different paradigms relate to each other (taken from [2]); the difference from one paradigm to another is always minimal, but they make the language feel completely different.

[1] http://en.wikipedia.org/wiki/File:Programming_paradigms.svg [2] "Programming Paradigms for Dummies: What Every Programmer Should Know", http://www.info.ucl.ac.be/~pvr/VanRoyChapter.pdf

= Subpages =
 * https://en.wikipedia.org/wiki/Special:PrefixIndex?prefix=User%3ADiego_Moya&namespace=0
 * User:Diego_Moya/List of console adventure games