4 ms·
I, for one, think you should do it. But you've got to realize, up front, this will be thrown away, will only work for 1 use case, will be slow, etc. Don't build
by arh68 13y ago
I, for one, think you should do it. But you've got to realize, up front, this will be thrown away, will only work for 1 use case, will be slow, etc. Don't build anything general, or anything reusable. Write in Go. Put everything in one big textfile. Start with O(slow) code. Use a simple 'schema', like tsv/csv/json. It will work.
Production-ready, simple, written by you: pick 2. The 'correct' thing to do is choose the first two. Have at it.