Unicode symbols is a good idea.
I'll call my compiler 👷♂️and my debugger 😈.
Even just being able to view the source code without cloning is very valuable. A bare repo does not provide that.
So, is the account actually read-only?
So it really is that simple: a small bash script, building locally, rsync'ing the changes, and restarting the service. It's just the bare essentials of a deployment. That's how I deploy in 10 seconds.
I'm strongly opposed to local builds on any semi-important or semi-complex production product or system.
Tagged CI release builds give you a lot of important guarantees involved in release concerns.
I'll take the fresh checkout and release build time cost for those consistency and versioned source state guarantees.
It's been over 10 years since we released Rogue Legacy 1, and in the pursuit of sharing knowledge, we are officially releasing the source code to the public.
https://github.com/flibitijibibo/RogueLegacy1/
License head
Rogue Legacy 1's source code is made available under a custom license. Basically, you can compile yourself a copy, for free, for personal use. But if you want to distribute a compiled version of the game, you might need permission first. See the EXCEPTIONS.md page for more information.
If you only care about contributing improvements, no, it doesn't matter.
If you want to at least be recognized as an author, and be able to say "I made this", the license opposes that.
Waiver of Rights: You waive any rights to claim authorship of the contributions […]
I don't know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.
TOML instead of YAML or JSON for configuration.
YAML is complex and has security concerns most people are not aware of.
JSON works, but the block quoting and indenting is a lot of noise for a simple category key value format.
What do you mean by professional?
Be paid, even if really bad, and a net negative for the projects and companies you're involved with? Then it's certainly possible.
Dada data structures
giggle
Webcrawlers count as users too, right?
Memory safety issues were a thing even before bootcamps and "bootcamp culture".
Even if you fix expertise, intention, and mindset - the entire workfield environment and it's people - mistakes still happen.
If you can categorically evade mistakes and security and safety issues, why would you not?
"We see no evidence of that which we do not monitor."
These press releases/responses seem to never include "we track x and y and see no evidence". Or "we would be able to identify them but do not see evidence". I can only assume the worst.