This is probably an obvious answer to/.ers, but what on earth does http://local.live.com/ have to do with Windows (other than the o/s the service runs on?) This appears to be just another web app, with the windows adjective thrown in for no other reason than brand recognition.
And maybe it's also a sneaky effort on MS's part to convince internet users that dynamic DHTML+JS web pages are somehow related to their operating system... NOT. Kind of surprised it's not "MSN Local Live", or "MSN Live Local" or something... maybe that says something about where the MSN brand is going...
Until they begin selling the battery and everybody realizes it's in a new, proprietary form-factor, with new, proprietary terminal connections - patented, so they'll have that market to themselves. Priced at a premium to match LiON batteries.:)
ATMs do not need to be particularly secure - customers make complaints and banks do audits. If the cost of dealing with the complaints and audits is less than the cost of the extra security, we'll continue to have insecure ATMs.
Voting machines do not need to be particularly secure - voters make complaints and administrative judges review them and make decisions. If the cost of dealing with the complaints and judicial reviews is less than the cost of stealing an election, we'll continue to have insecure voting machines.
And that's how things stand today, because voting machines are even less secure than ATMs.
You take the actions of corrupt individuals, squint your eyes and say "yup! the U.N.'s a for-profit entity!"
Using that logic, the Republican-controlled U.S. Congress is for-profit entities, going by the guilty pleas and indictments over the last few weeks. Sheesh.
In NYC, whenever I spot an ATM being serviced, I discreetly check out the hardware. Very often it's a PC, with the touchscreen wired via USB or some other means. Often I see a MS Windows interface when it's in "service mode."
Some of these ATMs use the default Windows "asterisk" system sound as audio feedback for certain keypresses, and system shutdown sound for cash dispense, etc.
In a word, these are not very secure-looking ATMs. There's word in NYC that one type of identity theft occurs with these cheapie ATMs, usually found at bodegas and your local korean deli. I steer clear of em.
The earliest example that I've noticed of "ajax"-like functionality was on Amazon.com. When you vote on comments for a product, there's a javascript snippet that communicates with the server, using a hidden image object. No XMLHttpRequest object necessary.
While it was a good idea, what doomed Microsoft's effort was that they implemented it as a feature unique to only their browser, based on ActiveX.
It wasn't until after the Mozilla team implemented XMLHttpRequest that it became widely used. So, all this talk which implies that Microsoft is responsible for AJAX's popularity today is hogwash. They invented it, but it took others to make it cross-platform and useful.
I'm absolutely correct no matter what you say. Setting aside that fact, the very public presence of The Donald has left everybody with the impression that he does run the military. From Bush's spleen, to the Donald's brain, to the troops on the ground in Iraq, Afghanistan, the Philippines, etc.
The Donald runs this Pentagon. You need look no further than the Iraq war and its buildup. If you think different, you're living in a different decade from the one I'm posting to/. in.:)
Funny thing is, I've only heard of that happening in the 'burbs. In NYC it's never a problem, but maybe that's coz we're mobbed with pro photographers.
This is a plan that looks great on paper, and sounds lousy in reality.
Cell service providers are all about upping minutes usage, which translates to maximising usage of their infrastructure, which CFO's love. It improves some ratio like hardware amortization cost to utilization.
Somebody at Cingular put all this together and said "aha! I'm buying a boat next year!" Don't make that downpayment until the results come back, buddy...
Fluoride ions (from toothpaste, drinking water, etc) replace the hydroxyide ions, creating fluoroapatite. Fluoroapatite is much, much more resistant to acid than hydroxyapatite, so the teeth are much, much stronger. Far less cavities occur.
In the lab, yes. In your mouth, how long does this effect last for? After rinsing, and after saliva secretion washes any residual fluoride and fluoroapatite into your gullet, what effect does it have then?
The fluorides added to dentifrice are toxic enough that Crest and all other products of their kind carry a "Poison Center" warning on their labels. They're known immunodepressants, enough to whack the function of lymphocytes and leucocytes.
Add to regular brushings the ~1-3mg/L of fluorides contained in each glass of drinking water delivered by most municipalities in the United States, and that's quite a daily dosage. Over the teeth and into the digestive tract, where it's doing nothing for your teeth, and possibly not good for the rest of your body.
Much better to floss, brush, and rinse with alcohol-based mouthwash, and keep food and sugar off of your teeth between brushings. Just like Mom says.
Ah, okay, you're right - I remember the tree control, but mostly because it didn't run in Netscape.:) MS didn't provide an alternative for non-IE browsers for what seemed like a long time. It was pretty cool, though. Would've been cooler if they'd outed that technology more generally, as at the time I figured it for an activex control. Ta.
Microsoft may have "invented" XMLHTTPRequest, but then they ignored it for, what, 5-6 years?
Did they see the potential? No. They created a transfer mechanism back when XML was getting hyped, then forgot about it. And it wasn't the only mechanism "invented" back then, and it's not the only one available to "AJAX" apps. For example, hidden frames, iframes, and hidden images.
It took other bright minds to see the potential of DOM/DHTML and background data exchange, and put it to use. Try googling for "XMLHTTPRequest" - see any microsoft.com URIs in the top ten? Nope?
Under Windows XP, Firefox has become my browser of unchoice, because it's clipboard functionality is totally borked. I posted to bugzilla, and saw that about a million other people have too.
True, true. I mostly develop java for server-based apps, the kind that run for months on end. The startup penalty's not felt there.
For desktop apps, having to download a 50MB JRE is pretty much out of the question, when it comes to online distribution. This probably has a lot to do with why Java isn't a favorite language among desktop shareware or utility authors. I look forward to GCJ and other native compilers making Java apps a teeny bit smaller for users to download.
In my experience, Java's slowness issues stem not from the bytecode JVM, but rather J2SE's class libraries, and generally the object-oriented approach to solving problems.
Now, before you attack that, I'm heavy into design patterns and all the rest. No problem there, but consider this: how many times does an original piece of data get touched, copied or transformed in a Java app?
Case in point, parsing HTML or XML documents. Under the J2SE scheme of things, even a tiny XML document can result in hundreds if not thousands of objects being created, even if you're after just one piece of info in that document. That results from the *lazy* use of Java's built-in parsers, which are inefficient due to their abstract nature.
You have to carefully monitor where your data goes, and what gets done with it, in a Java application that makes heavy use of J2SE's classes. They're entirely general purpose, which is great when you need to slam out some code. But if you're at all interested in performance, you're screwed, because general purpose = glacial performance.
When I can, code state machine parsers for problems like this, and look for other ways to avoid the heavily abstracted code that can result in data duplication and slow performance. JVMs today are quick, and code written from fundamentals of minimal work can achieve maximal performance.
Slashdot Mirror
This is probably an obvious answer to /.ers, but what on earth does http://local.live.com/ have to do with Windows (other than the o/s the service runs on?) This appears to be just another web app, with the windows adjective thrown in for no other reason than brand recognition.
And maybe it's also a sneaky effort on MS's part to convince internet users that dynamic DHTML+JS web pages are somehow related to their operating system... NOT. Kind of surprised it's not "MSN Local Live", or "MSN Live Local" or something... maybe that says something about where the MSN brand is going...
This week we like Sony?
:)
Until they begin selling the battery and everybody realizes it's in a new, proprietary form-factor, with new, proprietary terminal connections - patented, so they'll have that market to themselves. Priced at a premium to match LiON batteries.
ATMs do not need to be particularly secure - customers make complaints and banks do audits. If the cost of dealing with the complaints and audits is less than the cost of the extra security, we'll continue to have insecure ATMs.
Voting machines do not need to be particularly secure - voters make complaints and administrative judges review them and make decisions. If the cost of dealing with the complaints and judicial reviews is less than the cost of stealing an election, we'll continue to have insecure voting machines.
And that's how things stand today, because voting machines are even less secure than ATMs.
You take the actions of corrupt individuals, squint your eyes and say "yup! the U.N.'s a for-profit entity!" Using that logic, the Republican-controlled U.S. Congress is for-profit entities, going by the guilty pleas and indictments over the last few weeks. Sheesh.
In NYC, whenever I spot an ATM being serviced, I discreetly check out the hardware. Very often it's a PC, with the touchscreen wired via USB or some other means. Often I see a MS Windows interface when it's in "service mode."
Some of these ATMs use the default Windows "asterisk" system sound as audio feedback for certain keypresses, and system shutdown sound for cash dispense, etc.
In a word, these are not very secure-looking ATMs. There's word in NYC that one type of identity theft occurs with these cheapie ATMs, usually found at bodegas and your local korean deli. I steer clear of em.
Microsoft pioneered this whole way of thinking
The earliest example that I've noticed of "ajax"-like functionality was on Amazon.com. When you vote on comments for a product, there's a javascript snippet that communicates with the server, using a hidden image object. No XMLHttpRequest object necessary.
While it was a good idea, what doomed Microsoft's effort was that they implemented it as a feature unique to only their browser, based on ActiveX.
It wasn't until after the Mozilla team implemented XMLHttpRequest that it became widely used. So, all this talk which implies that Microsoft is responsible for AJAX's popularity today is hogwash. They invented it, but it took others to make it cross-platform and useful.
I'm absolutely correct no matter what you say. Setting aside that fact, the very public presence of The Donald has left everybody with the impression that he does run the military. From Bush's spleen, to the Donald's brain, to the troops on the ground in Iraq, Afghanistan, the Philippines, etc.
bwah-hahahahah!
The Donald runs this Pentagon. You need look no further than the Iraq war and its buildup. If you think different, you're living in a different decade from the one I'm posting to /. in. :)
Funny thing is, I've only heard of that happening in the 'burbs. In NYC it's never a problem, but maybe that's coz we're mobbed with pro photographers.
This is a plan that looks great on paper, and sounds lousy in reality.
Cell service providers are all about upping minutes usage, which translates to maximising usage of their infrastructure, which CFO's love. It improves some ratio like hardware amortization cost to utilization.
Somebody at Cingular put all this together and said "aha! I'm buying a boat next year!" Don't make that downpayment until the results come back, buddy...
Fluoride ions (from toothpaste, drinking water, etc) replace the hydroxyide ions, creating fluoroapatite. Fluoroapatite is much, much more resistant to acid than hydroxyapatite, so the teeth are much, much stronger. Far less cavities occur.
In the lab, yes. In your mouth, how long does this effect last for? After rinsing, and after saliva secretion washes any residual fluoride and fluoroapatite into your gullet, what effect does it have then?
The fluorides added to dentifrice are toxic enough that Crest and all other products of their kind carry a "Poison Center" warning on their labels. They're known immunodepressants, enough to whack the function of lymphocytes and leucocytes.
Add to regular brushings the ~1-3mg/L of fluorides contained in each glass of drinking water delivered by most municipalities in the United States, and that's quite a daily dosage. Over the teeth and into the digestive tract, where it's doing nothing for your teeth, and possibly not good for the rest of your body.
Much better to floss, brush, and rinse with alcohol-based mouthwash, and keep food and sugar off of your teeth between brushings. Just like Mom says.
http://download.mozilla.org/?product=firefox-1.5rc 2&os=win&lang=en-US
.MAR files, then found this link. Kind of silly to post an article with only an obscure updater format.
Scratched my head about
Ah, okay, you're right - I remember the tree control, but mostly because it didn't run in Netscape. :) MS didn't provide an alternative for non-IE browsers for what seemed like a long time. It was pretty cool, though. Would've been cooler if they'd outed that technology more generally, as at the time I figured it for an activex control. Ta.
Here ya go:
r mat=specific&order=relevance+desc&bug_status=__all __&product=Firefox&content=clipboard
https://bugzilla.mozilla.org/buglist.cgi?query_fo
FWIW, it looks like there has been some attempt to resolve, as some of these are in state closed. About to try out the release...
Microsoft may have "invented" XMLHTTPRequest, but then they ignored it for, what, 5-6 years?
Did they see the potential? No. They created a transfer mechanism back when XML was getting hyped, then forgot about it. And it wasn't the only mechanism "invented" back then, and it's not the only one available to "AJAX" apps. For example, hidden frames, iframes, and hidden images.
It took other bright minds to see the potential of DOM/DHTML and background data exchange, and put it to use. Try googling for "XMLHTTPRequest" - see any microsoft.com URIs in the top ten? Nope?
Catch you later.
Under Windows XP, Firefox has become my browser of unchoice, because it's clipboard functionality is totally borked. I posted to bugzilla, and saw that about a million other people have too.
True, true. I mostly develop java for server-based apps, the kind that run for months on end. The startup penalty's not felt there. For desktop apps, having to download a 50MB JRE is pretty much out of the question, when it comes to online distribution. This probably has a lot to do with why Java isn't a favorite language among desktop shareware or utility authors. I look forward to GCJ and other native compilers making Java apps a teeny bit smaller for users to download.
In my experience, Java's slowness issues stem not from the bytecode JVM, but rather J2SE's class libraries, and generally the object-oriented approach to solving problems.
Now, before you attack that, I'm heavy into design patterns and all the rest. No problem there, but consider this: how many times does an original piece of data get touched, copied or transformed in a Java app?
Case in point, parsing HTML or XML documents. Under the J2SE scheme of things, even a tiny XML document can result in hundreds if not thousands of objects being created, even if you're after just one piece of info in that document. That results from the *lazy* use of Java's built-in parsers, which are inefficient due to their abstract nature.
You have to carefully monitor where your data goes, and what gets done with it, in a Java application that makes heavy use of J2SE's classes. They're entirely general purpose, which is great when you need to slam out some code. But if you're at all interested in performance, you're screwed, because general purpose = glacial performance.
When I can, code state machine parsers for problems like this, and look for other ways to avoid the heavily abstracted code that can result in data duplication and slow performance. JVMs today are quick, and code written from fundamentals of minimal work can achieve maximal performance.