News for hackers. Stuff that matters.
Re:The History and rationale of the Python 3 Unicode model f... by Alir3z4 on Wednesday December 14, 2022 @02:52PM (#33989234)
Unicode errors were one the most painful and annoying issues I had. Regardless of working with xml files, parsing text or just dealing with anything text related. When upgrading to Python 3, they just vanished.

Anti ORM people probably don't know what ORM is or confused about their usage and benefit they bring.

Once you're dealing with several tables and relations and lots of aggregation and annotations, raw sql is the one way ticket to insanity.

By the way, thank you very much for making SQLAlchemy. You saved millions of hours of developer time and god knows how many SQL bugs have been prevented by using SQLAlchemy

Re:The History and rationale of the Python 3 Unicode model f... by kstrauser on Wednesday December 14, 2022 @03:15PM (#33989722)
I agree completely. Turns out all those TypeErrors that suddenly popped up when switching to Python 3 were actually uncaught logic errors all along. The biggest annoyance coming from the string/bytes split was realizing how sloppy I'd been about treating them identically.