home.social

Search

1000 results for “BRicker”

  1. @BRicker I don't think it's really diverged much. begat . Then Oracle unbegat it and the community begat by forking the last free release. There are then a bunch of distributions like and .

  2. @BRicker I don't think it's really diverged much. #SunMicrosystems begat #OpenSolaris. Then Oracle unbegat it and the community begat #IllumOS by forking the last free release. There are then a bunch of distributions like #OmniOS and #Tribblix.

  3. @BRicker I don't think it's really diverged much. #SunMicrosystems begat #OpenSolaris. Then Oracle unbegat it and the community begat #IllumOS by forking the last free release. There are then a bunch of distributions like #OmniOS and #Tribblix.

  4. @BRicker I don't think it's really diverged much. #SunMicrosystems begat #OpenSolaris. Then Oracle unbegat it and the community begat #IllumOS by forking the last free release. There are then a bunch of distributions like #OmniOS and #Tribblix.

  5. @BRicker I don't think it's really diverged much. #SunMicrosystems begat #OpenSolaris. Then Oracle unbegat it and the community begat #IllumOS by forking the last free release. There are then a bunch of distributions like #OmniOS and #Tribblix.

  6. @BRicker @Boston_PM my favourite C portability screw up is which insists that `short` be 16 bits.

    Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like `int16_t`, was "fun".

  7. @BRicker @Boston_PM my favourite C portability screw up is #bzip2 which insists that `short` be 16 bits.

    Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like `int16_t`, was "fun".

  8. @BRicker @Boston_PM my favourite C portability screw up is #bzip2 which insists that `short` be 16 bits.

    Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like `int16_t`, was "fun".

  9. @BRicker @Boston_PM my favourite C portability screw up is #bzip2 which insists that `short` be 16 bits.

    Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like `int16_t`, was "fun".

  10. @BRicker @Boston_PM my favourite C portability screw up is #bzip2 which insists that `short` be 16 bits.

    Getting that to work on a platform where short, int and long were all 64 bits, and where you only had C89, no fancy C99 data types like `int16_t`, was "fun".

  11. @BRicker I was a VM/CMS user in the 1980s and don't think I knew about REXX. I saw Regina Rexx distributed with the Windows 95(?) Resource Kit and possibly the AmigaOS ARexx version before that. I follow current ooRexx development closely, but I have not written any. I don't believe REXX under CMS, TSO, or OS/2 was used as Shell on Unix: EXECs where small macros or scripts, but control constructs could not be used interactively, AFAIK. Happy to hear from mainframe REXX users!

    #rexx

  12. @BRicker I was a VM/CMS user in the 1980s and don't think I knew about REXX. I saw Regina Rexx distributed with the Windows 95(?) Resource Kit and possibly the AmigaOS ARexx version before that. I follow current ooRexx development closely, but I have not written any. I don't believe REXX under CMS, TSO, or OS/2 was used as Shell on Unix: EXECs where small macros or scripts, but control constructs could not be used interactively, AFAIK. Happy to hear from mainframe REXX users!

    #rexx

  13. @BRicker I was a VM/CMS user in the 1980s and don't think I knew about REXX. I saw Regina Rexx distributed with the Windows 95(?) Resource Kit and possibly the AmigaOS ARexx version before that. I follow current ooRexx development closely, but I have not written any. I don't believe REXX under CMS, TSO, or OS/2 was used as Shell on Unix: EXECs where small macros or scripts, but control constructs could not be used interactively, AFAIK. Happy to hear from mainframe REXX users!

    #rexx

  14. @BRicker I was a VM/CMS user in the 1980s and don't think I knew about REXX. I saw Regina Rexx distributed with the Windows 95(?) Resource Kit and possibly the AmigaOS ARexx version before that. I follow current ooRexx development closely, but I have not written any. I don't believe REXX under CMS, TSO, or OS/2 was used as Shell on Unix: EXECs where small macros or scripts, but control constructs could not be used interactively, AFAIK. Happy to hear from mainframe REXX users!

    #rexx

  15. @BRicker I was a VM/CMS user in the 1980s and don't think I knew about REXX. I saw Regina Rexx distributed with the Windows 95(?) Resource Kit and possibly the AmigaOS ARexx version before that. I follow current ooRexx development closely, but I have not written any. I don't believe REXX under CMS, TSO, or OS/2 was used as Shell on Unix: EXECs where small macros or scripts, but control constructs could not be used interactively, AFAIK. Happy to hear from mainframe REXX users!

    #rexx

  16. @BRicker @futurebird lawlessness is what failing to follow through on law breaking with law enforcement and constitutional consequences has wrought.

  17. @BRicker @futurebird lawlessness is what failing to follow through on law breaking with law enforcement and constitutional consequences has wrought.

    #14as3

  18. @BRicker @futurebird lawlessness is what failing to follow through on law breaking with law enforcement and constitutional consequences has wrought.

    #14as3

  19. @BRicker @futurebird lawlessness is what failing to follow through on law breaking with law enforcement and constitutional consequences has wrought.

    #14as3

  20. @BRicker @futurebird lawlessness is what failing to follow through on law breaking with law enforcement and constitutional consequences has wrought.

    #14as3

  21. @BRicker @swaggboi And I know that TOPS-20 a/k/a #TWENEX was also the road not taken as far as network-connected OSes go, that’s why I’m grateful #SDF preserves and makes available the actual hardware to run it

  22. @BRicker @swaggboi And I know that TOPS-20 a/k/a #TWENEX was also the road not taken as far as network-connected OSes go, that’s why I’m grateful #SDF preserves and makes available the actual hardware to run it

  23. @BRicker @swaggboi And I know that TOPS-20 a/k/a #TWENEX was also the road not taken as far as network-connected OSes go, that’s why I’m grateful #SDF preserves and makes available the actual hardware to run it

  24. @BRicker @swaggboi And I know that TOPS-20 a/k/a #TWENEX was also the road not taken as far as network-connected OSes go, that’s why I’m grateful #SDF preserves and makes available the actual hardware to run it

  25. @BRicker @swaggboi And I know that TOPS-20 a/k/a #TWENEX was also the road not taken as far as network-connected OSes go, that’s why I’m grateful #SDF preserves and makes available the actual hardware to run it

  26. Für Fans des Steckerl-Eisklassikers „Brickerl“ heißt es Abschied von einer liebgewonnenen Gewohnheit nehmen. Eskimo, ein Unternehmen des Lebensmittelkonzerns Unilever, kündigte am Dienstag das Aus für das Schokoladeneis an. Im Netz sorgte das für einigen Aufruhr. orf.at/stories/3394417/

    #_Lifestyle

  27. Nach über 50 Jahren wird der Eisklassiker „Brickerl“ eingestellt. Grund dafür ist laut dem Hersteller Eskimo die geänderte Nachfrage seitens der Kundinnen und Kunden sowie der begrenzte Platz in den Truhen. „Das ‚Brickerl‘, wie wir es heute kennen, gibt es seit 1973. Nach dieser langen Zeit fällt ein solcher Schritt natürlich nicht leicht“, hieß es heute in einem Statement gegenüber der APA. orf.at/stories/3394390/

    #_Wirtschaft #_APA

  28. europesays.com/dk/58671/ Warsaw’s Joslyn Bricker finishes as top vote-getter on 2025-26 AP girls all-state basketball team | Agate #agate #national_sports #Poland #sports #Warsaw