gbrown_

129 ms·

1. 661.▲
   by gbrown_ 9y ago

   Agreed. I carry the personal view that when someone says "text editor" they are implicitly implying plain text. As such the leading paragraph of the article makes me twinge a little when "text editor" is used rather than
2. 662.▲
   On Ways to Agree, Part 2: Path to Atomic Broadcast(medium.com)

   17 points by gbrown_ 9y ago|1 comments
3. 663.▲
   by gbrown_ 9y ago

   The images really need to be larger or at the least be available in a higher resolution.
4. 664.▲
   How Lua Banished the Semicolons(dev.to)

   1 points by gbrown_ 9y ago|0 comments
5. 665.▲
   Scaling throughput processors for machine intelligence [video](graphcore.ai)

   1 points by gbrown_ 9y ago|0 comments
6. 666.▲
   by gbrown_ 9y ago

   OpenBSD's patch handles ed style diffs internally now and also it is not permitted to execute other programs thanks to pledge. https://marc.info/?l=openbsd-cvs&m=144498099601083&w=2
7. 667.▲
   Explain Types (In Programming) as If I Was a Normal Person(medium.com)

   1 points by gbrown_ 9y ago|0 comments
8. 668.▲
   Consistent Hashing: Algorithmic Tradeoffs(medium.com)

   2 points by gbrown_ 9y ago|0 comments
9. 669.▲
   BranchScope: A New Side-Channel Attack on Directional Branch Predictor [pdf](cs.ucr.edu)

   2 points by gbrown_ 9y ago|0 comments
10. 670.▲
    by gbrown_ 9y ago

    The base 60 Sexagesimal system used by the Sumerians is always an interesting one. https://en.wikipedia.org/wiki/Sexagesimal
11. 671.▲
    LibBF – a small library to handle arbitrary precision floating point numbers(bellard.org)

    159 points by gbrown_ 9y ago|60 comments
12. 672.▲
    Analysis of Concurrent Lock-Free Hash Tries with Constant-Time Operations(arxiv.org)

    2 points by gbrown_ 9y ago|0 comments
13. 673.▲
    Capability-Based Type Systems for Concurrency Control [pdf](uu.diva-portal.org)

    2 points by gbrown_ 9y ago|0 comments
14. 674.▲
    Jump Over ASLR: Attacking Branch Predictors to Bypass ASLR [pdf](cs.ucr.edu)

    2 points by gbrown_ 9y ago|0 comments
15. 675.▲
    Managing Speculation on AMD Processors [pdf](developer.amd.com)

    4 points by gbrown_ 9y ago|0 comments
16. 676.▲
    Efficient Functional Programming Using Linear Types: The Array Fragment [pdf](lopezjuan.com)

    3 points by gbrown_ 9y ago|0 comments
17. 677.▲
    by gbrown_ 9y ago

    Surely this is in breach of Nvidia's updated EULA for GeForce drivers?
18. 678.▲
    Optimizing Tagless Final – Saying Farewell to Free(typelevel.org)

    2 points by gbrown_ 9y ago|0 comments
19. 679.▲
    Debugging Emacs Or: How I Learned to Stop Worrying and Love DTrace(nullprogram.com)

    3 points by gbrown_ 9y ago|0 comments
20. 680.▲
    /proc/pid/stat is broken(lobste.rs)

    1 points by gbrown_ 9y ago|0 comments
21. 681.▲
    by gbrown_ 9y ago

    The final paragraph caught my eye also with the "disclosure at this time". Understandably Mill presentations have followed the team securing patents so we may see more details on this later. Not sure if anyone from the Mill team m
22. 682.▲
    by gbrown_ 9y ago

    Do you not think it's reasonable to believe that the Mill is immune to these flaws without hardware given the information presented in this paper?
23. 683.▲
    When Are Lexer Modes Useful?(oilshell.org)

    2 points by gbrown_ 9y ago|0 comments
24. 684.▲
    Wandering through linear types, capabilities, and regions [pdf](pauillac.inria.fr)

    1 points by gbrown_ 9y ago|0 comments
25. 685.▲
    Zip-Folding(benjamin.pizza)

    1 points by gbrown_ 9y ago|0 comments
26. 686.▲
    by gbrown_ 9y ago

    > Team Mill - we're immune too and will put out a light paper on how these attacks apply to in-order processors that support speculation and what we're doing to prevent them Will this be sent to the mailing list when released?
27. 687.▲
    by gbrown_ 9y ago

    This is the real question, too many people seem to be blindly throwing around "Regression of X%". Phoronix have put out some benchmarks for Linux [1][2]. As one may expect I/O seems to be hit noticeably given it's handle
28. 688.▲
    by gbrown_ 9y ago

    The links for libcrypto, libssl, libtls, openssl(1), nc(1), and ocspcheck(1) all go to online man pages.
29. 689.▲
    by gbrown_ 9y ago

    > Please tell me where the very first OpenSSL link takes you. That's the one I clicked just to check. Are you referring to the line informing the reader that LibreSSL is a fork and provides a link the the OpenSSL project?
30. 690.▲
    by gbrown_ 9y ago

    > there literally isn’t any documentation of LibreSSL. This is plain wrong, it's particularly annoying as a great deal of effort has been put into updating the documentation [1]. > Instead, you just have to read the OpenSSL docs,