8 ms·
Like most estimates, these seem off by about 3x. At least if you're writing it for the first time.
by saulpw 1y ago
Like most estimates, these seem off by about 3x. At least if you're writing it for the first time.
- mikebenfield 1y agoOr more. Actually some of them seem inverted. Simple compiler takes 3 months but a GameBoy emulator takes 2 weeks? That’s not my experience at all.
- azhenley 1y agoWhat I like about these projects is that you can make them as simple or as complicated as you want.
- tatjam 1y agoIMO the difficulties are a bit off, if a 2D physics engine is 5/10, then orbital simulation cannot be 10/10 (even with the difficult stuff like J2 perturbation) ;)
- zesterer 1y agoThe 10/10 was a copy & paste typo, sorry! Amended now.
- jart 1y agoAlso what's up with this 1 week to make a hash map? In C it's only slightly harder than creating a growable array.
- Jtsummers 1y agoAnd a POSIX shell is only 3 days. It's an interesting list but the difficulty/time elements are all over the map.
- jart 1y agoI wrote a shell that's designed to be good enough for the things likely to be passed to system() and popen(). It probably took me a week. To make it a non-toy POSIX shell, I could see potentially taking me a year. The shell is nuts. There's a reason why Thompson got replaced with Bourne and Bourne got replaced with Almquist, and most people use Bash, and then a lot of people started using Zsh. It's simple enough to attract greenfield implementors, and complicated enough for them all to get improved upon.
- layer8 1y agoFor some, it depends on the definition of “toy”.