Chronotope’s avatarChronotope’s Twitter Archive—№ 70,318

                              1. This project doesn't use semicolons, b/c overly formalize functions, css names and file structures but don't bother with formal line endings
                            1. …in reply to @Chronotope
                              Seriously, do you ever get the feeling 90% of the javascript community styles projects b/c they like just heard an idea from a guy once?
                          1. …in reply to @Chronotope
                            Please explain to me how building and using entire packages on formal typing but not doing formal line endings makes sense?
                        1. …in reply to @Chronotope
                          This is the shit I'm talking about... do you think someone is just sitting out there thinking up ways to make javascript less clear?
                      1. …in reply to @Chronotope
                        Some people must be sitting out there saying to themselves 'no one will respect javascript because it isn't arcane enough, let's fix that'
                    1. …in reply to @Chronotope
                      Seriously, you know where this ends, everyone using anything but javascript to write javascript. Write it with Go! github.com/bep/gr
                      OpenGraph image for github.com/bep/gr
                  1. …in reply to @Chronotope
                    Or write Javascript with oCaml github.com/bloomberg/bucklescript ! Because people can't tell what the best practice way to write actual JS is
                    OpenGraph image for github.com/bloomberg/bucklescript
                1. …in reply to @Chronotope
                  Seriously, tho, I can't even find two React/Redux projects that look marginally similar. Sometimes being verbose in your code is useful...
              1. …in reply to @Chronotope
                ... because verbose code explains itself and its standards and makes it clear what those standards are. And we're compressing this anyway!
            1. …in reply to @Chronotope
              I dunno, mby I'm being grumpy because I used to be able to type an input field w/html and now it takes 8 libraries and 3 files.
          1. …in reply to @Chronotope
            I get it is about prepping to scale up, and I love React and the idea of Flux & company etc... etc... but surely there is some better way?
        1. …in reply to @Chronotope
          I really should port my projects to TypeScript, which at least expresses types formally, but damn, just another thing to add to the stack.
      1. …in reply to @Chronotope
        I think the worst offense in all this is that JavaScript was never a particularly DRY language, but it seems to be getting even less so.
    1. …in reply to @Chronotope
      Look, we all have auto complete. Doing something like making .bind less verbose with fat arrows isn't any more DRY than doing it verbosely
  1. …in reply to @Chronotope
    Javascript is now, in practice, always going to have a build task. So dropping characters from typed code is fundamentally pointless.
    1. …in reply to @Chronotope
      I know, *I know*, that we're still in the process of fundamentally reinventing JS, that this is all transient and unfinished, but still.


Search tweets' text