Quote:
"BeeHive software could be 1 Windows update away from extinction."
I can't speak for the people who maintain the Beehive code, but I don't think that Windows updates specifically will affect it, what with it not being based on the Microsoft tech stack.
But, changing the question slightly - what happens if *something* - a PHP update, or an HTML standards change, Opera becoming the world's most popular browser, whatever, means that something stops working? I mean, Beehive still uses frames, FFS! Well, I'd hope that someone would take a look at the source code, and make the necessary changes. However, that leads quite nicely onto the next question...
Quote:
"as most know, the BeeHive software is not supported any longer"
Again, I can't speak for the various people who maintain the code, and have done since 2002(!), but in those 18 years, a lot has changed. The group of enthusiastic amateurs coders from 2002 are pretty much all grizzled IT veterans now, and I imagine they've got more pressing things to worry about. Bear in mind the last point release was 2016, and I don't think there's an active roadmap for new features or anything like that.
Also, since 2002, the nature of the internet has changed. Things have solidified and codified. There are a smaller number of platforms, and the mechanisms for monetising are (slightly) clearer and have made those who own those platforms (significantly) richer. What's the point of creating your own thing, when Amazon or Google or Facebook or Twitter or Reddit or Wordpress or PHPBB or whoever else (Microsoft?) offers the tools to do whatever it is you want to do?
I like to think that if any breaking changes and Beehive stops running, someone will figure out a fix - I'm just now sure who that would be. Maybe Matt'll get his hands dirty again. Maybe BoughtonP will convert it to ColdFusion. That said, it's open source software, so if there's interest in doing something, there are ways and means.
Kenny |