• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • It’s a silly flag to use as it only works when running 32-bit Windows applications on 64-bit Windows, and if you’re compiling from source, you should also have the option to just build a 64-bit binary in the first place. It made a degree of sense years ago when people actually used 32-bit Windows sometimes (which was usually just down to OEMs installing the wrong version on prebuilt PCs could have supported 64-bit) if you really wanted to only have one binary or you consumed a precompiled third party library and had to match its architecture.







  • Part of it depends on how you define things. They’re not a monopoly in terms of having eliminated all their competitors, but they’re a defacto monopoly in terms of being able to do the things a monopoly can. As an example, they can dictate pricing for the whole market as their margins are better than AMD’s, so if AMD undercut them, they can retaliate by dropping their prices to the point AMD would have to sell at cost, so AMD can only sell things in the narrow price window where Nvidia doesn’t feel threatened. On the other hand, AMD does exist and does sell things.



  • I think you’ve misunderstood my complaint. I know how you go about composing things in a Unix shell. Within your post, you’ve mentioned several distinct languages:

    • sh (I don’t see any Bash-specific extensions here)
    • Perl-compatible regular expressions, via grep -P
    • printf expressions
    • GNU ps’s format expressions
    • awk

    That’s quite a lot of languages for such a simple task, and there’s nothing forcing any consistency between them. Indeed, awk specifically avoids being like sh because it wants to be good at the things you use awk for. I don’t personally consider something to be doing its job well if it’s going to be wildly different from the things it’s supposed to be used with, though (which is where the disagreement comes from - the people designing Unix thought of it as a benefit). It’s important to remember that the people designing Unix were very clever and were designing it for other very clever people, but also under conditions where if they hit a confusing awk script, they could just yell Brian, and have the inventor of awk walk over to their desk and explain it. On the other hand, it’s a lot of stuff for a regular person to have in their head at once, and it’s not particularly easy to discover or learn about in the first place, especially if you’re just reading a script someone else has written that uses utilities you’ve not encountered before. If a general-purpose programming language had completely different conventions in different parts of its standard library, it’d be rightly criticised for it, and the Unix shell experience isn’t a completely un-analogous entity.

    So, I wouldn’t consider the various tools you used that don’t behave like the other tools you used to be doing their job well, as I’d say that’s a reasonable requirement for something to be doing its job well.

    On the other hand, PowerShell can do all of this without needing to call into any external tools while using a single language designed to be consistent with itself. You’ve actually managed to land on what I’d consider a pretty bad case for PowerShell as instead of using an obvious command like Get-ComputerInfo, you need:

    (Get-WmiObject Win32_ComputerSystem).FreePhysicalMemory / 1024
    

    Even so, you can tell at a glance that it’s getting the computer system, accessing it’s free physical memory, and dividing the number by 1024.

    To get the process ID with the largest working set, you’d use something like

    (Get-Process | Sort-Object WorkingSet | Select-Object -Last 1).Id
    # or
    (Get-Process | Sort-Object WorkingSet)[-1].Id
    

    I’m assuming either your ps is different to mine, or you’ve got a typo, as mine gives the parent process ID as the second column, not the process’ own ID, which is a good demonstration of the benefits of structured data in a shell - you don’t need sed/awk/grep incantations to extract the data you need, and don’t need to learn the right output flag for each program to get JSON output and pipe it to jq.

    There’s not a PowerShell builtin that does the same job as watch, but it’s not a standard POSIX tool, so I’m not going to consider it cheating if I don’t bother implementing it for this post.

    So overall, there’s still the same concept of composing something to do a specific task out of parts, and the way you need to think about it isn’t wildly different, but:

    • PowerShell sees its jurisdiction as being much larger than Bash does, so a lot of ancillary tools are unnecessary as they’re part of the one thing it aims to do well.
    • Because PowerShell is one thing, it’s got a pretty consistent design between different functions, so each one’s better at its job as you don’t need to know as much about it the first time you see it in order to make it work.
    • The verbosity of naming means you can understand what something is at first glace, and can discover it easily if you need it but don’t know what it’s called - Select-String does what it says on the tin. grep only does what it says on the tin if you already know it’s global regular expression print.
    • Structured data is easier to move between commands and extract information from.

    Specifically regarding the Unix philosophy, it’s really just the first two bullet points that are relevant - a different definition of thing is used, and consistency is a part of doing a job well.


  • Powershell isn’t perfect, but I like it a lot more than anything that takes sh as a major influence or thing to maintain backwards compatibility with. I don’t think the Unix philosophy of having lots of small tools that do one thing and do it well that you compose together has ever been achieved as I think being consistent with other tools you use at the same time should be part of doing your thing well, and things like sed, grep and perl all having different regular expression syntax demonstrate inconsistency and are easy to find. I also like that powershell is so verbose as it makes it much easier to read someone else’s script without knowing much powershell, and doesn’t end up getting in the way of actually writing powershell as the autocomplete is really good. I like having a type system and structured data, too.

    Some of these things are brought to a unixier shell with nushell, but I’m not convinced it’ll take off. Even if people use it, it’ll be a long while before you Google a problem and the solution also includes a nushell snippet, whereas for any Windows problem, you’ll typically get a GUI solution and a powershell solution, and only a maniac would give a CMD solution.




  • The legalese in the US (which might as well be everywhere as you need to have compatible copyright with the US to have a trade deal with the US, and your country is in trouble if it doesn’t have a trade deal with the US) is basically that:

    • If you buy a physical copy, you’ve become the owner of that one copy of the IP contained within. As the owner of that copy, you can do stuff with it like read it, display it, destroy it, or sell it on to someone else thanks to the First Sale Doctrine (but you can’t do other things like copying it, unless it’s a DVD as there’s a specific exemption for the copy your DVD has to make to RAM in order to decode the DVD). There’s nothing the copyright holder of the original can do to stop you exercising these rights.
    • If you buy a digital ‘copy’, you’ve not bought a copy, you’ve bought a licence to use one of the publisher’s copies that they’ve given you permission to have on your device(s). They’ll also have given you permission to do things like read it if it’s an ebook or play it if it’s a video game, but as it’s their copy, not yours, you don’t automatically get rights to do anything they’ve not explicitly permitted you to, and it’s not in their interests to permit you to sell it on unless they think you’ll pay enough more for a resaleable copy that it covers a potential future lost sale.

    I’m sure plenty of publishers would love for the second set of rules to apply to things like books, and from a quick googling, it seems like occasionally academic textbooks have included a licence agreement instead of you actually owning the physical book, but I imagine that most publishers are concerned about bad PR from attempting this with a hit novel and also don’t want to be accused of fraud for having their not-a-book-just-a-licence on the shelf next to regular books and thereby tricking consumers into thinking they were buying a regular book. EA attempted to double-dip over a decade ago with Battlefield 3, which included a copy of the game (with regular First Sale Doctrine rights) and a licence key for the online pass (which wasn’t transferrable) and got bad press because of it. Newer PC games often come as a key in a box with no disk or a disk that only runs a web installer, so you’ve not got a copy of the game to claim you’ve bought and obviously only have a licence, and this seems to have caused less upset. This wouldn’t work with a book, though, as you have to fill in the pages at the printing factory, and can’t magically do it only after the user’s got it home.


  • Epic donated hundreds of thousands of dollars to Godot when Unity was being dumb this summer, so either they think an open-source project is on the brink of making their competitor unprofitable and collapse, and think enough of the studios jumping ship will come to Unreal to cover that sum, or they’re concerned that someone will start enforcing antitrust laws and want something to point at to say they’re not a monopoly.