Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon Lumberyard: A Scream of Anguish

viva64.com

Post reply on HN
Print view View original

51–58 of 58 posts

Re: Amazon Lumberyard: A Scream of Anguish

#51

Post by tormeh »

wlll wrote: post #36
nik736 wrote: post #7

Why would anyone choose Lumberyard over CryEngine directly? I would think that ones core product will always be better maintained then just some side project that was bought in.

Crytek recently (and it may still be going on) sued Cloud Imperium Games (CIG, the people behind StarCitizen) for switching from Cryengine to Lumberyard. The details are few and far between, but the possibility or being sued by the vendor would be a bit off putting for me.

I remember reading about this and being left with the impression that CryTek was in the green there. Don't remember any details, but it wasn't as ugly as it sounds, though I also got the impression that CryTek weren't entirely graceful.

Re: Amazon Lumberyard: A Scream of Anguish

#52

Post by wlll »

tormeh wrote: post #51
wlll wrote: post #36

Earlier quoted context omitted.

Crytek recently (and it may still be going on) sued Cloud Imperium Games (CIG, the people behind StarCitizen) for switching from Cryengine to Lumberyard. The details are few and far between, but the possibility or being sued by the vendor would be a bit off putting for me.

I remember reading about this and being left with the impression that CryTek was in the green there. Don't remember any details, but it wasn't as ugly as it sounds, though I also got the impression that CryTek weren't entirely graceful.

I think you might have written CryTek there when you meant CIG so I'm not sure quite what you meant. Was it:

> I remember reading about this and being left with the impression that [CIG] was in the green there.

If so, ISTR CIG is fine, but then they have a lot of money and fancy lawyers, a lot of smaller companies might have fared less well, and it doesn't really look good when a vendor is seen to be suing their customers because it is rumoured they are running out of money.

Re: Amazon Lumberyard: A Scream of Anguish

#53

Post by Jare »

usrusr wrote: post #10
nik736 wrote: post #7

Why would anyone choose Lumberyard over CryEngine directly? I would think that ones core product will always be better maintained then just some side project that was bought in.

E.g. because Amazon might still be around next week? This hasn't been a given regarding Crytec for quite a while now.

Intel is still around but a number of game technologies they bought are not anymore. Lumberyard appears to be rather far from the core (or even the periphery) of Amazon's business, so it's a valid concern.

Re: Amazon Lumberyard: A Scream of Anguish

#54

Post by tormeh »

wlll wrote: post #52
tormeh wrote: post #51

Earlier quoted context omitted.

I remember reading about this and being left with the impression that CryTek was in the green there. Don't remember any details, but it wasn't as ugly as it sounds, though I also got the impression that CryTek weren't entirely graceful.

I think you might have written CryTek there when you meant CIG so I'm not sure quite what you meant. Was it: > I remember reading about this and being left with the impression that [CIG] was in the green there. If so, ISTR CIG is fine, but then they have a lot of money and fancy lawyers, a lot of smaller companies might have fared less well, and it doesn't really look good when a vendor is seen to be suing their cust…

No, I meant CryTek. RPG explains: https://www.google.com/amp/s/www.rockpapershotgun.com/2017/1...

Would someone like Unreal have swallowed that from a client in order to avoid bad PR? Possibly. But if the allegations are true then I wouldn't go so far as to expect (in the moral sense) CryTek to let it slide.

Re: Amazon Lumberyard: A Scream of Anguish

#55

Post by wlll »

tormeh wrote: post #54
wlll wrote: post #52

Earlier quoted context omitted.

I think you might have written CryTek there when you meant CIG so I'm not sure quite what you meant. Was it: > I remember reading about this and being left with the impression that [CIG] was in the green there. If so, ISTR CIG is fine, but then they have a lot of money and fancy lawyers, a lot of smaller companies might have fared less well, and it doesn't really look good when a vendor is seen to be suing their cust…

No, I meant CryTek. RPG explains: https://www.google.com/amp/s/www.rockpapershotgun.com/2017/1... Would someone like Unreal have swallowed that from a client in order to avoid bad PR? Possibly. But if the allegations are true then I wouldn't go so far as to expect (in the moral sense) CryTek to let it slide.

I'm not sure that CryTek have the moral high ground here as you seem to suggest.

CIG have moved to Lumberyard, a tech based on CryEngine, so lines of similar looking code are seemingly expected.

And the license was negotiated for a single game, not two as StarCitizen now is, but this would seem to be negated by the fact that these games are no-longer using CryEngine.

On the subject of CIG passing back engine improvements or not to CryEngine, I don't know.

Re: Amazon Lumberyard: A Scream of Anguish

#56

Post by [deleted] »

jhare wrote: post #26

Easy to pick on an open source project, suggest changes, but not actually make them on your OWN fork? Clickbait, gross. Similar to linting, where often I need variation in rules, sometimes there's red herrings even in static code analysis. Game software in general can be fly-by-the-wind because it's real-world software ... of course this is all me reacting and trying to argue with the clickbait :/

[deleted]

Re: Amazon Lumberyard: A Scream of Anguish

#57

Post by pjmlp »

cmjqol wrote: post #35
jhare wrote: post #26

Easy to pick on an open source project, suggest changes, but not actually make them on your OWN fork? Clickbait, gross. Similar to linting, where often I need variation in rules, sometimes there's red herrings even in static code analysis. Game software in general can be fly-by-the-wind because it's real-world software ... of course this is all me reacting and trying to argue with the clickbait :/

> not actually make them on your OWN fork? Clickbait, gross. Yup. Something like : > You have bugs in your codebase of 1M+ line, you want to fix them ? Buy my proprietary software for 30$/Month per user , which was built 100% on open source tech obviously. Getting traffic using linting issues from a large codebase to promote a proprietary software , Outrageous.

Well that is what happens when releasing open source tech with licenses that support this kind of behavior, nothing to be outrageous about.

Re: Amazon Lumberyard: A Scream of Anguish

#58

Post by pjmlp »

deng wrote: post #43
royjacobs wrote: post #2

One thing that puzzles is me is why some of these checks aren't just part of the warnings that a compiler emits. I get that you wouldn't want to enable them all the time, but usually comparing a variable to itself is not what you want.

Two main reasons: Many warnings that a static analyzer will emit are quite costly to detect, so the compilation would get slower. And since compilation speed is an important benchmark (if not the most important), one would usually not sacrifice this for some warning. Also, people usually do not accept false-positives in compiler warnings. Static analyzers often have heuristics to detect typos like these: a.x = x; a.y…

That is why it should at very least, be turned on the CI server.
Post reply on HN