I usually just use Unit Test coverage as extra insurance that I didn't accidentally forget a path when writing up tests for new classes, or when trying to assess others tests to see if/what they miss. Outside of that, I basically ignore it.
That (per)mutation testing, sounds like pitest, which I've had fun with using to gauge the effectiveness of tests I've written in the past.
Yep, basically. I looked into Racketscript a while ago, seems like it was a graduate thesis project that heavily built off of a similar python project iirc. It's based on a very old version of rkt, pre-chez, and probably would need a huge investment just to work with the newer ecosystem.
Iirc, an interesting bullet-point in their backend rework to make the move to chez meant that doing things like targeting js might be easier now than ever. I would absolutely love a js backend for rkt, it seems like it would be a huge boon to the ecosystem.
I was really excited when I started using racket that I could switch to static typing when I wanted it. However after trying out contract's, I must say I'm quite a fan of them as an alternative. Sure, you lose out on static, compile time checking, but honestly, I haven't missed it. And it's _even more_ seamlessly integrated into un-contracted code.
You can express more interesting things and complex relationships between parameters using the ->i contract than any type system I know of will allow. There's some limitations, but between it and unit testing, I've been having a blast.
I know I hate it when I join IRC channels and have no context as to what anybody has been talking about, as there is no history to quickly go over. Even just having the past days history would help in this regard, at least for more active channels.
It's the same as just barging into a conversation a group of people are having. You don't want to just join and start talking about a completely different topic. So you join, and wait for a bit to get a feel for what they're talking about before piping in. But with IRC, sometimes it can take _days_ to get that amount of information, depending on how active the channel is. The same thing could easily be accomplished by being able to read the last 10 messages in the channel.
I feel like Solution 1 is pretty close to what I see as the "solution".
I think for commonly requested permissions that are not commonly accepted, they should just use a smaller, more discreet icon for notifying the user; one that doesn't hang down over the chrome and block/cover up the site. That way, it can be easily ignored.
It should be more obvious than the one they're using in that solution. Maybe something equivalent to an icon next to the refresh button or something. The text icon they had in #1 was probably /too/ easy to ignore.
I haven't really checked out LineageOS before. Just briefly browsing their site gives me a bit of skepticism. It doesn't seem to be very professional. For example, their about page, and one of their most recent blog posts.
I'm definitely looking for an OS to move to from Android. I suspect Librem will have its own flaws, but they inspire more confidence in me than my first impressions of LineageOS from their website.
That (per)mutation testing, sounds like pitest, which I've had fun with using to gauge the effectiveness of tests I've written in the past.