Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AG
AggressivelyPassive @ agressivelyPassive @feddit.de
Posts
16
Comments
1,465
Joined
2 yr. ago

  • The part is what drives me mad. Podcasts and audiobooks are not that hard to do properly. You could very easily separate them into distinct apps or at least a special tab that acts like a proper player. Instead audiobooks are basically albums.

    There's a shuffle button.

    On an audiobook.

  • Spotify actually doesn't make that much profit, if any.

    But the record labels are major shareholders and definitely influence the pricing structure. Spotify is essentially a marketing frontend for the record industry.

  • Again, that's not what obfuscation means.

    Also, what exactly is the difference between cat and journalctl? You can't read a text file without a program either.

    Of course, raw text files are more common, but what you're drawing up here is a mixture of old man yells at cloud and tin foil hat territory.

  • Are you really sure, you're using "obfuscation" right? Because that implies that someone intentionally makes something harder to read to hide something. That's not the case here. Nothing is hidden, it's all there, the formats are well defined and easy to read.

  • "Base load" is not that much. Off shore wind is almost always blowing, and all the other renewables can be stored via batteries or hydrogen (or tanks, in case of biogas). Yes, that's a whole lot of stuff, but the technology exists, can be produced on large scale and (most importantly) doesn't cause any path dependencies.

    Nuclear is extremely expensive, as the article highlighted. And to be cost effective, power has to be produced more or less constantly. Having a nuclear power plant just for the few hours at night when wind and sun don't work is insane - and insanely expensive.

  • I think you don't quite understand the comment.

    Current pharmaceuticals are usually a (life)long prescription. It's not like antibiotics, where you get a dose for a few days or weeks and you're done. Antidepressants have to be taken for years. Every day. That means revenue every day. It's a treatment, not a cure.

    MDMA on the other hand is a (potential) cure. You take it a few times under supervision and that's it.

    Problem is, this takes away customers from the former group. And that means, far less revenue from "traditional" psychopharmacology products. MDMA cannibalizes other drugs.

  • I think you are either trolling or you fundamentally don't understand, what you're talking about.

    Nothing is obfuscated. You can download each and every code file, audit it, and build the binaries from exactly that code. You can even compare the binaries to the ones provided by major distros thanks to reproducible builds.

    Just because you don't understand code, doesn't mean it's obfuscated. Following that logic, even a loaf of bread is "obfuscated" because you don't understand sour dough.

  • And how many people do you think could accurately, or even ballpark, estimate their workload? I couldn't tell you, whether my workload would benefit from more e or p cores and by how much.

    What you're implying here is an illusion of accuracy. You want accurate numbers for something that you can't really judge anyway. These numbers don't mean anything to you, they just give you the illusion of knowing what's going on. It's the "close door" button in an elevator.

  • For example being able to get a grasp of the rough performance from the have.

    i5 10500 is faster than i5 10400. But is 6p4e better than 4p8e?

    It's illusionary to fit everything about a CPU into its name. What you're proposing is essentially the entire value column of the spec sheet concatenated.

  • The reality is, that hardly any projects actually need or benefit from micro services.

    Most applications would scale just fine as a monolith, micro services seem to be rather an organizational tool to separate modules, because you can't come up with a proper architecture.

  • The number behind Ultra is pretty much the same as with the i$x scheme. 3 is entry, 5 is mid range, 7 is high end, 9 is bad decision making.

    The number after that kind of works like before. So higher number means more better. Probably with an extension for coming generation. Remember, the first i5s had 4 digit names as well, the fourth digit was prepended to indicate generations.

    Thing is, there's no really good naming scheme, because there are so many possible variants/dimensions. Base clock, turbo clock, TDP, P core count, E core count, PCIe lanes, socket, generation ,..... How would you encode that in a readable name?

  • That's actually how the comment above interpreted the ellipses. The difference is more, why the words are missing.

    The "modern" interpretation is that you are too annoyed or afraid to finish the sentence. In the sense of "son of a ...." in case of annoyance.

    The "old" interpretation is either temporal (I'm not finished writing) or simply an acknowledgement that the fragment is just a fragment.

    So the modern reader will interpret much more context into the missing words, leading to the exchange above.