• 6 Posts
  • 39 Comments
Joined 8 months ago
cake
Cake day: March 4th, 2024

help-circle


  • umbraroze@lemmy.worldtoProgrammer Humor@programming.devLanguages
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    1 month ago

    Yeah, I was about to say.

    Perl 5 is like Esperanto: borrowed neat features from many languages, somehow kinda vaguely making a bit of sense. Enjoyed some popularity back in the day but is kind of niche nowadays.

    PHP is like Volapük: same deal, but without the linguistic competence and failing miserably at being consistent.

    Raku (Perl 6) is like Esperanto reformation efforts: Noble and interesting scholarly pursuits, with dozens of fans around the multiverse.










  • Like I said this was in the Vista era. Or possibly before the Vista release, part of the Longhorn hype train (Longhorn got some super hyped features, such as an epic next-generation filesystem to replace NTFS, which Microsoft ultimately canned, and Vista ended up, you know, being Vista).

    This was so long ago that I unfortunately don’t remember what exact feature this was about, but it was about some new Windows component.


  • I can’t remember it, but I read one Microsoft blog post (in Vista era?) about how one team at Microsoft would develop some amazing new Windows component. They’d proudly name it AmazingNewService.dll. And then the operating system team would come in and say “that’s all fine and good, but you have to conform to the naming convention.” 8+3 filenames. First two letters probably “MS”, because of reasons. …and 15 years later, people still regularly go “What the fuck is MSAMNSVC.DLL?”






  • This was so long ago that I can’t actually remember the actual reason why things had to be done by hand. Part of it may have been a conversion snag, but there were probably some other reasons why it wasn’t as simple as writing a script to do the job. Because I distinctly remember I wrote some scripts to help with other data conversion jobs.


  • Flashback to my first job. Coworker designed a giant complex web app with bazillion UI messages. Another coworker (in the Management) sent me the UI messages. As an Excel file.

    I was tasked to manually convert the messages to a PHP data structure of some description (because this was 2002 and Excel files didn’t exactly lend themselves to scripting in Linux). Surprisingly, the management person did acknowledge my complaint that the conversion process was far more painful than necessary. Not that this helped, because soon after the startup got acquired and as far as I know the tech currently only exists in conceptual level in some big corporate vault or other.



  • Not exactly boned but it probably doesn’t make practical difference to store “local time + tzinfo timezone” than just UTC time.

    • You record an event occurring at local time
    • You store it as UTC
    • Local time zone definition changes
    • Well whoop de loo, now you need to go through tzinfo to make sense of the past data anyway rather than relying on a known offset

    Even if you store everything in UTC, you may be safe… but figuring out the local time is still convoluted and involves a trip through tzinfo.