Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "garbo"
I'm not too proud of it but.... https://github.com/PythonTryHard/...
It's garbo, especially on code quality but it's my coolest piece of garbo9
I don't know what the devs at ProShow are smoking but I want some. Their product, specifically ProShow Production, is garbo. Don't get me wrong, the stuff is great for making slideshow with effects and stuff but good GOD.
+ If your image's name or the full path to the image contains anything that is not (I think) ASCII, the program will refuse to work with it.
+ If you're using non-English characters for eg. caption ("ẫ" for example) even on a Unicode font that supports that char, it will render a box. You know which box it is. You have to specifically use a font family to have it rendered correctly at the exchange of ugly-ass fonts that has been overused.
+ A majority of keyboard shortcuts are not supported while editing a slide (Ctrl + A, Ctrl + Z being my two favorite).
The best part? I'm forced to use this thing because of time constraints. I'd rather fry my puny 4GB RAM stick and crappy Intel HD Graphics 550 working with Premiere/After Effects than using ProShow. But nooope. ProShow. Fuck you.
Being a Varikist is encountering in the same document one's own previously-written useless functions, which span across multiple lines, in addition to functions which only operate properly because the planets have aligned in something akin to an elliptic curve; these are not indecipherable because the program entirely lacks comments, but because the comments pertain to a program which is somewhat different from that which one wishes to understand.
An example of this is “if senderOfMessage != regexpressiona...senderOfMessage = regexpressiona”; I am wholely uncertain of my reason for having written the program in this manner, but I will not be changing it, because my programs can be diplomatically described as having been developed with a utilitarian approach; they merely need to be functional, and, as such, a lot of repositioning is used during the development process. Of course, for the programs which I write for occupational reasons, I create flowcharts before beginning work on the program, and I imagine that the adoption of this habit for personal projects would likely not kill me.3