|
|
|
|
|
|
by professorTuring
2528 days ago
|
|
|
I can't agree. Do you know which application who rely heavily on events is anywhere and it is programmed in OOP all around the world? Windows management systems. Everywhere. OOP works like a charm. Also, all that stuff you are saying about "expression-based" triggering, it exists and working fine... Also you are mixing OOP with files and folders and I can't understand why... |
|
|
Good enough, perhaps. Charm, no.
Re: Also, all that stuff you are saying about "expression-based" triggering, it exists and working fine...
Perhaps, but expression-based dispatching is not OOP. It's more comparable to relational or functional.
Re" Also you are mixing OOP with files and folders and I can't understand why...
I don't necessarily proposing mixing. If we can do it without OOP, that would be fine by me. I prefer the source code be organize by how a shop wants to work, not how the framework forces you to. Conway's Law.
Better yet, manage it in a database so one can sort, search, group, and filter by specific need at a given time. Why hard-wire a grouping when we have relational? If I want to see all button-handling events together, query, boom, done! If I want to see events for widgets with labels having the text "cup" in them, query, boom, done! Etc. Bill Gates won't determine my grouping/view, you don't determine my grouping/view, but I do. Me, myself, and I. I like that, it makes me productive.