just-boris

@boriscoder

Welcome to T H E I N T E R N E T !

Berlin, Germany
Vrijeme pridruživanja: lipanj 2012.

Tweetovi

Blokirali ste korisnika/cu @boriscoder

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @boriscoder

  1. 2. velj

    If fact, they do and it is more damaging. In the case of React, you can pin a legacy version and stick to that. With WebComponents, browsers force you to do an upgrade, because old API will be removed and your website will break

    Prikaži ovu nit
    Poništi
  2. 2. velj

    If your team chooses React, you are required to analyze risks: * How hard would it be to upgrade to a new version? * What if the React team would abandon their project? With web-components you are getting some kind of blessing as these issues would never happen.

    Prikaži ovu nit
    Poništi
  3. 2. velj

    Today I learned/recalled that there was a big breaking change in CustomElements spec: Damn, this list of breaking changes is bigger than upgrading from React 15 to 16

    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    2. velj

    All Palindromes: – ISO date: 2020-02-02 – German date (DD.​MM.YYYY): 02.02.2020 – USA date (MM/DD/YYYY): 02/02/2020

    Prikaži ovu nit
    Poništi
  5. 1. velj

    Unwinding: npm test -- -- -- -u lerna run test -- -- -u [in package] npm test -- -u [in package] jest -u

    Prikaži ovu nit
    Poništi
  6. 1. velj

    Updating all snapshots in a monorepo via lerna: npm test -- -- -- -u 🙄

    Prikaži ovu nit
    Poništi
  7. proslijedio/la je Tweet
    23. sij

    Of course, today’s web component libraries don’t suffer from this. And people enjoy them! But it’s a curious reversal of roles. When something “built on standards” and with a 1.x version tag might be more fleeting than 0.x experiments.

    Prikaži ovu nit
    Poništi
  8. 23. sij

    * At first they convince you to use their new modern framework * This framework relies on non-standard apis * Then they use you as an argument to protect their api from changing Please avoid using lit-element, it is damaging the web

    Poništi
  9. proslijedio/la je Tweet
    22. sij

    Folks! I'm happy to share what we've been working on: 📣 Playwright is like Puppeteer, but cross-browser.

    Poništi
  10. proslijedio/la je Tweet
    16. sij
    Everything works in every browser. Except server rendering. Oops.
    Poništi
  11. 15. sij

    AWS is looking for web developers with a focus on accessibility. Join our team and make interfaces better for everyone!

    Poništi
  12. 13. sij

    And another example, They claim that bundle is not required, and have rollup in their dependencies.

    Prikaži ovu nit
    Poništi
  13. 13. sij

    Marketing is all over frontend packages now. Fun part about „no breaking changes“. If there is none, why is this a major version bump

    Prikaži ovu nit
    Poništi
  14. 8. sij

    Spoiler: they are mostly about cross-browser support

    Poništi
  15. proslijedio/la je Tweet
    6. sij

    oops I made a minimap for webpages

    Prikaži ovu nit
    Poništi
  16. 5. sij

    Hooray, instead of setting NODE_PATH or use other tools, you can now require a module from your own package starting the import from the package name

    Poništi
  17. proslijedio/la je Tweet
    3. sij

    A .gitignore in a project should only cover artifacts caused by the contained source code, not those caused by the personal choice of editor and/or environment of a developer.

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet

    Your periodic reminder that using map/filter/reduce instead of a for loop doesn't automatically make your code better.

    Poništi
  19. proslijedio/la je Tweet
    19. pro 2019.

    I think people are exaggerating here.

    a chart of 'CSS proficiency' where most candidates say they are experts in CSS or 'intermediate'. From the stateofjs.com
    Poništi
  20. 19. pro 2019.

    The data visualization in the report is very awful. Look at this wonderful growth of React from 91% to 89%!

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·