xlsx VS excelize

xlsx/tutorial/tutorial.adoc - tealeg/xlsx - GitHub

Your library is nice, I keep going back to taelag just for WriteStruct and WriteSLices https://github.com/tealeg/xlsx/blob/master/write.go#L88

A true single-pass .xlsx writer that emits inline strings, declares sheets upfront, writes rows directly into a live ZIP stream, and never touches temp files. Go's excelize library does something close to this. Java POI doesn't. This is architecturally possible but would essentially be rewriting POI's OOXML layer — a multi-month effort. I've raised this as an RFC with the POI community.

Then I found out that WPS only supports ecma376 standard encrytion for xlsx files. Then I referred to the official documentation and libraries in other languages, such as msoffcrypto-tool written in python. msoffcrypto-tool) and go's excelize. Since I don't know much about encryption and decryption, the process of implementation is also a bit of a twist.

But if you absolutely need xlsx files, I would seek the best library for the job and write this in golang.

Documentation website with multilingual: Arabic, German, Spanish, English, French, Russian, Chinese, Japanese, and Korean, which has been updated

Golang excel: https://github.com/qax-os/excelize

Yeah, I'm reading it now and just parse, I didn't find a implementation of "calculation engine" all the available libs just read previous saved value from a opened and calculated excel file. See: https://github.com/qax-os/excelize/issues/65

Hey guys, i tryed using this https://github.com/qax-os/excelize to read excel table ,(70+columns and 500k rows). When using the sheet method from the documentation it takes about 3 to 4 minuts to find search item, and ofcourse limitation is that it needs to be a match.

Much like excelize for go lang.

Suggestion: When a method is safe for concurrent use, document such in its godoc comment. None of the formal documentation mentions concurrency, and its unclear what methods are concurrency-safe. The only tip-off that something might be safe for concurrent use is the occasional use of the sync package. This eventually led me to a year-old release footnote as the only documentation across the entire project about concurrency. This information isn't even in the Git tag, just the GitHub release page.

The title more or less says it all, but to give some background to the question, as long as it’s done safely (for example, with a mutex and locks) like with concurrent writing to a txt file, does anyone know if concurrent writing to an excel file, particularly while using excelize/v2 is possible? I have a 2D slice of data produced after processing an image that needs to be written to an excel file created with excelize/v2 and it’s plenty fast up to a certain set of dimensions, but I’d like to support even larger dimensions and was considering using concurrency to do so. But the only examples of concurrently writing to a file with Go that I could find were txt file examples. So I’m not quite sure if my scenario is possible.