I hate ads, but you're actually right in this case. If done with moderation and purpose—like the YouTube videos that promote a high-quality cooking ingredient while meaningfully explaining why it’s better—it could work well.
From a consumer’s perspective, paying for a product or service is an exchange of money for value. Even with a service, there’s a tangible result—like a fresh haircut or the convenience of not dealing with tax filing. Paying only makes sense when there’s value in return, which isn’t true for many subscription services. Arguments about “maintenance costs” hold little weight for customers who don’t perceive any added value.
In some cases, subscriptions are reasonable, such as when software would be a heavy burden on personal devices, like power-intensive language models, or when it needs to stay compliant with evolving legal requirements, like an accounting software or something.
A larger issue is Apple’s push for subscription-based software in almost everything, often to bolster its bottom line, while damaging the industry as a whole for the reasons mentioned.
Also subscription to a developer is a product for them, it has nothing to do with the product they create for others
It's baffling that people can still think this way in 2024. Almost none of Musk's forecasts, estimates, or product promises have been delivered on time. His history is basically a long list of missed deadlines. Believing that Musk is a good leader is pure delusion, especially now.
i checked them, but libredirect removed the twitter option from the config menu (i guess because of the changes in the twitter api) and the other just a generic url to url redirect. but thanks anyway
I think the more correct statement would be: "The world is moving away from imperative programming altogether, towards declarative programming".
IMO functional programming is just a special kind of imperative programming. I think real distinction is between "imperative/functional", where you describe how to do thing, and "declarative" where you don't care about the hows, but you specify what is the end result you want to see. For example: html (declarative) "I WANT A RECTANGLE AT THIS POSITION AND SIZE": <div style="top, left, height, width">, while imperative, you exactly tell the how, like <for i> then <for j> draw a pixel at that position i,j. Making drawing a box as functional does not make too much sense, because that is a task, which does not benefit from the functional paradigm, but it does helps a lot with cardinality and null checking problems when dealing with other kind of problems.
I think it is already changing into this. Basically every single framework is one kind of declarative wrapper over an imperative language, or you can say every single function library makes the way how you work a little bit more declarative (like in the box drawing demo, you can just use function to write a box. I think in 20-30 years, in a very twisted way programming will be completely declarative by you telling an AI to write a code, first at a very low level of abstraction, but in time more and more complex ways. We'll see
There are lot of think could be done not to pay $12 delivery fee over a $20 order. For example, the cost of delivering a $100 order is pretty close to a cost of a $10 dollar order. This could be used for subsidizing the cheaper delivery cost by the more expensive ones, like saying delivery fee is 25% of the order and no tip, but minimum $5 (or something). So you pay $5 for a $10, $5 for a $20, and $25 for a $100 delivery, which is way easier to swallow. But this is just one of the most primitive ideas to handle that, the point is the make companies to figure out what is feasible, instead of letting them run rampant with whatever shady sh*t they can come up with.