Yes, your problem is how to get people to invest their time on your product, and make the product better than the competition. The customer is always right, even when he's wrong.
No, it is mine because I cannot force spring to close for users who do not have the hardware to run it. Thus I get tons of fucking emails asking why spring crashes as that assume it is my fault instead of their shitty hardware. MOST games close out or error or something meaningful. like "hey your hardware is too weak, get better stuff"
Jools wrote:
Yes, your problem is how to get people to invest their time on your product, and make the product better than the competition. The customer is always right, even when he's wrong.
My problem is that they are trying to run spring with stuff that even after they force spring to run on their hardware, they can barely actually play.
"The customer is always right.. " you forgot the most important part "while they are paying you." See they are not paying me, therefor, not customers. Keep applying generalized terms to specific situations in life, it will serve you well and you will be successful btw, *insert race* are stolen bikes and chicken.
"The customer is always right.. " you forgot the most important part "while they are paying you." See they are not paying me, therefor, not customers. Keep applying generalized terms to specific situations in life, it will serve you well and you will be successful btw, *insert race* are stolen bikes and chicken.
No, I mentioned the paying part, only in this case it is not money but time and attention. If you want to make code that no-one sees you can just as well put it to pastebin or something. I think most people that work with spring also want the code to be useful for someone.
Guess what, if you want it to be useful, it should tell them upgrade their shit. Otherwise, they will spend all day trying to run spring only to find out after they finally post their infolog that DERP they cannot because intel onboard.
Your argument is backwards. Hardware is one level up in hierarchy from software. The purpose of software is to make hardware work. Do you also first buy the CD player and then after it the car in which it will be put?
Come to think of it, maybe it goes a bit hand in hand.
But the point is that you start from an idea, research the interest and relevant customer segments (feel free to not call them customers), then you make the product. Why is this so hard to grasp? Even virus makers understand this concept.
Your argument is backwards. Hardware is one level up in hierarchy from software. The purpose of software is to make hardware work. Do you also first buy the CD player and then after it the car in which it will be put?
I think it is a language barrier issue for you. I am saying we cannot effect a change on the hardware with the software. Feel free to click the link I provided to prove me wrong.
Jools wrote:
Come to think of it, maybe it goes a bit hand in hand.
But the point is that you start from an idea, research the interest and relevant customer segments (feel free to not call them customers), then you make the product. Why is this so hard to grasp? Even virus makers understand this concept.
What are you even saying? research interest and relevant customer segments, are you high? That has 0 to do with the hardware limitations brought about by people trying to run spring on hardware that is unsuitable.
Users browsing this forum: Google [Bot] and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum