• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle

  • There was a reason I switched to Sidebery over The native implementation but I can’t remember. Maybe it was the Panels feature that FF Containers didn’t offer at the time.

    I do miss some of the functionality of the Mozilla add-on though, I don’t think they opened up APIs to some of the extended tab/window options.






  • This is actually the sole reason I went with laser - I print so rarely that a traditional inkjet would not stand up to long periods of inactivity, as the ink wells would either dry up or the printer firmware would force replacement.

    A monochrome laserjet should run you about the same price as an inkjet and cartridge refills (since the included inkjet cartridges won’t last long), and would probably suit 90% of most user needs. I highly recommend the Brother line of monochrome laser with duplexer, mine is 10 years old and going strong.



  • I’ll be the first to admit that my technical experience in this field is limited, but I have been following the tech for some time.

    Transparent display tech has come a long way since its inception, but from either a transparency standpoint or as a high fidelity interface for VR I can’t see how it’s a viable option. Given the choice I would much rather have a crystal clear UI with simulated AR than compromise display quality with adjustable transparency.

    Why Apple chose to develop the googly-eyes outward-facing display is beyond me though. Maybe it looks better in person than in their promos.




  • It would be literally impossible for me to do my job effectively without Sidebery for container management in FF. As someone with multiple accounts used for various CSPs and other services, being able to spin up an environment with no irrelevant cached user sessions is something I depend on heavily (looking at you, Azure).


  • I can relate to both sides of this fight, but to lend my POV on Apple’s stance, they have a valid argument.

    When you sign the developer agreement and submit an app to the App Store, you are entering into a contract to make concessions to Apple’s business model, and Epic clearly violated these T&Cs.

    If Epic truly wanted to institute change in App Store policies in order to maximize their profits from Fortnite, they would have first engaged Apple to initiate the discussion and work towards an amicable solution, which Apple would likely flat out deny. It’s at this point that Epic could have used its substantial presence in the industry to rally the developers, the press, and its own user base to stand up to Apple policies and effect that change.

    As it stands, their decision to wait for their assured dismissal from the App Store to pursue litigation and position themselves as trying to “stand up for indie developers” comes off as insincere and primarily seeking publicity based on Apple’s action in simply abiding by its own long established policies.

    Note: While I am primarily a Mac user in my personal life, I tend to be very critical of Apple’s business practices in general, and while I have my own negative opinions about Fortnite’s transactional model, I try to be unbiased in my response to their actions and subsequent behavior.