• (disco)

    "you know, it figures that you'd get an error when trying to divide something by potato," wrote Bryan B.

    [image]
  • (disco)

    Great, in order to fix this, I need to uninstall programz. [image]

    How will this help? Because raisins!

    Filed under: Flip the transmogrifying snaflaget!

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Great, in order to fix this, I need to uninstall programz.

    Nah, just uninstall Windows 10. :trolleybus:

  • (disco) in reply to HardwareGeek

    Instructions unclear. Penis now stuck in window. Send help

  • (disco) in reply to LB_

    Not even the jelly variety?

  • (disco)

    It sure is expensive to apply that citronella to those potatoes, just to keep them from sprouting. Personally, if it were me, I'd rather risk them sprouting.

  • (disco)

    Two things:

    1. RIP is actually the proper term for software that converts page description languages (PCL and Postscript) to a printer's internal representation.Yes, capitalized.

    2. Interesting that Microsoft has given up and started calling it the System Tray instead of sticking to the proper Notification Area name.

  • (disco) in reply to Weng
    Weng:
    2) Interesting that Microsoft has given up and started calling it the System Tray instead of sticking to the proper Notification Area name.

    This wouldn't be the first time either.

    Wikipedia:
    Taskbar ... The notification area is commonly referred to as the system tray, which Microsoft states is wrong, although the term is sometimes used in Microsoft documentation, articles, software descriptions, and even applications from Microsoft such as Bing Desktop. Raymond Chen suggests the confusion originated with systray.exe, a small application that controlled some icons within the notification area in Windows 95. ...
  • (disco) in reply to David_C

    And from the original source:

    Even worse, other groups (not the shell) picked up on this misnomer and started referring it to the tray in their own documentation and samples, some of which even erroneously claim that "system tray" is the official name of the notification area.

    [...]

    Summary: It is never correct to refer to the notification area as the tray. It has always been called the "notification area".

    Just because Microsoft sometimes calls it the System Tray doesn't make it right.

  • (disco) in reply to Protoman

    A rose by any other name...will never be called a system tray.

  • (disco) in reply to Protoman

    At this point I think it's a bit of a lost cause. If everyone knows it as the system tray, including people internal to the company, it is the system tray. Just like I can get annoyed at people misusing "begging the question" as much as I want but it won't change the modern meaning

  • (disco)

    x/0! = x

  • (disco) in reply to CreatedToDislikeThis
    CreatedToDislikeThis:
    x/0! = x 
    > NaN/0 is NaN
