4 ms·
> ketchup (html parser and DOM Tree builder) mayo (css parser and Render Tree builder) mustard (UI Toolkit, events and OpenGL) sauce (requests, cache and filesy
by als0 6y ago
> ketchup (html parser and DOM Tree builder)
mayo (css parser and Render Tree builder)
mustard (UI Toolkit, events and OpenGL)
sauce (requests, cache and filesystem)
bun (css layout calculator)
Off topic, but I've encountered some more serious projects that used strange nouns to name their components. I've never figured out why, but it usually results in me spending more time cross-checking what each component does. Can anyone comment?
- ad404b8a372f2b9 6y agoBecause it's fun and if you work regularly with the codebase it makes no difference. Organizations adopt terms that aren't strict descriptors of the things they refer to all the time, stuff like the Johnny.Decimal system, someone will refer to "form 4.54" or "being compliant with 13485" and everyone will know what it refers to even though it's a perfectly opaque name to outsiders.
- damagednoob 6y agoEngineers think they are being cute when they do this. In reality it hampers new devs because you can't just look at a component and have an idea of what it's doing. I've been on projects like this and after a year I was still second-guessing myself.
- sumtechguy 6y agoI used to do this. Now I use 'boring' names. My funny joke is not very funny anymore spin 2 years on (even then it was only slightly funny). Then you end up with a lookup chart for what does what. When if I had just used 'normal boring' names in the first place I would not be trying to remember what object 'funnyname' does vs 'movedatatodb' object name.