Live data from Hacker News

Parsing Excel Spreadsheets with Swift's Codable Protocols

31–32 of 32 posts

Re: Parsing Excel Spreadsheets with Swift's Codable Protocols

#31

Post by watersb » Thu, Nov 15, 2018, 4:29 AM UTC

Serow225 wrote: post #25

ken wrote: post #19

Earlier quoted context omitted.

When I worked at Boeing, technical specs were built in a giant object/hierarchical database. There would be objects for Requirements, and in the design you could link Systems to the Requirements that they implemented. Then you could trace back from the design to see what requirements weren't implemented, or what systems had no apparent purpose, or who edited a particular requirement last. When they needed a hard copy…

DOORS ?

Ahh! I had not encountered that one for 20 years. Wow.

Re: Parsing Excel Spreadsheets with Swift's Codable Protocols

#32

Post by mpweiher » Thu, Nov 15, 2018, 3:14 PM UTC

maxdesiatov wrote: post #16

mpweiher wrote: post #14

Earlier quoted context omitted.

> Codable protocol in Swift is game-changing Which is really weird, considering Objective-C had automatic "activation/passivation" from the beginning (early 80s), and it was pretty trivial to adapt similar mechanisms later.

Except that in Objective-C it's a runtime feature, which is by definition slower. Swift's Codable implementation is generated by the compiler or is hand-written with an obvious benefit of a stronger type system.

Have you measured this? (I have)

Post reply on HN