998 karma · joined June 17, 2014
It just so happens that for most collections, `IntoIter` is also defined for references to them, which typically gives you the same behavior that `.iter()` would give.
I know many people swore / swear by the datatables plugin, but now that Bases in core, you can get pretty far without it, no?
Well, they'll call it a design decision, not a bug. I guess I'm being charitable.
This isn't enough. What was the _full train of thought_ for this? Why would it be added when AI isn't used?
The infamous you can't parse (X)HTML with regex¹ meme is from 2009, yet this fix was done in 2019. I guess the SO answer never mentioned SVG.
That's when I remember seeing a broader shift towards app-terminated TLS.
I've yet to see tools that handle zero-downtime-migrations well. The manual task of keeping two versions of the same query / model alive (version N and version N+1) is... well, how else would you handle it?
While tools that can generate the model or schema are nice, they never seem to account for this.
Is there some alternative approach I'm missing?