home.social

#deprecation — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #deprecation, aggregated by home.social.

fetched live
  1. A quotation from Euripides

    JASON: The curse of children’s blood be on you!
       Avenging Justice, blast your being!
    MEDEA: What god will hear your imprecation,
       Oath-breaker, guest-deceiver, liar?
     
    [ἸΆΣΩΝ: ἀλλά σ᾽ Ἐρινὺς ὀλέσειε τέκνων
       φονία τε Δίκη.
    ΜΉΔΕΙΑ: τίς δὲ κλύει σοῦ θεὸς ἢ δαίμων,
       τοῦ ψευδόρκου καὶ ξειναπάτου;]

    Euripides (485?-406? BC) Greek tragic dramatist
    Medea [Μήδεια], l. 1389ff (431 BC) [tr. Vellacott (1963)]

    More about (and translations of) this quote: wist.info/euripides/85172/

    #quote #quotes #quotation #qotd #euripides #medea #argument #bickering #curse #deprecation #dishonesty #dishonor #divineanger #divineretribution #divinewrath #dvinepunishment #gods #hospitality #punishment #reputation #unworthiness #vengeance

  2. A quotation from Euripides

    JASON: The curse of children’s blood be on you!
       Avenging Justice, blast your being!
    MEDEA: What god will hear your imprecation,
       Oath-breaker, guest-deceiver, liar?
     
    [ἸΆΣΩΝ: ἀλλά σ᾽ Ἐρινὺς ὀλέσειε τέκνων
       φονία τε Δίκη.
    ΜΉΔΕΙΑ: τίς δὲ κλύει σοῦ θεὸς ἢ δαίμων,
       τοῦ ψευδόρκου καὶ ξειναπάτου;]

    Euripides (485?-406? BC) Greek tragic dramatist
    Medea [Μήδεια], l. 1389ff (431 BC) [tr. Vellacott (1963)]

    More about (and translations of) this quote: wist.info/euripides/85172/

    #quote #quotes #quotation #qotd #euripides #medea #argument #bickering #curse #deprecation #dishonesty #dishonor #divineanger #divineretribution #divinewrath #dvinepunishment #gods #hospitality #punishment #reputation #unworthiness #vengeance

  3. A quotation from Euripides

    JASON: The curse of children’s blood be on you!
       Avenging Justice, blast your being!
    MEDEA: What god will hear your imprecation,
       Oath-breaker, guest-deceiver, liar?
     
    [ἸΆΣΩΝ: ἀλλά σ᾽ Ἐρινὺς ὀλέσειε τέκνων
       φονία τε Δίκη.
    ΜΉΔΕΙΑ: τίς δὲ κλύει σοῦ θεὸς ἢ δαίμων,
       τοῦ ψευδόρκου καὶ ξειναπάτου;]

    Euripides (485?-406? BC) Greek tragic dramatist
    Medea [Μήδεια], l. 1389ff (431 BC) [tr. Vellacott (1963)]

    More about (and translations of) this quote: wist.info/euripides/85172/

    #quote #quotes #quotation #qotd #euripides #medea #argument #bickering #curse #deprecation #dishonesty #dishonor #divineanger #divineretribution #divinewrath #dvinepunishment #gods #hospitality #punishment #reputation #unworthiness #vengeance

  4. A quotation from Euripides

    JASON: The curse of children’s blood be on you!
       Avenging Justice, blast your being!
    MEDEA: What god will hear your imprecation,
       Oath-breaker, guest-deceiver, liar?
     
    [ἸΆΣΩΝ: ἀλλά σ᾽ Ἐρινὺς ὀλέσειε τέκνων
       φονία τε Δίκη.
    ΜΉΔΕΙΑ: τίς δὲ κλύει σοῦ θεὸς ἢ δαίμων,
       τοῦ ψευδόρκου καὶ ξειναπάτου;]

    Euripides (485?-406? BC) Greek tragic dramatist
    Medea [Μήδεια], l. 1389ff (431 BC) [tr. Vellacott (1963)]

    More about (and translations of) this quote: wist.info/euripides/85172/

    #quote #quotes #quotation #qotd #euripides #medea #argument #bickering #curse #deprecation #dishonesty #dishonor #divineanger #divineretribution #divinewrath #dvinepunishment #gods #hospitality #punishment #reputation #unworthiness #vengeance

  5. ⚠️ skerkour/bloom

    This repository is considered obsolete and points users to a separate legacy codebase that contains the maintained source code and continues receiving updates

    ⭐ Stars: 1531
    📅 Last Update: Jun 09, 2026

    github.com/skerkour/bloom

    #selfhosted #homelab #selfhost #selfhosting #opensource #deprecation #legacy

  6. ⚠️ skerkour/bloom

    This repository is considered obsolete and points users to a separate legacy codebase that contains the maintained source code and continues receiving updates

    ⭐ Stars: 1531
    📅 Last Update: Jun 09, 2026

    github.com/skerkour/bloom

    #selfhosted #homelab #selfhost #selfhosting #opensource #deprecation #legacy

  7. ⚠️ skerkour/bloom

    This repository is considered obsolete and points users to a separate legacy codebase that contains the maintained source code and continues receiving updates

    ⭐ Stars: 1531
    📅 Last Update: Jun 09, 2026

    github.com/skerkour/bloom

    #selfhosted #homelab #selfhost #selfhosting #opensource #deprecation #legacy

  8. Every time I see someone saying “Oh no, I missed the CFP deadline”, I can’t help thinking about all those features in Python or Django that were deprecated for years… and then someone is shocked when they finally get removed. 🫠

    Weeks of announcements. Years of warnings. Deprecation messages in the logs. And still: surprise. 😅

    Maybe warnings and deadlines only become real the day after they expire. 🪄

    #Python #Django #Community #CFP #Deprecation #Warning

  9. Every time I see someone saying “Oh no, I missed the CFP deadline”, I can’t help thinking about all those features in Python or Django that were deprecated for years… and then someone is shocked when they finally get removed. 🫠

    Weeks of announcements. Years of warnings. Deprecation messages in the logs. And still: surprise. 😅

    Maybe warnings and deadlines only become real the day after they expire. 🪄

  10. Every time I see someone saying “Oh no, I missed the CFP deadline”, I can’t help thinking about all those features in Python or Django that were deprecated for years… and then someone is shocked when they finally get removed. 🫠

    Weeks of announcements. Years of warnings. Deprecation messages in the logs. And still: surprise. 😅

    Maybe warnings and deadlines only become real the day after they expire. 🪄

    #Python #Django #Community #CFP #Deprecation #Warning

  11. Every time I see someone saying “Oh no, I missed the CFP deadline”, I can’t help thinking about all those features in Python or Django that were deprecated for years… and then someone is shocked when they finally get removed. 🫠

    Weeks of announcements. Years of warnings. Deprecation messages in the logs. And still: surprise. 😅

    Maybe warnings and deadlines only become real the day after they expire. 🪄

    #Python #Django #Community #CFP #Deprecation #Warning

  12. Every time I see someone saying “Oh no, I missed the CFP deadline”, I can’t help thinking about all those features in Python or Django that were deprecated for years… and then someone is shocked when they finally get removed. 🫠

    Weeks of announcements. Years of warnings. Deprecation messages in the logs. And still: surprise. 😅

    Maybe warnings and deadlines only become real the day after they expire. 🪄

    #Python #Django #Community #CFP #Deprecation #Warning

  13. RANT:

    Why do people insist on breaking backward compatability by removing 'deprecated' features that there is no valid reason to remove - i.e no safety issues, no clash with the thing superseding them etc.

    In the worst cases it can force rewrites of large sections of code to accomodate a different methodology and even introduce problems if the developer overlooks something like a different unit scale.

    Removing widely used things in favour of different things when they can co-exist is a shitty practice - unless in extreme cases where there is a real security risk.

    Deprecate this 🖕

    #coding #deprecation

  14. RANT:

    Why do people insist on breaking backward compatability by removing 'deprecated' features that there is no valid reason to remove - i.e no safety issues, no clash with the thing superseding them etc.

    In the worst cases it can force rewrites of large sections of code to accomodate a different methodology and even introduce problems if the developer overlooks something like a different unit scale.

    Removing widely used things in favour of different things when they can co-exist is a shitty practice - unless in extreme cases where there is a real security risk.

    Deprecate this 🖕

    #coding #deprecation

  15. RANT:

    Why do people insist on breaking backward compatability by removing 'deprecated' features that there is no valid reason to remove - i.e no safety issues, no clash with the thing superseding them etc.

    In the worst cases it can force rewrites of large sections of code to accomodate a different methodology and even introduce problems if the developer overlooks something like a different unit scale.

    Removing widely used things in favour of different things when they can co-exist is a shitty practice - unless in extreme cases where there is a real security risk.

    Deprecate this 🖕

    #coding #deprecation

  16. RANT:

    Why do people insist on breaking backward compatability by removing 'deprecated' features that there is no valid reason to remove - i.e no safety issues, no clash with the thing superseding them etc.

    In the worst cases it can force rewrites of large sections of code to accomodate a different methodology and even introduce problems if the developer overlooks something like a different unit scale.

    Removing widely used things in favour of different things when they can co-exist is a shitty practice - unless in extreme cases where there is a real security risk.

    Deprecate this 🖕

    #coding #deprecation

  17. RANT:

    Why do people insist on breaking backward compatability by removing 'deprecated' features that there is no valid reason to remove - i.e no safety issues, no clash with the thing superseding them etc.

    In the worst cases it can force rewrites of large sections of code to accomodate a different methodology and even introduce problems if the developer overlooks something like a different unit scale.

    Removing widely used things in favour of different things when they can co-exist is a shitty practice - unless in extreme cases where there is a real security risk.

    Deprecate this 🖕

    #coding #deprecation