3 ms·
This is all a very neat summary, but I'll go out on a limb and say that for most of us, the first-order approximation should be "don't. Just don't". Been there
by groby_b 3y ago
This is all a very neat summary, but I'll go out on a limb and say that for most of us, the first-order approximation should be "don't. Just don't".
Been there. Done/sort of doing that. Have impressive collection of scars. There are no t-shirts to be had.
This document only barely scratches the surface of the work necessary. If this is your calling, by all means, but expect to sink a good chunk of your life into it. Things are glossed over in a paragraph that mean years of work. (My favorite is the internationalization section, closing with "But don’t worry: there’s a standard. All you need to do is implement it." - All you need to do, indeed :)
To be clear: Colin knows it's years of work. He's been working on a number of excellent projects in the space (xi-editor, druid, ...). But I really feel this deserves a warning sticker, lest you accidentally spend a decade or two of your life on it.
- ReactiveJelly 3y agoEh, re-inventing wheels is fun. I learned a lot making my own games from scratch with no engine. I'll make a bad one-user GUI kit some day too.
- c-smile 3y agoWell, it is definitely not a suicide mission. At least in my Sciter I've implemented all those by myself in reasonable time frame - first version was made in 9 months. But "yes", you need some prior experience, in order to come up with flexible architecture that will allow to expand it further without major redesigns. First version had DOM/CSS and used just GDI. GPU support (Direct2D, OpenGL|Metal|Vulkan via Skia) was added later with API staying the same.