2 ms·
I don't know what you suggest we do about that. I want my users to be able to use my programs in their languages, that requires translatable strings, UNICODE, I
by jchw 8y ago
I don't know what you suggest we do about that. I want my users to be able to use my programs in their languages, that requires translatable strings, UNICODE, IME. We didn't lose anything: I still could've used Allegro. I wouldn't because it no longer meets my needs. If you want to develop applications that don't meet modern expectations, you can use whatever framework makes you happy. Hell, some people really do still use primitive UI toolkits.
- badsectoracula 8y agoI do not suggest anything, my post was to explain that you (that is a "royal you") do not always need all the features you wrote. For example you write that you want your users to use your programs in their language, but most often that does not require Unicode - people did it before Unicode was a thing. It is just that Unicode makes it easier. My post was an example of someone who doesn't need any of the stuff you mentioned and from my perspective these are just adding bloat since i wont use them. This isn't a recommendation or anything like that. If you consider people being able to use your programs in their language and consider it a good thing to do, a toolkit that provides that feature will do fine for your case.