Re: [mh] Where next with MisterHouse

I don’t love Perl, but a re-implementation would suck way too much effort. Even re-implementing just Insteon would be quite a lot of effort and testing. My thought is to implement a UI in some other language/toolkit and then use MH as a backend. I’m not even complaining about IA7, it’s just that I don’t understand MH well enough to extend/customize/contribute to MH enough to my taste. 

Though I have worked with .NET, that would rather blow up the cross platform nature of MH. Cross platform is key. 


Sent from my iPhone

> On Jan 4, 2021, at 9:42 PM, Spencer Ryan <[email protected]> wrote:
> 
> 
> Maybe a userbase split isn't a bad thing. I think more people are turned off of the legacy aspect of MH than are drawn to it. How many new users move to the platform vs the X10 users who have been here 20 years? Yes, customizations would have to be redone, but at some point you have to acknowledge that it will be easier for most people in Python/.NET/Whatever than in a language that is dead for all useful purposes. 
> 
> I came to MH for the Insteon support, but the perl code with it's way of life, subpar web interface, among have left me wanting for something modern. 
> 
> 
> 
>> On Mon, Jan 4, 2021 at 9:16 PM Paul Onley <[email protected]> wrote:
>> With regard to the idea of a language change, While I do not possess the 
>> coding expertise to write a module to manage something like the new 
>> Tasmota or mqtt modules I do have a lot of perl code doing specific 
>> things tailored to my home that would likely be of no value to anyone 
>> else. I'm sure I'm not alone and if the mh project changed language then 
>> all that 'user' code that everyone has written for their particular 
>> needs would have to be redone also. In other words, every customization 
>> to every mh installation would also require a rewrite and if the user 
>> does not know the new language your base shrinks as they, like me, will 
>> stay with the 'last perl' mh effectively splitting your user base into 
>> two groups that don't speak the same language.
>> 
>> Paul
>> 
>> On 1/4/21 7:47 PM, Jeff Siddall via misterhouse-users wrote:
>> > I am mostly OK with using master, but I still think there is something 
>> > to be said for keeping major releases: if contributors know there is 
>> > desire to "release" a new stable version there is often a push to get 
>> > new code contributed, and the code that is contributed is definitely 
>> > tested more than random commits.  It also gives some basic indication 
>> > of project activity.  When I see a project with no stable releases I 
>> > am more likely to assume it is dead than go looking into git to see if 
>> > anything is really going on.
>> >
>> > It could also make support a little easier if someone is on the stable 
>> > release versus some master from who knows when.
>> >
>> > Those aren't strong opinions, just my $0.02.
>> >
>> > I do have stronger opinions on rewrites and will agree with Rick here 
>> > and say no.  I still have a few working X10 devices around -- some 
>> > from as far back as the 1980's.  I know what you are thinking: how can 
>> > X10 stuff from 30 years ago still work?  I don't have a good 
>> > explanation, but it does.  That's just an example to say I have a wide 
>> > range of technologies in use and simply wouldn't adopt some new home 
>> > automation thing that was missing some of them.  That's basically the 
>> > reason I am still using MH.  I think many others are in a similar 
>> > situation, making it impossible to keep everyone happy without 
>> > rebuilding basically everything from scratch, and I just can't imagine 
>> > anyone would be that committed to the idea.
>> >
>> > What I could see working is a next generation python (my preference 
>> > for the "new" language) version of MH that could talk to a the legacy 
>> > perl MH as a proxy.  That way you could [potentially] keep the working 
>> > legacy stuff if you needed it while still developing new code in a new 
>> > environment.
>> >
>> > Regarding bi-directional devices, the Tasmota stuff I wrote recently 
>> > does this now, as does the MySensors stuff I wrote a while back.  I 
>> > don't see that being a limiting factor but maybe I am missing something.
>> >
>> > Jeff
>> >
>> >
>> >
>> > ________________________________________________________
>> > To unsubscribe from this list, go to: 
>> > https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>> >
>> 
>> 
>> 
>> ________________________________________________________
>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>> 
> ________________________________________________________
> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>

________________________________________________________
To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users