Personally, I feel this talk lacks insights. Here’s why.
- Similar systems already exist in the forms of Silverlight, Flash or Air. So the theory itself is nothing new, but the actual implementation is.
- How do they address accessibility?
- How do they make the content indexable?
- With no hierarchy (or a complex grid of hierarchies), how can information be managed effectively? Since our brand can’t cope with large amount of data cross referencing each other in this matter.
Unless they’re proposing to replace the whole current Internet data storage, indexing and searching systems (stares at Google) and its ecosystem, like the one from Microsoft’s research lab (I forgot the name of the project though, sorry).
I’m more interested to reading theses on the theory level, rather than seeing a bunch of fancy demo applications (with multi-touch sometimes), but that’s just me.
Here’s a rundown of what has happened, what is currently happening and what is going to happen.
Over the weekend, a fire surpression unit in the data centre went off during a regular fire test. It wasn’t our hosting provider’s fault.
All our servers were down for about 10 hours on the day the incident happened.
After the incident, our hosting provider began rebuilding disk arrays to replicate data. This has caused major IO lag across the board. The reason the site went up and down constantly, was because the web server couldn’t cope with the amount of traffic under heavy IO lag.
At one point our server load surged to 5000% (comparing to 50% in normal circumstances).
We’ve now made necessary adjustment to the server configuration to better cope with the load. However, because we are having ongoing IO issues, the site performance is degraded.
We are now in the process of evaluating new hosting environments. In the upcoming weeks we will start migrating our sites.
The sub-par level of support we received from our hosting provider post-incident is the major reason we are moving on.
There is good news though. We’ve been making some client side and server side optimisations to the Tuts sites, including use of one of the best CDN vendors Akamai (who is used by Microsoft, Apple and many other Fortune 500 companies). We will start rolling them out once our hosting issue is fully resolved.
Hope that clears things up a bit.
It was caused by a failed fire test in the data center. Some drives in our hosting provider’s SAN infrastructure are damaged (no data loss) so they’re replacing those drives.
Our primary servers are still in the process of recovering.
Keep an eye on the Nettuts Twitter account, I’ll post a tweet once the servers are back up.
The next marketplace will be selling souls. Be prepared.
There’s also an #Envato channel on freenode.
So the big question is: Can CodeIgniter hold a large website …
The short answer is, no.
Don’t get me wrong, CodeIgniter is a fantastic framework to get you up and running very quickly. However, a couple of ‘flaws’ make it very difficult to use for larger scale projects -
- Lack of DB object mapping (a.k.a Object Relational Mappers, or ORM ). CI’s so called Active Record classes are essentially query binders. It is a mis-use of the ActiveRecord pattern as seen in Ruby on Rails and other projects. There are 3rd party ORM solutions for CI, but that adds one more layer of uncertainty – what do you do if/when the library is no longer being maintained?
- Lack of OOP foundations. CodeIgniter was first released in 2006, shortly after Ruby on Rails became popular. The adoption of PHP5 back then was still not great, hence why frameworks like CakePHP all started as PHP4 /5 combo.
- Supporting PHP4 means the core framework cannot provide adequate error handling (via exception).
- The framework itself isn’t unit-tested, so you might bump into quite a few bugs: http://codeigniter.com/user_guide/changelog.html
I personally wouldn’t use CodeIgniter for anything other than a tiny project that doesn’t require much maintainance. For example, our Envato invoicing system is built on CodeIgniter.
By the way, I wrote a comparison review of CodeIgniter, Kohana and Yii a while ago: http://www.beyondcoding.com/2009/03/02/choosing-a-php-framework-round-2-yii-vs-kohana-vs-codeigniter/
And also this post over at Fsw forums: http://forum.freelanceswitch.com/topic.php?id=7134
If I had to choose a PHP framework for a large project, it’d be Yii. Yii’s model layer is much more robust (albeit more difficult to use) than Kohana’s.
Just my 2 cents worth of opinion. Hope that helps.
A tuts+ forum would be nice