On Fri, Jan 03, 2020 at 11:31:48AM +0100, Josef Reidinger wrote:
V Fri, 3 Jan 2020 11:14:15 +0100 Ancor Gonzalez Sosa
napsáno: See more details at https://github.com/ancorgs/y3storage
Hi, this is quite interesting. Especially similarities in testing looks nice. I have few questions:
1. do you compare speed? Is really crystal significantly faster then ruby? And what about size? 2. how is crystal supported in SLE? Can we easily use it for speed critical parts of yast? 3. how works bindings to C++? I expect FFI should work fine, but C++ is not much FFI friendly.
Oh, interesting! Thanks for sharing, Ancor. Among the motivations why one would be interested in Crystal, I also care about better type safety. https://crystal-lang.org/ says:
Crystal is statically type checked, so any type errors will be caught early by the compiler rather than fail on runtime. Moreover, and to keep the language clean, Crystal has built-in type inference, so most type annotations are unneeded.
All types are non-nilable in Crystal, and nilable variables are represented as a union between the type and nil. As a consequence, the compiler will automatically check for null references in compile time, helping prevent the dreadful billion-dollar mistake.
Are you interested in this? Have you found any problems/benefits during the porting so far? -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner