Youtube comments of (@SRG-Learn-Code).

  1. 24
  2. 24
  3. 20
  4. 14
  5. 14
  6. 14
  7. 8
  8. 6
  9. 6
  10. 5
  11. 5
  12. 4
  13. 4
  14. 4
  15. 4
  16. 4
  17. 4
  18. 3
  19. 3
  20. 3
  21. 3
  22. 2
  23. 2
  24. 2
  25. 2
  26. 2
  27. 2
  28. 2
  29. 2
  30. 2
  31. 2
  32. 2
  33. 2
  34. 2
  35. 2
  36. 2
  37. 2
  38. 2
  39. 2
  40. 2
  41. 2
  42. 2
  43. 2
  44. 2
  45. 2
  46. 2
  47. 2
  48. 2
  49. 2
  50. 2
  51. 2
  52. 2
  53. 1
  54. 1
  55. 1
  56. 1
  57. 1
  58. 1
  59. 1
  60. 1
  61. 1
  62. 1
  63. 1
  64. 1
  65. 1
  66. 1
  67. 1
  68. 1
  69. 1
  70. 1
  71. 1
  72. 1
  73. 1
  74. 1
  75. 1
  76. 1
  77. 1
  78. 1
  79. 1
  80. 1
  81. 1
  82. 1
  83. 1
  84. 1
  85. 1
  86. 1
  87. 1
  88. 1
  89. 1
  90. 1
  91. 1
  92. 1
  93. 1
  94. 1
  95. 1
  96. 1
  97. 1
  98. 1
  99. 1
  100. 1
  101. 1
  102. 1
  103. 1
  104. 1
  105. 1
  106. 1
  107. I'm not a web developer nor a game developer, but I've used both because most likely web in the future will be 3d interactive (meta... is about something else), anyway, I went into some interesting rabbit holes. My favourite was web development in ue4: let's say you use blueprints to create a "game" level and a webpage. Doable, I made some test to create metadata of the level in form of html and css, the problem was later automating the load of the files in git to deploy in a server and all of that, it was mainly hardcoded for the demo but apart from that quite enjoyable, you choose your "weapon" as it could be a post, an image, etc (etc means various TODO) and place them in the level, then you could copy the html code (very basic) and pasted into a file, upload it to a cdn and voila, a web page made with ue4, but, here is the twist. That page could be loaded from within the game!!!... yeah, there are many in-game browsers, what a surprise... but, no, for real, the structure of the web page had ton's of id, classes and data embedded to be parsed into a 3d level. I had some nice results using json directly and some proof of concepts parsing some tailored html, but it had to be made within the demo, couldn't get to parse other sites without some hard manual work, so the rabbit hole got deeper, I tried to create a visual parser, let me explain, you take the full html and represent it as a physical object in the game, then you go picking tags and positioning them in the level and the you give them some style and then... you discover that you want an external scrapper and feel like you are working more than playing and that part was not enjoyable. That was a long time ago, maybe I still have the files? it was ue4.18 or something like that. Quite interesting but unreal didn't have a great support for the Chrome Embedded Framework, I think is still an experimental feature today (more like legacy), I should recheck to see what has change since UE5, thanks fireship for reflaming this old project of mine. I think I'll try to experiment again with this.
    1
  108. 1
  109. 1
  110. 1
  111. 1
  112. 1
  113. 1
  114. 1
  115. 1
  116. 1
  117. 1
  118. 1
  119. 1
  120. 1
  121. 1
  122. 1
  123. 1
  124. 1
  125. 1
  126. 1
  127. 1
  128. 1
  129. 1
  130. 1
  131. 1
  132. 1
  133. 1
  134. 1
  135. 1
  136. 1
  137. 1
  138. 1
  139. 1
  140. 1
  141. 1
  142. 1
  143. 1
  144. 1
  145. 1
  146. 1
  147. 1
  148. 1
  149. 1
  150. 1
  151. 1
  152. 1
  153. 1
  154. 1
  155. 1
  156. 1
  157. 1
  158. 1
  159. 1
  160. 1
  161. 1
  162. 1
  163. 1
  164. 1
  165. 1
  166. 1
  167. 1
  168. 1
  169. 1
  170. GENTOO X SCRENSAVER PENIS While talking to my boss and her visiting niece and nephew (<10 yrs old), they remarked about my screensaver. It happened to be GLsnake, a part of the xscreensaver package. This screensaver takes a common child's toy and manipulates it into different shapes (like a bendable linear lego set). Anyway, the niece (who happened to have one of those toys with her at the time) instantly became amazed at the shapes on the screen. As it cycled through the models, she would try to guess the shape (which is described in the upper left corner of the screen). Unfortunately the GLsnake bent itself into the shape of an "Erect Penis", then a "Vagina", and then "Flaccid Penis" and then to "Penis". To my horror my bosses' niece started asking everyone what a erect penis was, and some less than pleasant faces looked at me asking why my bosses' neice was seeing genitalia on my screen. These "shapes" were added in the latest release of xscreensaver (and very quietly mind you). It is a trivial "patch" to remove those "shapes" from the GLsnake source code. Should I submit the patch to bugs.gentoo.org, ask the xscreensaver package to give an option to show genitalia, or just keep my mouth shut? I realized that this suddenly became a "censorship" issue, so what is everyone's take on censoring this kind of stuff? Completely harmless, but potentially troublesome (especially from your boss). Should a patch be provided by Gentoo, or should it only come from the original developer (unlikely), or should no such alteration be done?
    1
  171. 1
  172. 1
  173. 1
  174. 1
  175. 1
  176. 1
  177. 1
  178. 1
  179. 1
  180. 1
  181. 1