CI Reactor 2.0.2 sparks and fire_log

[eluser]talkingnews[/eluser]
[quote author="osci" date="1309527813"]There is actually a user contribution that is up to date here[/quote]

Ah, now we're cooking! That got me back on track. So, I have to agree with the person below the video at learn-codeigniter who said

"codeigniter.com should take these tutorials to their page, they have old ones and for newbies their tutorials mess everything around"

I suppose that's my only "complaint" really - a newbie comes to code-igniter, downloads the current version, finds themselves unknowingly watching a video for a different version.
Right on the front page, the "get started" video says "Hello World! Introduction to CodeIgniter". I suppose that's my only gripe.. why not point newbies towards the correct introduction rather than confuse them with old syntax which won't work on the current version?

[quote author="osci" date="1309527813"]

Thanks for the info - back to procedural php for me for now though.

This won't do you any good. Procedural php is (almost) dead, and no company will use you for your procedural coding skills. So if you plan to make a living through coding that was a wrong statement.[/quote]

I'm not looking to program commercially, just solve simple problems for my own site. I'm interested in your hypothesis that "Procedural php is (almost) dead", I recently read a persuasive argument on Stackoverflow, which I can't find now, but here's one similar. (oh yeah, helpfully I can't post links - you can find it I'm sure - the title is "How do i get out of the habit of procedural programming and into object oriented programming?"

When all I want to do is read a csv file into a database via cron once a month, why OO it over procedural? I've seen two php scripts that will read id3 from an mp3 file - the procedural one is about 30 lines line, the OO one is about 500 lines over 3 files, the end result is the same.

Just saying... anyway, now I've found an intro that works, I'll give CI another go. Thanks for the pointer.