Skip to content

Create language/notable-design-decisions page #1002

Closed

Description

@AlexDaniel

Another item originating from #728.

When I started using Perl 6, I really enjoyed stuff like this: https://perl6advent.wordpress.com/2014/12/24/day-24-seeing-wrong-right/. I think it helped me see why some things are this way and not another. Also, who knows, maybe this page could give people more incentive to be open-minded to stuff like sigils.

Activity

  1. added
    docsDocumentation issue (primary issue type)
    on Oct 30, 2016
  2. added
    wishlist"nice to have" issues; might require a lot of work or a big change or be low priority
    on Dec 2, 2016
  3. changed the title [-]Create language/notable-design-desicions page[/-] [+]Create language/notable-design-decisions page[/+] on Jan 9, 2017
  4. JJ commented on May 6, 2018

    @JJ
    Contributor

    Not sure about this one. Design decisions are probably implementation-dependent, and thus should go to rakudo. Will this help Perl 6 users in some way? Not sure, but probably not.
    Then there's the problem on how to document those decisions. Unless whoever took the decision does it, it's probably impossible for the average perl6/doc contributor to find that out. So if you don't feel strongly about this, I'm for closing it.

  5. AlexDaniel commented on May 6, 2018

    @AlexDaniel
    MemberAuthor

    Design decisions are probably implementation-dependent, and thus should go to rakudo.

    I am talking about language design decisions, and that can only fit language docs.

    Will this help Perl 6 users in some way?

    I think understanding why-s can help a lot when learning a language.

    Unless whoever took the decision does it, it's probably impossible for the average perl6/doc contributor to find that out

    It is still possible to talk about pros and cons, and then ping one of the Larrys to check if it's correct and if there's anything to add.

  6. added
    bigIssue consisting of many subissues
    on May 6, 2018
  7. JJ commented on May 6, 2018

    @JJ
    Contributor

    Then we'll have to do two (big) things here:

    • Identify which are the notable design decisions we want to talk about
    • Document them
  8. removed
    docsDocumentation issue (primary issue type)
    on Nov 14, 2022
  9. locked and limited conversation to collaborators on Feb 4, 2023
  10. converted this issue into a discussion #4190 on Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bigIssue consisting of many subissueswishlist"nice to have" issues; might require a lot of work or a big change or be low priority

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions