• 26 Posts
  • 391 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle
  • Visual Studio provides some kind of AI even without Copilot.

    Inline (single line) completions - I not always but regularly find quite useful

    Repeated edits continuation - I haven’t seen them in a while, but have use them on maybe two or three occasions. I am very selective about these because they’re not deterministic like refractorings and quick actions, which I can be confident in correctness even when doing those across many files and lines. For example invert if changes many line indents; if an LLM does that change you can’t be sure it didn’t change any of those lines.

    Multi-line completions/suggestions - I disabled those because it offsets/moves away the code and context I want to see around it, as well as noisy movement, for - in my limited experience - marginal if any use[fulness].

    In my company we’re still in selective testing phase regarding customer agreements and then source code integration into AI providers. My team is not part of that yet. So I don’t have practical experience regarding any analysis, generating, or chat functionality with project context. I’m skeptical but somewhat interested.

    I did do private projects, I guess one, a Nushell plugin in Rust, which is largely unfamiliar to me, and tried to make use of Copilot generating methods for me etc. It felt very messy and confusing. Generated code was often not correct or sound.

    I use Phind and more recently more ChatGPT for research/search queries. I’m mindful of the type of queries I use and which provider or service I use. In general, I’m a friend of ref docs, which is the only definite source after all. I’m aware of and mindful of the environmental impact of indirectly costly free AI search/chat. Often, AI can have a quicker response to my questions than searching via search ending and on and in upstream docs. Especially when I am familiar with the tech, and can relatively quickly be reminded, or guide the AI when it responds bullshit or suboptimal or questionable stuff, or also relatively quickly disregard the entire AI when it doesn’t seem capable to respond to what I am looking for.






  • One of the two associations is in power and actively dismantling society. The other develops a technical product and runs a Lemmy instance many people and other instances have blocked.

    Handling or concluding them a bit differently seems quite fine to me.

    That being said, I’ve seen plenty of Lemmy dev connection criticism on this platform. I can’t say the same about FUTO.





  • The attack surface is the flaw. The chain of trust is the flaw/risk.

    Who’s behind the project? Who has control? How’s the release handled? What are the risks and vulnerabilities of the entirely product delivery?

    It’s much more obvious and established/vetted with Mozilla. With any other fork product, you first have to evaluate it yourself.



  • I strongly disagree.

    Coloring is categorization of code. Much like indent, spacing, line-breaking, aligning, it aids readability.

    None of the examples they provided looked better, more appropriate, or more useful. None of the “tests” lead me to question my syntax highlighting. Quite the contrary.

    By reducing the highlighting to what they seem important, they’re losing the highlighting for other cases. The examples of highlighting only one or two things make it obvious. When you highlight only method heads, you gain clarity when reading on that level, across methods, but lose everything when reading the body.

    I didn’t particularly like their dark theme choice. Their initial example is certainly noisy, but you can have better themes and defaults with more subtle and more equal strength colors. The language or framework syntax and spacing can also influence it.

    Bolding is very useful when color categorizes code to give additional structure discoverability, just like spacing does.


  • I failed the question about remembering what colour my class definitions were, but you know what? I don’t care. All I want is for it to be visually distinct when I’m trying to parse a block of code

    Between multiple IDEs, text editors, diff viewers and editors, and hosted tools like MR/review diff, they’re not even consistently just one thing. For me, very practically and factually. Colors differ.

    As you point out, they’re entirely missing the point. What the colors are for and how they’re being used.







  • It’s intended to become a spiritual successor to ThiefMD.

    What does it want to or already do different or better than ThiefMD?

    I see the release has a flatpak. A Windows binary or installer would be great too, attached to the release, so it doesn’t require cargo toolchain and build to use.

    Wait. Does it even support Windows? I guess not? I read Rust and GTK and assumed it would.