For me, it was the parity system and the fact that i could mix different disk sizes and the vm + graphic card pass-through setup. Unraid helped me to start in this world.
Years later, after gaining experience on all of that and investing in dedicated pcie card and disks, I’ve moved to truenas my data and containers.
Still using unraid for the vm part. But i plan to migrate to truenas too at some point.
Really nice! Thanks for sharing this
Make sure to check your bandwidth capacity. Streaming data to 5 people could reduce your capability to navigate on Internet if they are outside your local net as the upload speed is usually the weak point of many ISP. If you have good fiber, it won’t be a problem.
Didn’t expected a “Great Teacher Onizuka” meme after all these years but yeah!
It’s “fuselage”.
It’s called like that because of it came from the word “forme fuselé” (Tapered shape) and it’s a french word mainly because we created it in 1908.
You’re welcome :-)
Indeed, you can achieve a better result with less verbose naming convention. And choose better variable name to make it obvious than 0 Hp is death. While i don’t like having too verbose variable name (as it impacts the readability and quick understanding of the function), i’m not against that for the function name… without going too far of course!
Best is too have proper datamodeling of the object manipulated on top of some classic basic comments. Good interface contract is also a minimum. Best is to have full datamodeling of all the services, objects, in and out interactions between them, etc.
Documentation is a mandatory piece of the code delivery (with tests being the other important part) far too much forgotten if you don’t enforce it on your teams.
I don’t see the benefit of this long naming convention…
It still allow bug to exist… like the fact that, with this code, the player can still play with 0 Hp.
Should have been better to put a “if(health <= 0)” instead of “< 0”
Same feedback here. Works well with Navidrone