• 5 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: November 21st, 2023

help-circle





  • why not just add the options to it?

    If you are asking me, personally, it’s because making any contributions to ls is far beyond my capacities and will remain that way for the forseeable future.

    Personal deficiencies aside, would it even be a good idea to modify ls in this way? It seems to me that stability and predictability is a feature, not a bug. Basically you know how ls will work on every linux system. Adding all these features would turn it into something else and potentially introduce chaos. ls is tested on >millions of systems in every context; a known quantity. A feature set which is limited to the necessities avoids introducing bugs, flaws, security issues etc.

    And once added, a feature probably shouldn’t be removed. In 2024 I love having git status optionally integrated into my ls-type tool. But in 2034 will git still be as ubiquitous? What about 2054? ls is for the ages. eza is for right now.






  • I freaking hate blue LEDs.

    I actively avoid buying anything with a blue LED because they are so obnoxious. So bright. Why do I want to read by the light of my HDD? Does this video explain why they have to be like that?

    Maybe if you have a separate wing of the mansion to do computing stuff it is not annoying. But if like a lot of people you have electronics in your living space, these lights are extremely disruptive.

    It seems that can’t really be dimmed… I had to give up on a couple of blue backlit alarm clocks because there is no way that the time can be visible without illuminating the whole area around them.

    For whatever reason, red is the best one. I would prefer another color aesthetically. For whatever reason, red is the only color that does what it has to do and nothing more.





  • I was trying to learn this again last week. I just play around with this stuff for fun.

    If I want to consolidate all the commits into a a single message (to create a changelog sort of), which kind of merge do I use?

    Another question: I’m torn between wanting to keep a complete history of my work, for my own benefit, and not wanting anyone to see how messy and crappy everything is. I’ve been trying to work in one branch then merge only when a task is “complete”. But it’s a bit confusing for me especially if I leave a project for a while then come back to it. Especially especially if submodules are involved. Is there some sort of convention about how to do this? Or am I thinking about it wrong?



  • why was Google able to find the answer to questions exactly like this 6+ years ago?

    curious if there is any way to know for sure if this is the case? is there documentation of vague google searches over time to track their results? sort of seems like a “don’t know what you got til it’s gone” sort of thing for the average user. but maybe there is some academic work or industry publications to this effect?

    We do have a good 10-20 years of every news story intro containing a line like “a google search for ‘spatula’ returns 2.5million results”. remember when journalists and other writers thought that just putting a single search term into a search engine was the way to conduct online research?

    otherwise it is really just your recollection how it felt then vs now. i can’t comment on @merc@sh.itjust.works’s programing skills but the point about changing expectations is a good one. not to mention that the amount of available data has exploded.