Disclaimer I am a developer of EFL and I write C daily. This troll is massively around a C vs C++ so I will try to stay out of that part as it is a completely useless discussion.
A few fact :
- Evas is a scenegraph that predate Qt Scene Graph.
- Edje predate QML and has been its source of design and inspiration (Their first iteration of QML was named QEdje).
- As for the choice of EFL vs Qt, which is what you are implying here. It has been put on the table a few time, but one time it was made in the open by someone like you (I mean someone who was forced to work with a toolkit he is not used to in a language he is also not used to). So he did a benchmark to prove his point with real number. Here was the result https://phab.enlightenment.org/phame/live/1//post/simple_efl_vs_qml_comparison_again/ . You are welcome to write another benchmark.
- Also you seems to over estimate the type checking capability of the C language. Maybe you should write a proposal on how to improve it if you have some idea. EFL is after all an open source project, there is nothing that prevent you from proposing improvement.
- As for writing a video player, I am quite certain it is not the job of a 15 peoples for a year. You can check https://git.enlightenment.org/apps/rage.git/ for an example of how to do one. I do like the name quite a lot considering your post
Now I am not a complete fool, I perfectly know where Qt is better than EFL without even the need to ask for justification :
- Documentation, tutorials and examples (Well, Samsung has never though investing in upstream documentation was useful, so it is mostly community based documentation and sure when you come from Qt and go to EFL you get quite a ride !)
- Community is way bigger for Qt than EFL
- Qt has a large set of widget designed for the desktop that do work quite well
- Qt work better on Windows and MacOS X than EFL
Oh and there is one thing that has been great so far with everyone that I know who actually work on Qt itself, they are great people that don't troll around. That how we learn from them and they learn from us. Your behavior here is more the one of a fan boy than of someone who actually does the hard work in those toolkit. If you were actually contributing in any of those toolkit, you would know already that they have weakness and strength that you should take into account.
Oh and hint, for you crash. Just run your application under valgrind, you will enjoy seeing the application (and not the toolkit), doing all those bad memory access. Have fun.