• 0 Posts
  • 189 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • Seems the pitch is just that it supports Apple specific bells and whistles like the emoji bar and beyond that has the stuff other terminals have. I use tilda and use that because it has a critical core feature I haven’t seen in other terminals: it appears full screen over all other windows with a keypress and disappears the same way. Since I use terminal heavily I don’t want to treat it as just another window but as a first class experience which tilda allows. I don’t really get why you’d make yet another terminal without some fundamental core functionality difference like that.














  • 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
    ·
    5 months 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).