A butt complains about web development, all wacky hipsters get dudehurt



  • Ahhhhhh, my bad. I just saw the extract and buttumed he had actually changed his mind for some reason.



  • Just because DOM started as part of JavaScript doesn't mean that it's still part of JavaScript. The two were split off into separate standards decades ago.

    ...besides, Node is a headless environment. Not surprisingly, you can't interact with windows that way.



  • Firstly, node-webkit is a thing. A travesty that shouldn't exist, but does.

    Secondly, I'm well aware that the two things are separate. I was more riffing on how blakey is so adamant that these two things are separate and anyone who doesn't know it is a moron and how it appeared that he'd changed his mind. The 🚎 should have been explicitly stated, I guess.



  • @powerlord said:

    No, I'm the one that pointed out that DOM was created as part of JavaScript.

    And Botts' Dots were created as part of the Federal Highway System; that doesn't make them the same thing as the Federal Highway System.

    @powerlord said:

    Blakey's the one that gets upset if you equate the two as being the same.

    Because they aren't? DOM was designed to be used with any programming language, not merely JavaScript. C# has a DOM API for XML documents, and it's never been used on the web. For example. VBScript which was used on the web for some time implemented DOM as well.



  • I hope people actually click through to that because it's a pretty funny post.


  • kills Dumbledore

    You also claimed that HTML5 is Javascript. I'll be repeating all this next time I interview for a web developer position



  • The context implied they weren't offended at all, because the actual jokes didn't imply gender, only the complainers implied gender.

    only thing I find offensive the automatic presumption by those of you complaining

    The surrounding comments were erroneously complaining that the joke material implied men didn't need consent. Whereas if you read the actual code, it was the exact opposite. It could easily have been read, from the perspective of a woman, that she could do whatever she wanted with a man's dick if she felt she owned it. She could put it where-ever she wanted, etc.

    The complainers assumed the code implied man with dick acting on woman's body. But of course, people easily offended, read what they want into what they read.

    So, in this manner, the complainers were acting like @Fox, and this commenter was a trans that was finding a way to make it funny for themselves by upping the ante on the complaints against the complaints themselves.

    In other words

    "You guys are the ones assuming. And by assuming, you leave trans out of it. Disenfranchising trans in order to paint comments as offensive is offensive to me."



  • @blakeyrat said:

    And Botts' Dots were created as part of the Federal Highway System; that doesn't make them the same thing as the Federal Highway System.

    @powerlord said:

    Just because DOM started as part of JavaScript doesn't mean that it's still part of JavaScript. The two were split off into separate standards decades ago.



  • @Arantor said:

    So how can I use jQuery with NodeJS?

    nQuery?


  • FoxDev

    @Arantor said:

    So how can I use jQuery with NodeJS?

    cheerio pip pip old boy and other stereotypes



  • Why not MingeJS?


  • ♿ (Parody)

    Meh...I heard that was just a DOM libeary. I need something I can use with javascript.


  • Trolleybus Mechanic

    I heard the DOM is a lie berry. As in: it isn't a berry, and anyone who tells you that is a liar.



  • @Lorne_Kates said:

    anyone who tells you that is a liar.

    The cake is a lie?

    That ass!


  • Notification Spam Recipient

    @Magus said:

    Why not MingeJS?
    I don't like to socialize and sure as shit don't want my code tarting itself up and wiggling its wears all over town. It will stay in the basement I trapped it in.



  • All I can think of is Finding Nemo.


  • Ming Ge will be so upset!



  • Ze drem vil finali kam tru for strong-static-typing enthusiasts.



  • @blakeyrat said:

    you are literally the only Linux user I've ever heard of that wasn't constantly pissed-off about how out-of-date and buggy the Flash plugin for Linux was.

    Things have actually got a lot better since Adobe stopped supporting the Linux plugin, because that decision forced the open source community to invent a bunch of duct tape and baling wire compatibility adapter hacks that actually work better than Adobe's shitty non-installer ever did.

    I'm on Debian. The pepperflashplugin-nonfree package downloads Chrome for Linux from Google's site, extracts the Flash plugin and discards everything else, and makes the extracted Flash available to Chromium and any other browser that supports the Pepper API; the browser-plugin-freshplayer-pepperflash package is an NPAPI to Pepper adapter shim that does a quite acceptable job of allowing that same Flash version to work in Iceweasel.

    Even the Break All The Things brigade at Mozilla understands that they can't get away with refusing to support Flash:
    [quote=NPAPI plugins in Firefox]Because Adobe Flash is still a common part of the Web experience for most users, we will continue to support Flash within Firefox as an exception to the general plugin policy. Mozilla and Adobe will continue to collaborate to bring improvements to the Flash experience on Firefox, including on stability and performance, features and security architecture.[/quote]


Log in to reply