Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
0
Comments
637
Joined
3 yr. ago

  • wasn’t really thinking about it, because all I did was launch the games I wanted to play.

    It getting increasingly belligerent trying to get me to switch to a Microsoft account over the last decade was by itself enough to make me furious.

  • I think posts about LLM technology itself can be interesting, but random self promoting blogspam from founder types and tech bros about how they've found the secret to using "agentic programming" responsibly is the most boring thing imaginable. So yes, if it has to exist please put it somewhere else.

  • Proton is a combination of technologies. The main ones are wine and dxvk

  • To paraphrase, "I'm seeing negative effects from using LLMs. For some reason I apparently think simply not using the tool producing negative effects is an option so I'm going to make a bunch of rules that amount to balancing out any supposed productivity gains with more human work and invest in even more slop tools"

    Insane

  • Yeah node's --experimental-strip-types exposes the absurdity immediately. The only incompatibility is that it has type annotations.

  • You're being too generous. Calling typescript a rewrite shows the author chose something as an example they clearly don't understand the first thing about.

  • TypeScript, for those who aren’t familiar, is a Microsoft rewrite of JavaScript that’s incompatible with basic JavaScript in multiple ways

    Wut

  • Deleted

    Permanently Deleted

    Jump
  • I'm not a fan of python so I was prepared to commiserate but...

    Tuples, Sets, Dicts, Lists

    These are all useful in every language... I don't use tuples that often, but lists/arrays and associative arrays/dictionaries/hashmaps are in every language and completely different from each other, and there are plenty of reasons to use sets when that is what your data actually is and you get easy access to set operations

  • Everyone knows you want as much income inequality as possible. That's why it's a win condition in civilization games right?

  • You are correct that it is the deserializer's choice. You are incorrect when you imply that it is a good idea to rely on behavior that isn't enforced in the spec. A lot of people have been surprised when that assumption turns out to be wrong.

  • Physical therapy

  • There are really good uses for XML. Mostly for making things similar to HTML. Like markup for Android UIs or XAML for WPF. For pretty much everything else the complexity only brings headaches

  • Information set isn't a description of XML documents, but a description of what you have that you can write to XML, or what you'd get when you parse XML.

    This is the key part from the document you linked

    The information set of an XML document is defined to be the one obtained by parsing it according to the rules of the specification whose version corresponds to that of the document.

    This is also a great example of the complexity of the XML specifications. Most people do not fully understand them, which is a negative aspect for a tool.

    As an aside, you can have an enforced order in XML, but you have to also use XSD so you can specify xsd:sequence, which adds complexity and precludes ordered arrays in arbitrary documents.

  • That capability is what enables billion laugh attacks, unfortunately, so not having it enabled in cases where there is external input possible is wise

  • In HTML, which things are attributes and which things are tags are part of the spec. With XML that is being used for something arbitrary, someone is making the choice every time. They might have a different opinion than you do, or even the same opinion, but make different judgments on occasion. In JSON, there are fewer choices, so fewer chances for people to be surprised by other people's choices.

  • That's correct, but the order of tags in XML is not meaningful, and if you parse then write that, it can change order according to the spec. Hence, what you put would be something like the following if it was intended to represent an array.

     xml
        
    <items>
      <item index="1"></item>
      <item index="2"></item>
      <item index="3"></item>
    </items>
    
      
  • Honestly, anyone pining for all the features of XML probably didn't live through the time when XML was used for everything. It was actually a fucking nightmare to account for the existence of all those features because the fact they existed meant someone could use them and feed them into your system. They were also the source of a lot of security flaws.

    This article looks like it was written by someone that wasn't there, and they're calling people telling them the truth that they are liars because they think features they found in w3c schools look cool.

  • JSON also has arrays. In XML the practice to approximate arrays is to put the index as an attribute. It's incredibly gross.