Devon C. Estes

@devoncestes

dev at . International software person. “The Clark Griswold of programming.”

Berlin, Germany
Vrijeme pridruživanja: svibanj 2009.

Tweetovi

Blokirali ste korisnika/cu @devoncestes

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

  1. prije 1 sat

    Each of those colors represents 2 reductions (1 to call the function and 1 to return), and yet that red one is executing at least an order of magnitude more instructions than the others!

    Prikaži ovu nit
    Poništi
  2. prije 1 sat

    For example, this is some real BEAM assembly for a module. Since it's basically impossible to read, I've adding some color to show which represents individual functions. Seeing this, of _course_ reductions don't take the same amount of time to execute!

    Prikaži ovu nit
    Poništi
  3. prije 1 sat

    Ok, thanks to 's awesome decompiler package, I've figured this out. Each reduction corresponds to a function call or return, but a single function call can have any number of BEAM VM instructions in it, meaning they take a variable amount of time!

    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    prije 19 sati

    I've been surprised that there isn't a more direct correlation between reduction count and wall-clock execution time for a function. Anyone know where I can read more about why some reductions appear to execute faster than others, and what those kinds might be?

    Poništi
  5. proslijedio/la je Tweet
    Poništi
  6. proslijedio/la je Tweet

    Meanwhile, in Silicon Valley...

    Poništi
  7. prije 19 sati

    I've been surprised that there isn't a more direct correlation between reduction count and wall-clock execution time for a function. Anyone know where I can read more about why some reductions appear to execute faster than others, and what those kinds might be?

    Poništi
  8. prije 23 sata

    Imagine that there's an existing (private) API that you need to extend. You see there is a "bad" pattern there (like a GET request inserting records in the database). Do you stick with this pattern to stay consistent, or do the "right" thing even though it's inconsistent?

    Poništi
  9. 3. velj

    Would it be a controversial opinion to think that all functions in your application should have a known purpose at compile time? Basically, they should either be clearly called in your app, or be part of a behaviour implementation.

    Poništi
  10. proslijedio/la je Tweet
    Poništi
  11. 31. sij

    ‚with‘ is without question Elixir‘s most complicated form of control flow, and other than brevity it offers nothing to developers.

    Prikaži ovu nit
    Poništi
  12. 31. sij

    Oh, hey, it‘s everything I don’t like about ‚with‘ summed up in one nice Issue! Maybe after a few more changes like this I’ll actually like using it.

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

    I really want to send Seth & Jonathan from some of these alcohol-free protein beers. This seems like just about the wildest thing someone could dream up.

    Poništi
  14. 30. sij

    Nobody's ever gonna invite me back on their podcast if I don't learn to speak more clearly, slowly and concisely. I just ramble on so long... I still have fun doing it, though, and that's what really matters I guess!

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

    Meanwhile, in Michigan...

    Poništi
  16. proslijedio/la je Tweet
    29. sij
    Poništi
  17. 29. sij

    I always had this feeling that there must be two Josés out there because of how fast he was, and I think we finally have proof.

    Poništi
  18. 29. sij

    These kinds of pieces are great to have as most (business) people‘s fear about adopting Elixir is „nobody uses it.“ This is the best kind of stuff to help with adoption.

    Poništi
  19. 29. sij

    And don't get me wrong - it's totally ok to adopt the "do no harm" approach and not be ok with your software being used for things you don't agree with! But you need to know that if that's important to you, then contributing to open source isn't an option.

    Prikaži ovu nit
    Poništi
  20. 29. sij

    If you think suing people who violate your license is going to solve the problem, think again. This is only used by big companies to sue other big companies. You'd bankrupt yourself suing Palantir.

    Prikaži ovu nit
    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:

    ·