home.social

#encapsulation — Public Fediverse posts

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

  1. Flavor Oils Market in Europe | Report – IndexBox

    Europe Flavor Oils Market 2026 Analysis and Forecast to 2035 Executive Summary Key Findings The Europe Flavor Oils…
    #Europe #EU #BakedGoods&Mixes #Blending&Compounding #Encapsulation(forstability) #FlavorOils #forecast #FrozenDesserts&IceCream #Gums&ChewingProducts #Hard&SoftCandies #ingredientmarketreport #marketanalysis #MolecularDistillation&Fractionation #NaturalFlavorProductionviaBiotransformation
    europesays.com/europe/29843/

  2. Today is the day we're getting our front (worst) crawlspace done here in Western North Carolina. A messy job, but the guys say they do it every day, and it won't take a full day to finish. Putting in a small vent fan and a large dehumidifier. Will see if removing humidity from this space helps with the newly finished basement, or if we'll need to duct the dehumid into that space as well.

    Sigh. Why in the world do they build houses with these stupid spaces?

    #IAQ #Humidity #Encapsulation

  3. After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:

    * If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
    * If you’re walking down a long uncertain chain, I have two arguments:
    * Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
    * Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

    Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

    #NullCoalescing #NullChaining #LanguageDesign

  4. After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:

    * If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
    * If you’re walking down a long uncertain chain, I have two arguments:
    * Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
    * Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

    Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

    #NullCoalescing #NullChaining #LanguageDesign

  5. After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the , and here’s why:

    * If you’re getting just one thing, the getter can take an optional default result value. works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
    * If you’re walking down a long uncertain chain, I have two arguments:
    * Knowing the path that leads down into the object to the specific thing you want kinda sounds like an violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
    * Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

    Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

  6. After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:

    * If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
    * If you’re walking down a long uncertain chain, I have two arguments:
    * Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
    * Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

    Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

    #NullCoalescing #NullChaining #LanguageDesign

  7. After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:

    * If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
    * If you’re walking down a long uncertain chain, I have two arguments:
    * Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
    * Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?

    Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.

    #NullCoalescing #NullChaining #LanguageDesign

  8. Một bài viết từ /u/EgregorAmeriki thảo luận về đóng gói (encapsulation) trong lập trình không cần dùng từ khóa private, thay vào đó áp dụng thiết kế dựa trên giao diện (interface-based design) để tối ưu tính bảo mật và tính linh hoạt của code.

    #Lập_trình #Object_Oriented #Design_Pattern #Công_nghe #Thiet_ke_phan_mem #Programing #OOP #SoftwareDesign #Encapsulation #InterfaceDesign

    reddit.com/r/programming/comme

  9. 📜 Behold, a relic from the distant past—2013! Back when "Page Object" was the new black in the world of #testing, because clearly, nobody knew that UIs change. 🤯 Marvel at the revolutionary idea of not frying your tests with a side of HTML spaghetti, as if #encapsulation wasn't already a thing. 🍝
    martinfowler.com/bliki/PageObj #HackerNews #PageObject #HTMLSpaghetti #UITrends #HackerNews #ngated

  10. 📜 Behold, a relic from the distant past—2013! Back when "Page Object" was the new black in the world of #testing, because clearly, nobody knew that UIs change. 🤯 Marvel at the revolutionary idea of not frying your tests with a side of HTML spaghetti, as if #encapsulation wasn't already a thing. 🍝
    martinfowler.com/bliki/PageObj #HackerNews #PageObject #HTMLSpaghetti #UITrends #HackerNews #ngated

  11. 📜 Behold, a relic from the distant past—2013! Back when "Page Object" was the new black in the world of #testing, because clearly, nobody knew that UIs change. 🤯 Marvel at the revolutionary idea of not frying your tests with a side of HTML spaghetti, as if #encapsulation wasn't already a thing. 🍝
    martinfowler.com/bliki/PageObj #HackerNews #PageObject #HTMLSpaghetti #UITrends #HackerNews #ngated

  12. 📜 Behold, a relic from the distant past—2013! Back when "Page Object" was the new black in the world of #testing, because clearly, nobody knew that UIs change. 🤯 Marvel at the revolutionary idea of not frying your tests with a side of HTML spaghetti, as if #encapsulation wasn't already a thing. 🍝
    martinfowler.com/bliki/PageObj #HackerNews #PageObject #HTMLSpaghetti #UITrends #HackerNews #ngated

  13. quotes from the text:

    "The concepts rejected as “not complex enough” might be simple building blocks, like molecules in a living body, that can be combined with other concepts to create a framework that can handle an adequate amount of complexity."

    "I.e. that the black box has only the purpose of simplification and not that of knowledge elitism and hidden power structures."

    #ComplexSystems #Encapsulation