Wait until they are out there, for the general public to use and judge. Then we all will see which is best, in the view of those who count: The users.
Re: Arantor back on SMF Team!
« Reply #30, on October 20th, 2013, 01:29 PM »
Wait until they are out there, for the general public to use and judge. Then we all will see which is best, in the view of those who count: The users.
You're more than welcome to fork and fix it :cool:
Hm, let me summarize: Arantor doesn't want to be the bad guy, so he decides to merge Wedge's "top features" into SMF, leaving some more "boo-fucking-hoo everyone hates me" wherever he can.
Good and consistent decision, pal.
I wonder what they had to do to make him work with them again. Granting unlimited freedom regarding any changes he wants to commit? Not that SMF wasn't dead enough already...
Popcorn, anyone?
look at his 05be2b92 revert
Other than that, I couldn't care less about what he has to bring to SMF. Good for them. But any code/ideas he takes from Wedge? Shame on him.
I still have not learned much on using it...LOL.
SMF, Elk and others are having theirs open, so people can see what is going on, and even test it out, via download from GitHub. That's what I meant by showing all, and by the larger community.
I mean heck, I've not even been able to look into the admin section of Wedge, so I can't even give much opinion on how it is.
Granted, as a user, I do see a lot that I like. If I did not, I would not have signed up here. Just because I'm a team member for SMF, does not mean that I have to use just that for all my sites.
I do have plans on trying Wedge with at least one of my sites. :)
1. | In fact, even GH's Windows application only shows the most basic things you can do with it; it's even simpler than TortoiseSVN in concept, so that goes to show, you don't HAVE to know everything about it... Thankfully. |
I wish I could!Quote from Nao on October 20th, 2013, 04:26 PM look at his 05be2b92 revert
Basically, it's "his own work" he contributes (again). I don't know if the Wedge license allows that though. :whistle:
I'm not saying that they all should share everything...
Just the things that may improve security for all, and some of the things that they all may be able to work on jointly, for the betterment of all.
SMF and the SMF forks are together, against all the rest, and sharing some things would be a good idea, in my opinion.
To make things short... The Wedge license doesn't allow it, no.
SMF may not be as fully featured as Wedge, but there's absolutely no way the code is better in Wedge. The amount of stuff rammed through the buffer at the end of page processing is shocking.
So you actually put shocking code into Wedge until it was too much and now you complain about it being too much? :whistle:
$smcFunc['query']('', 'SELECT * FROM {db_prefix}table');
wesql::query('SELECT * FROM {db_prefix}table');