TXP vs EE

hcgtv · 2006-07-19 02:35:57

aarplane,

So you run both TXP and EE, and you’ve decided to help us with the admin interface.

Interesting.

aarplane · 2006-07-19 02:51:24

hcgtv wrote:

So you run both TXP and EE, and you’ve decided to help us with the admin interface. Interesting.

hmmmnn?

Mary · 2006-07-19 08:29:49

Hardly a debate, but: ee vs. textpattern debate.

Looks like issue was taken with some of David’s comments.

While I can see the appeal of comparing software on technical merit, features, or whatnot, there is really only one metric that matters: Does it get the job done within any applicable constraints?

Yep. This thread was started to discuss what things each does well and not-so-well, not which one can “beat up” the other or have the most fanbois. i.e: when should I use Txp versus when should I use EE. :)

Syntax. This is just people being silly. Everything has a different syntax and, most of them, once you learn them they just feel natural. We went for something simple (tag, attributes, variables) but was distinguishable from HTML easily.

Not to me, and I’m not being silly. I prefer XML style tags because it’s not a new syntax to learn for designers, they already know (X)HTML. To the common user, yes, there’s no difference, you’d have to learn how either works.

I make no apologies for wanting dinner.

No one suggests that, at least, not “normal” people. ;)

Yes, the amount of plugins / hacks / mods required to do basic things in TextPattern (going from reading their forums, not from personal experience) is astounding.

Er. I run my sites with extremely few plugins (often less than 5). Makes me wonder what these mysterious “basic” things are.

Also on the owning code bit. I’ve done a little work here and there on Open Source projects and from my understanding of the majority of licenses just because the project is Open Source it doesn’t mean you retain any kind of ownership over the code. And just because the code is free it doesn’t mean that someone or some group doesn’t actually still own the code itself. In fact one of the Open Source advocates here is very adamant about this. You don’t own the code to FireFox when you download it. The Mozilla Foundation does. They are simply giving you permission to use and edit the code. Maybe its semantics but people who care greatly about Open Source seem to feel the distinction is important.

And pMachine doesn’t have any problem with me posting a hack to the EE files if others might find it useful. The fact that I can’t release my own version of EE doesn’t prevent me from making changes and sharing how to make those changes if I or others need them.

No one really cares who “owns” it in the strict sense, but what you’re allowed to do with it once you’ve obtained it. Typically, open source is very liberal on that front, but there are exceptions, of course.

The point is not “doom’s day” predictions about EE specifically, but about reality: you have to trust the creator(s). I’m sure people that trust the EE developers feel their trust is well-founded and will pay off.

You can’t always say that for just any given company though, and trust is earned over time. This is why some users will prefer to use open source over “just free” or “just a small fee”, because it requires no up-front trust, it’s a no-brainer. It gives, but expects nothing. For some people for some uses, that’s exactly what they’re after. Others couldn’t care less. Both are happy. :)

hcgtv · 2006-07-19 15:42:21

Mary wrote:

Er. I run my sites with extremely few plugins (often less than 5). Makes me wonder what these mysterious “basic” things are.

I think this is one of Textpattern’s strengths, you receive the basic set of features and then you can expand on it, if you so wish. I have 4 Textpattern sites and apart from mcw_templates to save off my templates and bas_lets_see_yours on my personal blog for the TxP blogmap, I haven’t seen the need for anything else.

Honestly, I’d take it a step further, removing more things from the core, like commenting or anything else that can be made into a plugin or extension module. This way you can use TxP for a site where you just want to put up a few static pages but you like the idea of being able to update it from anywhere.

At the end of the day it’s about putting out content, just give me a textarea with textile or markdown, I’ll let Firefox check my spelling and I’m a happy camper.

Ray · 2006-07-19 15:42:57

I still frequent these forums on a regular basis (in the background) but don’t post much any more (less noise ; )). Almost didn’t make this post but… I’m gonna anyway.

This thread has the potential of becoming embarrassing. How about dropping the personal feelings and just stick with the facts (as you know them). Who cares what other people say outside your house.

guiguibonbon · 2006-07-19 19:15:50

hcgtv wrote:

Honestly, I’d take it a step further, removing more things from the core, like commenting or anything else that can be made into a plugin or extension module.

I like that idea a lot. It might actually go even further : let plugins manage images, files, tag builders, clean urls, textile and other text-editors, etc. It would ease the developpement a lot. And speeden it quite a bit too. The only problem being backwards-compatibility, I presume. Couldn’t we vote on this? Because I presume (though it’s a bit sad considering all the work done recently) that it wouldn’t be too hard to implement (edit: I meant in crockery of course).

Last edited by guiguibonbon (2006-07-19 19:55:01)

Mary · 2006-07-19 21:31:33

This thread has the potential of becoming embarrassing. How about dropping the personal feelings and just stick with the facts (as you know them). Who cares what other people say outside your house.

Eh, what? It’s rude to ignore people invited to a discussion. Otherwise you’re just talking to yourself.

Ray · 2006-07-19 23:23:59

Mary wrote:

Eh, what? It’s rude to ignore people invited to a discussion. Otherwise you’re just talking to yourself.

Not talking about ignoring people Mary.

NyteOwl · 2006-07-19 23:41:36

Actually I was looking to use another product but the huge level of modularity (virtually anything you wanted to do besides post a static page required installation of some module/plugin or other) turned me right off. Modular extensibility is a good thing, but not when taken to extremes. The problem with relying on modules/plugins for everything but minimal core function leaves you open to version skew and it’s related problems.

I must confess to being a relative beginner with TxP. I have only built one site with it (ve1cbf.ca) and am in the process of redesigning another. The only plugins I have used in the first are zem_contact (the original with a couple of hacks), zem_nth, and zem_PR. The second uses the same three plus zem_article_info. While nth and article_info are surpufluous to the effective function of the site, IMHO the functionality of contact and PR should have been part of the core features.

Anyway this is wandering off topic. I have tried EE Core and my biggest compaint was the unweildiness (to me) of the admin interface, and some of the documentation seemed terribly convoluted (or the concept they were explaining was – I’m not sure). TxP has a wonderfully simple admin interface but suffers, not from convoluted documentation but, until the past 6 months rather unorganized documentation. TextBook is a great improvement and these forums are invaluable. The EE forums are informative and helpful but do not seem to have quite the same level of “community” as here. Just a difference in personality, like people :)

Shaliza · 2006-07-22 03:11:27

The last three & first one are why I don’t use EE. It may be good for some people, but it wasn’t for my site. TXP does exactly what I wanted in the first place. No hassle or anything.

I’ve been using TXP since December/January & I’ve come across even more publishing scripts & they didn’t faze me.

Textpattern CMS

Textpattern CMS support forum

#37 2006-07-19 02:35:57

Re: TXP vs EE

#38 2006-07-19 02:51:24

Re: TXP vs EE

#39 2006-07-19 08:29:49

Re: TXP vs EE

#40 2006-07-19 15:42:21

Re: TXP vs EE

#41 2006-07-19 15:42:57

Re: TXP vs EE

#42 2006-07-19 19:15:50

Re: TXP vs EE

#43 2006-07-19 21:31:33

Re: TXP vs EE

#44 2006-07-19 23:23:59

Re: TXP vs EE

#45 2006-07-19 23:41:36

Re: TXP vs EE

#46 2006-07-22 03:11:27

Re: TXP vs EE

Board footer