33 karma · joined March 18, 2009
Step 2: After waking, splash cold water on face, then eat your lunch at you desk.
Also, I agree with others that trying to sell a CLI version will probably go nowhere. In fact, it may stifle adoption after you switch to the GUI version (since prospective users might think "Oh, that's that terminal program, right? Yuck!").
Results I've found: Mornings really suck. I'm putting on weight. I also feel terribly unhealthy. I'm not as sharp as I am at full power (though this is subjective and very hard to discern). I can fall asleep in minutes if given a place to lay down. Also, I get sick much more often than usual (which was hardly at all). Subjective opinion: it feels like I'm prematurely aging myself.
Trying to "make up" the sleep on weekends doesn't work for me. Oversleeping just leads to bad headaches.
When I do get a solid 8 hours I feel like Superman the next day.
I'm hoping that I'm not doing any long-term damage to myself, but there's really no way out right now. :( The current job ends very soon (2 weeks!), and then I'll be able to resume normal sleeping habits (7-8 hrs/night).
Are you saying it's difficult in general to find good C devs? Because it would seem that's the case for C++, but not for C.
Just because it's not currently maintained does not mean it won't be maintained in the future.
Not only that, but it's poison for attracting new developers.
Fact is, computing has benefitted from some core technologies (ex. lithography) that have lended themselves to order-of-magnitude increases in things like number of transistors per square cm. It's been a happy coincidence, but, inevitably, that ship has about finished its trip and is heading back to the dock.
Here's what will happen (and is happening) when hardware hits that limit: pretty much nothing. People will still use computers for email, browsing the web, watching videos, numerically solving partial differental equations, etc. There will be no clamour to make faster computers because computers are pretty much fast enough for what we want them to do. If they're not fast enough, then tasks can be spread out and handled in a distributed manner.
Oh, also, computer hardware companies will find that they can't get you to upgrade every few years to get the latest and greatest. This is great news, btw, for, say, schools; since they'll be able to invest in computers and expect to keep them long enough to be worth the investment.
Hopefully the Perl community will take advantage of that spike. For example, it would be cool to see mod_perl6/mod_parrot hit stable at around the same time. Maybe even along with some key modules recoded in Perl 6 too (for webapps, maybe CGI::Application?).
[1]: Yes, I realize Perl 6 is the spec, but my guess is that Parrot + Rakudo will be the canonical implementation.
You might try Fink. Seems like they're still active, but their last news update (on their homepage) is from 2008-07-23.
One benefit of an LLC might be a somewhat more professional image (for some customers anyway). Also, my guess is that corporate customers may not want to do business with you unless you're an LLC (though I wouldn't know for sure as I have no corporate customers).
Anyone here go from having your own LLC to dissolving it and going sole proprietership?
It's interesting to hear what people think of as "long-term".
Hawaii seems to already be testing this out... (don't have the link handy)