39 ms·
Wouldn't these happen in the DB? I can see some algorithms for showing related articles being complex — but writing them in Assembly also invites other challen
by jbm 3y ago
Wouldn't these happen in the DB?
I can see some algorithms for showing related articles being complex — but writing them in Assembly also invites other challenges (them being difficult to update and improve, concentrating on memory issues rather than algorithm, etc...).
I still think it's a cool project mind you.
- jacquesm 3y agoKeeping any assembly codebase up and running, especially through changes in requirements is a massive challenge, requires extreme hygiene and will be very, very costly. My largest assembly projects were around the 16K object code mark (the size of the largest EPROM) and I hope to never ever have to do stuff like that again. But the kind of performance you can get out of very modest hardware is amazing.
- 10000truths 3y agoThe DB in this case is SQLite, which is embedded.
- chefandy 3y agoWould that not still result in a disk IO bottleneck? Also, DB code is pretty well optimized. Are we sure that remaking that functionality in assembly will be dramatically better?