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/)S
Posts
6
Comments
552
Joined
8 mo. ago

  • No. They might have reasons, but passing on violence and pain to others is never justified.

    If it's justified for one person to bully another because of trouble at home, then the other person is justified to hit back and so on. That's how you get blood feuds. Dumb idea.

  • I started work on an automod a year or so ago, and there was no real interest in it. Tbh, I think lemmy is far too small to really benefit from an advanced automod.

    Remember, all of lemmy together is smaller than the Crackberry forum or the LTT forum. It's smaller than many city subreddits.

    That means the time investment of setting up and tuning an automod bot and the trouble caused by false automod actions probably isn't worth the time saved by the automod's correct actions.

  • The problem there is that an UK patent is practically worthless. For a patent to be somewhat worthwhile, you need an international one.

  • The patent system is fundamentally broken. It could be fixed, but right now, in the current state, it totally fails all its good for.

    • Patents can be filed with hardly any checks in place. The point of a patent office is to issue patents, not to issue valid patents. Validity is verified in court.
    • Patents don't give you an actual claim to anything, only the right to sue, if you have enough money to afford a lawsuit. In patent court, running out of money is a common way to lose, which means that patent court strongly favours those with money.
    • Patents are really expensive. We are talking about tens of thousands of Euros.

    All that means that patents are completely unviable for the "small inventor" they were meant to protect. Patents largely function as a way for large corporations to bully smaller competitors out of the market.

    It is a totally viable strategy to get an invalid patent and use it to bully a smaller competitor off the market who can't afford to invalidate your patent.

    As a small inventor patent law becomes an absolute minefield, since there's hardly any way to find all the patents that you might accidentally violate with your invention.

    Follow-up patents (meaning, you change some minor detail when your patent runs out to artificially extend the life of your patent by getting a new patent on the slightly modified versions) also break the other goal of patents which was to force inventors to open-source their invention through the patent.

    So instead of a way to protect small inventors and making sure that ideas end up available to everyone, the current patent law does the exact opposite.

  • Considering how important WASM is, I haven't seen a single application of it.

    WASM on the server seems especially weird since it's not much more than a bytecode interpreter. At that point you could just use a JVM, maybe with some more cut-down API to make it more sandboxed.

  • What most people intuitively understand, though, is that public roads are expensive, not profitable and still a worthwhile investment.

    It's kinda baffling that the same isn't intuitively understandable to everyone when it comes to public transport.

  • Yeah, the problem is the balance. In-house code sucks. Nobody outside the team tests your code. Self-developed code is not battle hardened. You can only use the skills available in your team and especially for specialist topics like databases, security or cryptography having in-house expertise is rare and expensive.

    Using external dependencies sucks. You are dependant on externally developed code and on someone elses skills, quality controls and trustworthyness, and you usually don't have time or ability to really verify any of that. Even a good dependency can get stuck in some kind of development hell (like e.g. OkHTTPClient) and not deliver updates for years, and supply-chain attacks are constant threat.

    In the end both options suck for different reasons and it really depends on the scenario where one or the other is useful. Leftpad is an extreme example, but most options are less obvious.

  • You had your first total team wipe within 3 months? Impressive.

    I had three of them so far, but within 12 years.

  • Calling a non-prostitute woman a prositute is quite offensive in most languages I would guess.

    Offending someone's mom (and by extension their heritage) might be anachronistic in some regions, but it really isn't in others.

  • It's kinda like AI upscaling.

  • "There is no game" was also kinda similar in the aspect of 4th wall not existing. The game conversing with the player is one of the main plot points.

  • I'd argue if something needs to be talked about in news/late night talk shows as a curiosity it's not mainstream.

    Today, streaming is totally mainstream and the concept is not something that would appear in news/late night talk shows unless there's something specifically extrodninary (e.g. a death) that happens in the context of streaming. But the concept of streaming on its own is so commonplace, that it wouldn't be talked about in TV.

  • I could maybe have been clearer when saying "significant capacity".

    Most projects I worked in did use OOP in some capacity, but only in quite small amounts.

    My point mainly was that a lot of people think that using the keyword "class" for structs (aka data classes) or modules (aka service/controller classes) counts as OOP and that's not the case.

    But I agree that Java and similar languages could use some other type of syntactic sugar for modules. But then again, it would literally just be another name for the same thing.

  • Yeah, a lot of things existed way before they got mainstream.

  • Seems to be English-specific. German, for example, doesn't do that.

  • Have you ever seen a real-world project that actually uses OOP in any significant capacity? I haven't.

    When using Java, you might write "class" on top of your structs and modules, but actual OOP with self-contained classes that contain both data and business logic using inheritance and all the other OOP concepts, that's incredibly rare.

  • It's a double-edged sword and understanding when to re-use and when to re-implement is an art that goes wrong more often than right.

  • I've been working as first a Python and then a Java dev for the last 15 years and I can count the amount of times when I've seen actual OOP on one hand.

    I mean, we write "class" at the beginning of our modules and at the beginning of our structs, and we write "interface" at the beginning of our header files, but none of that is actually OOP.

    If you use Spring Boot, you are essentially doing C (not even C++) in Java.

    You have data-only classes without methods (at best there's a conversion method or something shallow like that) that work identical to C structs. You have service interfaces, which serve the same purpose as C header files. And then you have data-less collections of functions (service/controller classes), which work like .c files.

    Nowhere in this whole process are you actually using OOP techniques.

  • The KPI approach.