#ruby - 24 March 2018
« Back 1 day Forward 1 day »
[20:15:36] jjaii9: hey is it bad practice for a Ruby console program more or less have one "large" class that holds everything and initialize the class at the bottom, or it typically better to have a separate runner class and/or a rake task to execute things?
[21:06:36] phaul: so far I only heard people complaining about active record saying it does too much. You think something that does a lot more is better
[21:11:43] gizmore: phaul: look at this;: https://github.com/gizmore/gdo6-helpdesk/blob/master/howto/HOWTO.md
[21:12:14] gizmore: jhass: my main idea is that every datatype knows how to behave in 5 different scnearious
[21:12:22] gizmore: jhass: my main idea is that every datatype knows how to behave in 5 different szenarious
[21:12:24] gizmore: jhass: my main idea is that every datatype knows how to behave in 5 different szenarios
[21:13:55] jhass: what if I want to serialize to YAML? Protobuf? Messagepack? My own custom encoding?
[21:15:16] jhass: a serializer should know datatypes and conversions, not the datatype should know its serialzations and conversions
[21:16:30] gizmore: in gdo... there are unlimited types... the disatvantage is that they all need to implement a lot of cases
[21:17:11] gizmore: the cases are; 1) DB 2) DB to App and vice versa 3) JSON 4) JSON configforJS 5) .... thats it
[21:18:52] jhass: how about you write a blogpost and post it to rubyflow or whatever instead of spamming this channel?
[21:22:54] gizmore: just saying that Rails only offers 5 datatypes in DBA.... and it's isolated from the rest of your souce
[21:26:33] gizmore: imagine a world where you can plug GDT_Telephone into your DBA,JSON,HTML,Tables,Forms. etc