It's a shame that these papers were published before they were polished by the authors.
[0] https://forums.spacebattles.com/threads/claims-of-room-tempe...
312 karma · joined January 1, 2019
It's a shame that these papers were published before they were polished by the authors.
[0] https://forums.spacebattles.com/threads/claims-of-room-tempe...
TL/DR: 30 $, Legend mode for sure, Arena and Classic mode maybe or a few weeks after. More updates (graphics, Mac & Linux support) a bit later. Adventure mode will follow.
[0]: https://store.steampowered.com/app/975370/Dwarf_Fortress/
What needs to be said though is that reimplementing something from a paper is near impossible. I had to do that a couple of times and I was only fully successful if the paper was accompanied by some open source code as there always are tiny little edge cases or initialization details that won't be covered in the paper.
Also from experience, it helps if universities have closer ties to industry. As an industrial player you can't work with software that does not deliver reproducible results.
That would ensure that the contributions of the PhDs does not get lost and they learn how to properly contribute to a project.
PhDs having their own version of the code, incompatible with the one of the Postdoc sitting opposite of them. Each slaving away at their niche project but nobody there to bring it all together. This particular university had really great code and they thought they could sell it. But they did not even use git and when I gave a presentation there about it, I was met with absolute rejection. They don't have an idea on how much effort it takes to maintain a commercial code, unit tests, customer support etc.
I'm now working at a company that produces simulation software spun out from university. Fantastic job and we do all of those things mentioned above. But obviously my paper output has been near zero even though we sometimes do cutting edge research.
I wish I had a solution to the problem as so much grant money is wasted that produces a paper or two and the corresponding software for that just goes to digital nirvana, it's a real shame.
[0]: https://www.kraftmusic.com/brands/korg/synthesizers/nts2
Some more info: https://www.sciencealert.com/astronomers-are-about-to-make-a...
Of course RUDs of engines happened but they were the exception and not the norm.
The safety protocols have also evolved over times. Nicks death for example has triggered a rewrite of the rules that would require a medical examination after a blackout or if you cough up blood. This examination can result in a ban from further competing for the next days for example.
Of course it's not a safe sport, it's an extreme sport in an extreme environment. But lots has been learned in the past decades, as it is still a rather "new" sport and if exercised correctly it is rather safe. Also the article just talks about a competition. Most freediving happens either in training or when people do it recreationally. While accidents happen there as well, these are mostly about the lack of safety divers, that's why the first rule of freediving is, never dive alone.
Finally, on your last paragraph, freediving does change your day to day life, at least from my experience. I just do it recreationally, so I'm far from these depths and times Alexey and the others achieve, but the mental control you learn can be applied in many situations.
Basically, he advocates a new license that he wants to develop that basically improves remuneration for open source developers. Use case: A "Post Open" software is used by a company, then this company has to pay a certain percentage (1 to 10%) of their revenue to the "Post Open" software. If it is using multiple "Post Open" packages this percentage is divided among them (according to usage).
Software in this scheme will be allowed to be modified, redistributed etc. and it will also contain a public API that defines the boundaries of the program (so it's not about linking anymore).
I hope that captures the key points.