... speaking of efficiency: full-quoting 5 levels of mail history just to add two wee lines way down? ... just saying.
In the good old days, we would quote only the necessary to avoid filling up precious mailbox space. > On 9. Oct 2025, at 18:34, Martin Terra <[email protected]> > wrote: >> On 9/10/2025 9:48 pm, Andrea Del Bene wrote: >>> On Thu, Jul 17, 2025 at 11:01 AM Andrea Del Bene <[email protected]> >>> wrote: >>>> On Wed, Jul 16, 2025 at 1:25 PM Martijn Dashorst >>>> <[email protected]> wrote: >>>>> On Tue, Jul 15, 2025 at 3:12 PM Richard Eckart de Castilho >>>>> <[email protected]> wrote: >>>>> >>>>>> Does the memory usage matter a lot? >> >> There's a reason Linux is still written, mostly, in 40 year old C. Some >> recent efforts to convert some parts to the latest shiny thing, Rust > > have ended up with lower performance than their C based originals. > > 1+ Facilitating alternative ways of doing something doesn't mean the old / low-level approaches have to go away. I'm using quite a bit of lambdas with Wicket without having changed a single line of code in the core framework (although I have Lambda* variations of several key classes and components). Thing is, if I find this useful, maybe others will too. And what's the point of each of use maintaining our own versions of such lambda helpers and utilities. Let's figure out what ideas people have and where they best may go - be it Wicketstuff, a core extension, or the core itself. Mind that while the the core already does have a lambda support in a (very) few places, e.g. LambdaModel, nobody is force to use it. But it is there and it is at times quite useful. Cheerio, -- Richard
