I really appreciate your honest answer! It’s actually one of the big problems in dev.feedback when developers start to defend a lack of a feature. Obviously we all can agree that TumultHype being able to create those favicons etc would be the best solution… BUT what you said makes more than sense. It might not be the best bang for the buck and I do agree that I’d rather have the features that Hype currently has than change one of those to automatically generated favicons. It proves that you have a clear focus and vision that pushes Hype on the right direction.
Personally I’m one of those users who know how to copy-paste script to do some of the things that WYSIWYG buildrs cant do. I’m able even to modify the script to fit my need at times. But I’m certainly not up to scripting almost anything myself be it CSS, HTML5 or any of that sort. The best part of Hype is that you can create amazing things without going into the script. Obviously I cant do the same things as someone who knows how to script HTML5 and so forth, but what I can do is more than enough and it’s getting better by the version.
Thanks for both of you, for the favicon html that I need to utilize and reasonable reason for favicon staying on the maybe list!
PS. I think that Hype is dev driven product, not feedback driven. And thats super! Because all the app developers who I’ve seen to drive app development by user feedback have proven to have no vision. The end result to user feedback driven app development is usually something that doesnt please anyone at the end and is still missing too many features compared to ten of it competitors.