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/)PJ
Posts
0
Comments
938
Joined
2 yr. ago

  • I've used both Enpass and Proton. Enpass is a bit more feature-ful, mainly because Proton Pass is new. I switched away from Enpass as I didn't like that they basically had me pay for it three times, even though the first one was a lifetime license. But I needed my passwords. Finally decided to put in the effort to move away from them as their constant begging to subscribe was annoying. So switched to Proton since I already subscribe to the plan that includes Pass.

    Proton is working on expanding features and have added a few in the short while I've had it. I'd suggest Bitwarden over Enpass personally, particularly if you want features Proton Pass doesn't offer yet (like no desktop or web app yet, but they are working on both, so until then, I need to use a browser extension)

  • No, quality is independent of location of production. Proof of the pudding is in the eating as they say. Reputation is tied to the producer. Quality is tied to an individual instance of the product. Thats why certain things have QA tags. This technology doesn't represent quality. It only verifies sourcing.

  • Somewhat of a tangent, but can we stop caring about the location where a product was made and focus solely on quality itself? Like, I bet the counterfeiters make a lot of money by producing quality cheese that taste just as good but are just made somewhere else.

  • But the same result would occur in socialism. Even communism. I don't know what you expect to happen in any societal economic structure that would suddenly give you the freedom to do whatever you want whenever you want. Jobs existed the same way all the way back then as they do now. And that was the birth of capitalism, not before it. Most didn't own their land. It belonged to a king or emperor. Sure there are exceptions and caveats, but to say capitalism didn't exist back then isn't accurate. Capitalism isn't bad. It's how it's implemented that makes it awful. I think we need to migrate to socialism via capitalism. But it requires winning of the minds of the populace and that won't happen until folks have an accurate understanding of both capitalism and whatever system you want them to transition to. I don't even know what system you're supporting with your question. It sounds like you're trying to describe some sort of star trek utopia that supposedly is advanced beyond economic systems (yet how many episodes revolved around trade deals between planets and races.... but I digress).

  • ? I mentioned it twice. And you sounded like a manager a little bit in one comment, and then a lot in the followup reply to it. To the point it sounded like you were defending it. Making claims that developers aren't allowed to make the choice you were saying to make. So it was really weird. I don't even know how your stance makes sense from your point of view.

    Edit: and thanks for ignoring anything of actual value to reply to.

  • That sounds like bad business. No application is 100% unique in everything. Code reuse saves time. If you are unable to bring anything from one app to another, you're doing it wrong.

    Let me guess though, I was right. You're a manager not a developer.

  • In my world we prioritize one.

    Weird. In most cases priorities change as the situation demands. The application doesn't matter when it comes to maintainability. Tech debt will take down any application if you keep ignoring maintainability at the expense of just delivering more and more. You sound more like a manager than a developer.

  • You're setting up a theoretically boogie man that no one said exists and then setup the extreme opposite point of view. You're annoying the people that are actually sane. You're being dogmatic in your one views and too extreme.

  • maintainability is arguably not a value-added for the end user. But still absolutely important. Robustness of code is arguably not visible to an end-user, until it fails. And that's very important. Features are great, but quality is still important and is basically the mortar between the bricks that are features. Only caring about features leads to poorly written applications.

  • I'm sorry. Whoever wrote that should give up trying to write articles. It's poorly written and will never convince anyone to change their mind. It's shit. "I know how to convince people they're wrong. Insult them. Setup a ton of strawman arguments. Genius."

    Whoever wrote that is bad and should feel bad.