LPH
Well-known member
This is quite a quandary: to develop my own bridge or continue working / tinkering on another. Which is appropriate, should I release my own bridge or support an existing bridge? What is your opinion?
Cons
The bridge I use is an amalgam of a paid script and my own work.
The paid script still works but can use some tweaks to be better.
I am a novice and coding takes time, with lots of trials and errors.
Supporting a script is time consuming.
I'd have to set up my own store.
Pros
A bridge is vital to my site.
Development is always just a local server box away.
I wantneed to get better with OOP.
I want to give back to the community.
XenWord is in alpha. It works.
It would take 100 plus of my hours to recode to ensure the code is unique and not someone else's work. Yes, I'm slow.
What do you think? Do I move forward with XenWord or continue supporting the current bridge? What is best for the community?
Cons
The bridge I use is an amalgam of a paid script and my own work.
The paid script still works but can use some tweaks to be better.
I am a novice and coding takes time, with lots of trials and errors.
Supporting a script is time consuming.
I'd have to set up my own store.
Pros
A bridge is vital to my site.
Development is always just a local server box away.
I want
I want to give back to the community.
XenWord is in alpha. It works.
It would take 100 plus of my hours to recode to ensure the code is unique and not someone else's work. Yes, I'm slow.
What do you think? Do I move forward with XenWord or continue supporting the current bridge? What is best for the community?
But on a serious note, its something that a lot of people will benefit from it.
