That being said, I have no particular stance on whether this feature is a good change to the language; in a decade of Ruby this is the only situation I can recall that really merited it, and the concerns articulated by byroot and others do resonate with me.
[0] https://github.com/panorama-ed/memo_wise/blob/main/benchmark... [1] https://github.com/panorama-ed/memo_wise/blob/main/memo_wise...
I’m not a huge runner but still find myself using it all the time, both for my own occasional running goals and to satisfy my curiosity for questions like “how quickly would an elite sprinter’s pace finish a marathon?”
I may buy a car (new or used) soon and am a little worried about all the software in cars these days. Software can control pretty much every aspect of a modern vehicle, and so the idea of bugs in a vehicle's software scares me from a safety perspective. Poor software engineering has been implicated in automobile safety incidents in the past[1].I'm aware of the NASA/JPL rules for developing...
It tends to behave poorly when there's a word it doesn't recognize (like "doll'd"—I hope to add support for more of these poetic spellings just as I added support for spelling words like "dancing" as "dancin'"), so that might be partly at play with some of what you're seeing. But I think there's also something else going on here—it previously didn't ever generate so many consecutive syllables with the same stress, so I probably introduced a regression at some point. I'll investigate and add more tests for that too!
Lastly, a byproduct of my own background and the corpuses I use is that this does work better with "modern" poetry. For example, Shakespeare's Sonnet 29 starts with this line:
> When, in disgrace with fortune and men’s eyes
In the intended iambic pentameter, it would be:
> when, IN disGRACE with FORtune AND men's EYES
I don't know enough history to know if people ever spoke English like that, but that interpretation is way off to a modern reader. If I didn't know it was supposed to be iambic and was trying to diagram the stresses, I'd do something like:
> WHEN, in disGRACE with FORtune and MEN'S EYES
Meter is hard!
It turns out if you have enough control over your server you can make it do a lot of things! (Which may or may not conform to a spec.)
Should have another fun post out within the next week!
(Still among the best-commented code I’ve ever written.)
I've reported all this in the past, but since we're giving feedback in this thread, some big pain points for us are:
1. The lack of a way to view all Dependabot security alerts/security PRs (across repos) in one place. With Old Dependabot, we could do a GitHub Issues search like `is:open is:pr label:security org:<our-org>` and see them all, and actually built quite a lot of automation around PRs with the `security` label. But New Dependabot has no way to configure security PRs to get the `security` label, so it's easy to miss vulnerabilities when you have two dozen repos, and our automation no longer works. :/
2. Dependabot reporting `No security update is needed as <dependency> is no longer vulnerable` when in fact there are multiple versions of the dependency, including vulnerable ones, in our yarn.lock file. (Webpack has a lot of transitive dependencies!)
3. Dependabot can't update a vulnerable version of, say, rails, because rails requires the same version of activerecord, even though these are essentially the same project. (I get the sense this is being worked on as "grouped dependency updates"?)
P.S. Just wanted to clarify: feedback is love. I wouldn't be writing this if we didn't find Dependabot valuable (Old Dependabot was actually the reason we moved to GitHub years ago!).