@SenseException I blame popular libraries and frameworks that are still array-based. (#Laravel and AWS-SDK at the top of that list. #Drupal, less than it used to be but still.) And people who cut their teeth on CodeIgnighter et al and never grew past that.
@Crell@SenseException Arrays are just so easy to use in #PHP. Perhaps with property hooks and interface properties (combined with past changes to support property types), value objects will be easier.
@ramsey@SenseException I don't think the new rfc does much to change that balance, sadly. If someone isn't tempted away from the dark side by property types, I don't see how interface properties will do it.
@Crell@SenseException Maybe not, but I think it gives properties on objects a full story. I’m not sure at this point why we would need a struct-like data structure.
@ramsey@Crell@SenseException the syntax for property hooks is very meh. Properties on interfaces is wonderful though. Very much looking forward to that.
@shadowhand@Crell@SenseException The syntax doesn’t bother me. I’ll probably standardize on always specifying the argument, though, for the set hook (i.e., set(type $value) {} ).
@heiglandreas@ramsey@Crell@SenseException Part of the property hooks RFC is the ability to define properties with expected hooks on interfaces. (Won't work for generic properties; basically defines if a get, set or both hooks are required in the implementation.)
@mwop@heiglandreas@ramsey@SenseException It absolutely will work with generic properties. A plain boring public property will satisfy an interface requirement for both get and set. A readonly public property will satisfy a get-only interface requirement.
@mwop Ah. That isn't allowed, no. Specifically, the interface can say "this property must be readable" and/or "this property must be writeable." That's the minimum set of requirements you can place.
Those can be satisfied by plain properties or hooked properties, as your implementation prefers.
@Crell@mwop I am not sure though why the interface declares an implementation detail.
The property hook should not be part of the API IMO. It's just an implementation detail of what to do with the passed information when setting or getting.
Or I completely missunderstood the whole concept....
@mwop@heiglandreas@Crell in the example it just enforces that the $name property should be publicly accessible. That’s more than just an implementation detail if you ask me 😄
@Crell@deleugpn@ramsey Not to mention that devs can stuff any data in any form or structure into an array (which is what you already called "hell to maintain"). It reminds me of RDBMS/SQL vs. Document DBs/NoSQL.
@dusoft As far as I can remember objects became faster and faster over the last decade with newer php versions. I'm sure you'll find a history of such tests in Google.
The benefits of VOs are about structure, api, maintenance and/or archtecture.
or you have to pass them in via constructor arguments in the correct order and it's just a pain. I always try to use them, but every time I find it inconvenient because it's so cumbersome.
@SenseException (thinking about it, now with named arguments and constructor property promotion, it may no longer be an issue. Haven't connected the dots on these two features, it seems.)
Add comment