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

help-circle
  • It’s one thing to pay, and another to be squeezed dry.

    When ads were mostly static banners on websites almost nobody was blocking them, because they were mostly unobtrusive.

    However, they would often link to shady websites that would install random crap, so the usecase for blocking them was already there.

    Then they became animated, and they multiplied. It was one at the bottom of content at first. Then a couple. Then two vertical banners on the sides too. Then more rectangular banners here and there for good measure.

    Then they became unkillable javascript popups, then proper new browser windows. Then autoplaying videos with audio were added. And this is just the visible stuff. Add tracking pixels, tracking cookies, browser fingerprinting, and tons of other spying technology deployed under the guise of “but the content is free”.

    After every step the use of ad and tracking blockers became more legitimate as serving ads moved further and further away from paying for free content and squarely in the space of selling user data collected without consent for huge profit margins.

    If ads and subscriptions were enough to just make a normal amount of profit, very few would be blocking ads or pirating content, because the amount of ads or the price of subscriptions would be reasonable and affordable.

    But since everyone wants to make a 1000% markup on the content they generate, they will drive their very own paying customers away.

    Youtube could have served me a couple ads per video and I would have kept using it forever. Instead they served me a minimum of 20 ads per video, so now they will serve me zero, forever.

    Netflix could have gotten 12 euros every month out of me for their dwindling and dwindling content selection. Instead they wanted 14 after a while. And 17 after a while. And 19 after a little while more. All the while refusing to serve me the 4k content I paid for.

    So instead they now get zero too.

    I am very happy to pay for content, and a lot of people like me. But the comment you originally replied to was in reference to youtube increasing the price of their subscription by ludicrous amounts. You replied there content isn’t free, and I replied that youtube has no problem making money. The increases are not to keep youtube afloat, is to make youtube make 10 billions in profit rather than 8 next year.

    It’s not about paying a fair amount of money for content, it’s about making you pay all that you can give and suck you dry.

    So to your question “how do you pay for content/services in general?” I answer “with money”, but that is not what is happening here.




  • Meh. Been developing professionally with C++ for 10 years at this point. I’m one of the weird people that kinda likes C++ and its pragmatism despite all its warts.

    I’d like C++ better if it didn’t have inheritance. There are better solutions to model interfaces, and without inheritance people can’t write class hierarchies that are 10 levels deep with a different set of virtual functions overridden (and new virtual functions added) at each level.

    And yes, that is not hypothetical. Real codebases in the real world shipping working products do that, and it’s about as nice as you can imagine.


  • You do have a terminology mismatch. In C++, an abstract class is a class with at least one pure virtual method.

    Such classes cannot be instantiated, so they are useful only as base classes.

    An interface is more of a concept than a thing.

    Sure you can say that Iterable is an interface that provides the Next() and Prev() methods and you can say that Array is an Iterable because it inherits from Iterable (and then you override those methods to do the correct thing), and that’s one way to implement an interface in C++.

    But you can also say that Iterable<T> is a class template that provides a Next() and Prev() methods that call the methods of the same name on the type that they wrap (CRTP aka static polymorphism).

    Or you can say that an algorithm that scans a collection T forward requires the collection to have a Next() method by calling Next() on it.

    And I can think of at least 2 other ways to define an interface that isn’t using abstract classes.

    And even if using abstract classes, inheriting from them is definitely the least flexible way to use them to define an interface, because it doesn’t allow one to do something like mocking functionality in tests, because it’s not possible to redefine the class to be tested to inherit from the test interface implementation with mocked functionality, so one still needs something to the effect of dependency injection anyway.

    So yeah, abstract class is very different from inheritance, and it’s also very different from interface, even though it relates to both.