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/)PY
Posts
2
Comments
188
Joined
2 yr. ago

  • Basically the company is "losing" money every time someone claims the promotion because they are giving their service away for free.

    Normally, companies will have a good estimate on how many people will make use of the promotion and how much money they will "lose", but sometimes the reality exceeds expectations and so they put a cap on tbe number of times a promotion can be claimed so as to not get exploited too much.

    Btw I say "lose" in quotes because it may not be an actual loss of money but a loss of potential earnings from a customer. Also, don't worry about the downvotes, I've seen many innocuous comments also get a few downvotes for no reason.

  • Reading your comment and #32459, I realize that VSCode source control did have some major issues back then.

    It looks like they have improved though, as the latest VSCode I use doesn't auto-initialize repositories anymore.

  • He wouldn't have seen the "Discard Changes" button at all if source control wasn't already setup (and detected by VSCode).

    No sane program will delete files when you initialize source control either.

    As I found later, VSCode did have weird behaviors with source control back then. My experience is more with the latest versions.

  • "Changes" encompass more than you think. Creating / Deleting files are also changes, not just edits to a file.

    • If the change is an edit to a tracked file, "Discard Changes" will reverse the edit.
    • If the change is deleting a tracked file, "Discard Changes" will restore it back.
    • If the change is a new untracked file, "Discard Changes" will remove it as intended.

    It can also be all of them at the same time, which is why VSCode uses "Changes" instead of "Files".