• 1 Post
  • 319 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle









  • Plus, the license was only changed on a secondary branch. The default branch still has the MIT license. The text at the top isn’t “this is the license file you have open” it’s “the repo is licensed under this” so it’s correct behavior but bad UX. It would be most user-friendly to show repo license and then also say “this branch has an invalid license, beware shenanigans”







  • I imagine they’d be eyeing things like having a partnership with patreon so patrons get access to an exclusive subreddit at a certain tier (with reddit getting some cut). Not saying patreon specifically would go for that but I imagine that type of monetization is what they’d be mostly considering. Or maybe a better example would be something in the realm of substack. Paying directly for access is hard to get people to go for without a third party with financial incentive to drive content.




  • MXRoute is about a decade old and based in Texas. It’s in that “unix philosophy” category of doing something well and stopping there so you won’t get them advertising their new crypto wallet or AI software on you. It’s mostly geared for more technical bring your own domain type of usage. If you’re wanting to use it more as a forwarder and want to store the history locally (or if you don’t email files) there’s a “lifetime” plan available.


  • key@lemmy.keychat.orgtoProgramming@programming.devDefault To Large Modules
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    That makes no sense. If you join b’ and b’’ into b then the external interface of b is the union of the external interfaces of b’ and b’'. The risk of conflicts between those two interfaces is minimal in the situation they described so no need for namespacing.

    I expected the argument to be based on total effort to split then join the internal code compared to the context switching cost of splitting and then splitting again (with an appeal to agile vs waterfall). But this argument feels like they were either dealing with a language/stack with a broken module system that lacks an explicit separation of internal vs exposed or were just joining things strangely.

    Expressing a general rule based solely on a specific situation is a disservice (irony intended).