Live data from Hacker News

Cryengine Source Code

github.com

1–10 of 149 posts

Re: Cryengine Source Code

#4

Used to work with cryengine some time ago. That is by far the worst c++ codebase i've ever seen.

While your opinion is appreciated. It would be more helpful, if you could point out sone of the reasons why it was so bad in particular.

Re: Cryengine Source Code

#5
Would it be an overreaction to not want to touch this licence with a barge pole?

Even ignoring the “We may change this licence at any time and it applies to you” parts, there seem to be serious restriction on usage and basically have to ask them to do _anything_ beforehand.

Maybe it makes sense if you are already in a project that is using this Licenced? Is this intended as a general engine licence rather than viewing the source code?

Re: Cryengine Source Code

#6
I considered using cryengine recently but there was an almost total lack of learning resources: I could barely find a tutorial that was newer than 5 years, especially one that involved it’s c++ APIs.

I suspect that lumberyards greatest advantage over cryengine in the future will simply be usable documentation provided by amazon. Cryengine is simply not usable without better docs or else an incredible amount of time. Crytek is having financial troubles but I bet their engine would have 10x adoption if they hired a team technical writers

Unreals docs are fairly bad also, but at least there are some third party resources to turn to

Re: Cryengine Source Code

#7

Used to work with cryengine some time ago. That is by far the worst c++ codebase i've ever seen.

Interesting sentiment, I sometimes wonder if a "messy" codebase can have advantages for performance.

Many very highly performance tuned applications I saw in the wild would fall into the category of "horrible codebase" when looked at through that lens.

Re: Cryengine Source Code

#8
That license looks like a minefield. Any lawyers able to chime in on the reality of becoming tainted? Given their recent history, this is one codebase you really wouldn't want to risk becoming tainted by.

Re: Cryengine Source Code

#9
post #8

That license looks like a minefield. Any lawyers able to chime in on the reality of becoming tainted? Given their recent history, this is one codebase you really wouldn't want to risk becoming tainted by.

What is their recent history?

Re: Cryengine Source Code

#10

Used to work with cryengine some time ago. That is by far the worst c++ codebase i've ever seen.

Generally, things that are not open source are rarely not well written, since there are less programmers who will read your code, and all questions on the code can be done internally, so developers only write code so it works.

Open source generally leads to better quality code, since it's the best way to attract other developers to contribute to it.

So I'm rarely interested by any accomplished project that opens its code.

For example, if microsoft opened its OS, I doubt developers would really try to do things with it. The windows kernel would obviously be high quality code, but a lot of the rest is probably short lived garbage.

Post reply on HN