P. Oscar Boykin

@posco

Human. formerly , . Programming, Hadoop, Scala, co-author of , , husband of , father of .

Maui
Vrijeme pridruživanja: rujan 2007.

Tweetovi

Blokirali ste korisnika/cu @posco

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

  1. Prikvačeni tweet
    4. ruj 2015.

    Young , here is your copy of TAOCP, vol 1, which belonged to your father and his father before him.

    Poništi
  2. prije 5 sati

    Why programming language X was right for my project: a post-hoc justification of my social group’s aesthetic preferences framed as an engineering exercise.

    Poništi
  3. proslijedio/la je Tweet
    2. velj

    Read the horror that is Scott Aaronson's account of how quantum computing is discussed at Davos: Here is a quote from a senior vice president at IBM:

    Poništi
  4. 1. velj

    Most Americans would be in revolt if they understood wealth distributions and where they are their loved ones are in those distributions.

    Poništi
  5. 1. velj

    Wouldn’t any unscrupulous advisor to Trump advise him to start planning to meddle in the election? Why shouldn’t he? His deep principled commitment to democracy? Congress or the courts would intervene? I’m not seeing the downside here?

    Poništi
  6. 1. velj

    Reminds me of a joke I saw on here: “how dare you burn the flag of the nation I’m hoarding guns to defend myself against”

    Poništi
  7. 31. sij

    did you know if you change a semigroup from combine(a, b) to combine(b, a) it is still associative? Also you can glue items between and stay associative: combine1(a, b) == combine(a, combine(middle, b)) -- PR to add to cats:

    Poništi
  8. 31. sij

    Are any TVs using deep neural nets to do upscaling or frame interpolation?

    Poništi
  9. 30. sij

    I bet there are R senators that believe: 1. It is bad if I’m not a senator 2. I don’t have the power to impeach Trump and if I support it I lose my seat 3. Since we can’t remove Trump it damages the republic least to not have witnesses vs stronger evidence then acquittal.

    Poništi
  10. 29. sij

    In decades past, universal basic income seems like it would be a conservative idea for a safety net: let the individual direct the money, not bureaucrats, and reduce size of government administration. Lastly, it is uniform across everyone, something conservatives usually like.

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

    We all want to help address the climate crisis. But it’s such a complex issue that it can be hard to distinguish between data-backed improvements and feel-good distractions. So here's your data-backed guide:

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

    10. My real interest is a data-artifact build system: today's artifacts depend on yesterday's artifacts plus the events that just came in. A principled system like Bazel (your build as a pure function) plus a time-axis could represent a real advance for data workflow systems.

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

    9. Bazel should add more ease to making hermetic repo rules, the only rules that can do network access. Unfortunately, the obvious approach requires dynamic graphs, which the bazel developers are loathe to expose to users. Without that, repo-rules have to fetch magic binary tools

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

    8. By assuming you are on the JVM, you can make fetching maven/ivy artifacts first class. It makes the model a bit less general, but in practice MUCH more easily usable.

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

    7. Bazel is more similar to Make than to Maven: it basically understands nothing of external packages. Modern build tools generally conflate package management with build. Due to bazel's static graph API, writing hermetic package management in bazel is a serious challenge.

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

    6. In Bazel all tools are native binaries, but we also want total reproducibility, so setting up toolchains (e.g. c compilers) is a big pain and a source of non-reproducibility. My system makes all tools jars, and builds jars, so the problem is FAR simpler and easily explained.

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

    5. Bazel tries to elide when you are dealing with a Record, a Build[Record], a string that is a path, or a string that is a label for a build output. This confusion makes it challenging to write complex plugins for bazel which must be done in an untyped python subset language.

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

    4. So, I'm doing a few things: first, use a typed language to describe builds. We have a Build[A] type that is sort of like a Future but for builds. If we are forced to write types on all our builds a lot of bazel's magic (and difficulties) evaporate.

    Prikaži ovu nit
    Poništi
  19. 28. sij

    3. So why write a new build system? My main motivation is to explore key design elements from Bazel in a simpler setting with the aim to make them better known and more widely applied. The build problem (more generally processing DAGs of tasks) is very general yet ignored by many

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

    2. There are many downsides to using Bazel, and those can be summarized around a few problems: Google owns development and external contributors are 2nd (or 3rd) class citizens. A high churn rate: you deal with constant deprecations/breakages/redesigns. Ergonomics are at best ok.

    Prikaži ovu nit
    Poništi
  21. 28. sij

    1. is IMO the best choice for a build system if you a very large codebase you want to build entirely from source, or even if you don't have a large codebase but you have many different languages (some Go, some Java, some Python, some C, some C++, some ....)

    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:

    ·