• 0 Posts
  • 93 Comments
Joined 3 years ago
cake
Cake day: July 5th, 2023

help-circle


  • It’s been a while, but the last time I checked, the Australian censorship board primarily limits works which can be sold in Australia. I believe that it’s explicitly legal for adults to own anything that doesn’t break any other laws (including decency and pornography laws, but those are surprisingly not terrible IMO), provided that they don’t buy it in Australia.

    There are also some laws about using the postal service to transmit classified works, but I think they’re less restrictive; for decades there was a thriving mail-order pornography trade based in the ACT (which had more relaxed censorship than the other states).


  • The most insidious part of OneDrive and Google’s equivalent (Photos, etc.) on Android is that they both treat the cloud copy as the “original” and the local copy as temporary. That is, in normal usage, if you delete the local copy it remains in the cloud, but if you delete the cloud copy it also deletes the local copy automatically. Under both systems, if you want to delete something from the cloud but keep the local copy, you have to go through a separate, clunky web interface.




  • There’s a whole lot of math in that article, and to be honest I’m not 100% clear on what they’re trying to say. I think they’re talking about how standard quantization isn’t making full or “accurate” use of the number space, although if you read through to the end they note that there’s really nothing terribly wrong with the standard way. But here’s my take.

    To simplify, I’ll use an integer range 0-4 instead of 0-255, but the principle’s the same.

    So, say that we’re quantizing from a floating-point range of 0.0-1.0 to an integer range of 0-4. Doing things the usual way, that’d be the orange numbers on the bottom of this diagram:

    But you can see that this doesn’t line up cleanly with a nice, regular division of the range into 5 equal blocks. If we just multiply by 4 (our integer max) and then round off to the nearest integer, the original value ranges represented by our integer 0 and 4 are half the size of the others. E.g. 0.0 to 0.49 become 0, but 0.5 to 1.49 become 1.

    Now, if we want to represent true 0.0 and 1.0 simply with our integer range (0-4), we should use 0 to exactly equal 0.0, and 4 to exactly equal 1.0. And converting from integer to float by calculating [value / 4] (or [value / 255] in reality) will get us exactly that. I wouldn’t change that.

    What I would suggest changing–to anyone who cares enough about it–is how the numbers are converted from float to integer. If you look at the diagram again, you can see that there is one orange integer per evenly-divided block, even if they don’t line up with the centers of the blocks. If we take a float (0.0-1.0) representation and multiply it by our integer max plus one, we’ll get the blue numbers at the top of the diagram. Then all we have to do is round down to the nearest integer and cap the result at 4 (or 255, or whatever our integer max is), and we’ll have a nice, even distribution in our conversion.

    I could have misunderstood, but it seems like all of the errors and uncertainty discussed in the article come from how the multiplied floats are truncated into integers. I think that this method eliminates that cleanly.



  • Surely it shouldn’t be surprising that a technology which literally can only regurgitate bits of things which others have already made, when put into the hands of people whose imagination is limited to what already exists (or alternatively, is not meaningfully directed) precisely because they lack an understanding of the underlying principles, results in only slight variations of the things we already have.

    I can’t immediately give you a smartphone app concept that completely breaks an existing, arbitrary taxonomy, but there are two good reasons for that. One; anything that can still run on a smartphone can almost certainly be shoehorned into any existing taxonomy by carefully-worded arguments. Two; by the time a break with tradition is clear enough that such arguments become impossibly tenuous, smartphones will be things that our great-grandparents used to use.

    To counterpoint the author’s smartphone analogy, think of how people looked at their TVs in the early 1970s. It was a society-changing but by that time relatively established technology with high growth. And people had all sorts of ideas for “new” things to do with it. You could’ve made arguments regarding most of them in the same vein as the arguments in this article. Most of those ideas were half-baked and failed at the time… only to resurface decades later, altered, refined, and successful, on PCs and smartphones. But PCs and smartphones are not, in any real sense, TVs.

    Which surprisingly, once I hunkered down and pushed my way through this lengthy essay, is essentially one of the points that I think the author is making (although obliquely): That by the time this technology has evolved beyond its current limits, it will no longer be something that we recognize as “software” in the current sense.

    I suggest trying to keep the concepts of “integrated system design” and “algorithmic process definition” separate from “digital computer software” in a similar way. Which, funnily enough, are the parts of all of this at which humans arguably still beat LLMs.


  • “Of course, consoles are important, but the proportion of people who play on PCs is steadily increasing. Even in areas where consoles are not widely available, there are many people who say, ‘I can play it on PC.’”

    This quote hits a little different when you know that Sega sells almost everything digitally for PC in the Americas and Europe, but virtually nothing within Japan and other selected countries.

    They do not care about making their games available to customers. They care about profits. Overseas, the PC segment is big enough to be worth pursuing. In some countries it outstrips the console segment. But in Japan it’s small enough that it makes more sense not to support PC, but rather to try to keep customers locked in to consoles, where they have tighter control and less competition.


  • It’s 2026 and people are still falsely conflating digital with suspect and physical with safe. We live in a world where plenty of commercial software that comes “on a disk” is unuseable without constant approval from the publisher, and plenty of “digital download” software can be downloaded once and then used and reinstalled forever without needing to ask for anyone’s permission.

    I understand the confusion. For a long time, you got an item on physical media, and no-one could take it away from you. Then downloads and cloud services became popular, and at the same time this crap started happening. But not everyone’s trying to screw us with downloads, and the people who are, are doing their damndest to screw us via physical media as well.

    The issue isn’t digital vs. physical, it’s own vs. lease.



  • In both cases the trading value of the currency has almost nothing to do with who originated it, and almost everything to do with how the general public feels about it.

    Just like crypto, most “government” currencies are worth what they’re worth only because everyone agrees that they are. That’s called “fiat” currency. And that’s why fiat currency exchange markets exist. The US Dollar hasn’t been “convertible” (redeemable for a fixed amount of precious metal) since 1971, and many other world currencies were already backed in some way by the US Dollar at that time.

    The real difference is in the supply.

    Government fiat currency is difficult to counterfeit, although the government (or reserve bank) can always make more whenever they want. We trust them not to print more money, increasing the money supply and devaluing the currency. However, this is exactly what has happened sometimes in the past, and no doubt will happen again in the future.

    Crypto currency is virtually impossible to counterfeit, and IIRC there’s a finite (but not precisely known) amount of it that can be made, no matter who you are.

    Personally, I still use physical fiat currency and no crypto. I’d like to use crypto, but regulation in my country makes it very difficult to use without registering your details with a central authority. And although everyone’s pushing e-money options which are similarly tracked, thankfully I still have the option of using anonymous cash.

    I don’t do anything bad or illegal. I just believe that government and big business don’t deserve to know everything I do in my life simply because they want to.


  • I presume that the code was tested for various cases where there was at least one previous password on record, but everyone forgot about new users with no previous passwords. However I’m having trouble imagining what the code could actually be doing.

    I can only imagine a dynamically typed language, and a “checkedPasswords” variable being declared but uninitialized, then a loop incrementing that variable for each non-similar password pulled from the records, and finally a check to see if checkedPasswords equals the number of stored previous passwords.

    The execution environment could type and initialize the variable by default after the first increment, but in the case of the user having no previous passwords on record that wouldn’t happen, and the final equivalency check would be comparing an integer to some internal “NaN” state, thus failing.





  • Initialization in C++ is so simple that somebody wrote a nearly 300-page book on the subject

    There’s a book about 101 ways to cut potatoes. Perhaps that could be a real mike-drop bit of evidence that we shouldn’t be cooking potatoes.

    Here’s a 249-page book “just” about atomics and locks in Rust. Does a book this large about only one aspect of Rust prove that it’s a terrible language? No, because as with the C++ book, if we look at the summary of contents we can see that it actually covers a great deal more, simply with a focus on those topics.

    Luckily we don’t have to be compete masters of every aspect of a language in order to use it.

    Honestly, I think that modern C++ is a very piecemeal language with no clear direction, and it has many issues because of that. But the title and page count of a single book is not a convincing argument of anything.


  • I’m all for humourous roasts of things, but does anyone really find this funny? Was the author possibly being serious? I don’t know. What I do know is that I stopped watching after the first four examples because they were all deliberately incorrect or misleading, but also didn’t seem funny to me.

    1. Crazy initialization
      That sure is a lot of ways to initialize a variable! Even though some of these variables are quite different and would be initialized differently from each other in many other languages, even only counting the initializations that are functionally equivalent, there are a bunch of abuses of syntax that I’ve never seen used in the wild.

    At this point I had hope that this was meant to be amusing.

    1. Printing to the console
      C++ has had a version of C’s printf function from the very beginning. That weird stream syntax has some hardcore fans but many people ignore it. I did my CS degree close to 30 years ago, and the only time I used stream syntax was for one lab class exercise in which we had to show that we understood how to use stream syntax.

    They still could be going for a comedy roast, I guess.

    1. Getting a random number
      Much like the printf statement for number 2 above, C++ had its own version of C’s rand function from the start. I’ve never even heard of the stuff that’s being shown in this part of the video.

    OK that was virtually the same fake point as the previous one, and still no punchlines in sight.

    1. Having to type “static_cast” every time you recast a variable
      Nope, you don’t. You’re free to ask the compiler to automagically recast your variables to another type without giving any further detail just like you can in C. In fact, they’re often called “C-style casts”. There are even implicit casts, where you literally don’t add anything, and just cross your fingers that the compiler does what you think it should do. It’s like a little bit of the thrill of dynamic typing brought into C++! By using the static_cast keyword, you can tell the compiler that you understand that there’s a potential issue with this recast, but that you expect that the standard way of handling it will be fine. There are other keywords for more unusual situations; it’s not just a random bit of busywork added for no reason.