V Fri, 3 Jan 2020 11:14:15 +0100 Ancor Gonzalez Sosa <an...@suse.de> napsáno:
> Ok, and now that I got your attention, let's rephrase the subject into > something more realistic: "I'm starting to port to Crystal a very small > and limited subset of yast-storage-ng". > > See more details at https://github.com/ancorgs/y3storage > > Is something I wanted to do in the past Hack Week... and in the previous > one... and so on. So finally I used the downtimes of my recent trip to > Nuremberg and some vacation time to get it started. > > Since next Hack Week will take place soon, I hope to continue with that > and maybe experiment with automatic translation or bindings. Let's see. > > So far, you can get surprised about how similar both languages are by > displaying y2storage/disk_size.rb side by side with > y3storage/disk_size.cr, or also y2storage/disk_size_test.rb and > disk_size_spec.cr. > > Cheers. > > PS.- No, there is no evil plan to migrate YaST to Crystal. This is just > done in the Hack Week spirit of "what if". 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. Josef -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
