No one is saying scam. I think offering a market that is clearly labeled isn't comparable to someone trying to pass off testnets to someone trying to buy Bitcoin.
it doesn't matter how it is labeled, as long as something that is
designed to not have any value is being
sold, that is the definition of scam.
Seems kinda rude
... testnet is cryptocurrency too. Why can this be the "world currency" and this be worthless, but they are basically the same thing? That makes no sense to me.
bitcoin being the world currency has nothing to do with testnet-bitcoin being sold!
I would bet that testnet gets more stable for people using
testnet is already stable.
making testnet better and easier to use for Testers.
testnet is already both easy and good to use for testers. i have never had any issues using it.
if you had any issues YOURSELF then please share your issue and lets discuss why YOU are facing an issue. if you are just concerned about the number of people who have been complaining lately, know that they want to get large sums of tbtc so that they can exchange it for some scam token that may have a value someday if it doesn't die. they are not testing anything!
Haha, I'm sure hacks have happened because of a decimal missed here or there... if people can only test with dust, I could see this as an issue.
Plus, it's good for the imagination to see your application work with large numbers of coins if that what you intend it to do... rather than just be a dust bowl.
It should be noted that I am not a coder... I am, however, fairly familiar with Bitcoin.
any application has different layers. imagine if you wanted to test if the car's window button (roll up handle), you just focus on that button not fill the tank with gas and start the car, go in highway and test the button while driving!
in your example the decimal issue is a UI problem, it doesn't even get to backend. to test it, we focus on that part only. there is absolutely no need to create a transaction and broadcast it to test something as simple as this. all it takes is a good code, preferably following IoC principle then we write test cases that are testing the edge cases on the UI thread only. then the same tests on backend but this time it only accepts int-64 instead of decimal (decimal only exists in UI) and similar edge cases are tested there too. same with any other part.
then all these parts are joined together and work like a well oiled machine.
long story short, in my experience whenever a developer is complaining about hardness of a certain test, that's because their code is bad and needs a big refactor.