Backticks are not very distinct, as they can be confused with single quotes (depending on the font). Also $() shows the beginning and end of the command very clearly. This is even more important when you have multiple of them in some variable in example. Not to mention that you can nest $(), but that is something I personally don't like to do anyway.
There are some functional differences too: https://www.gnu.org/software/bash/manual/html_node/Command-Substitution.html , such as that backtick command set as an alias in your bashrc will be executed once on load. While $() version is executed every time you execute the alias. Also backslash is literal in the backtick variants (with exception). All in all I never use backtick command substitution; it's confusing, limited and deprecated.
!(r.SendNow || r.DryRun) requires you to read the entire statement and then negate the result. While !r.SendNow && !r.DryRun each part of the statement stands on its own and is negated for themselves. That is how I read. I like the Ai suggestion more, because that is how I would write it myself. What I like about it is, that the negation of is right there with the variable. It gets more important, the more you divide sub-expressions in multiple lines.
It's actually the first time I used to do Ai assisted unit test creation. There were multiple iterations and sometimes it never worked well. And the most important part is, as you say, think through and read every single test case and edit or replace if necessary. Some tests are really stupid, especially stuff that is already encoded in the type system through Rust. I mean you still need a head for revision and know what you want to do.
I still wonder if I should have just gave it the function signature without the inner workings of the function. That's an approach I want to explore next time. I really enjoyed working with it for the tests, because writing tests is very time consuming. Although I am not much of test guy, so maybe the results aren't that good anyway.
Edit: In about 250 unit tests (which does not cover all functions sadly) for a cli json based tool, several bugs were found thanks to this approach. I wouldn't have done it manually.
I like writing code myself, its a process I enjoy. If the LLM write it for me, then I would only do the worse part of the job: debugging. Also for many people let the Ai write code means less understanding. Otherwise you could have written it yourself. However there are things when the Ai is helpful, especially for writing tests in a restrictive language such as Rust. People forget that writing the code is one part of the job, the other is to depend on it, debug and build other stuff on top.
And yes, within reason I think you should let a 6 year old do what they want with their free time.
You have lot of assumptions about how the parents raise and teaches their kids. I think the parents should teach and bring the tech to the kid, because the parents think its a good thing. From there it can go any way. Without trying you wouldn't know. I think we both should let the parents parenting the kid and not assume anything more than the question. Let the parent show the kid some Linux stuff.
I think this is a good preparation for the future, so it does not become too much dependent on Windows and knows difference and strength of Linux early on, so it can make his own choice. Parent does not force here, just teaches some stuff. I don't know why you have a problem with that.
So you expect the 6 year old knows exactly what he wants to do, and parents should never introduce some tech they like?? Best, leave the kid alone let the internet and friends guide him. No need to have parents at all.
Well that wasn't meant to be too serious. You are surely aware of the situation that Haskell is not often used language in production. And a huge project you are doing with lot of Haskell is definitely something special.
he’s very familiar with C and C++. In his associated writeup on his Gopher page (link though Floodgap) [jns] simply declares it’s a language he’s quite fond of, which is reason enough of us.
So there are no technical reasons to do so. Its totally understandable to like and use a language for personal feelings. But it kinda feels like unnecessary complicated. So this should be done as a hobby project on something that is not important in my opinion.
Oh I see, yes that's a misunderstanding here. I was just confused. :D
As for the second point of Windows lock-in, this is no longer the real issue thanks to the integrated efforts of Proton. Developers don't even need to build a Linux version of the game. It really mostly comes down to the anti cheat, which doesn't work on Linux the same way as Windows. There are anti cheat systems that work on Linux, but they are not as effective, because it does not have the same Kernel privileges as on Windows.
these statistics are only about Steam games, not 90% of Windows games
90% of games does not equal to 90% players / users
Most players don't care how many games from the Steam catalog are playable, if their favorite game is not. That's the point. And the article did a bad job of making it clear.
Only if you are dependent on Ai, because you cannot program yourself or don't want to.