3 ms·
Sure - but it is a departure in tone and sandwiched by more normal and productive comments (from that dev). It isnt ideal but it is also a pretty normal and min
by burnished 3y ago
Sure - but it is a departure in tone and sandwiched by more normal and productive comments (from that dev). It isnt ideal but it is also a pretty normal and minor human mistake (growing frustrated and then short to be specific).
And the previous comments were claiming that this project's data was 'proprietary' and not 'open' and the situation was inexcusable, basically because they assumed a database was this big scary thing (as opposed to an open book). That is a frustrating experience, and yeah maybe indicates that the person telling you how to write software doesn't know what they are talking about (for the folks following along at home, those frivolous cries of foul play were distracting from the real need they had for plain text over a database, someone else describes it quite succinctly a little later)
- fauigerzigerk 3y agoSure, it's no big deal and it's completely understandable. I just wouldn't characterise it as "incredibly polite". I think file system vs database storage is very much about trade-offs. Unfortunately the debate descends too quickly into who is right and who is wrong. It's always difficult for developers to talk to users who often really don't know what they are talking about. I know that very well. The only thing you can do as a developer (if you have time and patience) is to translate what users say into the closest thing that does make sense in terms of trade-offs. But nobody is always patient.
- burnished 3y agoOh! That makes sense, I'm a little jealous then. To me the way that discussion did not crash and burn due to a little friction was incredible