tux spinning

codeberg: https://codeberg.org/asudox

aspe:keyoxide.org:D63IYCGSU4XXB5JSCBBHXXFEHQ

  • 33 Posts
  • 1.09K Comments
Joined 1 year ago
cake
Cake day: January 18th, 2025

help-circle









  • If you check the ActivityPub object, you actually do see the link:

    https://browser.pub/https://beehaw.org/post/23981271

      "source": "https://www.tomshardware.com/tech-industry/artificial-intelligence/chatgpt-could-prioritize-sponsored-content-as-part-of-ad-strategy-sponsored-content-could-allegedly-be-given-preferential-treatment-in-llms-responses-openai-to-use-chat-data-to-deliver-highly-personalized-results",
    
    {
    ...
          "href": "https://www.tomshardware.com/tech-industry/artificial-intelligence/chatgpt-could-prioritize-sponsored-content-as-part-of-ad-strategy-sponsored-content-could-allegedly-be-given-preferential-treatment-in-llms-responses-openai-to-use-chat-data-to-deliver-highly-personalized-results",
          "type": "Link"
    ...
    }
    

    I wonder why it isn’t shown.


  • asudox@lemmy.asudox.devtoFediverse memes@feddit.ukPieFed be like
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    3 days ago

    Once it approaches maturity, surely it could switch to e.g. moar reliability at the expense of agility?

    Unfortunately, you can’t just “switch” to more reliability. That’s not how it works. Reliability is affected by the design and implementation of the software. If your software wasn’t reliable in the beginning, you’ll have lots of “fun time” rewriting and even more “fun time” debugging components to try and make it more reliable.

    At some point, this is no longer practically viable and the unreliable parts stay as they are. Especially if the unreliability is a design flaw. This is known as “technical debt”:

    While an expedited solution can accelerate development in the short term, the resulting low quality may increase future costs if left unresolved.

    However, failure to prioritize and address the debt can result in reduced maintainability, increased development costs, and risk to production systems.

    https://en.wikipedia.org/wiki/Technical_debt

    As for the 0 priority of testability, I found a test directory in the repo: https://codeberg.org/rimu/pyfedi/src/branch/main/tests

    Though I haven’t looked at how much the tests cover, there seems to be some sort of testing. So perhaps this importance table is a bit outdated indeed.

    although tbf that is only one of several, others being “it’s too complex”

    As I explained in my original comment, Rust has a few strict rules and concepts that force a particular discipline (I guess you could also call it style of code). And since it has those safety guarantees, you need to have things like lifetimes and trait bounds and such. These things naturally make the code harder to read and/or complicated. But as I said, they are worth it and will save you many bugs that might occur at runtime (especially ones you do not want to debug at runtime. like concurrency bugs).


  • asudox@lemmy.asudox.devtoFediverse memes@feddit.ukPieFed be like
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    3
    ·
    edit-2
    3 days ago

    You’ll appreciate Rust the more you use it. Especially if you come from languages that do not have the same luxuries like Rust.

    The type system and the safety guarantees that are enforced by the compiler are so pleasant to work with, I actually do not ever want to use any other language.

    This is also one of the reasons why many companies are now choosing to use Rust. It is not just because it is new and “shiny”, but because it has real world benefits. Memory safety, for example. The tooling is also superb.

    Yes, you will not be able to write at the speed a Python dev will write a project, but the rules and concepts Rust introduces are very worth it.

    I think the importance table of Piefed demonstrates this pretty well:

    • Performance 4/5
    • Scalability 2/5
    • Agility 5/5
    • Reliability 1/5
    • Security 2/5
    • Testability 0/5
    • Modifiability 5/5
    • Affordability 5/5
    • Manageability 5/5

    https://codeberg.org/rimu/pyfedi/src/branch/main/docs/ARCHITECTURE.md#desired-quality-attributes

    You simply cannot have good reliability or security if you prioritize agility over everything. Same goes for scalability

    Also why does testability have a priority of 0?