Conversation I had with a coworker today:

me: When transferring an object from C++ to QML you have to set the parent of the object. If you don't QML thinks it can just delete this object.

coworker: So if you don't set the parent of the object then the orphans get Anakined?

me: Yes

TeamLeader : "Come two seconds"

TL : "I'd like you to check that out when you do that"

Me: "But it's your job to do this"

TL: "Yeah, but I'd like you to just check in case I forgot"

THEN DO YOUR FKING TASK PROPERLY WHATS THE POINT IF YOU FORGOT AND I DO IT

Edit my english sucks

been exploring the options for cross platform desktop app, and i found :
java : both awt and swing look ugly, i really like OOP of java, and the way projects are organized is easy to scale, but i need to deploy the jdk, and the speed on gui apps isn't that great
C# : (.net/ mono, i can't grasp F# and vb is stupid) looks native on windows, not so much alien on both linux/mac, and being a java cousin is a pro, i found the Eto library for mono even looks more native on *ix than winforms
wxwidgets: for C/C++ so far this looks like the best option for total native feel and performance, but man i fucking hate C code, and this looks a lot like C code, even with proper native Cpp support, maybe i should dive deeper in it
GTK+ : did any one mention C code ? because this mother fucker is plain C with macros all over the place, it made me realize why wx is promoted as Cpp friendly, i doubt I'll use this
tcl/tk : even tho ive never wrote a single line of tcl in my life, the tk lib is the default ui for both python and ruby on all supported platforms,
and i really love ruby, and Python is Usually a joy to work with
Qt : this by far looks like the best option, proper OOP in C++, bindings for python (ruby binds are outdated), almost native look and feel on supported platforms, and even has a gui builder in xml or json/js (qml) however i bet I'll use such a thing, the building tho depends on an external preprocessor "moc" and some wicked macros, also makes working with templates a fucking mess, and the heavy dependence on QObject inheritance makes integrating external libraries a bit more tiring, the signal slot system makes more sense in python than in C++, since it makes me confused about the flow of the code
lazarus: is a freepascal implementation that looks and feels like delphi, not so much for native look and feel, but good performance and easy language to handle
electron : this fat mofo is fat, it's the slowest of all options, if i want an html app, I'll just compile a stripped down webkit and deploy that
what do you think ? and did i miss something ?

The Qt QML TreeView is a steaming pile of shit...
That is all.

I think it's just me.
Every time I build something I feel as if I completely mess it up. For example, after a few days of working on an Android app after school, I feel like It's already become a mess. Perhaps it is just my aversion to making thousands of classes for every little detail, because I feel as if it would slow down my app (even if it were a minor penalty), but it usually makes for a onStart() function with ~90 lines of code which just makes me feel bad on the inside (and also a bad developer, so I wouldn't dare ask money for an app I built). Either way, if I would add these calls to other functions my Fragment/Activity class would still be fat. Also, typing 'context: Context' or 'Context context' just seems awkward.
I also feel like most frameworks are just a mess. Take Qt, for example. Quite a community touting how great it is (I use KDE Plasma btw) and I'm sure it is. I've got an idea for a desktop app but just the idea of it using some sort of JS (yes, I'm talking about QML which I'm considering) gives me the shivers. I already don't like Electron, so the idea of having JS embedded in a desktop app just doesn't sound right to me. But again, maybe it's just me ¯\_(ツ)_/¯

Holy f-ing hell!
Why do the small things have such fucked up corner cases?
This is very likely a giant bug with Qt, but how does this even happen?
I am using Qt with QML and sending data to a database on the backend. I call functions in QML from a Date JS object (property actually, but it calls functions) to set the date as a QDate. This is stored in the database as yyyy/MM/dd. This is fine. When I read the date out I convert it back from string to QDate and send this object to QML. Which then converts this to a Date object in JS in QML.

But at the point where it converts from a QDate to a Date object it loses an entire day. Seriously? You didn't gain a day going from Date -> QDate, but you lose a day going from QDate -> Date?

How long has QML and Qt been around? At least 5 to 10 years. How has this bug lasted this long? I don't want to do a bug report. I will, but I don't want to .