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

help-circle
  • It doesn’t come across insulting at all. It comes across as naive.

    Like, it literally has a Wikipedia page and doesn’t mention anything else.

    I mean, literally isn’t used to mean just figuratively. It’s actually an exaggeration to mean that the concept is so strong that it literally triggered the figurative comparison for real. Context is key there. And context is important. That’s the great thing about that though is you rarely need extra information to show which definition you mean. If I said it’s so hot outside that I’m literally on fire, you don’t need to question the meaning.

    But here? Let’s be honest. The word usage has exploded on Lemmy. They wanted so badly to use the term in the cool way. No one would have used the word that way before. No one uses its ‘literal’ definition now really. Because it’s generally not how humans in society have discussions. No one describes the enshitification of something as a clinical description. If it were used as a joke? Sure. But now it’s either someone so divorced from reality that they don’t even know how to communicate or it’s just folks who heard the word, thought it was cool, but didn’t really understand it. That’s all that is. I can’t believe folks are trying to defend the “evolution” of language on one hand by describing a loss of accuracy and clarity in language, but then on the ither hand defending it from some weird historical perspective. It’s honestly entertaining to see people come at this and argue with entirely contradictory points of view. “Words change meaning and this is it’s new meaning” vs “that’s been its meaning forever”. Like, let’s try to at least coordinate the defense of the person who wanted to sound cool. No one says “enshittified” in place of “it’ll go to shit” or “get fucked”. But instead you expect me to believe this is some ole-timey bastard saying, “sir, it will be enshittified.” Come on buddy. It’s weird you even thought all those words you spoke would sound insulting. Like you actually had a good point or something. See? That last bit there. That’s what something insulting sounds like.







  • Except it means nothing in that usage. Some people ran with it. Others decided to not be ridiculous and just apply it without rhyme or reason. Outside the Fediverse, it’s nearly unknown. Inside the fediverse, when it’s misused, it’s usually in a very obvious and uncritical manner. It is still commonly used properly.

    Don’t take the power away from words just because you literally like the word itself. It’s immature.

    If you use it to apply to all unpopular corporate decisions, it’s no longer powerful and doesn’t have any meaning.


  • The general driving force is different though. It’s a process that involves devaluing a service by basically commoditizing two forces against each other. Simply dropping value-added features to save money is just the race to the bottom.

    Dropping a feature is the equivalent of charging for extra BBQ sauce packets. It’s not the same driving force like Instagram where they play two forces against each other. Like the way Google has been going with shoving way too many ads in there. That is a different motivation because it’s valuing one customer at the expense of another. Something like dropping free service XYZ is just cutting costs.

    The word is getting overplayed and it feels like everyone has the same word-a-day calendar and are now trying to use it as much as possible.

    It’s more impactful and retains meaning if we keep it succinct instead of just the equivalent of “an unpopular decision that saves money to increase shareholder value”. It’s all about recognizing you are a product as well as a user. It’s that the services don’t have an incentive to serve you. Its just so much more meaningful as long as we don’t remove all of that meaning to just show we don’t like corporatism.


  • But their entirely different processes. One is exploiting one market vs the other. Here it wouldn’t necessarily be exploiting a market, but destroying value of a free service. If you’re worried about personal info being the exploitation, it’s going to be very limited and likely already in place. An account structure is usually more the first move toward monetizing the service directly and enabling the ability between free and premium services. That’s still shitty, but for entirely different reasons. So I just don’t like seeing the original word lose all meaning whatsoever beyond its root word. It basically guts it of all of its nuance and importance and just turns it into a noun form of taking something and making it shitty. We don’t need to do that.


  • Can we stop the overuse and over-generalization of “enshitification” which Doctorow had given very explicit meaning to in regards to social networks? It does not simply mean commoditization which is not quite the same but almost synonymous with 'race to the bottom’s in regards of trying to increase revenue while simultaneously decreasing costs.

    Edit: I’ll admit narrowing to “social networks” is a bit too narrow, but the point still stands that it’s for two way platforms where there are “two markets.” Phillips Hue does not have a two sided market.








  • The summary uses the term “vanilla JS” in a weird way. It’s just to further denote it’s not TypeScript because TypeScript is a language that essentially extends JavaScript. It’s not a framework. This is about language choice of TS vs JS inside large complex libraries only.

    Libraries tend to have a need for generic typing due to the nature of being code used by other code. So you get a lot of syntax craziness involving Type parameters.

    You can still use the libraries mentioned in a TS project. They’re just not written in TS. TS and JS can be in the same project. Moreover, it even states this isn’t about developers using TS in non-library projects.


  • Before the link was edited, when it was just a raw url with no markdown code.

    It’s always with markdown. Lemmy is the only web app that can access it without markdown. I explained it like four different ways now. If you don’t understand it by now, you never will.

    It worked for me and it’s why I provided a full link. Since it was created on Kbin, it was escaped by Lemmy as well. So lemmy will display the app just like Kbin would. But anyone who creates a link on lemmy, it will always look wrong in every other web app or third party app. It’s simply not possible for a third party app to display a link properly that was created by a lemmy user. Same goes for code boxes. They can only be displayed properly by Lemmy and no one else. It’s not possible for third party apps to display them properly.

    Lemmy is the only one that can display links and code boxes created by Lemmy users. Links and code boxes created by every other platform displays properly everywhere.

    You’re literally hand waving it away because it still works even though it’s impossible to parse by any other app. Just because it is only aesthetic doesn’t mean it’s a bug. The bug affects jerboa more than Kbin. I still helped those users instead of your pretentious ass by saying “oh well, not my problem.”

    When there’s a problem that only exists with lemmy, it’s lemmy.

    Do you need me to explain it yet another way? Do you need an ELI5?

    You’re the pretentious one speaking from some authority without having any clue what the fuck you’re talking about.

    I’m done. You’re blocked so I won’t be angered by any stupid replies from you.


  • The link works for me. I was helping other folks who may have an issue with bare links as pointed out by the other commenter.

    Either way, Lemmy is the reason non-lemmy readers can’t actually properly parse the information. The information is not what’s stored in the database. Only Lemmy can display it properly since it wraps it up in a bunch of markup that is then provided to third parties. As a developer, I don’t know what reasoning you still think you have to believe it’s not Lemmy. Everything you’ve said so far does nothing to backup that point.

    Edit: also, I’m done here. I’m not interested in convincing a non-developer their favorite platform isn’t perfect.