indygreg

@indygreg

Version control and build system guru. Avid cyclist and skier. Cheese and beer connoisseur. Former Mozillian. Currently at Airbnb. Views here are my own.

San Francisco, CA
Vrijeme pridruživanja: srpanj 2008.

Tweetovi

Blokirali ste korisnika/cu @indygreg

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

  1. 2. velj

    This bar in the heart of Hayes Valley is packed to the gills to watch

    Poništi
  2. 2. velj

    I was nearly run over by a car turning right from Hayes onto Gough who was trying to beat the pedestrian crosswalk signal. I have no clue why right on red isn’t banned and there’s no green light delay given the high pedestrian foot traffic at this intersection. cc

    Poništi
  3. 2. velj

    It took me several hours to figure out how to bootstrap pip in a secure and reproducible manner: . Security and determinism in packaging tools should be table stakes and I'm disappointed Python makes this so difficult.

    Poništi
  4. 2. velj

    Do you use to bootstrap Python's packaging tools? Did you know its behavior isn't deterministic and it doesn't verify hashes of files it downloads from the Internet? Now you do:

    Poništi
  5. 31. sij

    The compiler error occurred after I had been using the trait. Only once I introduced some pattern involving dyn Trait did I get an error due to missing &self. I have no clue where this restriction originates. Should something warn if trait contains mix of static and method funcs?

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

    I’ve been using Rust (casually) for over a year and just started implementing my own traits and using Box<dyn Trait>. I ran into an issue where I couldn’t use dyn Trait somewhere because not all trait functions accepted &self. 1/

    Prikaži ovu nit
    Poništi
  7. 27. sij

    PyOxidizer 0.5 is out! I view it as a transitional release in order to realize the shift to Starlark configuration files. There are some rough edges and regressions. The eventual 0.6 should hopefully restore feature parity and much more. Release notes at .

    Poništi
  8. 26. sij

    A working using PyOxidizer on Windows! Still a few bugs to work out, but it is mostly there!

    Poništi
  9. 25. sij

    For the umpteenth time, I with Python had actual language specifications instead of a labyrinth of PEPs + CPython as the reference implementation. There should be canonical specifications and a PEP should be a diff to specifications + change rationale.

    Poništi
  10. 23. sij

    looks like an interesting Git tool to facilitate monorepo workflows. Implemented in Rust too!

    Poništi
  11. 21. sij

    Update: drops 5-6ms from startup time by expanding the scope of the lazy module importer!

    Poništi
  12. proslijedio/la je Tweet
    19. sij

    Git 2.25 just shipped with effective support for "sparse clone". I've been talking about the need for that for a while now. Here's my list of features for an ideal VCS in 2020:

    Poništi
  13. 18. sij

    Before anyone asks, Mercurial's demand importer doesn't work on Python 3.5, hence why its timings are bad.

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

    Python 3 startup overhead regressions as told through Mercurial. If you care about low-latency processes (CLIs, frequently-called scripts in build systems, etc), you may want to avoid Python.

    Prikaži ovu nit
    Poništi
  15. 18. sij

    I take pride in knowing about obscure constraints in operating systems. But it was only today that I learned about a ETXTBSY race in UNIX platforms related to executing a just-written file.

    Poništi
  16. 16. sij

    If you are looking for a company with a similar operating mentality and ethos as Mozilla, Cloudflare and GitLab would be on my short list.

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

    Feeling sad for the entire Mozillians community tonight. For those affected (or looking for an exit), your time at Mozilla opens lots of doors. Reach out if you'd like some guiding towards some.

    Prikaži ovu nit
    Poništi
  18. 15. sij

    Either my Mercurial Python 3 porting post didn't make the point well enough or a lot of commenters don't seem to have a grasp of the complex and difficult trade-offs involved in maintaining large software projects.

    Poništi
  19. 14. sij

    I usually try to avoid replying to HN comments on content I write. But sometimes the setup for a zinger is just too perfect to pass on.

    Poništi
  20. 13. sij

    Update: take that Sam Altman :p

    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:

    ·