Qt 6 - Episode 8 - Qt smart pointers

[@sg990]

Great overview, much appreciated! Regarding the article you link to, though - it's 2021, not 2009 and STL smart pointers are now widely supported by major compilers, so the rationale given in the article is no longer valid. I myself work with C++17. Considering this, is there any other reason why I wouldn't want to use STL smart pointers with Qt?

[@leonidasprinceton1183]

Pro tip : watch movies on flixzone. Me and my gf have been using them for watching a lot of movies during the lockdown.

[@josbexerr5166]

Muy bien explicado la magia de Qt6

[@abdurahmongulomqodirov1781]

nice video, I always learn something new from you, thanks a lot

[@michah3956]

Hello Brayan. What you think about Rust + Qt?

[@vitaliys56]

Hey Bryan. Seems there is a mistake. 12:18, line 33. You receive a pointer by value, not by reference. So you will have two shared pointers which use the same object.

[@platin2148]

Noo not another one framework lost on the worst encoding of unicode (utf16) Choosing that one that takes more space and is variable width seems to be popular. As a side note win32 supports now utf8 with the A functions per default.

[@VNActivityProjectRem]

Variable width is also in UTF-8, if I recall correctly. It's just popular because it makes the most sense. You shouldn't use more memory than strictly necessary and the variable encoding ensures this by assigning less memory usage for common code points and reserving the higher width for the lesser popular code points. The only difference is that UTF-8 seems to prefer more efficiently encoding latin alphabet code points but at the expense of inefficient width usage for Chinese characters and other non-latin alphabets. As Qt most likely wants to go global and be used when developing internationalized applications, it makes sense for it to use UTF-16, as the asian market is significant.

[@platin2148]

@@VNActivityProjectRem The asian market is sadly not so big if you don’t want to go china which makes a entire other set of problems (alone text layout) For US,EU utf16 is space waste and also very often not correctly implemented because of surrogate pairs etc.

[@VNActivityProjectRem]

@@platin2148 That is true. The issue is that Qt and many frameworks, operating systems and any development platforms really do need to support China though (and Japan, South Korea and all other countries with their own alphabets). From the perspective of a developer, you may not need to care about China if you plan on making a game in English, that's true. But when you're making a tool for making games, that's an entirely different story. For every game you make that won't come out in China, there will be 2 games that a Chinese developer would make. Developers will write variable names and function names in their own language so you need to support this. Dialog boxes and messages need to be encoded efficiently, especially for esoteric stuff. Yes, text layout, orientation, specific characters and other stuff will be a problem but platforms would lose far too much money if they ignored it. After all, China has more than 4x the population of the US. One would argue that the Chinese market is more profitable than the entirety of Europe but that's debatable

[@platin2148]

@@VNActivityProjectRem Since when does chrome support japanese text layout? Or windows, ... Can’t remember that they where capable of dealing with that. Also don’t think Qt does that sort of layouting. Even worse about that stuff is that there are way too many combinations from my current understanding there is not a single pice of software that can handle all of that. Left to right right to left top to bottom all of that already requires more than just switching to Japanese but a complete redesign. Also in what language will you program that supports non ascii variable names with full access to Qt? Or do you use clang extensions to support that? Also for games i wouldn’t use qt at all it’s not really made for this.

[@VNActivityProjectRem]

@@platin2148 OK, vertical text layout is not supported in either windows or chrome. But they do use the Japanese alphabet in their language packs, which means that it has to be encoded in an efficient way. This means UTF-16. I guess vertical text would be too difficult to do properly. About the non-ascii variable names, I was wrong about that. I knew someone that used greek alphabet letters in their source code but it wasn't Qt. Still, Qt needs to support string literals in Chinese (so assignments to QString) or stuff like comments in the source code which should and is supported by Qt. There are screenshots on the web that show comments in Chinese (not variable or function names, as I stated originally, though) Finally, why not use qt for games? It supports OpenGL, after all, so graphical acceleration is there. It doesn't make use of the widgets but I see no reason why not