Hazardous cheese obsession?
One of Jack’s odder food obsessions at the moment is Cheese Strings. He has them in his lunchbox for nursery, and he has them as a ‘snack’ at weekends when we let him.
As a bit of a cheese lover, I’d prefer him to be obsessed with something a bit more flavoursome, but we indulge him nonetheless. They are a good, healthy source of calcium after all.
Like so many things in childhood, Jack’s Cheese Strings obsession originates in the school lunch hall, where so many of his pals also have them in their packed lunches.
Preparing his lunchbox earlier this week though, I made a rather shocking discovery. Cheese Strings packets carry a health warning, advising adult supervision during consumption.
Now, obviously it’s sensible to keep a close on children whatever they’re eating – as much to ensure its being eaten rather than spread over the floor/table/chair as to prevent choking.
What amused me was that something as innocent as a piece of stringy cheese would require a health warning. It summoned all sorts of weird images to mind. Children, in a state of sugar-fuelled lunchtime exuberance, flicking lengths of cheese into each others’ eyes, or attempting to biting off more stringy cheese than they can chew.
I’m very much of the opinion that health and safety rules are pretty sensible. It’s also quite admirable that manufacturers go to these lengths to protect children’s safety. Bravo to the maker of Cheese Strings.
However, it’s also pretty funny that something as innocuous as a piece of cheese – albeit one designed to be ‘fun’ – is a potential health risk.
I notice that an ordinary block of cheese doesn’t carry this warning. I also wonder whether Baby Bells do (I haven’t checked, mind you). Yet, I would think a block of cheese, thrown with enough venom, could cause more damage than a stringy Cheese String?
All said and done, I doubt I will pay any more attention to Jack’s eating ritual with Cheese Strings than any other foodstuff. But it could be a good way to convince him to eat a ‘safer’ cheese instead…