並び順

ブックマーク数

期間指定

  • から
  • まで

1 - 9 件 / 9件

新着順 人気順

please tell me whyの検索結果1 - 9 件 / 9件

  • No Way, PHP Strikes Again! (CVE-2024-4577)

    Orange Tsai tweeted a few hours ago about “One of [his] PHP vulnerabilities, which affects XAMPP by default”, and we were curious to say the least. XAMPP is a very popular way for administrators and developers to rapidly deploy Apache, PHP, and a bunch of other tools, and any bug that could give us RCE in its default installation sounds pretty tantalizing. Fortunately, for defenders, the bug has o

      No Way, PHP Strikes Again! (CVE-2024-4577)
    • The History of 18+ VTubers: Part 1

      Hello again. Obviously, this article deals with adult topics, so don’t read it if you’re under 18. I won’t have any super explicit images on screen, but I don’t recommend reading this in public nonetheless. With that out of the way, I wanna preface this piece with some thoughts. The goal of this Substack is to record parts of VTuber history that have been forgotten or aren’t well known, in a way t

        The History of 18+ VTubers: Part 1
      • This is why you should never use parser combinators and PEG

        Let me tell you why you should (nearly) never use PEG (parsing expression grammars). Nearly everything I will say applies to parser combinators (parsec in Haskell, nom in Rust), too. So, don't use PEG. Use CFGs (context-free grammars) instead. They are more natural. I feel that CFGs more naturally represent how we think. Thus when you have some language in your head and you try to write it down as

          This is why you should never use parser combinators and PEG
        • Engineering for Slow Internet – brr

          Engineering for Slow Internet How to minimize user frustration in Antarctica. Hello everyone! I got partway through writing this post while I was still in Antarctica, but I departed before finishing it. I’m going through my old draft posts, and I found that this one was nearly complete. It’s a bit of a departure from the normal content you’d find on brr.fyi, but it reflects my software / IT engine

          • xavxav - Visions of the future: formal verification in Rust

            May 22, 2024 In response to a recent Boats article, I mentioned that Rust’s type system drastically changes things for verification. This comment seems to have aroused a lot of interest, so I figured I’d expand on it, explaining how Rust simplifies formal verification and why this had the verification community excited for a while now. I assume that most of you reading this post won’t be experts i

            • Akiya in Japan: How to Buy Cheap Abandoned Houses

              We have long heard that houses in Japan are expensive. Then, all of a sudden, someone tells you that you can buy a cheap house in Japan. Imagine the waves such a statement will cause. The same thing happened with the Akiya phenomenon in Japan. Akiya, or abandoned cheap houses, has always existed in Japan. However, lately, this has become a buzzword, especially among foreigners, both in and out of

                Akiya in Japan: How to Buy Cheap Abandoned Houses
              • Things you wish you didn't need to know about S3

                Daniel Grzelak May 30, 2024 2 min read Things you wish you didn't need to know about S3 A time travel paradox in the title is a good place to start a blog post, don’t you think? You don’t yet know the things you need to know so you can’t wish you didn’t need to know them. There is a solution though – Read this blog post. This all started because Plerion is trying to build a comprehensive risk mode

                  Things you wish you didn't need to know about S3
                • Rust's iterators optimize nicely—and contain a footgun | nicole@web

                  I saw a claim recently that in functional programming using "map/filter iterates over the list twice, while the foreach loop iterates only once." The author continued that "Haskell can fuse maps together as an optimization but I don't think you safely fuse arbitrary map/filters? I dunno." There are really two claims here: in functional programming, map/filter will do two iterations there is an opt

                  • Askar Safin

                    This is why you should never use parser combinators and PEG June 2, 2024 Let me tell you why you should (nearly) never use PEG (parsing expression grammars). Nearly everything I will say applies to parser combinators (parsec in Haskell, nom in Rust), too. So, don't use PEG. Use CFGs (context-free grammars) instead. They are more natural. I feel that CFGs more naturally represent how we think. Thus

                    1