Shared folders is one of the big features they're working on. Look for it in 1.1 (in alpha now) or 1.2.
The filters thing would be nice, but Maildrop is nicer even if it isn't integrated into the GUI. With a GUI, it would be the greatest thing since sliced onions.
Do you run your own mail server at home? If so, try changing to Dovecot. They passed 1.0 (1.0.2 now) and they deserve it. Handles maildirs, GSSAPI, and it's fast. I have 5,981 messages in my Inbox alone, probably 5 times that in all the other folders, every non-spam e-mail I've ever sent or received since I started running my own mail server... God, it was 6 years ago now. Anyway, I had to switch away from Courier-IMAP about 9 months ago because it's a dog when you have large maildis, and Dovecot was the only thing that supported it without ridiculous caveats. So glad I did.
Of course. Things like an 8-12 hour workday obviously play no part in it. Not economics, either. It's not like healthier food has a cost premium on it or anything...
Funny. Mine has a microwave oven for us to eat our oh-so-healthy lunches in 10 minutes. Let's not assume everyone has your sweet job, hm?
Funny, I eat much more than 7/8 of my meals from a microwave. They cost $1.69, and have about 350 calories each. They're also pretty good. Healthy Choice is the brand, no nasty (fat, gristle, overcooked, the usual TV dinner crap) meat.
Easier, sure. Cheaper, maybe (I'm not sure how a month's worth of Prozac/Paxil/happy-pill-of-the-day goes for, but if it's not generic, it might be more than a few cartons of cigarettes/month). Irrelevant, definitely.
Wha? Or you could just, you know, quit. Nicotine gum, which allows you to gradually bring your levels down, costs way less than an equivalent time period smoking. If you're going to drug yourself, why not hit the root of the problem, your dopamine addiction? Go get an 8-ball and snort it. After three days without a cigarette you'll be the happiest person alive with a couple rails up your nose.
Other than some of the depressed people, yeah, it is that easy. I never even noticed it, but I got up to 25 lbs. overweight. You know what I did? I ate less. Counted calories, weighed myself and got the rate right, at about 3 lbs a week, and in a little over three months I lost 40 lbs. Then, once you reach your goal weight & fat percentage you slowly eat more until you're holding steady. Done, you're not fat anymore.
Smoking? Stop. Chew some gum, survive a week, don't go get drunk for a few months, you're done. That's how I did it.
Skinny? Eat more. Lift weights. Join the National Guard, try four months of infantry training. You won't be skinny anymore. Once again, that's how I did it.
Basically what I'm saying is, if you can't handle these simple tasks then you suck at life. No, seriously, you do, almost by definition. And at least half of the depressed people, too. The other half? Stop going off your meds! It's only been a month! Yes, you're still crazy!
The seemingly unrelated piece of code has its own unit test, which 99% of the time catches behavior changes. No, I haven't used strcpy() since I had to do a small project in C. I have to deal with integral overflows, but the idea is to check for them, and catch them before they happen. Look up SafeInt, I have a custom version of that that actually gets its type information from #include <limits> so even if I'm rushing I can just wrap it in that and get an error during testing because I tried the function with numeric_limits::max() and friends, instead of weird sporadic errors 8 months later. This is walking across the room stuff, friend.
No, you're right, I do those things sometimes, even after all my testing. I don't know what I was thinking using hyperbole around 200,000 aspies. The point is, it's exceedingly rare, like two double-frees in 8 years that I can think of and no, not a single buffer overflow (that I know of). As for big projects, if they're managed well it's not that much of an issue. There are coding standards, what you work on is well-defined and had better be documented (edge cases, calling conventions, invariants, etc.) plus you check the input anyway, unless it's real expensive and you're optimizing, and you've made your proposal in front of the team, and then you mark your unsafe function with a u_ or whatever your standard unchecked input marker is. Luckily, I've never worked at one of these big, greasy, code factories where everyone's got sloppy bits up to their elbows and there's a sign over the door that says, "Three (3) days since the last industrial accident (resulted in loss of limb)!" I have walked out in the middle of an interview at a place like that though, I think my head would asplode to work around that, plus it was fun to interrupt Mr. In The Real World Things Are Broken And That's Normal mid-sentence.
Yeah, I don't know why I picked that example, I've almost never used either function, and when I did I checked string length/null termination myself before... and after... man, they suck... just the first thing that popped into my head and I was ranting.
Yeah, I remember that now. To be honest I was just trying to come up with an example of checking your buffers, I've only used either function a couple times at best. Should have unit tested that post.
Payroll, insurance submission, medical records, you name it. I worked in a shop where we basically handled every programming task a hospital could want. No, not firmware for dialysis machines, but it was plenty complicated, and it could be your ass if you make a mistake. There was a time, if you so much as walked in the door of a hospital in New York anywhere outside of NYC, and one there, that you were pushing bits through my code. Of course, a huge hospital IT company came in and took every last one of our customers with PowerPoint slides and free lunches, but the pain those people went through with that crap software was more than enough to wash away my angst. Over that particular matter, anyway. I work in a much lower-pressure job these days, and I'm happier, but sometimes I miss praying to sweet Christ that the code I just uploaded doesn't make today the first (and likely last) time I ever lost data.
Easier, yes. But people still don't develop their software rigorously, so all it does is push these errors into another class. This is something that could be solved just as well with a library in any given language, you don't have to use Python to be sure you aren't hitting these bugs.
Yeah, there was a little hyperbole there, but I was trying to make a point. Although, to be fair, I still run all of my code through Valgrind and I've only caught an error like that twice in about 8 years. Once was C++ type demangling to make an error message human-readable, which as I recall was really poorly documented as to whether you or the library freed the memory, and the other was interfacing with getopt_long(), I tried to free argv. Whoops. I do have bugs, but it's extremely rare that it's of that type. I view a programmer making that type of a mistake about the same as a person trying to walk across the room and falling on his face. Which I've done, twice.
Eliminating a class of bugs is a great thing, but GC doesn't do it. Instead of memory leaks, you have object leaks. People start to trust the GC too much, and it takes away more control than it's worth. That's just a personal preference, of course, and I'll write GC code, but since I don't like it I'll take a 10% lower salary if I don't have to deal with it.
It prevents the common mistake of using the assignment operator "=" when you meant the equality operator "==". I like it better your way too, since it illustrates the object of the comparison better, but if I'm rushing out code that I don't have time to write good unit tests for, I switch over.
Slashdot Mirror
Yeah, and then imagine how much power could be generated by burning every tree on the planet! Thermodynamics be damned, our worries are over!
Shared folders is one of the big features they're working on. Look for it in 1.1 (in alpha now) or 1.2.
The filters thing would be nice, but Maildrop is nicer even if it isn't integrated into the GUI. With a GUI, it would be the greatest thing since sliced onions.
Aww, wtf, Google ref stuck in my link. That'll teach me. Here's the right link.
Do you run your own mail server at home? If so, try changing to Dovecot. They passed 1.0 (1.0.2 now) and they deserve it. Handles maildirs, GSSAPI, and it's fast. I have 5,981 messages in my Inbox alone, probably 5 times that in all the other folders, every non-spam e-mail I've ever sent or received since I started running my own mail server ... God, it was 6 years ago now. Anyway, I had to switch away from Courier-IMAP about 9 months ago because it's a dog when you have large maildis, and Dovecot was the only thing that supported it without ridiculous caveats. So glad I did.
Funny, I eat much more than 7/8 of my meals from a microwave. They cost $1.69, and have about 350 calories each. They're also pretty good. Healthy Choice is the brand, no nasty (fat, gristle, overcooked, the usual TV dinner crap) meat.
Wha? Or you could just, you know, quit. Nicotine gum, which allows you to gradually bring your levels down, costs way less than an equivalent time period smoking. If you're going to drug yourself, why not hit the root of the problem, your dopamine addiction? Go get an 8-ball and snort it. After three days without a cigarette you'll be the happiest person alive with a couple rails up your nose.
I can tell that you're tough by the way you call people Chief.
How much do you want to bet that nearly every person upset by the GP is either fat or fucking someone fat?
Other than some of the depressed people, yeah, it is that easy. I never even noticed it, but I got up to 25 lbs. overweight. You know what I did? I ate less. Counted calories, weighed myself and got the rate right, at about 3 lbs a week, and in a little over three months I lost 40 lbs. Then, once you reach your goal weight & fat percentage you slowly eat more until you're holding steady. Done, you're not fat anymore.
Smoking? Stop. Chew some gum, survive a week, don't go get drunk for a few months, you're done. That's how I did it.
Skinny? Eat more. Lift weights. Join the National Guard, try four months of infantry training. You won't be skinny anymore. Once again, that's how I did it.
Basically what I'm saying is, if you can't handle these simple tasks then you suck at life. No, seriously, you do, almost by definition. And at least half of the depressed people, too. The other half? Stop going off your meds! It's only been a month! Yes, you're still crazy!
The seemingly unrelated piece of code has its own unit test, which 99% of the time catches behavior changes. No, I haven't used strcpy() since I had to do a small project in C. I have to deal with integral overflows, but the idea is to check for them, and catch them before they happen. Look up SafeInt, I have a custom version of that that actually gets its type information from #include <limits> so even if I'm rushing I can just wrap it in that and get an error during testing because I tried the function with numeric_limits::max() and friends, instead of weird sporadic errors 8 months later. This is walking across the room stuff, friend.
OMG! I like to make up numbers to support something I've already decided too! 98.-6% of mothers agree, we should hook up.
*sigh*
It's hard to convince other people that you're perfect when you forget to close your <i> tags.
Somebody mod me up to +5 Funny and back down to -1 Overrated.
No, you're right, I do those things sometimes, even after all my testing. I don't know what I was thinking using hyperbole around 200,000 aspies. The point is, it's exceedingly rare, like two double-frees in 8 years that I can think of and no, not a single buffer overflow (that I know of). As for big projects, if they're managed well it's not that much of an issue. There are coding standards, what you work on is well-defined and had better be documented (edge cases, calling conventions, invariants, etc.) plus you check the input anyway, unless it's real expensive and you're optimizing, and you've made your proposal in front of the team, and then you mark your unsafe function with a u_ or whatever your standard unchecked input marker is. Luckily, I've never worked at one of these big, greasy, code factories where everyone's got sloppy bits up to their elbows and there's a sign over the door that says, "Three (3) days since the last industrial accident (resulted in loss of limb)!" I have walked out in the middle of an interview at a place like that though, I think my head would asplode to work around that, plus it was fun to interrupt Mr. In The Real World Things Are Broken And That's Normal mid-sentence.
Yeah, I don't know why I picked that example, I've almost never used either function, and when I did I checked string length/null termination myself before... and after... man, they suck... just the first thing that popped into my head and I was ranting.
Waaaait... is this 1967? No? Shit!
You caught me. I have no idea what I'm talking about. *waves hand*
Yeah, I remember that now. To be honest I was just trying to come up with an example of checking your buffers, I've only used either function a couple times at best. Should have unit tested that post.
Payroll, insurance submission, medical records, you name it. I worked in a shop where we basically handled every programming task a hospital could want. No, not firmware for dialysis machines, but it was plenty complicated, and it could be your ass if you make a mistake. There was a time, if you so much as walked in the door of a hospital in New York anywhere outside of NYC, and one there, that you were pushing bits through my code. Of course, a huge hospital IT company came in and took every last one of our customers with PowerPoint slides and free lunches, but the pain those people went through with that crap software was more than enough to wash away my angst. Over that particular matter, anyway. I work in a much lower-pressure job these days, and I'm happier, but sometimes I miss praying to sweet Christ that the code I just uploaded doesn't make today the first (and likely last) time I ever lost data.
Easier, yes. But people still don't develop their software rigorously, so all it does is push these errors into another class. This is something that could be solved just as well with a library in any given language, you don't have to use Python to be sure you aren't hitting these bugs.
Yeah, there was a little hyperbole there, but I was trying to make a point. Although, to be fair, I still run all of my code through Valgrind and I've only caught an error like that twice in about 8 years. Once was C++ type demangling to make an error message human-readable, which as I recall was really poorly documented as to whether you or the library freed the memory, and the other was interfacing with getopt_long(), I tried to free argv. Whoops. I do have bugs, but it's extremely rare that it's of that type. I view a programmer making that type of a mistake about the same as a person trying to walk across the room and falling on his face. Which I've done, twice.
Eliminating a class of bugs is a great thing, but GC doesn't do it. Instead of memory leaks, you have object leaks. People start to trust the GC too much, and it takes away more control than it's worth. That's just a personal preference, of course, and I'll write GC code, but since I don't like it I'll take a 10% lower salary if I don't have to deal with it.
Hospitals.
It prevents the common mistake of using the assignment operator "=" when you meant the equality operator "==". I like it better your way too, since it illustrates the object of the comparison better, but if I'm rushing out code that I don't have time to write good unit tests for, I switch over.
Unfortunately, a hammer does you no good when you're omg standing on the surface of the sun! so we should throw away all the hammers.
I think he was just trying to illustrate a simple point, not post the One True Memory Management pattern :P
Man. We can dream, anyway.
I'm sorry, you're right, there's way more than 20 of us out there. What I should have said is, why can't the other 1,999,999%?
No, wait...
Yeah, I just read that again. Guess I got a little carried away...