| ▲ | daledavies 2 hours ago | ||||||||||||||||
I think we have to try these things at least once. My own attempt to write a javascript framework ended with me realising that I needed to put more effort into planning and research, which was a valuable lesson for me. | |||||||||||||||||
| ▲ | kyzcdev 2 hours ago | parent | next [-] | ||||||||||||||||
Yes building tools from scratch is a great way to learn. In my carrier a rewrote bunch of front-end frameworks, but then instead of rewriting everything from scratch I decided to simplify existing structures. Once I tried to create my own front-end framework from scratch. I created signal library, mounting/unmouting, context etc but never able to write v-dom diffing or using existing vdom libraries. Then I decided just implement my API on top of Preact. Preact did vdom-diffing for me and mounting/unmounting which was enough for my need. The final project looked nothing like Preact, it even had it's own context system, data loading, signals, setup + render and context which just hooks itself into Preact Context but taught me a lot about how a front-end framework work. | |||||||||||||||||
| ▲ | vector_spaces 2 hours ago | parent | prev [-] | ||||||||||||||||
Right, I think the usual point here that if your goal is to make a game, then this is usually the painful route and conveniently one that up-fronts the likely more exciting and comfortable part for a software engineer, namely the software engineering. It also tends to defer the very important business of learning rather quickly whether our idea even leads to a fun game in the first place That said, it's still a worthwhile exercise that one can learn a lot from. | |||||||||||||||||
| |||||||||||||||||