< true

    ... and now i see a subtle, and important thing about your code...

    you wrote (x/(0!)) = x

    i read (x/0) != x

    .... oopsies?

  • (disco) in reply to accalia

    Operator precedence FTWTF. Just when you get all cowboy about the precedence in your favorite language, you have to switch to some other language and the precedences change. Lesson: always use parentheses. <--sorry for the flame war igniter.

    My "favorite" inconsistency is x = 1:10/10 . What is x?

  • (disco) in reply to accalia

    No, 0!=1

  • (disco) in reply to PleegWat
    PleegWat:
    No, 0!=1

    (0!) == 1, true

    0 != 1, true

    also stahp confusing my brain! i have enough cognitive dissonance trying to type with the fingers on my paw/hands!

  • (disco) in reply to accalia
    accalia:
    `0 != 1`

    Will you believe I missed that? Sloppy me.

  • (disco) in reply to PleegWat
    PleegWat:
    Will you believe I missed that? Sloppy me.

    ...THIS IS WHY PARENTHESIS ARE IMPORTANT! [image]

  • (disco) in reply to CreatedToDislikeThis
    CreatedToDislikeThis:
    x/0! = x

    Unless x is NaN, because NaN is always unequal to itself.

  • (disco)

    TRWTF is still listing the price in French Francs almost fourteen years after that currency was replaced. They might as well list it as 1050 Francs instead.

  • (disco) in reply to Gurth
    Gurth:
    TRWTF is still listing the price in French Francs almost fourteen years after that currency was replaced. They might as well list it as 1050 Francs instead.

    maybe they havent updated the price in the last fourteen years?

  • (disco) in reply to accalia
    accalia:
    ...THIS IS WHY PARENTHESIS ARE IMPORTANT!

    Shouldn't that be "Parentheses are important" Or, "A parenthesis is important"?

  • (disco) in reply to tharpa
    tharpa:
    accalia:
    ...THIS IS WHY PARENTHESIS ARE IMPORTANT!

    Shouldn't that be "Parentheses are important" Or, "A parenthesis is important"?

    me am spellaring gud.

  • (disco) in reply to Protoman

    In my philosophy every NaN is a special snowflake and no two NaNs are comparable.

  • (disco) in reply to accalia
    accalia:
    NaN

    Does the type of x admit NaN in the first place? :smiley:

    cellocgw:
    My "favorite" inconsistency is x = 1:10/10 .

    What does the : operator mean in this case? For someone coming from a C-like expression background, that's just a confusing incomplete statement…

  • (disco) in reply to Weng
    Weng:
    RIP is actually the proper term for software that converts page description languages (PCL and Postscript) to a printer's internal representation.Yes, capitalized.

    To be precise, it's an acronym for "Raster Image Processor". Before digital printing became the norm (late last century), a RIP was a high-end piece of kit.

  • (disco) in reply to accalia
    accalia:
    maybe they havent updated the price in the last fourteen years?
    More likely is that they haven’t updated their brains in the last fourteen years.
  • (disco) in reply to Gurth
    Gurth:
    they haven’t updated their brains in the last fourteen years

    We aren't permitted to update our brains here in the EC before the bureaucrats in Brussels have come to an agreement about how do do and document it properly.

  • (disco) in reply to dkf
    dkf:
    Does the type of x admit NaN in the first place? :smiley:

    if it's an IEEE flaoting point.... yes. they're built into the spec.

  • (disco) in reply to accalia
    accalia:
    if it's an IEEE flaoting point

    My point exactly. (Well, modulo spleling erorrs…)

  • (disco) in reply to dkf
    dkf:
    Well, modulo spleling erorrs…

    did you forget who you were tlaking to?

    :rofl:

  • (disco) in reply to accalia
    accalia:
    did you forget who you were tlaking to?

    noep ;)

  • (disco) in reply to dkf

    **

    dkf:
    accalia:
    did you forget who you were tlaking to?

    noep ;)

    at lseat yuor spellaring is imporving

    strong text**

  • (disco) in reply to dkf
    dkf:
    accalia:
    did you forget who you were tlaking to?

    noep ;)

    Joep's brother?

  • (disco) in reply to accalia
    accalia:
    at lseat yuor spellaring is imporving

    Mu spleeign is abotu as goood as ti eevr wasb utI usully bohter to corect it beefor psotign/

  • (disco) in reply to accalia
    accalia:
    strong text**

    You can't even speel that right?

  • (disco) in reply to Watson

    In the print industry, they still are high end pieces of kit.

    My "workgroup printer" (we produce code that makes page description code, so we need something to test with that doesn't involve monopolizing production gear) cost $500,000. The printer itself is just an overgrown MFP with a every single piece of optional equipment. $50k at best. The other $450k is all software and a shitbox Unix workstation that doesn't even have a mousewheel to run it.

    Of course we lease it from the manufacturer, paying per page. The manufacturer takes a huge loss on that particular unit, but they figure it's good business because the production machines are ALSO leased per page and this one machine allows us to write code that runs on hundreds of production machines.

    While I'm on a printer rant, there's only one manufacturer in that space that actually understands the value in having their entire lineup be cross-compatible. Stuff gets added, different models have different features, UIs get rearranged, but at the end of the day I can make a PostScript file that uses certain features and, as long as the machine is physically equipped, it will run on everything from a 20 year old low speed black and white copy machine (with an attached RIP) to a fantastic high speed ultra-modern full+highlight color behemoth and produce the same result.

    Other manufacturers require different commands for the same feature on different models in the lineup. Hell, different commands for different RIP versions for the same feature on the same model. Ain't nobody got time for that shit.

    Of course, the shitty manufacturers are cheaper and better at sales. The good manufacturer is considered a dying dinosaur.

Leave a comment on “In Memoriam”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article