You missed the part where a year later you get hired away by another company in an unrelated space because of your "superior reputation for team-building".
Per the parent, I presently possess a patent pending pertaining to patents with prior prototypes.
Re:Now that you got your HDTV plasma,
on
CNET's HDTV World
·
· Score: 2, Informative
It is a neat camcorder, but before anyone buys one thinking their home movies are going to suddenly rival the video quality of network HDTV, know that the HDR-HC1's actual measured resolution is closer to 656x480:
http://www.camcorderinfo.com/content/Sony-HCR-HC1- Review.htm
To be fair this is better than any DV camcorder but set your expectations properly.
So... perhaps Google needs to play a little catchup, but Google's idea of 'labels' instead of 'folders' I think is far superior.
This concept had been in a number of e-mail products for years before GMail came along, except it was called "categories".
As I read through these posts of "GMail is better because it has 'X' feature", very often people are praising a feature that's been in other mail software (desktop- and/or web-based) for much longer than GMail has been around.
So I guess really what Google's got going for them is superior feature marketing (or usability?), because otherwise intelligent, aware people are seemingly oblivious that all these things existed before.
This doesn't make any sense. The time consuming part of a credit card transaction is where the cashier checks your signature against the one
on the back of the card.
This probably should be the most time-consuming part but anecdotally folks (including myself) spend more time getting the card, handing it to the cashier/waiter/clerk/etc., waiting for them to (walk back to and) run the card through the register, waiting for receipts to print, waiting for them to walk back to you, getting your signature, (theoretically) checking your signature, separating the merchant copy from the customer copy, etc. It's not closing a mortgage but gratification can always be a little more instant - that's what MC's going for here.
If you just touch the card, there's no way for anyone in authority to verify that you are you
Yes, without any sort of biometric or other guard, it reduces to possession is authentication. Again it's a gamble that this will facilitate more purchases than fraud.
The only place where RFID cars are convenient is for rapid transit fare control.
That's the only place they'd be convenient? Really? Or is it just the only application with which you could be comfortable using them? Fraud and debt issues conveniently aside, PayPass approaches waving your hand to make a purchase, like some sort of magician. What could be more convenient to consumers (or yes, to thieves too)
On the flipside, the card never has to leave your physical possession.
MC's gamble is that contactless payment will thus thwart more fraud than it facilitates, while simultaneously encouraging consumers to buy more goods and services, because the PayPass transaction is perceived to be "easier" than exchanging cash or presenting plastic.
How cheap (and this how practical) could this be made to be?
If the break-even point is beyond the typical service life of a vehicle anyway, the appeal is just environmental. And if that's the case, do I want to fork out 5 figures to hybridize my car... or simply invest in legitimate alternative fuels research?
I think I understand why you and Minna Kirai are jumping on his post.
If you generalize "program" as he uses it to mean "any code path which takes responsibility for allocated memory and then abandons it" (rather than taking it literally to mean, a process), his point is still valid: classic GC helps when your "program" forgets to release memory; still no cure for heap cancer.
I'm seeing the names of fancy GC libraries being dropped in this thread, and I'm not familiar with all of them, but I would think any GC that's going to protect the heap by trying to outsmart me asynchronously with heuristic "observations" about my intentions, could be a big bitch of a bug for someone else to debug later on!
I also don't see where the grandparent was claiming that GC should be rejected out of hand because it doesn't solve all memory problems. All he said was, it doesn't solve all memory problems. If you code like there isn't a safety net, you probably write better code. If a yeoman programmer grows up believing that merely using GC, or auto_ptr, or RAII, or popular-pattern-of-the-week will always save him, he stands to get sucked into the "aw, fuck it" (a.k.a. MaxRequestsPerChild) coding mentality. Broken windows, etc.
You're very angry and I appreciate that! I hope you equally appreciate hearing that your argument is a fucking failure because it fucking assumes that implementing a fucking scalable fuckfuckinging mail server reduces to a few fopen(); read(); fclose() calls.
Anyone who's actually done more than tried to fucking lecture somebody the fuck on why they're not using the right fucking approach to implefuckmenting a fucking cock ass fuck shit mail server would realize that if you don't use some sort of database back-end, you still end up creating data fuckstructures and cockindexes on top of this magical filesystem of yours, and fucking code to manipulate those fucking data structures, and code to update the fuck out of those data structures and fucking indexes, and fucking code to fucking partition the godly file system directories so they are fucking balanced, and lo and behold you've fucking implemented something that looks like a fucking database! The difference being, you wrote it so it's got newer and more interesting fucking bugs than My-fucking-SQL, but god fucking damn it, you used the FILE SYSTEM so eat a fuck!
Unfortunately garbage collection is not a cure-all for memory leaks; the programmer(s) still must take care to ensure that references to memory-consuming objects are removed when no longer needed. This can be a nontrivial task e.g. in a complex application where state is shared among multiple threads and certain corner case situations blur who is responsible for reference clean-up.
Slashdot Mirror
Gives new meaning to 7-layer burrito, doesn't it?
Why should he do what? What did I miss?
Specifically, he was quoted as saying, "$15 million should be enough for anybody."
When is Office 2006 coming out, anyway?
Is it safe?
You missed the part where a year later you get hired away by another company in an unrelated space because of your "superior reputation for team-building".
3. Implement real-time interactive phone sex engine based on vocal likeness of Jenna Jameson
No, but they defected because of a compensation parity error.
free spelling correction?
Scalability means you can't readily observe service degradation as usage increases, so scalable systems can hide abuse pretty well.
Per the parent, I presently possess a patent pending pertaining to patents with prior prototypes.
It is a neat camcorder, but before anyone buys one thinking their home movies are going to suddenly rival the video quality of network HDTV, know that the HDR-HC1's actual measured resolution is closer to 656x480: http://www.camcorderinfo.com/content/Sony-HCR-HC1- Review.htm
To be fair this is better than any DV camcorder but set your expectations properly.
As I read through these posts of "GMail is better because it has 'X' feature", very often people are praising a feature that's been in other mail software (desktop- and/or web-based) for much longer than GMail has been around.
So I guess really what Google's got going for them is superior feature marketing (or usability?), because otherwise intelligent, aware people are seemingly oblivious that all these things existed before.
MC's gamble is that contactless payment will thus thwart more fraud than it facilitates, while simultaneously encouraging consumers to buy more goods and services, because the PayPass transaction is perceived to be "easier" than exchanging cash or presenting plastic.
I stand cor*****ed!
Inquiring minds want to know what the extra letter in "bitches" is.
... or run Virtual PC?
The other one that gets me is "sanction", which as a verb means to approve or to penalize for, depending on usage.
If the break-even point is beyond the typical service life of a vehicle anyway, the appeal is just environmental. And if that's the case, do I want to fork out 5 figures to hybridize my car ... or simply invest in legitimate alternative fuels research?
If you generalize "program" as he uses it to mean "any code path which takes responsibility for allocated memory and then abandons it" (rather than taking it literally to mean, a process), his point is still valid: classic GC helps when your "program" forgets to release memory; still no cure for heap cancer.
I'm seeing the names of fancy GC libraries being dropped in this thread, and I'm not familiar with all of them, but I would think any GC that's going to protect the heap by trying to outsmart me asynchronously with heuristic "observations" about my intentions, could be a big bitch of a bug for someone else to debug later on!
I also don't see where the grandparent was claiming that GC should be rejected out of hand because it doesn't solve all memory problems. All he said was, it doesn't solve all memory problems. If you code like there isn't a safety net, you probably write better code. If a yeoman programmer grows up believing that merely using GC, or auto_ptr, or RAII, or popular-pattern-of-the-week will always save him, he stands to get sucked into the "aw, fuck it" (a.k.a. MaxRequestsPerChild) coding mentality. Broken windows, etc.
You're very angry and I appreciate that! I hope you equally appreciate hearing that your argument is a fucking failure because it fucking assumes that implementing a fucking scalable fuckfuckinging mail server reduces to a few fopen(); read(); fclose() calls.
Anyone who's actually done more than tried to fucking lecture somebody the fuck on why they're not using the right fucking approach to implefuckmenting a fucking cock ass fuck shit mail server would realize that if you don't use some sort of database back-end, you still end up creating data fuckstructures and cockindexes on top of this magical filesystem of yours, and fucking code to manipulate those fucking data structures, and code to update the fuck out of those data structures and fucking indexes, and fucking code to fucking partition the godly file system directories so they are fucking balanced, and lo and behold you've fucking implemented something that looks like a fucking database! The difference being, you wrote it so it's got newer and more interesting fucking bugs than My-fucking-SQL, but god fucking damn it, you used the FILE SYSTEM so eat a fuck!
Unfortunately garbage collection is not a cure-all for memory leaks; the programmer(s) still must take care to ensure that references to memory-consuming objects are removed when no longer needed. This can be a nontrivial task e.g. in a complex application where state is shared among multiple threads and certain corner case situations blur who is responsible for reference clean-up.
Bugs is bugs!