News for hackers. Stuff that matters.
Re:Exploring Flutter for Cross-Platform Mobile Development by johnfn on Sunday May 28, 2017 @05:12AM (#14433640)
> Personally, I think it makes sense to differentiate between something which takes one child and something which takes an array of children.

Could you please explain this - it doesn't make sense to me.

To me it seems clearly and unambiguously true that a single child is not a special case vs multiple children, but rather just a list of children that is 1 long. I can't think of any cases where handling both as an array would possibly have you write worse code.

Re:Exploring Flutter for Cross-Platform Mobile Development by gman83 on Sunday May 28, 2017 @05:22AM (#14433672)
Take the Container class in Flutter, it can only take a single Widget as a child. Having to write a list of children that is 1 long every time I use a container doesn't make sense to me, and to me seems confusing as it will lead to people trying to add more items. I don't know, that's my opinion, maybe I'm wrong :)
Re:Exploring Flutter for Cross-Platform Mobile Development by johnfn on Sunday May 28, 2017 @05:35AM (#14433694)
Hmm, perhaps it's me not understanding the flutter paradigm, but if something only accepted a single child, I would stop calling it a child and start calling it a more precise name. Like perhaps contents in the case of a container?
Re:Exploring Flutter for Cross-Platform Mobile Development by sureshv on Sunday May 28, 2017 @11:43AM (#14434789)
Sounds like they took that from Android where IIRC a scrollview could only take one child. Coming from Win32 Android, back in the G1 days, always had its own idiosyncrasies.