I was hoping that this was a clone of the Atari game. https://en.wikipedia.org/wiki/Kaboom!_(video_game)
[deleted]
KABOOM in 180 lines of bare C++
61–68 of 68 posts
Re: KABOOM in 180 lines of bare C++
#62Earlier quoted context omitted.
The project was just an example of HN bias against GPUs. At least for doing graphics on GPUs. Try searching "GPU" on this site. 100% of the first page of results are about using GPGPU in the clouds. Do you think that matches what people buy GPUs for, or amount of code developers white for them?
I searched "GPU" and almost all of the top results were people doing weird/unusual things with the GPU: terminal emulator, Postgres query acceleration, stripped down HTML engine, APL compiler, etc. A search of "Direct3D" suggests HN doesn't have much interest in Direct3D, though.
> weird/unusual things with the GPU: terminal emulator, Postgres query acceleration, stripped down HTML engine, APL compiler
Exactly. People here mostly do general-purpose computations on them, despite “G” stands for graphics.
Search for “Graphics”, and the majority of top results are for CPU-based stuff, pixel graphics in terminal, python, Skia. There’re some results for GPU-based graphics, like graphic studies for MGS and GTA, but they’re minority.
I think graphics is how the majority of users use their hardware for, but it’s under-represented here.
Re: KABOOM in 180 lines of bare C++
#63Oh. I thought it was the Atar2600 game.
Kaboom! was awesome... need paddle controllers to really appreciate it though.
Re: KABOOM in 180 lines of bare C++
#64Aw, here I thought it was an implementation of the 1980's Atari 2600 Activision game :/
Re: KABOOM in 180 lines of bare C++
#65Impressive effect. I didn't realize openmp was so easy to use. It isn't realtime but you could bake up some cool effects with this. AMD FX8320 3.5GHz $ time ./tinykaboom real 0m4.176s user 0m28.631 sys 0m0.012s
I saw the openmp pragma and thought to myself "neat! should be fun to watch the cores work hard at this" and went ahead and compiled and run it and smiled at the 400% cpu usage in top. $ time ./tinykaboom ./tinykaboom 78.08s user 0.02s system 369% cpu 21.159 total Then I wondered how it would fare if I were to port it to Go and went ahead and hastily did port to Go and thought that, "hmmm this should run a bit slower…
There are a few potential improvements here:
1) Use a look up table for 'sin' rather than using 'std::sin'.
2) Tell the compiler what instruction sets to use; for example, tell GCC to use 'skylake' instructions (https://gcc.gnu.org/onlinedocs/gcc-6.2.0/gcc/x86-Options.htm...).
3) Many of the functions could be 'inline constexpr'.
4) Although 'ofs <<' is buffered, it can still be very slow. Create the output in memory and use a lower level function like 'fwrite' to write it to file.
5) Use 'std::thread' or 'std::async'. It makes the multi-threading more portable and clear.
Re: KABOOM in 180 lines of bare C++
#66I ported this [1], as well as ssloy's previous [2] article that was featured recently in HN, in Golang.
I wanted to say he's an excellent introduction to graphics. As a sysadmin, I had never drawn more than simple lines and the whole thing seemed daunting. Now I see how fun it can be, and I'm waiting for next weekend to pick up some more!
Re: KABOOM in 180 lines of bare C++
#67I was hoping that this was a clone of the Atari game. https://en.wikipedia.org/wiki/Kaboom!_(video_game)
Me too!
Re: KABOOM in 180 lines of bare C++
#68[deleted]