Perhaps a dedicated node type is an interim solution, but it is VERY limiting.
not limiting at all. see below.
As an example of what can be done by using flexinode/event: I am currently developing a site where the client wants visitors to be able to signup for (paid) workshops and classes. I created a flexinode content type with fields for things like 'presenter', 'subject', 'additional info', and whatnot. Then I configured this node-type to receive fields from event.module and location.module. We can then use the ecommerce "product" tab to add price and inventory management (workshop capacity) to this geocoded, date-tagged node! And it shows up on the calendar, on the product page, and is searchable by location. Very powerful!
a very fine example - thanks.
Let's be sure that we don't inadvertently limit that with a narrow view of what an "event" is.
a dedicated event node type would be an *option* for people who just want to add events to their site in a quick, easy way. noone is talking about precluding other node types from becoming events.