• 0 Posts
  • 230 Comments
Joined 2 years ago
cake
Cake day: September 2nd, 2023

help-circle

  • The problem with that is that reviewing takes time. Valuable maintainer time.

    Curl faced this issue. Hundreds of AI slop “security vulnerabilities” were submitted to curl. Since they are security vulnerabilities, they can’t just ignore them, they had to read every one of them, only to find out they weren’t real. Wasting a bunch of time.

    Most of the slop was basically people typing into chatgpt “find me a security vulnerability of a project that has a bounty for finding one” and just copy-pasting whatever it said in a bug report.

    With simple MRs at least you can just ignore the AI ones an priorize the human ones if you don’t have enough time. But that will just lead to AI slop not being marked as such in order to skip the low-prio AI queue.




  • I don’t like this article. The only 2 options considered are:

    • One color for each different token equally spaced by hue + colorized brackets.
    • Almost no coloring at all.

    There is a huge range of options in between.

    I use my own theme because I dislike every theme I’ve tried so far.

    It is basically all browny orange (because it is easy on the eyes) on a #000000 black background. However, each token type has a distinct color (within the same hue). This makes it easy to read since there is no constant color switching. But it’s also very easy to see which type a token is, since the colors are distinct enough. Obviously no colored brackets.

    And I still have room for highlighting special tokens that I care about. For example self/this is dim pistachio green instead of orange. String literals are greeny yellow and numerical constants bright orange. And punctuation is dark green.

    It also not only doesn’t colorize variables as the article suggests, it colorizes them with semantic highlighting. Parameters, and local variables are different colors. They also differ if they are mutable (for rust for example). Which means at least 4 different colors just for variables. And it helps a lot.

    I also dislike that the article dismisses the main purpose of colorizing keywords, which is typos. Colors allow to see typos as you write them. Having a section of code and saying “find me the typo” is not a realistic scenario. As you type “return”, you expect that it is red whole writing, and blue when you type the last “n”. If it doesn’t turn blue when you finish writing it, you know you didn’t do what you wanted to do. Which is instant feedback. This goes for all tokens, not just keywords. If I write the name of a struct, but it has the color of a variable, I probably wrote it wrong or I need to import it.







  • Rust is not fully functional. But I am legally obligated to recommend it any time I can.

    Jokes aside, this doesn’t apply to you, since you seem to actively learn functional programming. But for people that are scared of it, rust looks like “normal” languages, but has tons of features that can be attributed to functional programming. Even more so if you avoid using references. You can easily “mutate” objects the functional way, by passing the object to the function, and the function creates a new object with just some value changed.

    It has algebraic data types. Function pointers. Iterators. Pattern-based match statements. Don’t have class inheritance. Inmutable by default. Recursion. Monads. And probably other FP features that I’m missing.

    It has basically every functional feature while having familiar syntax.

    It’s also extremely easy to install. Which I didn’t use to appreciate, but then I tried to learn OCaml and had to give up because I couldn’t set up a proper dev environment on windows.




  • As an analogy, just like dragging a 1000kg at 1m/s is not the same experience as dragging a 10g sphere at 1m/s. The same thing happened “something moved at 1 m/s”, yet they were very distinct experiences.

    That being said, Occam’s razor applies here. If it’s the same brain activity, it probably results in the same experience.

    But there’s still room for doubt. Since brains don’t all have the exact same amount of neurons arranged in the exact same way. And their chemical composition might be slightly different. They also change with age.

    I don’t think science can prove definitely that a slightly different brain structure won’t result in a different perception of color. Just like it can’t prove/disprove the existence of god. Some questions are just unsolvable. But science can get far enough so we say “this is probably true/false”



  • I’m no biologist. It’s very possible it’s an incomplete definition, and I don’t claim it to be a perfect one.

    I guess if we apply my definition to mules, each mule would be a different species lol.

    The horses one is a non-issue though. It doesn’t matter that they can create offspring of different species. Since 2 horses can potentially create a horse, then the horses are of the same species.

    And yes, my definition works only for sexual reproduction, since as seen by this article, asexual reproduction can get very complicated.

    I wouldn’t say it’s outdated and mainly for children. Just like Newtonian physics are very useful if we use it correctly. Having simple models that work in the situations we encounter most is useful even for adults.