• 5 Posts
  • 559 Comments
Joined 1 year ago
Cake day: July 3rd, 2023
  • hemko@lemmy.dbzer0.comtoLinux@lemmy.ml•Zed on Linux is out!English
    3·
    5 days ago

    I’m probably more of a git noob than you

    Doubt =D

    And more to the point, I do appreciate a good user interface with information at a glance or click instead of having to type out a command each time.

    Agreed with good user interface, my criticism was specifically for the vscode default git plugin which I was not compatible with at all but it could be just a me-problem

  • hemko@lemmy.dbzer0.comtoLinux@lemmy.ml•Zed on Linux is out!English
    6·
    5 days ago

    Git has some counterintuitive commands

    Yeah… ‘git merge main’ weirds me out because my brain likes to think the command is merging current branch TO main instead of other way around

    Some IDEs have extra non-native Git features like have inlined “git blame” outputs as you edit (easily see a commit message per-line, see who changed what, etc.), better diff/merge tooling (JetBrain’s merge tool comes to mind), being able to revert parts of the file instead of the whole file, etc.

    Okay this sounds very good, so they actually improve git cli feature wise in addition to implementing GUI for it.

    Thanks for the reply!

  • hemko@lemmy.dbzer0.comtoLinux@lemmy.ml•Zed on Linux is out!English
    11·
    5 days ago

    Going to check out if there’s git integration, because I couldn’t easily find it.

    Asking this because I’m noob, not elitist ass: Why a git integration in ide instead of using the cli? I’ve been working only on few projects where git is used, but the cli seems to be a ton easier to understand how to work with than the git integration in vscode which I discarded after few attempts to use

  • hemko@lemmy.dbzer0.comtoNo Stupid Questions@lemmy.world•What makes it “Legitimate Interest“?English
    66·
    6 days ago

    Copypasting here answer to similar question in superuser.com

    https://superuser.com/a/1624773

    Under GDPR there are 6 grounds based on which anybody can process personal data. Those are:

    • Consent

      You explicitly agreeing to it. This needs to be opt-in, informed, specific and freely given, but also gives the greatest freedom to a company.

    • Contract

      This is the basis which raj’s answer confused with legitimate interests. This is the processing that is required to fulfil a contractual obligation (note that contracts do not always need to be signed, e.g. an order from an eshop).

      need to process someone’s personal data:

      • to deliver a contractual service to them; or
      • because they have asked you to do something before entering into a contract (eg provide a quote).

      Source: ico.org.uk

    • Legal obligation

    • Vital interests

    • Public task

    • Legitimate interests

      Legitimate interests are the most flexible lawful basis for processing personal data. In the words of the UK’s ICO 1:

      It is likely to be most appropriate where you use people’s data in ways they would reasonably expect and which have a minimal privacy impact, or where there is a compelling justification for the processing.

      Source: ico.org.uk (worth reading!!!)

      The underlying text from the GDPR itself (definitions and links added are mine)

      processing is necessary for the purposes [=a specific minimal type of processing] of the legitimate interests pursued by the controller [=the company wanting to process your data] or by a third party except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject [=you] which require protection of personal data, in particular where the data subject is a child.

      Source: GDPR Article 6(1f)

      So basically a legitimate interest claim by a company is them saying ‘we are convinced that our interest outweigh the negligible impact on the privacy of the people whose data we process’. This doesn’t give them a free pass though, as GDPR also gives the right to object

      The data subject shall have the right to object, on grounds relating to his or her particular situation, at any time to processing of personal data concerning him or her which is based on point [public interest] or [legitimate interest] of Article 6(1), including profiling based on those provisions.

      Source: GDPR Article 21(1)

      Which then require the company to either concede and stop the processing or justify their claim. Companies in practise have taken this to mean they can basically just do a bunch of processing and as long as they make the objection process (=opt-out) easy enough the theory is that they will get away with it.

    Notes:

    1 The UK left the EU, but they still have by far the best English language resource explaining GDPR and for the time being “UK GDPR” matches “EU GDPR” one on one as far as I am aware