I'm not entirely sure if I should feel happy about this. Probably less, though.
Re: Not So Mixed Signals
« Reply #30, on September 6th, 2013, 04:49 AM »
Also, telling someone who is considered to be depressed to just snap out of it is actually making it worse, along with all the comments about how I should essentially just man up.
Control versus contribution
Ironically, had Nao outlined to me on day one that this is how he wanted to work, I could probably have made that work. It was always stated that we were equals and yet we never really acted as equals.
I think the reason it worked flawlessly over the first couple of years is that (1) we still thought we had time to release Wedge so we just set aside a lot of the uneasy discussions we might have wanted to have, and (2) we were both involved at the same level, and neither of us had yet to experience a breakdown or anything related. Life happens.
Two people may be a crowd when it comes to a decision, but saying that one has to take the lead is not right. One took the lead in the absence of decision and just carried on with what he wanted to do despite the opposition.
And was that a bad thing to do...? Realistically, I mean..?
On where we came from, and maybe where we're going
Nao always made it clear that he wanted to push towards what Noisen is, essentially a form of localised social network
Technically, for those who don't know of the story... My idea of my contributions to Wedge was to integrate into it every single thing I'd developed on SMF for myself, i.e. Aeva Media and Noisen features. AeMe was easy, it was just a mod, but I never really got around to overhauling it, and that's a mistake I made. Noisen was more complicated. I made a huge (800KB..?) patch file of all differences between vanilla SMF and Noisen, and then proceeded to apply all of these features, one by one, to Wedge. It turned out, halfway into it, that many features couldn't be integrated as such, either because the codebase had already become too different, or because the code became unneeded because of internal improvements, or simply because it was a lot to do. The most important thing to me was integrating the privacy system, and I think I did all of it over the years... I mean, it was mainly about adding some code to all MySQL queries involving the topic table, but it was still a bitch. Over the years, I moved away from my desire to adapt Noisen into Wedge, but I still have plans to use Wedge over there, because Wedge rocks, and I'm willing to lose all of the Noisen features I didn't integrate into it, at least for a time.
The saddest part is that even when I disentangle myself, baring myself in a way I just do NOT do normally, being more honest with myself than I have been for a very long time, too many people still don't get it.
I get it... And I'm okay that you're leaving. Simply, I don't think you're leaving for the right reason.
Pick a CLA, if the terms aren't unpleasant, I'll sign it. E.g. the Apache CLA will be fine.
The reality is that I'm just not the same as you, and as I've said before I can't live up to your standards.
If you remove themes, 1) it absolutely prevents themers adding their own language strings
and 2) it absolutely prevents replacing templates on a large scale. Sure, there are some nods made in the other direction with <we:cat> and <we:title> but a themer simply isn't going to be able to go to town and really change up the look.
I see from the changelog you've made some more strides, but let me ask you this. You've seen Crossing Overland, with the menu down the side, with the other stuff that's in the theme. The ONLY thing managed by the sources code is the extra subtitle on the menu, everything else is in a custom theme.
Can that be recreated with just skins?
Answer: no because the JavaScript would have to be reworked to make the menu work differently.
That's the point I was getting at: killing off themes and pushing it to skins means a designer can only change the markup they're given, they can't really go to town with new markup which is a considerable hit on flexibility.
We did some good stuff. And I'd love to see some good stuff from this project in the future because you don't need me. You never needed me, not really.
You have the power to take Wedge in any direction you choose now, whatever works for where you want to take it, and for those who will undoubtedly follow you.
I'm free to go away and think about what I want to say, and how to say it. I've read this post half a dozen times this evening before I replied to it.
Firstly, accept the notion that you're going in a direction where you're loading stuff only on demand. In my world, primarily a CMS, I don't need a censor all the time. Inside the forum, perhaps, but not more generally. So I can hive it off somewhere else. And then only load it when I actually need it.
Keeping the files a bit smaller, then, is a major difference. Especially when you typically already consume 10MB per page load just in general approach.
This last year we've both had stuff going on that has made it hard to focus. I'm sorry I wasn't more forthcoming either, because this might have ended a little differently otherwise.
Eh, I don't know that they'll love it. They'll deal with it, simple as that.
Firstly, there is evidence to suggest that themers don't like having to deal with specific CSS variations for a given system due to preparsers - like XenForo discovered - but I think Wess is strong enough that it'll overcome the issues.
I was against the idea for reasons I'd explained multiple times, including earlier in this post. I'm skeptical of the claim that you can do 'pretty much everything skin-less themes could do' because there are an awful lot of things that just aren't covered in that.
See, that's the problem... I don't like face to face meetings. I much, much prefer online communication. I'm rather inept socially in person,
because my brain thinks faster than my mouth and I trip up on words so much.
Heck, I'm not even on Skype.
That said, I think it might be nice to let this stuff go, and in a while when it's all settled and we're doing what we're doing, to just meet up, shoot the breeze. Not as would-be/wannabe/former partners in crime, but two geeks that are just friends, you know?
Seriously though, there has been a mass defection to Facebook and Google+ over the last few years. All the forum packages are in decline, I've even heard from phpBB and MyBB folks that are seeing a decline in users for this very reason.
For a lot of discussions, a group or page on Facebook will be enough, especially in response to something like a band or similar because they'll already have a presence on FB and don't really need to open up a forum for anything else.
I can register on a forum and be effectively anonymous should I choose. It's not a single overarching thing where my family, my friends, my professional acquaintances and whatnot all get smushed together unlike Facebook.
Getting back on track though, more and more requests on sm.org are about bridging to WP or using it alongside an existing site, rather than it being the site as a whole.
As for people coming back to forums, I've been saying since 2011 that there's going to be a shift back towards forums as people start to reclaim their privacy. While I didn't predict PRISM, since 2011 I was speculating 2014 as the time when forums would reclaim some of the lost ground. While the PRISM stuff has died down a touch now, there is a swing back towards forums. I'm just expecting it more en masse next year.
Oh, I've never doubted that the software needs to exist. I'm just challenging the notion that it has to be the primary focus of the software.
I'm asserting the notion that a piece of software that allows you to run a website should allow for a forum but not be a forum with some other stuff integrated in to it.
The point where I suggested it, I forget where it was but it was on this site, and you were very hostile to the idea of having a CMS with 'the best forum plugin' and would much rather have the forum as the core and content stuff around it. At least, that's how it seemed, and after that I just dropped the idea.
A blog is a very different beast from a forum. A forum is essentially a democratic concept, where anyone in the community can have a say and speak their mind, whereas a blog only allows for the privileged few to speak their mind and let everyone else comment. True, a forum board can be used as a blog, and that becomes mostly a matter of permissions and UI juggling, but it's a very different beast to market and to work with as a whole.
Messages are what a forum is *made* of. It's not what a forum is *about*. There are other components to a community, where messages don't necessarily make a huge difference. I look at the site I use to discuss development; the shoutbox has nearly 400,000 entries, while the forum has barely 3,000 posts, mostly which just summarise and formalise what the shoutbox had in it at the time.
The main reason I didn't want to run a release at this stage was simply because of how much stuff I felt was unfinished - not 'waiting for perfect'. The permissions stuff is still a mess.
The media area still needs a serious (IMHO) overhaul,
and to me that seemed like it needed to be done before 1.0 but I didn't know what to do with it. I just knew I didn't like it.
It was a good idea in a lot of ways, but I'm sure it would have failed for the reason above, we would have tried to keep things in step enough to be able to reuse each other's work and we would both have been hamstrung by it in time.
It would have gone one of two ways, either it would have meant a complete separation much as we're at now, or it would have ended up diverging and converging after a while and a ton of work to bring them back under one roof (which would invariably have lead to a lot of rewrites)
Oh, I know that. At least, I think I know that. But my self esteem doesn't really care *why* it's being pulled apart, simply that the end result is a B-minus grade.
I couldn't really find a better analogy, and I did want to make some kind of a meta reference, knowing one of the largest topics in the private board. It made me smile a little to make a private reference.
Oh, it required team work, but I didn't entirely feel like I was doing good at being in a team.
But therein lies the problem. Committing something subpar was wrong
and trying to commit perfection meant I committed nothing while trying to make it perfect. My best just isn't the same level as yours, ultimately.
To a point. Certainly when working alone I don't have the feelings of inadequacy. I can just enjoy working on code for its own sake and it doesn't matter if I don't commit it, and it doesn't matter if I don't finish it and it doesn't matter if I abandon it.
Let me show you something. This wasn't public knowledge. Some months ago I made a mod of some of the anti spam stuff in Wedge and released it to sm.org.
Interestingly the commit log from 21/4 (r2066) does actually mention that I was AWOL and had been for a day or so at least... This would have been in the middle of the thousands of lines of warning system rewrite that as I tried to tell people was close to giving me a breakdown all on its own.
That comment wasn't actually directed at you, but everyone else who seems to say that I should just man up and accept that this is how it should be.
It is slightly ironic that Wedge itself was founded on the notion that we shouldn't just accept how things are being on the wrong end of a team relationship that wasn't working, but that's what I'm being asked to accept 'for the good of the project'.
The last few days have been very interesting. There are people that believe I should go and be lead developer for SMF in the hopes of rescuing it but I don't really see that working for much the same reasons, and I feel bad about working on my own project in light of the comments made here, but I still love the idea of doing different things with the forum and CMS concept. I guess I'll just have to bend over and accept something in the end :(
One issue that has cropped-up very recently is that of restricting the customization of Wedge's look and feel. Nao has designed some very attractive themes but - and here I agree with Pete - the only major difference between two sites running Wedge may be the colours employed and that would be a Big Mistake, in my view. It could well be, for example, that a Forum owner doesn't want the standard sidebar to appear in "Message View" and only on the "Board View" ('Home' Page) - that would certainly be my personal preference FWIW.
I truly hope that he and Nao can come to some understanding which would allow Pete to continue participating in an advisory role - if nothing else. And if he does, Nao, I also hope you will listen to him and pay heed to his advice!
As for the gentleman who suggested that Pete should "snap out of it" and "man up", I have nothing but contempt for those remarks and I suggest that you, sir, show some humility and compassion for your fellow man.
Guess I'll have to reply this, at some point...
Sure, why not. But as the Apache CLA only applies to future contributions, I suppose you'll have to pre-date it..?
But my standards are mine, and only apply to myself. What you should say is, you can't live with the idea that I'm modifying your code. Except that sometimes I have to (oversights, bugs...), and other times... Well, it's just cosmetic. What should you be proud of? How you indent your code, or how it does something awesome or innovative..?Quote The reality is that I'm just not the same as you, and as I've said before I can't live up to your standards.
The skins folder contains your CSS and PHP stuff, and in your PHP code, you can simply declare a loadLanguage()...
It may not be super-practical, but it's no more unusable than the SMF way, I'd say.
And, knowing myself-- I'll probably even add a setting allowing for skins to load some language files automatically on every page. I already have a <language> setting IIRC (determining what languages the skin accounts for in the CSS files), so I'll just have to add a new one like <loadLanguage>, or something. As long as it's in beta, I can still change that kind of thing, and update all skin files manually...
If it's absolutely needed, then they'll tell me what I should change into a macro.Quote and 2) it absolutely prevents replacing templates on a large scale. Sure, there are some nods made in the other direction with <we:cat> and <we:title> but a themer simply isn't going to be able to go to town and really change up the look.
If it's not, then it's unlikely they'll simply update all template files for the sake of updating all template files.
Can't see why not..?Quote I see from the changelog you've made some more strides, but let me ask you this. You've seen Crossing Overland, with the menu down the side, with the other stuff that's in the theme. The ONLY thing managed by the sources code is the extra subtitle on the menu, everything else is in a custom theme.
Can that be recreated with just skins?
And here, I can't see what JS is needed exactly to make it work. I don't see any JS at hand here...Quote Answer: no because the JavaScript would have to be reworked to make the menu work differently.
And even then-- <script include="mycustomskin">, and you're done... (??)
If someone needs an object method to be rewritable, I can declare it outside the scope, so that it can be redefined/overloaded/prototyped.
MacrosQuote That's the point I was getting at: killing off themes and pushing it to skins means a designer can only change the markup they're given, they can't really go to town with new markup which is a considerable hit on flexibility.
Custom JS
Custom PHP
Custom CSS
Final HTML raw replacement
Dunno what can be done with themes, that skins could not do.
Of course, it's another way of handling things. And it needs documenting. That's where skins are weak. There's a basic documentation in Warm/skin.xml (the only thing I actually really worked on documenting, unlike Wess!), but it could be better, I suppose. I'll improve it as questions come and go.
I needed your expertise on many domains that I'm very weak at (database, security, UI, JS, and so on -- and yes, I got a bit better at UI, and I quickly realized I wasn't as bad at JS as I feared), and quite simply, I needed your enthusiasm. Two people is better than one. Oh, just a simple example... These days, Milady and I try to jog at least once a week, sometimes twice a week. We started slow with 12mn rounds, and now we're at 30mn rounds. We're still bad at this, but we're still doing it, because what matters is that we try. Milady told me today, after our jogging session, that she enjoyed running with me, because she did 45mn sessions many years ago, and stopped after a year because she was fucking bored. I told her, "you need me because you feel better when you're so tired and you see that I'm in an even worse shape; and you need me because you want to encourage me to keep you with you when you're feeling better." She agreed with that entirely. Sometimes, being two just means that when someone is not at their best, they can count on someone else to fill up their job, and when they're at their best, they're happy that someone is encouraging them.
Sure. Removing themes would be a bold move, one in the likes of your own past bold moves, so I guess it's like the name change-- a way to make it clear it's "mine" from now on. However, all I want, at this point, is to finish the dozen or so features I want to finish (better privacy settings, better UI for blogs, etc.), and then release it to the world. I think that's what's going to make it clear that it's mine: I've always been willing to release it, because I am confident people will love it, as flawed as it is. ;)
Ah, well, I tend to reply as I'm reading. I didn't read this post until now (I did read your previous long post entirely before replying, but that's more an exception), because I will usually be discouraged to reply after I've read. "Too many things to say, will take me hours to reply..."
So, I guess my posts tend to be seen as hot-headed, more spontaneous, unlike yours. Figures.
Okay, so, the censor code... It's less than 5KB, including all of the fancy scramble stuff. Or just 1.2KB for the core function. I don't see autoloading it as being very helpful for performance...? Heck, at worst I could simply have it in a Subs-Censor.php file, and loadSource it from within Subs-BBC if needed...
But it certainly doesn't make a project more manageable... Functions should be categorized by themes, not by size. I'd rather maintain a 100KB file for some Aeva feature, than have to deal with ten 10KB files with the same code, because every time I want to make a more global change, I have to search all of these files for relevant code, when in a single file, I can just do a quick search... Things like that.
Look, the best example is skin CSS... Originally, I only had suffixes. Got plenty of files for each browser or action or whatever. Then I added @if support. Suddenly I removed most of those extra files, because it was much easier to maintain similarly themed CSS in the same file, rather than in multiple index.ie6.css-whatever files. Made my life easier...
Better than waiting until 2015 or 2016 for a release you'd finally deem suitable.Quote Eh, I don't know that they'll love it. They'll deal with it, simple as that.
Dunno. I guess I can be convinced to switch to an all-bracket version of Wess by default (in index files etc), if people feel better about not having to deal with indentation, but I think it'd be a loss. One of the main advantages, though, would be the fact that Notepad2 would be better at providing syntax highlighting for it... :PQuote from Arantor on September 6th, 2013, 02:20 AM Firstly, there is evidence to suggest that themers don't like having to deal with specific CSS variations for a given system due to preparsers - like XenForo discovered - but I think Wess is strong enough that it'll overcome the issues.
Well, for now it's not removed; but I just have one thing to add: in the three years we worked on Wedge, none of us ever tried to make a non-default theme, even just to 'see' if it would work... I made so many changes to the internals, I'm not sure it'd work at all; it might be fixable and everything, but because my focus has been on making sure anyone can make a very minimal pseudo-theme (a skin) with just color changes or whatever with only a text editor and a FTP client (no admin manipulation, no database handling or anything), I'm hoping that once they get the feel of it, they'll want to add more features, which they can do while remaining in the same environment, as opposed to having to go through theme handling, which is more complicated, and more importantly, forces you to update your templates as Wedge or SMF is being updated.Quote I was against the idea for reasons I'd explained multiple times, including earlier in this post. I'm skeptical of the claim that you can do 'pretty much everything skin-less themes could do' because there are an awful lot of things that just aren't covered in that.
(If the theme system is removed, I'll probably be even more aggressive in splitting important templates into more functions and macros.)
I don't have the feeling that Louis had a problem with that, since he invited you for a long road trip together, one year after meeting you...Quote See, that's the problem... I don't like face to face meetings. I much, much prefer online communication. I'm rather inept socially in person,
And as a French speaking English like a Spanish cow (French expression :P), you don't think I would trip up on words as much as you do..? :PQuote because my brain thinks faster than my mouth and I trip up on words so much.
Well, it never was about Wedge anyway. It was about putting a real person in front of the online contact whom I've been talking to for all these years. What did SMF call that..? A meeting of the minds...Quote That said, I think it might be nice to let this stuff go, and in a while when it's all settled and we're doing what we're doing, to just meet up, shoot the breeze. Not as would-be/wannabe/former partners in crime, but two geeks that are just friends, you know?
Anyway, I might be coming back to London within the next few months; nothing set in stone, but my girlfriend discussed the possibility of staying at her brother's over there, as he's expecting a new kid soon.
It's not about the number of users (you realize we'd have been thrilled to even have 1% of SMF's current user base, don't you..?), it's about filling a void, and making life better for at least one person. A success story, if you will, case by case, one at a time. I may have sold thousands of copies of my game, but what really pushed me to continue working on it at the time was these little stories where people were telling me they were successfully using KMJ as a tool for their physiotherapy. It happened several times, I have no idea why. I even once had an hospital ask me for a group order of copies for their reeducation unit; I told them they didn't have to buy them, of course.Quote Seriously though, there has been a mass defection to Facebook and Google+ over the last few years. All the forum packages are in decline, I've even heard from phpBB and MyBB folks that are seeing a decline in users for this very reason.
That was a factor for me, more than the salary that came out of it.
Absolutely... And it's also much easier to set up than a forum, but once your community outgrows the facilities offered by Facebook, it happens from time to time that you'll want to go serious with it. In fact, to me, Facebook didn't replace forums... It simply replaced mailing lists (partly), and free hosted forums that sucked so much. You know, these slow websites that were filled with spam and messages from people asking 'when are you going to use a real forum anyway...?', things like that.
Absolutely, that's one of the important points. There are some forums where I'm registered, where I wouldn't want to tell people my real name.
Not that you CAN'T hide your identity on FB. One of my best friends has 'Yeo Wren' as his FB account, and that's actually his nickname. He never gave away his real name on FB, even though he's very active on it, and all of his RL friends are linked to his account. It's not that he's hiding his name... He just doesn't like revealing himself to anyone he doesn't know.
That's why I still have in my to-do list this item that says, lemme find it, "per-item privacy in profiles, e.g. real name". That means applying the usual privacy flag (contacts, members...) to individual entries in your profile area. For instance, you could put your real name in it, but only have it available for your conatcts. Or your e-mail address, etc.
Oh, that... Pete, I've always, always been against board index as the homepage for a forum. You'll remember I did rewrite the homepage early in the Wedge timespan, and even allowed for the ability to push a blog homepage as the main homepage of the forum. That is, to me, it's ALREADY a CMS per-se, although it's not really advertised as such.
(Possibly because I don't think saying "CMS" is gonna help make Wedge popular. If you'll look at cmsmatrix.org, they have over 1200 CMS systems listed... And they're almost all dead. To most people, CMS = what?! (and to them, WordPress is just a blog platform, only web developers/designers would really think of calling it a CMS); to a minority of them, CMS = WordPress (.net and Web Designer Magazine readerships :lol:); and to some of them, CMS = Drupal/Joomla/ExpressionEngine/SilverStripe/whatever CMS had a relative amount of popularity at one point or another. Doing a great CMS won't really help, as there are so many CMSes around already. What is going to help, though, is getting at least ONE great/popular website to use Wedge, and then popularize it by actually keeping using it. Again: one by one...
I didn't even know what PRISM was... I googled it, and was surprised by the amount of detail... So, that's what the Snowden story was about, uh..? Interesting. The media in France, I don't remember them talking about that at all... They only covered Snowden's escape, and I followed that a bit because it reminded of that amusing movie I saw a few months ago, Terminal.Quote As for people coming back to forums, I've been saying since 2011 that there's going to be a shift back towards forums as people start to reclaim their privacy. While I didn't predict PRISM, since 2011 I was speculating 2014 as the time when forums would reclaim some of the lost ground. While the PRISM stuff has died down a touch now, there is a swing back towards forums. I'm just expecting it more en masse next year.
Again and again: to me, it's a CMS all right, but CMS meaning "community management system", not "content management system". SMF, to me, like other good forum systems, excel in making users feel that they can set up a real identity on a website, and manage everything from one place. Call it a social network or whatever you like, but to me, it's just what the Web is about... Tim Berners-Lee himself said that the Web had always been about connecting people. Facebook didn't invent it, SMF didn't invent it.Quote Oh, I've never doubted that the software needs to exist. I'm just challenging the notion that it has to be the primary focus of the software.
And that's just great for them. That still makes it a forum... They just don't use the messages table as much as their equivalent thoughts table, I'd say... ;)Quote Messages are what a forum is *made* of. It's not what a forum is *about*. There are other components to a community, where messages don't necessarily make a huge difference. I look at the site I use to discuss development; the shoutbox has nearly 400,000 entries, while the forum has barely 3,000 posts, mostly which just summarise and formalise what the shoutbox had in it at the time.
It will be fixed over time.Quote The main reason I didn't want to run a release at this stage was simply because of how much stuff I felt was unfinished - not 'waiting for perfect'. The permissions stuff is still a mess.It will be fixed over time.Quote The media area still needs a serious (IMHO) overhaul,
I understand that you woudn't like it. Heck, I'd be lying if I said I liked it. But the reality isn't that. The reality is, there are dozen of people who would be thrilled to use Wedge right now, and adopt it, even if it's not ready yet.Quote and to me that seemed like it needed to be done before 1.0 but I didn't know what to do with it. I just knew I didn't like it.
I'm pretty sure I'd have been the 'weaker one' in that relationship, i.e. adopting more of your changes than you'd adopt mine, because I'd really, really strive to keep repos in sync as much as possible, and globally, even though I may have sent 'mixed signals' myself, I'm really happy with most of the changes you made. Even if they destabilize me, overall I know that they're for the better, and they're good for Wedge, for its future popularity. Software reviewers are gonna like the visuals, but they'll be absolutely thrilled by the admin area, I think.Quote It was a good idea in a lot of ways, but I'm sure it would have failed for the reason above, we would have tried to keep things in step enough to be able to reuse each other's work and we would both have been hamstrung by it in time.
Well, I wouldn't see any of us as doing that merge; maybe by someone else if both of our projects had collapsed, but that may simply have been seen as a 'fork from multiple sources', I don't know...Quote It would have gone one of two ways, either it would have meant a complete separation much as we're at now, or it would have ended up diverging and converging after a while and a ton of work to bring them back under one roof (which would invariably have lead to a lot of rewrites)
The idea was simply to find a solution to the issue where we were drifting apart, and to allow you to focus on your other software projects, while giving me free reign to make decisions when you wouldn't be available for advice, that's pretty much it...
Have you ever seen how many times I rewrote so many parts of my code...?Quote and trying to commit perfection meant I committed nothing while trying to make it perfect. My best just isn't the same level as yours, ultimately.
Went to see it, and indeed, there it was in all its glory... Because it's available for anyone to download, yes it's public knowledge. Not popular knowledge, but it's there. There's a mod out there at sm.org that publicly accuses me of wrongdoings.Quote Let me show you something. This wasn't public knowledge. Some months ago I made a mod of some of the anti spam stuff in Wedge and released it to sm.org.
I'm above that, but... Well, I prefer when people who have something serious to tell you, do it in front of me, rather than vent on the side.
If you already had a problem with me back in April, then you should have told me, because there's no reason I wouldn't have worked on this on my side, or at least talked you into understanding what I'm doing has never been against you, rather I was just trying to contribute.
Anyone would have a breakdown over such a comprehensive rewrite, really...!Quote Interestingly the commit log from 21/4 (r2066) does actually mention that I was AWOL and had been for a day or so at least... This would have been in the middle of the thousands of lines of warning system rewrite that as I tried to tell people was close to giving me a breakdown all on its own.
Why do you think I never took it upon myself to do a complete overhaul of AeMe... :P
Well... I know it won't do me any favours as I've been doing my best to stay as neutral as possible in this, and to be understanding of your position and the difficulties you experienced in the last three years; but to be brutally honest Pete, yet, a part of me also screams 'man up!', and considers you a bit of a drama queen.Quote That comment wasn't actually directed at you, but everyone else who seems to say that I should just man up and accept that this is how it should be.
We got together because we were both branded drama queens by the SMF team after all, and they weren't completely wrong. I've just learnt to be more philosophical about these things in the last year or so. I haven't been in a flame war for something like two years. The trick is losing interest. Looking back, I think it was a drug, coming as much from a sense of disbelief at the injustices around me (for some reason, any injustice around *me* seemed to be even worse), as a simple need for attention. As hard as it is to admit it, I did many things out of a need for attention, because of low self-esteem and a need to prove myself that I was a worthy guy, not by self-confidence, but by looking back and thinking, "okay, I made a few nice things". I'm sure today's youth are the same.
Being happy with what you did in the past, is better for your karma than some irrational idea of being important. So, yes, everyone was being childish at that point, and I should have seen that. It wouldn't even have stopped me from starting Wedge, actually. Just... In a different state of mind, I guess.
I just think, you should embrace our differences. I can accept that you'd leave the project over not being able to accept my quirks, such as these compulsive modifications on your code. But I don't think you should feel betrayed by me, or anything.
You should accept that I'm different. I accept that you're different, and I accept that it doesn't work for you, in the end. Just don't turn this into drama.
but you can always come back and keep contributing to it. It's your decision, in the end, whether you contribute or not.
I see you're also trying to contribute to Elk, at least trying to convince them to adopt some of your Wedge changes. I just have to say-- make up your mind already! :PQuote The last few days have been very interesting. There are people that believe I should go and be lead developer for SMF in the hopes of rescuing it but I don't really see that working for much the same reasons, and I feel bad about working on my own project in light of the comments made here, but I still love the idea of doing different things with the forum and CMS concept. I guess I'll just have to bend over and accept something in the end :(
Well, as I said... I think Pete teaming up with me is for the best, but it's tiring to go through so many periods during which I don't know what he's planning to do, so I'm sticking to my 'decision' of being the sole 'decision'-taker. (Which, ironically, was my first decision after Pete resigned from taking decisions alongside me... :^^;:)
But that shouldn't stop him from being passionate about Wedge itself and wanting to contribute more.
As for listening to him -- I'm the first to admit I'm not a very good listener. But not because I don't want to listen... It's mostly down to the fact that I get distracted easily. There's listening (= hearing something and processing it), and listening (= determining what's best based on several conflict advices). I'm not very good at the former, but I think I'm fair in saying I'm okay with the latter.
Well, it's a forum, so if someone wants to contribute, they can... I've seen so many forums that were ban-trigger-happy with people who shared ideas that weren't shared by the majority... It's usually an early sign of forum decay. I'm sure Pete can deal with this critic by himself. ;)
I'm not sure it does only apply to future contributions. SM are not so stupid that they extracted two CLAs from me that would only apply going forward.
Yes, because making themers have to jump through hoops is so much easier than them just adding a file called ThemeStrings.language.php to their theme/languages folder.
And with that attitude you're never going to get out of beta.
I saw, for example, that among the latest commits were an overhaul of Zoomedia... you're not even in beta and you're already rewriting something that most people have only seen a few times for something that I'd argue really isn't necessary - and given that you've said you're trying for a public release, I'd wonder why you're not spending time on the things that actually matter.
At this stage the question to ask: Is it free of known bugs?
The front page has the sidebar, as do the blog posts. But the minute you drop back to the forum or the trips pages, or indeed anything not actually in the blog posts, there's no sidebar. Now tell me how you'd do that in a skin.
So now you've finished the (second? third?) rewrite of Zoomedia, you'll be able to get right on those?
You can always tell when my posts are hot-headed and impetuous. But when it's important like this I try to give it a little time before I reply so that I've thought about it. The first draft of this reply was far more angry.
Right now, Wedge takes ~10MB of memory to build a page. My stripped down SMF 2.1 currently runs in the 4MB range for page building, and while it doesn't have a template system as powerful as Wedge's, when I've added Twig to it, it'll probably still consume less memory.
You and I both did search and replace across a hundred files at a time. What's the difference between that and doing it on a smaller scale?
I'd argue in front of anyone who cares to read the commit log that I'm not the one with a problem with quality.
The problem is I know only too well what happened at MOTM - much coding was done. It would end up being a coding session and I'm not sure that would work for us.
That might work.Quote from Nao on September 13th, 2013, 10:39 AM Anyway, I might be coming back to London within the next few months; nothing set in stone, but my girlfriend discussed the possibility of staying at her brother's over there, as he's expecting a new kid soon.
It's a funny old world... I discovered that SMF and phpBB are working together of sorts these days in an attempt to try to bolster the forum market, amongst other things.
Yes, it would be nice to enhance the world one person at a time but I stopped feeling like Wedge was going to do that.
To a point, sure. To a point it has supplanted that. But that means that by and large only established forums are the ones that are using forum software. Very few sites are starting and have any real modicum of success with pure forums. Taking it out of the forum context is the only real way to make it work.
And admins aren't going to notice or care. That might as well not be a feature.
Seriously, admins today do NOT do direct DB edits or raw PHP unless they have to, simply because the world has moved on. Most websites today are not run by people who are fit for the title of webmaster.
For example, amusing story this week - amusing if you're a developer, perhaps - the single largest SMF site had a malfunction this week when its operator decided that there was a chunk of code in a file that 'I'm not using any more', until it was removed at which point large amounts of the site fell over because the function was still being called.
That's the sort of people who run websites, people who need to be protected from their own ignorance wherever possible.
No, WordPress is no longer a blog platform in the public perception. It's long been understood that it's a CMS, even if it isn't a very good one at that.
The reality is that you and I disagree on this and in the next few years we'll see who was right.
That and the autoloading stuff would probably in themselves require too many changes to keep in step. (For example last week I rewrote all the semantics of the scheduled tasks system to make each task its own class, which incidentally solves a problem that Wedge has at present as far as I remember in that a scheduled task added from a plugin never gets to load a language file to indicate its name and description)
The only downside as I see it is that I'm not using the more modern Wedge codebase, and need to redo a bunch of stuff (like the conversion to UTF-8 only) before I can start really going to town on what I want to do.
Sure I did. The point is that that wasn't the signals you were giving out. You expected every commit of mine to be a higher standard than yours and you rewrote them to suit yourself.
That's one of the things. It's out there, but most people never saw it - including the Customization Team because they would have said something about it.
Oh I understood but when I talked about doing an overhaul, you were pretty adamant that you should be the one to do it,
I don't disagree... and one of the comments of the time - about preserving the SMF legacy - is also just as true today as it was back then. The project is on the verge of collapse, to the point where several senior figures were very enthusiastic about the idea of my contributing code.
Unfortunately, a certain person publicly called another person a lying two-faced cow, and I realised how much they were running around stabbing each other in the back.
Unfortunately in my world I just see things I could have done better. I rarely spend time thinking about what I've achieved, it's always what I could have done better. I've been that way most of my life.
Here's the thing, you made it quite clear that a return on my part would be on your terms, not mine. That's not a situation I'm prepared to compromise on.
Since I apparently have to declare my plans to you: I'm not going to contribute to Wedge or SMF. I may share ideas with Elkarte. I am primarily working on C# and Unity and exploring my CMS ideas in my spare time with a project based on SMF 2.1 called Pyrapage.
From my perspective, the latter tends to end up being listening to the difference advices and then going with what you were going to do anyway.
I won't deny, I've been a little happier in recent days where the only person I'm really answerable to is myself.
Where I don't have to argue things, where I can just run with my instinct and not feel like I need to defend every decision I make,
Because not everyone knows about grepWin or other mass s&r tools, not everyone wants to deal with these..?Quote You and I both did search and replace across a hundred files at a time. What's the difference between that and doing it on a smaller scale?
because of this or that obscure setting in PHP or MySQL that makes the whole thing 12% slower than if I'd done it this way.
Haven't heard about that.Quote It's a funny old world... I discovered that SMF and phpBB are working together of sorts these days in an attempt to try to bolster the forum market, amongst other things.
If you say so.Quote No, WordPress is no longer a blog platform in the public perception. It's long been understood that it's a CMS, even if it isn't a very good one at that.
Well, I did talk with Bryan (who recently resigned) about using Wedge as a basis for SMF 3.0, but apparently the idea is a long way from making any sense, especially considering that it comes with a recommendation that SMF can only survive if the dev lead is also the project lead, so... Not realistic enough, I guess.
Well, then it's simply a feature that plugin authors won't be able to use, unless live627 (or you)steps upis recruited by me and offers to fix it.
Well, I did talk with Bryan (who recently resigned) about using Wedge as a basis for SMF 3.0,
might not fit SMF's coding standards
none of us ever tried to make a non-default theme, even just to 'see' if it would work
Most text editors have a good (and some have a mediocre) built-in S&R by now. I'm not sure if grepWin counts as an insider tool anymore.
They don't seem to do it too successfully either. SMF's market share decreases AFAICS.
The public perception is wrong. WordPress brings basic CMS features indeed, but it still focuses on simplifying setting up a blog. The public perception is driven by marketing people who never touched a single line of code, that's why the public perception is a perception of stupidity.
I'm not sure if using a fork as the base would work anyway, given that it's mostly unreviewed code (which might not fit SMF's coding standards) and I'm not convinced that SMF heads into a modern direction at all.
"Stepping up" implies the ability to ask to be promoted at any time at will, which doesn't work in closed "ivory tower" development projects, such as this.
Wedge won't become SMF 3 because it's not "just a forum". That, and mod compatibility is totally broken...
Oh... right....Quote none of us ever tried to make a non-default theme, even just to 'see' if it would work
Notepad++ may be popular (and I use it for many files), but I've never liked its search tool, it requires too many clicks anyway.
Go tell that to the web design community. Most of them are very techy, and still consider WP as a proper CMS tool, so... I dunno. I guess it's just a matter of what you think a CMS is, eh..?
I'm the ayatollah of SMF coding guidelines.
Ctrl+h and the Tab key should work. :whistle: