The main problem with beta releases is we need to make it clearer on the site what kind of release you're downloading and make the release notes clearer. Ideally, everyone would still be on r80.2 (the last stable release), and just a few people would be installing r81 and r82 to help testing, since they're beta releases. However because it's not very clear everyone still ended up installing r81 and r82, then we get a lot of complaints about the releases not working. The intention is it shouldn't matter if beta releases don't work at all - they're just for testing and only people willing to trial the new features at the expense of stability should be installing them. From the r80 release notes I described why this is necessary:
e do test builds ourselves before release of course, but as a small team we simply do not have the resources to test quite like hundreds of people running it on their own particular software and hardware setups with their own unique usage patterns. Real-world beta testing is incredibly important to help make Construct 2 as reliable as possible.
In other words, due to our limited resources, it's inevitable that occasionally a new release will go out and it simply won't work. It's a fact of software development: we've seen the same happen to competitors, and even companies like Microsoft and Google have to occasionally rush out updates due to problems in releases, even with teams of hundreds of dedicated testers which we don't have (unless you count beta users!). The beta releases are supposed to reduce the impact of broken releases by only having a smaller number of users interested in testing try them out and report bugs, and then the majority of users who don't want to test and just want to stick to stable builds get the releases later, after wider testing has made it more reliably proven that they work. So I apologise for confusion over the latest beta releases and I'm working with Tom to make sure the site makes it a lot clearer.
Re: translations - we started this because a large company expressed interest in selling Construct 2 in a non-English company on the condition the software could be translated. So we've fast-tracked the translation feature. If you think it's a problem that we have such a small team, this is exactly the kind of feature that could bring us to wider markets and help us grow bigger. The non-English-speaking world is at least double or triple the size of the English-speaking world. I don't think anyone has realised the irony that everyone who's expressed concern about the feature has done so in English - of course, if you already understand English well, the feature doesn't affect you at all! But what about the many users who don't understand English who find Construct 2 but don't use it because they don't understand English? They're not here to express their complaints that it's English-only. We do have broader plans to translate the site, manual etc. as well, but translation is a long and complicated project.
I know there are a lot of other feature requests - tell me about it <img src="smileys/smiley1.gif" border="0" align="middle"> There are currently about 100 items on my todo list, and if each one takes just 3 days to plan, implement and test, that's still close to a year's work alone, not including other projects, bug fixes and maintenance we have to in the mean time. However, Construct 2 has only really been developed a little over a year so far, so please be patient and bear with us: hopefully given another year we'll have everything you've been hoping for finished and released! However in the mean time we have to balance a lot of different people's interests, and I hope you trust that we're working as hard as possible to do what we can for everyone.