warn the noobs away 😁 #1050
warn the noobs away 😁 #1050
Conversation
|
I don't think copying informal text of /rtfm command I threw a few years ago into main readme is a good idea. I do agree that having a more clear explanation of what this engine actually is (i.e. barebones engine for experienced developers) on main page is a good idea. (For same reason FAQ is still unofficial - I don't want to bother with rewriting it from informal language) |
|
yeah the informal tone is a bit rough, along with the unofficial FAQs, but when i personally stumbled upon that bit of text in the Discord, it hit me, hard. I felt that. And that just may have been what i needed, and what others need. also, i didn’t feel like i was in a position to write what Heaps is or isn’t, so i had to copy it from one of your mouths. 😁 |
|
I think the fact that Heaps is promoted as "cross-platform" on its website is most misleading. People expect a Unity-style write once, press button and publish to any platform kind-of engine. Hard truth is - while being able to run on all these platforms - almost nothing apart from Desktop is anywhere near out-of-the-box. This (apart from the lack of documentation) to me seems worth a word of caution to new users. |
|
from the repo:
from the site:
i just checked the web-site’s home-page, i think it was written to just kinda fit that generic product advertisement tone— “easy to get started”, it’s very fast! even a caveman can do it!—to it, lol. But yeah, i can see that being misleading... but maybe MonoGame advertises itself the same way... and that’s def not Unity one-click smooth. |
|
I agree that communication around Heaps engine is rather lacking and not explicit enough. I mean: we're not selling some product, it's just about "street credit" and opening the tools to advanced devs that could be interested in them. Don't get me wrong, Heaps is amazing and I will use it for most of my future projects. But I agree it's not an easy to use toolkit as falsely represented on the official website. So I think paying someone to rework the https://heaps.io website accordingly would be a better approach than tweaking the git README which is already an advanced thing for most people not used to open-source world. |
|
ahhhh hah, yeah that’s true, the site comes first since it’s more accessible. It’s a bit unfortunate as it looks like some soul put some love ‘n effort into making that site. :( i don’t even think anyone has to be paid. I think all it requires is some good writing to convey the right ideas about what Heaps is and what Heaps isn’t, which can then be copied to both the home-page and github readme (the github readme in lower priority). All it needs is a good, simple, honest summary, that we can all agree on. maybe i’ll close this and move to Heaps web-site repo, so i don’t bother the engine people... i’m sorry busy engine people 😢 |
please... i ask of you: please... you must spare them! 😭
lol, but really tho, it’s a warning to myself, me, about three weeks ago, that might have waded me away from the deep end, and saved me a few weeks; and i think some kind of warning or more detailed summary could successfully sway off others who aren’t ready for what they’re getting into.
obviously no offense or anything (i’m the noob!), but, there’s gotta be a way to communicate where in the game io framework to complete game engine spectrum this belongs... and surely it could save you pro programmers from us game-designer idiots asking idiot questions. :)