• 0 Posts
  • 104 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • When something that big barely turns a profit, I immediately suspect Hollywood accounting.

    But if true, they made a game, covered their costs, left the company with an asset that can keep making sales, and probably developed their in-house talent and tooling along the way. That’s a lot of points in the “win” column.

    Wise leaders understand that, in business, victory means getting to try another project with the same team, next year. Failure means disolution of the business. Earn enough years and projects with the same team in a row, and maybe you take one of the big wins one of those years.


  • This is terrific. Thank you for starting this discussion.

    I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.

    I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.

    But we know from XMPP that proprietary extensions are a huge problem.











  • I liked the big reveal, but I can see how it wouldn’t be everyone’s cup of tea.

    Partial Spoiler

    Normally when Trek is going to do a Trelane or Q story, it’s introduced early in the story. This was a weird left turn at the end, and leaves us wondering if any plotline later will also do so.

    I didn’t mind it in this season, because the season was so focused on about values and tradition, so I wasn’t expecting a hard scifi conclusion. Realizing they were ‘doing a Doctor Who’, wasn’t too shocking to me.

    But as much as I thought it fit here, it’s a weird way to resolve a Trek season, and I hope we don’t get that approach often.