• 0 Posts
  • 56 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • Honestly, this is a pretty badly written and researched article for someone that likes writing so much.

    Like, just the opening two paragraphs about Microsoft controlling document formats … They repeat the same information in both paragraphs and give a rather incomplete history of document formatting.

    It’s also wild to write that many words about Markdown and never discuss its connection to HTML and its foundation in formatting via declarative intent rather than imperative formatting instructions (i.e. in markdown you dont style your title by saying bold / underling / font-size:20, you declare your true intent which is this is the top level title / heading, but that all comes from the underlying structure of HTML which markdown is basically just a simplification of.






  • You’re viewing this through an incredibly skewed lense. The average person will never even consider self hosting nor will care, if anything the average person prefers cloud services.

    The only lens I’m viewing this through is one that dares to imagine that the Venn diagram of “computer users savvy enough to care about privacy” isn’t 100% contained within the circle of “computer users savvy with the terminal”.

    Quite frankly your stance that the ‘average person’ doesn’t care, when this post is LITERALLY from an ‘average person’ who does, is the one that seems off base on its face.






  • masterspace@lemmy.catolinuxmemes@lemmy.worldVim > VSCode
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Have you tried using VSCode / VSCodium? I’ve tried using a VIM based workflow and found myself missing many graphical dev features in VSCode.

    And sure, there’s nothing wild about continuing to use a process that works for you, but it is a little wild to insist that your process is the best and other people should learn it, if you also know that it has inherent limitations that alternatives don’t.





  • masterspace@lemmy.catolinuxmemes@lemmy.worldVim > VSCode
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    But it’s literally doing that in your image. When a horizontal and vertical line cross the horizontal line breaks.

    Yes, as an intentional graphical choice to illustrate the crossing of two paths.

    In lazyvim a vertical line, with no crossings, is still broken, as it is two pipes separated by the line space height.

    Oh, did you mean the points that represent actual commits? You’re arguing it’s trash because there’s no line between two adjacent commits? Really?

    No, I’m saying it’s trash because it CANNOT do something basic like drawing a continuous vertical line, because it is hamstrung by using the interface of a typewriter. A git branch is just one readily available example of a situation where something extremely basic like drawing a continuous line would make sense.

    You’ve brought it up multiple times now so I think it’s time you also source that claim. Cmon, source the claim where the code editor with better visual fidelity increases productivity.

    I can’t cite internal market research that is under NDA. I can point you to basic courses on design and UX, point you to information on concepts like cognitive overload, and point out to you the multiple trillion dollar software companies that got to where they are entirely through paying attention to little UX details that backend nerds previously claimed didn’t matter and were user skill issues.

    Yes, terminal can’t do everything, but I don’t think anyone is using VS code to look at a cube either. Actually, I’m not even sure if there is a VS code extension that draws cubes? So you wouldn’t use VS code for that either.

    Bruh, why would you even try and talk out of your ass like this? I am literally using jsCad and VsCode to do my personal 3d printing modelling, and I literally got my start programming using first VS, then VSCode, to build 3d modelling software for Autodesk. Not sure if you’re aware of this but modern websites have this little thing called WebGL that lets them display these little things called jraphics.

    Again, VsCode can do everything VIM can do, but not vice versa.


  • masterspace@lemmy.catolinuxmemes@lemmy.worldVim > VSCode
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    and if I do not want the GUI part, how come it surprises you that I do not use that superset?

    Go ahead and represent an arbitrary 3d shape using the command line, suddenly you may realize that a typewriter’s interface isn’t the fastest for accomplishing every programming task.

    Regardless, you can be happy with a limited subset of functionality and trying to cram every interaction into text, that’s not an argument that that way is better or that a new dev should go that route, just that you can get by using that method.


  • masterspace@lemmy.catolinuxmemes@lemmy.worldVim > VSCode
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    I said continuous vertical lines and literally posted a screenshot of it not being able to do it.

    It’s functionally the same visual representation of data so you’re literally arguing over it not looking like you want it to look.

    No, it’s not. The human brain does not process dashed lines as easily as it does continuous lines. A whole bunch of dashed lines are objectively harder to follow than continuous ones.

    You can think that’s not important, but the literal decades of UX research and attention to fine grained user interaction, can prove that you’re just flat out wrong.

    You look at the above and think they’re the same, but they’re fundamentally not. Literally just go ahead and try and visualize a basuc cube with this base point and dimensions through a CLI and watch that wow, maybe a fucking typewriter interface isn’t the best for absolutely everything:

    Cube([0.37, -300, 45], [37,-98,-100])


  • masterspace@lemmy.catolinuxmemes@lemmy.worldVim > VSCode
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    No, the conclusion I’ve been saying is that CLI developers are smart people who have spent a long time memorizing commands to get fast at things that can be done quickly and intuitively through basic 2d graphical interfaces.

    They’re now either in a situation where the gains from learning the new process aren’t going to outweigh the costs (though still doesn’t mean anyone else should follow their path), or they would, but they’re just stuck in their ways because of sunk cost fallacy.