Amazon Lumberyard: A Scream of Anguish
viva64.com
Amazon Lumberyard: A Scream of Anguish
1–10 of 58 posts
Re: Amazon Lumberyard: A Scream of Anguish
#2Re: Amazon Lumberyard: A Scream of Anguish
#3Re: Amazon Lumberyard: A Scream of Anguish
#4If it wasn't obvious from the URL, OP is more about a code analyzer product than Amazon Lumber, mentioned in passing as an example usage.
That being said, I think this article really overstates the dire state of Lumberyard. Yep, it has bugs. I don't think this convinces me that the sky is falling if the devs don't change their ways.
Re: Amazon Lumberyard: A Scream of Anguish
#5One 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.
NaN === NaN // -> false
This check is sometimes used to check if a number is NaN.Re: Amazon Lumberyard: A Scream of Anguish
#6It effectively shows value of their software while being interesting enough and relevant to something popular that already has (some) following. Perfect.
Makes me wish they had something similar for JS or Python. I know I've made these mistakes all too often.
Re: Amazon Lumberyard: A Scream of Anguish
#7Re: Amazon Lumberyard: A Scream of Anguish
#8One of the best blog-ads for a product I've seen in a long time. It effectively shows value of their software while being interesting enough and relevant to something popular that already has (some) following. Perfect. Makes me wish they had something similar for JS or Python. I know I've made these mistakes all too often.
It effectively paints the blog-spam as being a good article.
Re: Amazon Lumberyard: A Scream of Anguish
#9Re: Amazon Lumberyard: A Scream of Anguish
#10Why 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.