Those Reviewers are nonsense!
(1) Reliability problem: holding data in buffer may cause file system crash for sudden power failures.
My Viewpoint: 1TB HDD with 32MB Buffer also suffers the same problem - that is why we have journalised file system and battery backup expensive storage solution. When power cut - nothing will work!!! It's like you saying that your touch screen paper won't work because handicapped people without hand/finger can use it
(2) The buffering technique is not novel: High-end SSDs are using write-coalescing in the drive already.
--> As the market mature, component cost will drop, and HW solution (on-board write buffer) will be more popular. Therefore FlashFire solution will not be useful at that time.
My Viewpoint: What if the power loss during write-coalescing or only half of the "coalesced" block have been written to media and another half is being transmitted to media and power is lost? That will cause severe damage to file system or at least having same effect as power lost during flushing 32MB buffer in HDD. Flashfire solution can be tuned to a specific file system,like bypassing buffer for some important data for NTFS filesystem, because you can make it aware of the file system, so it is more novel than HW based solution which work at block level.
(3) Log-structured File System is better than FlashFire Solution: Log-structured File System can change random writes (small writes) to sequential writes, and thus there will be no performance problem with log-structured file system.
(and so on)
My Answer: NONSENSE - Flashfire was designed to be used by end user who has random access pattern. Log-structured file system would make the severe fragmentation in the long run. (hey! - there is virtually 0 seek but the reading will be non-sequencial and there will be some performance hit for CPU to resemble the pieces!)
Keep up the good work!
