Another great proposal by Jade Constantine, this time relating to Kill Rights and Bounty hunting. I won’t say too much here… she says it all much better than I can. Go read the article.
Monthly Archives: April 2008
I just read a great article by one of the CSM candidates for EVE Online, talking about some changes to how the Local channel works, along with changes to scanning and galaxy map intel. All in all, some great points, and I think that maybe Jade Constantine will be getting my vote, when the elections open up.
I have believed for a long time that Local didn’t need to change… but I’m slowly swinging around to the camp that believes that in 0.0 at least, and possibly in Low Sec space, Local should go away. It makes dangerous space both more dangerous, and safer, at the same time. It’s kind of an odd situation.
It’s more dangerous, because you can’t see who else is in the system with you anywhere near as easily, so you can’t be sure whether you just flew into the middle of an enemy fleet, unless you see them. And generally, by the time you see them, it’s much too late. Yes, there will be ways to scan for enemies, but those take time, and unless you have high skills, aren’t 100% accurate.
It’s safer, for exactly the same reason. Your enemies can’t easily see that you’re there, unless they can get eyes on you. In fact, unless they’re actively scanning, or have people watching the gates, it’s even safer than it is currently, because they won’t ever know you passed through their system.
Jade’s proposed solutions are a great answer, in my opinion. It’ll bring a lot of excitement and mystery back to living in 0.0. In fact, it may make it possible for the small corps to establish small inroads into 0.0, without getting caught as soon as they start doing anything worthwhile.
There are many frameworks out there for PHP. Too many, even, some might say. So how did I settle on using CakePHP for my prefered framework? Well, to be honest, I think I was just lucky. Chuck, a guy I work with, introduced me to it for a project we were working on, and I reluctantly tried it. The reluctance didn’t last long, however. Within a week or two, I was an avid fan, and a very eager convert. I have since worked on several personal projects, and at least as many paying jobs with CakePHP as the architecture of choice.
The thing I like most about Cake is the strong structure it brings to a project. “But wait!” I hear you say, “All frameworks do that!” Yes, they do. But the structure and methodology of Cake work very well for me. For other people, perhaps Symphony would be better. Or Zend. But my own rather biased opinion is that Cake is better than all the others. I’ve since looked at code written in a handful of other frameworks, and I’ve not been impressed by it. Perhaps it was merely that the code was written by people who didn’t really know what they were doing, so they didn’t properly take advantage of the framework. But I found all the other frameworks I looked at to be needlessly verbose and repetitious.
I also love how flexible Cake is, while still maintaining it’s structure. I can make it do almost anything I need. It may not be as efficient as a hand-coded solution to many problems, but the time it saves me in development is a huge payoff. Nothing I write is likely to ever need high end scalability. And if it does end up needing hand-tuning, then I’ll take the time and effort needed.
So, to make a long story short, I prefer CakePHP because it Just Works. It’s well structured, yet flexible, and it makes sense to me.