I'm not upgrading to Leopard until I get a new Mac or they offer something really compelling. Spaces? Yeah, it's cool. I've also been using it for years on Linux. I'm not shelling out however much for Leopard. I can't be the only one. Tiger's not going anywhere soon.
Re:Microsoft is thrilled by this news
on
Zune DRM Cracked
·
· Score: 1
dog/cat/wife/car/whatever You better cherish those pics of your wife. If she ever reads that comment you're through!
I thought it was born in the Mac world where each application can be handled as a unit, as well as controlling each individual window. In any case dedicating a virtual desktop to the GIMP might save you some headaches.
[OT: Every time I think about these things I want to create a WM that works similar to OS X's and has a dvorak-qwerty keyboard layout.]
There's a lot of stuff you can do on networks of comodity machines. But when you truly need a "no bit shall fall" environment there's still no substitute for a mainframe. Tell that to Google.
Care to elaborate? I'd like an educated opinion, why you think these aren't worth it. Do you have real experience with them or did you just dick around with each for 20 minutes? I did say that based on a quick hour-or-less session I did with several PHP frameworks. I checked out Symfony, Cake, Qcodo, Zend framework, and I may have taken a cursory look at a couple other. After evaluating those last summer (about a year ago exactly) I ended up using the Zend framework for that project.
Both Symfony and Cake seemed nice at first, but I couldn't even follow their 101 tutorials because the instructions were not correct for the current stable versions. Sure I could have figured it out, but when I have a fairly short time to evaluate these things I'm not going to start diving into the source just to get started! I didn't have to do that with Rails, and I didn't have to do that with the Zend framework (which was at v0.14 at the time).
Qcodo is interesting. Seagull looked fairly interesting as well, but this was a small internal project and the Zend framework fit the bill nicely.
So it was based on a quick 20-minute dicking around. If you're very interested in the projects then they may work well for you, and for all I know the docs actually match the code by now which I guess was the biggest turn off.
Or is it PHP that you don't like? I'm really interested. Propels XML is the only potential downside I can see. And that doesn't seen to much of a problem. I won't pretend to be a PHP fan but that didn't factor into my choice of framework since it had to be done in PHP. I didn't take more than a 20-minute glance at Propels (as part of Symfony iirc) so I don't have much of an opinion on it.
Cake and Symfony try very hard to be Rails. If you have a choice of language I strongly urge anyone looking at those 2 to just use the real deal instead. If you want to use PHP then I would still urge you to look at Prado, Seagull, Zend framework or Qcodo before these 2. At least those have some unique features and direction, rather than just picking up the scraps Rails throws away.
Note that neither him nor myself said that broadcasting all bits was the ideal solution. In retrospect I probably shouldn't have mentioned the word at all.
Slashdot Mirror
I'm not upgrading to Leopard until I get a new Mac or they offer something really compelling. Spaces? Yeah, it's cool. I've also been using it for years on Linux. I'm not shelling out however much for Leopard. I can't be the only one. Tiger's not going anywhere soon.
I thought it was born in the Mac world where each application can be handled as a unit, as well as controlling each individual window. In any case dedicating a virtual desktop to the GIMP might save you some headaches. [OT: Every time I think about these things I want to create a WM that works similar to OS X's and has a dvorak-qwerty keyboard layout.]
Fair enough. If you've seen it twice then surely it's happened more.
Both Symfony and Cake seemed nice at first, but I couldn't even follow their 101 tutorials because the instructions were not correct for the current stable versions. Sure I could have figured it out, but when I have a fairly short time to evaluate these things I'm not going to start diving into the source just to get started! I didn't have to do that with Rails, and I didn't have to do that with the Zend framework (which was at v0.14 at the time).
Qcodo is interesting. Seagull looked fairly interesting as well, but this was a small internal project and the Zend framework fit the bill nicely.
So it was based on a quick 20-minute dicking around. If you're very interested in the projects then they may work well for you, and for all I know the docs actually match the code by now which I guess was the biggest turn off.
Or is it PHP that you don't like? I'm really interested. Propels XML is the only potential downside I can see. And that doesn't seen to much of a problem. I won't pretend to be a PHP fan but that didn't factor into my choice of framework since it had to be done in PHP. I didn't take more than a 20-minute glance at Propels (as part of Symfony iirc) so I don't have much of an opinion on it.
Cake and Symfony try very hard to be Rails. If you have a choice of language I strongly urge anyone looking at those 2 to just use the real deal instead. If you want to use PHP then I would still urge you to look at Prado, Seagull, Zend framework or Qcodo before these 2. At least those have some unique features and direction, rather than just picking up the scraps Rails throws away.
Zope, Plone, Django, Turbogears -- cool.
Cake, Symfony -- stay the hell away from these crummy frameworks.
And sure Rails may be overhyped, but that doesn't mean that it's bad.
Assuming a suitable HDTV to use as a display, what the hell am I going to type on? T9 input? ha ha ha
I got it, I just posted this late at night with a poor description. In any case people are watching and talking about it, which was my goal.
Note that neither him nor myself said that broadcasting all bits was the ideal solution. In retrospect I probably shouldn't have mentioned the word at all.