• 0 Posts
  • 16 Comments
Joined 3 months ago
cake
Cake day: April 26th, 2025

help-circle

  • Yeah, why not? I’ll go ahead and make that suggestion.

    What? Do you understand what I’m asking? Do you understand what you’re suggesting?

    I mean, the terminal allows them to ctrl-c, ctrl-v a simple solution developed by someone else, even if that someone else didn’t bother to build out a GUI for applying their changes.

    So googling how to do someone, copy/pasting command is better than finding it in GUI? How high are you?

    The convoluted steps they would have to take to achieve the same effect with a GUI would seriously hinder the GUI-only user.

    Again a solved problem, just make a decent GUI for your application.





  • It is. It’s just… how do you know you’re actually talking to the fingerprint sensor and not a fake one that’s been plugged in?

    Think of it like a locked mailbox: the fingerprint sensor might securely match the fingerprint and only unlock if it’s correct—but if anyone can swap out the mailbox with their own lookalike, and the OS just blindly accepts the “unlocked” signal, the whole security model breaks. Without an attestation mechanism (like SDCP on Windows or secure enclave-backed verification), the OS can’t prove it’s getting input from trusted hardware. Match-on-chip helps, but it’s not enough unless the result is cryptographically signed by the sensor and validated by the OS through a trusted, authenticated channel.

    That’s the gap in Linux: there’s no widely adopted standard for verifying that trust path end-to-end.


  • 3abas@lemm.eetoProgrammer Humor@programming.devJavaScript
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 month ago

    Sure. And you’re entitled to yours. But words have meaning and this isn’t MY OPINION, it’s objective reality. It follows strict rules for predictable output, it is not nonsensical.

    You’re entitled to think it’s nonsense, and you’d be wrong. You don’t have to like implicit type coercion, but it’s popular and in many languages for good reason…

    Language Implicit Coercion Example
    JavaScript '5' - 1 → 4
    PHP '5' + 1 → 6
    Perl '5' + 1 → 6
    Bash $(( '5' + 1 )) → 6
    Lua "5" + 1 → 6
    R "5" + 1 → 6
    MATLAB '5' + 1 → 54 (ASCII math)
    SQL (MySQL) '5' + 1 → 6
    Visual Basic '5' + 1 → 6
    TypeScript '5' - 1 → 4
    Tcl "5" + 1 → 6
    Awk '5' + 1 → 6
    PowerShell '5' + 1 → 6
    ColdFusion '5' + 1 → 6
    VBScript '5' + 1 → 6
    ActionScript '5' - 1 → 4
    Objective-J '5' - 1 → 4
    Excel Formula "5" + 1 → 6
    PostScript (5) 1 add6

    I think JavaScript is filthy, I’m at home with C#, but I understand and don’t fear ITC.


  • 3abas@lemm.eetoProgrammer Humor@programming.devJavaScript
    link
    fedilink
    arrow-up
    11
    arrow-down
    5
    ·
    1 month ago

    It’s not nonsensical, implicit type coercion is a feature of JavaScript, it’s perfectly logical and predictable.

    JavaScript is a filthy beast, it’s not the right tool for every job, but it’s not nonsensical.

    When you follow a string with a +, it concatenates it with the next value (converted to string if needed). This makes sense, and it’s a very standard convention in most languages.

    Applying arithmetic to a string would be nonsensical, which they don’t do.






  • Real world development isn’t creating exciting apps all the time, it’s writing the same exact boring convention based code sticking to an established pattern.

    It can be really boring and unchallenging to create your millionth respiratory, or you can prompt your ide to create a new repo and with one sentence it will create stub out 10 minutes worth of tedious prep work. It makes programming fun again.

    In one prompt, it can look at my finished code and stub out half decent documentation that otherwise wouldn’t have been completed at. It does hallucinate sometimes, or it completely misunderstands the code, so you have to correct a few sentences, but the brain drain of coming to with the sentence structure to write useful documentation is completely lifted, and the code is now well documented.

    AI programming is more than just vibe coding, and it’s way more useful than everyone here insists it’s not.


  • Non of those examples are relevant.

    Those examples are specific tools or specific implementation pattern, AI in development is a tool.

    It doesn’t dictate how to write software or what the written code will look like, it’s a tool that speeds up your code wiring. It catches typos and silly bugs that take hours to debug, it’s able to generate useful unit tests, it can clean up and apply my code style way better than codemaid or resharper ever code, it’s taken care of so much tedious shit and made software development fun again.

    Vibe coding is not the future of development. If you aren’t learning to use AI as a tool in development, you are going to be left behind.

    It’s more apt to compare it to IDEs. Sure, you can still write you entire app in vim and compile it in the terminal, but you would have been very foolish to deny the future of development was in IDEs.