Night Wolf
I don't bite.
- Joined
- Feb 10, 2008
- Messages
- 581
- Solutions
- 8
- Reaction score
- 929
- Location
- Spain
- GitHub
- andersonfaaria
I find it funny that some people have read thousands of lines and arguments but still think I'm crying because I can't do what Kondra did.
Guys, the whole point is not about one person doing everything. We have different segments, different skills.
My server won't be as good as it could if I just fix everything myself, and worst, it will suck years of my life where I could be actually learning other skills more relevant to my professional life such as management, user experience, marketing and public dealing.
I could do literally whatever I want, even writting a whole client from scratch. The point is: how much energy it would take? How many years? And what would happen when I left? Will it be all in vain?
For me @edubart contribution of even thinking about developing a client is a milestone in it's own, yet he might have succeed in learning what he wanted but he failed to understand the public he was developing for and the flow of software development itself. Things are getting more and more less technical and not about 'do you know how to code this' but rather about, do you understand this logic and know how's to use google? We even can see that by Github and IEEE reports regarding most used programming languages or even at Hype Cycle trends such as the ones Gartner usually do.
This way you're not anymore talking about a community that only devs with a single skill can work to improve, but rather a whole community of different people with different jobs and skills can use their logic to build something great.
My opinion personally as someone who works in a fortune 70's company:
OTC: Few people understand it's architecture and we have little to none documentation. Several parts were rushed and made with not optimal or state-of-art algorithms so even in Edubart's case, he learned how to do them, but not learned how to do them THE RIGHT WAY.
Only devs that actually take their time to study the code are able to contribute and 'leechers' as testers.
Unity: Several parts of really technical processing can be replaced by the engine's version that is made using state-of-art algorithms.
We wouldn't need only bacharelors in Computer Science and enthusiasts to contribute as they could simply read the docs and implementing improvements with the engine.
Way more intuitive and customizable, several documentations online including videos sometimes. We could take everyone's help to improve quality of documentation of the parts done by Slavi and help designing the architecture of the project to allow it to grow healthly.
Unity once builded drop any feature that isn't utilized, so the claims here that it would be 'heavier' or 'slower' are not true. It has also one option that makes it WAY MORE ATTRACTIVE that is the fact that you can't mess with the files once they are build. So sprites would be protected and messing with the server source through the client would be way harder.
Guys, the whole point is not about one person doing everything. We have different segments, different skills.
My server won't be as good as it could if I just fix everything myself, and worst, it will suck years of my life where I could be actually learning other skills more relevant to my professional life such as management, user experience, marketing and public dealing.
I could do literally whatever I want, even writting a whole client from scratch. The point is: how much energy it would take? How many years? And what would happen when I left? Will it be all in vain?
For me @edubart contribution of even thinking about developing a client is a milestone in it's own, yet he might have succeed in learning what he wanted but he failed to understand the public he was developing for and the flow of software development itself. Things are getting more and more less technical and not about 'do you know how to code this' but rather about, do you understand this logic and know how's to use google? We even can see that by Github and IEEE reports regarding most used programming languages or even at Hype Cycle trends such as the ones Gartner usually do.
This way you're not anymore talking about a community that only devs with a single skill can work to improve, but rather a whole community of different people with different jobs and skills can use their logic to build something great.
My opinion personally as someone who works in a fortune 70's company:
OTC: Few people understand it's architecture and we have little to none documentation. Several parts were rushed and made with not optimal or state-of-art algorithms so even in Edubart's case, he learned how to do them, but not learned how to do them THE RIGHT WAY.
Only devs that actually take their time to study the code are able to contribute and 'leechers' as testers.
Unity: Several parts of really technical processing can be replaced by the engine's version that is made using state-of-art algorithms.
We wouldn't need only bacharelors in Computer Science and enthusiasts to contribute as they could simply read the docs and implementing improvements with the engine.
Way more intuitive and customizable, several documentations online including videos sometimes. We could take everyone's help to improve quality of documentation of the parts done by Slavi and help designing the architecture of the project to allow it to grow healthly.
Unity once builded drop any feature that isn't utilized, so the claims here that it would be 'heavier' or 'slower' are not true. It has also one option that makes it WAY MORE ATTRACTIVE that is the fact that you can't mess with the files once they are build. So sprites would be protected and messing with the server source through the client would be way harder.