home.social

#codereuse — Public Fediverse posts

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

fetched live
  1. Another little project of mine - #WebRTC Guide marquisdegeek.com/webrtcguide/ As seen in my "making phone calls in a
    browser" talks #codereuse

  2. Another little project of mine - #WebRTC Guide marquisdegeek.com/webrtcguide/ As seen in my "making phone calls in a
    browser" talks #codereuse

  3. Another little project of mine - #WebRTC Guide
    marquisdegeek.com/webrtcguide/ As seen in my "making phone calls in a
    browser" talks #codereuse

  4. Another little project of mine - #WebRTC Guide
    marquisdegeek.com/webrtcguide/ As seen in my "making phone calls in a
    browser" talks #codereuse

  5. 📱💻 Web devs rejoice! 🎉 With .NET MAUI, #Blazor, and HybridWebView, you can reuse your existing web skills to build native iOS, Android, Mac, and Windows apps 🙌🚀 #WebToNative #CodeReuse #dotnet #dotnetmaui

    dev.to/dotnet/leveraging-exist

  6. 📱💻 Web devs rejoice! 🎉 With .NET MAUI, #Blazor, and HybridWebView, you can reuse your existing web skills to build native iOS, Android, Mac, and Windows apps 🙌🚀 #WebToNative #CodeReuse #dotnet #dotnetmaui

    dev.to/dotnet/leveraging-exist

  7. I've tried multiple crates for parsing cli arguments, and I find them all very hard to use. More than once I've just done my own, missing all the features I wanted to get by using an available crate. Some things clearly does not work all that well for me when it comes to code reuse.

    #Programming #RustLang #Rust #CodeReuse #CliArgumentsParsing

  8. @berkes I like your post!

    @xpmatteo has previously explored the topic of not using frameworks. He may have something to contribute to the conversation.

    Given your interest in the topic I guess you may enjoy Ralph Johnson's work on frameworks (eg definition of framework vs library vs toolkit), its "rule" of Three Examples (from the book Evolving Frameworks) and here from the prev millenium 😀 a list of his resources blogs.ugidotnet.org/luKa/archi

    #coding #codereuse #libraries #frameworks #design

  9. @berkes I like your post!

    @xpmatteo has previously explored the topic of not using frameworks. He may have something to contribute to the conversation.

    Given your interest in the topic I guess you may enjoy Ralph Johnson's work on frameworks (eg definition of framework vs library vs toolkit), its "rule" of Three Examples (from the book Evolving Frameworks) and here from the prev millenium 😀 a list of his resources blogs.ugidotnet.org/luKa/archi

    #coding #codereuse #libraries #frameworks #design

  10. @berkes isn't this an instance of what's called framework lock-in?

    This is my take/guess on why:
    Framework authors
    1) don't use their own framework (or they use it but unlike users, with access and making changes to their framework code), they like to create it or sell it (and ignore all the good advice from Ralph E. Johnson)

    2) don't practice those good-design principles and don't expect the users of their framework to practice them either

    #coding #codereuse #libraries #frameworks #design

  11. @berkes isn't this an instance of what's called framework lock-in?

    This is my take/guess on why:
    Framework authors
    1) don't use their own framework (or they use it but unlike users, with access and making changes to their framework code), they like to create it or sell it (and ignore all the good advice from Ralph E. Johnson)

    2) don't practice those good-design principles and don't expect the users of their framework to practice them either

    #coding #codereuse #libraries #frameworks #design