Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

  • 0 Posts
  • 470 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle
  • I couldn’t get into matrix, but I was a huge fan of open fire. It’s interface was stupid easy for XMPP administration and for awhile I ran it no issue with my group of friends. granted we ended up just going back to discord not due to any issue with the server or protocol but because it was tedious trying to get people to switch off a platform that works for most people.




  • Yeah, I understand that point of view as well, especially for feature expansions. I don’t agree with that point of view at all for bug reports /fixes though. It’s not like I’m asking for an additional feature on top of the devs’ already existing code. I’m fixing a mistake that the dev added to their code that they haven’t had time to fix, I don’t see the need of multi week or month review processes for those.

    But at the end of the day I tell myself that if the dev wanted help with the project they would have made the system easier and I just move on with my life. or if it’s too much of a blocker or if it’s a small change just fork the code myself if allowed, fix it and then never bother with the hassle of submitting it upstream.


  • I don’t contribute to projects most of the time strictly due to the hurdles in place for contributions. if I see an issue with something, I would like to be able to properly fix it, not have to follow a multi month process to actually get it in

    The last project I wanted to contribute to had the following system:

    1. make an account (makes sense, its a self hosted tracker)
    2. verify my identity and specify what I wanted to do in a whole different project in order to get validated to be able to open issues in the tracker
    3. open an issue stating that I found a problem
    4. state in the issue that I was willing to fix said problem
    5. agree to sign the code away if done
    6. wait for response confirming that it was ok
    7. fork the project
    8. fix the issue on your fork
    9. create test units for the project
    10. submit a merge on the main project
    11. wait weeks to months for the actual maintainer teams to review the fix and make suggestions/alterations
    12. fix any merge conflicts that was created during the time that it took to review
    13. rinse and repeat the last 2 steps until it’s finally merged

    Luckily I had noticed that the timeframe of existing requests prior to doing it, and decided to pass on it.

    Don’t get me wrong, a lot of those steps are necessary for proper development cycles but, it’s the extra steps that are annoying. I’m looking to quickly contribute and move on. Too many steps or if the process seems like it will be a major pain in the butt = You can find and fix it yourself.

    Most projects if they have that I will at least open an issue for it so it’s known as a problem… but some projects don’t seem to want them reported, let alone fixed.






  • Personally, I think both are pretty bad, but yeah, spending extended periods of time in front of a computer screen isn’t very healthy. They’ve already stated in another comment about the physical aspects of it with being 30 centimeters from the screen.

    But there’s also the social development aspect of it. At the end of the day, humans are social creatures, regardless if you are an introvert or extrovert. You still need some amount of socialization. Many people that are habitually on computers have converted that socialization over to some digital platform like Discord(guilty as charged), Or have moved to a text based socialization. While this may meet our needs as human beings for socialization, It disconnects us from our emotions, and hinders our ability to have direct conversation.

    The consequences of tone doesn’t matter much online, which makes us more apt to respond or be blunt for discussion. The lack of video or a face also weakens the ability to be able to analyze body language, to be able to properly analyze the intent of the other parties. These attributes are crucial for communication.

    Things such as going in for job interview are now digitalozed (or in some fields discarded all together). Instances such as calling someone to verify an appointment or to ask questions are being replaced with text-based communications or no communication needed portals. We are currently seeing this among the millennials and Gen Z’s, but even the older Gen A’s are starting to show signs of a weaker ability to have face-to-face communication and be able to interpret body language. I’ve never liked talking on the phone in the first place, but my sister, who’s younger than me, avoids it like the plague. It’s to the point where if the thing that she’s doing doesn’t have an online portal or an ability to text, she isn’t going to do it. Because she’s not comfortable with having phone calls outside of her social circle, and she isn’t comfortable going and meeting someone to ask in person. When I’ve talked to her about it, she’s stated that she’s not different than most of her friend group, and that that’s just how it is now.

    It’s scary.



  • Way more than what should be concidered healthy. Mostly due to necessity(hobby and work), but I am trying to cut down the amount of time that I’m on Lemmy or social media networks.

    Even hobbies that I have go in front of the computer. Like D&D, I do via Roll20. Development, I do obviously on my system. The media that I consume is mostly YouTube or Twitch.

    I would estimate that I’m probably on the computer roughly 13-15 hours a day between coding, gaming, social media and surfing the web.

    edit: If I didn’t even think about my phone, if I included the phone, I probably am on it. From the time I wake up to the time I sleep. (on and off with the phone though)


  • Pika@sh.itjust.workstolinuxmemes@lemmy.worldit's just the worst
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    12 days ago

    I had to look up what that was because I’ve never heard of that law. I like that, and will likely use that in the future. I have to agree though, but from the other direction. Yeah, my response post to the LLM fallacy list was a lot of that, I knew it would be going into it though as any LLM response interpreting data on a specific level like that, generally needs that. That’s ultimately why I don’t like using LLMs in the first place. Because you have to go back and fix it anyway. (Note the LLM say that’s a fallacy since it doesn’t /always/ happen, and it will also post a fallacy saying that I’m saying that it will do so but I digress)

    I responded to the first fallacy post mostly to show how inaccurate LLMs can be when you use it to interpret dialogue. They are great for summarizing concepts and finding data sets, But actually classifying or generating information is one of their weak points. A good chunk of the claimed fallacies could have been summarized by it either misinterpreting the post, ignoring other parts of the post and or giving a redirection in order to fit it’s mantra. And some of them just straight out added additional fallacies to the mix as well.

    And yea, I agree. I’m done with this conversation as well. We’re no longer talking about fish anymore, the topic adjusted to isn’t crediting or discrediting the initial posts since it’s all built off LLM false attribution & strays away from the topic of the community lol


  • lol, its insane the inaccuracy of the LLM in that. It made me chuckle. I can give it 1 and 2 as I gave it already, but for the sake of the chuckle I’ll start from the bottom to top:

    • 25: its my opinion, can’t be a fallacy as it’s based off opinion, it’s not meant to change anyone’s mind or anything, its stating how I felt.
    • 24: I’m not assuming anything, it was a question, the LLM can’t interpret it apparently.
    • 23: it’s ignoring the critera/information I had already supplied prior to it thinking its based off objective
    • 22: Again, its based off the fact that more users = better ability to find documentation and sharing it. this isn’t fallacious in nature.
    • 21: this was just a warning cause I’ve seen it myself (I have 6 posts in the past 4 weeks that were technical and ended up being nuked)
    • 20: see 24
    • 19: my experiences are somehow an appeal to common practice? Like that’s my experiences with it
    • 18: unrelated to the current discussion but I can see why it would have it
    • 17: again my actual experiences with it that doesn’t make it a fallacy
    • 16: I love that it’s trying to say I don’t know my friend group’s shell usage as if I don’t share scripts with them already.
    • 15: Has nothing to do with the argument and is actually a misdirection in itself.
    • 14: I’ve always argued both metrics, I don’t see where it’s seeing a goalpost moving here… lol
    • 13: I said the exact opposite of what it’s claiming. I acknowledged that it would require effort and that wasn’t something I wanted to do
    • 12: I didn’t assume it was better in this case, I stated since it was easier to find scripts, it was less work to do
    • 11: I never claimed the stated assumption here, I stated why I did. It was counter intuitive to me, that doesn’t mean it’s not intuitive to others, that itself is also an illicit minor
    • 10: changes the comment away from my personal experience and tries to redirect it into a reason why others shouldn’t use it.
    • 9: Yes I agree it’s a generalization, that was the entire point of that, to show that most of my experiences shown that, and as such why I don’t use it.
    • 8: Invalid, I’m not attacking you, I even acknowledged that I can see why some people use it, I just can’t
    • 7: This isn’t a slippery slope as it’s accurate. There is less info available on fish shell, just due to the length of amount of time it’s available.
    • 6: Invalid claim
    • 5: I can kind of see this, but it’s not like I don’t think it doesn’t have it’s merits, its just not for me.
    • 4: Such evidence is bad on it’s own, but when supported by facts it’s valid
    • 3: I don’t think I understand this linking to authority but LLM’s definitely struggled converting bash to fish for me.
    • 2: already explained this one in parent post
    • 1: same as 2

    I love LLM’s at times, I can understand some info they give but, man do they not know how to read dialogue.



  • Pika@sh.itjust.workstolinuxmemes@lemmy.worldit's just the worst
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    13 days ago

    argumentum populum would not apply here, since that one is based off populous opinion and I’m making the logical guess that since fish is the least used shell of the three we have talked about that it’s usage would be proportional as well. This might not be the case obviously which was why I was asking if you did share your scripts. Lack of usage was my biggest reason for bailing on it. I do a lot of script sharing with my friend group and I’m not wanting to have to do everything twice in order to be able to share it.

    If you were looking for a argument from fallacy case, your best fallacy would be likely I believe appeal to probability, would be the close but not match as I am assuming most of your friends are not using fish, but I’m also basing it off the knowledge that it has a significantly smaller user base which makes it more likely. or possibly an illicit minor which would be the path of “My friends don’t use fish, so it’s unlikely that your friends use fish” which would potentially be valid, but again I am questioning the case not stating it as an exact, but since my initial question was based based off statistics and experience, I would go with the first one.

    but back to the topic:

    Documentation wise? I have read it. The examples are nice don’t get me wrong, but its layout needs work, the examples need better real world use cases and struggling to search for how to do something because the makers of the shell in their infinite wisdom decided to make a new keyword for something that was already stupid easy to use is just a hard pass for me (like I said I had already learned bash prior to this, whereas you had not learned bash). Not to mention with bash or zsh, I run into an issue I can just search the issue. What would take me 2 minutes to search for a problem with a script using zsh took me 10-15 minutes of research with fish and sometimes it wouldn’t even solve the issue at hand and required just rewriting it completely. Usually my path of research would require me to look up the issue using fish, find no solution so look up the issue using bash, then have to convert it to fish. Sometimes the issue would work fully in bash, and just not in fish. I came to the conclusion that if I was having to convert parts of it to bash anyway in order to research issues with it, I might as well do it in bash to begin with.

    I agree with you, the more people using it the more examples and documentation will be available as a result, but I’m not going to be a spearhead for it, I don’t want to have to exert more energy than necessary, and I found the gains I got using fish didn’t outweigh the losses. Like I said I might revisit the shell some day, maybe if it ever becomes super popular, but for now I have removed it and ported my scripts back to bash again.

    ammendum: btw LLM’s do not like fish shell for bash to fish conversion. I had tried it a handful of times resolving an issue (deepseek had the most success of them) but it was almost always a try 3 or 4 times, get something that has nothing to do with it, or uses something that fish shell doesn’t support, and then have to clear the context or find another path for resolution.

    ammendum2: also fair warning, the last 2 topics on fish shell that appeared in this community got nuked after 2 days, so it’s possible this entire thread will disappear as well(hopefully not but it seems to be a reoccurring issue).


  • Pika@sh.itjust.workstolinuxmemes@lemmy.worldit's just the worst
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    14 days ago

    zsh actually predates fish by almost 15 years and bash which 16 years while fish shell also ignores every standard known in favor of doing it’s own thing so yes I would say it’s re-inventing the wheel.

    Fish is known as what’s called an exotic shell, meaning that it doesn’t adhere to what is considered standard for Linux systems, which would be POSIX compliance. Now most alternative shells have partial compliance, not full compliance. But fish didn’t have any compliance. It didn’t attempt it. Like you mentioned, its use case was meant to be an interactive shell. So scripting on it was a back burner project.

    If it works for you, then that’s good. I tried it, hated the lack of information available for it, and hated the way that it didn’t follow standards. And at the end of the day, anything I made for it was exclusively for me due to the fact that I could no longer share configurations or chains with anyone else because they did not have fish shell. I’m sure it works for some but it didn’t fit my use case anywhere


  • That was the exact opposite with fish. I had already gotten fairly well first with bash by the time I started using it, and the way fish did it was just super counterintuitive to me.

    I couldn’t get into the overall design of how it looked and I disliked how command substitution and the built in’s worked, Combined with the fact that it’s a lesser used shell, so there’s less information available on it. I just couldn’t do it.

    You brought up a point though. That makes me ask. You must not have to share your scripts with anyone then, right? Fish has a very small user base in comparison to ZSH and Bash and when I make a script that’s more advanced I tend to want to share it with my friends and having them install a whole new shell just to run a script is just not helpful to me. ZSH is close enough to bash in compatibility that, generally speaking, if I want to share it, I can use zsh And then convert the minor discrepancies. Where with fish I have to redo the entire script.



  • This is a good way of putting it. It’s essentially ZSH with Autosuggest/complete and a theming agent. At least visual-wise.

    When you get into the scripting and the hot keys aspect of it, they reinvent the wheel and everything is different., Like for example ,!! and other bangs(I think that’s the right word?) like that are not valid on fish, And everything to do with variables is different from adding to your path to setting variables to creating functions. Also checking your error code is going to be different as well as it doesn’t follow the $x style inputs and doesn’t support IFS and globbing works differently.

    TLDR; fish is nice, but If you use it unless you want to relearn an entire type of language, keep your scripts on bash or zsh

    or if you wanna see the bigger differences fish has a dedicated bash transition page