As a user I understand that most of the proprietary crap that MS dishes out for protocols is indeed "cruft" (Most slashdotter's could shit better protocols in their sleep). I've experienced more bizarre behavior than I care to admit, but what are some technical or design examples that could be cited as to why most of their protocols (exchange in particular) are so bad? I know their implementation of IMAP is very poor, I think it has to do with various connection and sync commands not being fully or at all implemented which can cause all sorts of weirdness on the client end and lost mail on the server.
No, it's not. The US Secret Service working out of DC that protects former PsOTUS and FLsOTUS for up to ten years upon exiting their respective offices (it used to be lifetime), candidates for president are covered under this as well.
They also had a number of duties that until only recently put them under direction of the US Treasury and oversaw most if not all of the investigations therein. Before their move to the DHS they were assigned to investigate federal computer crime laws, a jurisdiction not removed with their transfer of ownership, as it were. Although publicly perceived as only protecting the president they are much like a handful of other somewhat small federal law enforcement agencies that do many other things than just what the public thinks they do. They were originally created in 1865 to go after currency counterfeiting, only being given the duty to protect presidents-and only informally-in 1901.
Same here. A total cockup. I'm considering canceling the order and telling them that's the reason, and that they just lost a sale to the cheaper Acer Aspire, even if it's a bitch to put memory into.
Li-Ion batteries work by placing anodes and cathodes next to each other, causing lithium ions to go to and from the anodes/cathodes. The resulting electro-chemical reaction "makes" electricity (this is over simplified!) When one of these things drops, is punctured or in any other way causes the two components to come into further contact with one another and then is "charged" the resulting energy can cause "expansion," excessive heat, fire and can even explode as we've seen previously.
This is a very simple explanation though. There are quite a few physical and electrical safeties on Li-Ion batteries but they aren't guarantees and as we've seen poor manufacturing or mis-use of these batteries can indeed be dangerous.
I had a friend once that put "I'm not tipping you" on his. If a clerk doesn't mention it, they don't get anything written on the tip line of the receipt.
Interesting. The entire reason we like Open Source is because we can change the code and fix bugs and make our lives better without being explicitly tied down to a vendor. But when I sign up with a vendor to provide support with things like this, I'm not able to fix those problems and worse off neither is the company that I signed up with.
The potential for exploits is huge, and with very severe consequences.
You mean, more so than Windows Mobile? Diebold machines work on the same security from obscurity concept, and are also based on the closed source Windows CE. Just because something is locked down or is closed source doesn't make it any easier to crack open. Many would argue the opposite. Please don't spread your anti-FOSS FUD.
1. Search for useful features (history, cache, saved entries) 2. Patent the removal of said features 3. ??? 4. Profit!
I see the point of removing or disabling histories in a browserâ"it makes senseâ"but these are just added features that some very old or very basic browsers don't have.
How can you patent the removal of features? It's not "making" anything, it's just tearing down something that already exists and only putting some parts back when you build it again. Obviously not everyone wants those parts, hence "privacy-aware" browsers exist, but you can't patent that!
As a designer this design makes me puke, crap and wee myself at the same time. While seizing.
Please make the text readable with black on white. I realize that there's plenty of pedantic crap that could be said about archaic hardware, 80 columns of text and green on black but we don't live in the 1980's anymore.;)
If Apple starts trying to support every combination of 3rd party hardware out there, OSX will start having reliability problems just like Windows does.
That's the point. They don't have to support anyone else. They just shouldn't be able to legally tie down there OS to their hardware through DRM. It's fine when the underlying hardware is some exotic blend that really can't be purchased elsewhere but when we're talking about fairly run-of-the-mill Intel reference designs...the same ones that Dell and HP use. It's just white-box PC hardware. Only the Mac Pro line is "exotic" and even then it's a fairly standard Intel workstation reference design.
I'm typing all this on my Dell Precision which for all intents and purposes was nearly identical to what Apple was shipping with Mac Pros when I got it about a year and a half ago. The biggest difference was the fact that spec'ing out the same exact thing with Apple was almost 750USD more. IIRC Apple was even shipping bottom-of-the-barrel consumer GeForce cards with there Mac Pros at the time, mine came with a medium-level Quadro with a cheap upgrade path.
This is without Dell's on-site, next-day warranty which doesn't require me to lug in my box to a "Genius Bar." I call my 800 number and generally have the problem nailed down within 15 to 30 minutes, they send out a tech the next day with the replacements and we're ready to rock and roll. I've not had to take them up on it with this box but I have on several others and it's really simple.
I love OS X and I would love to use it day to day, but I refuse to get dicked into a poor warranty and over-priced, generic hardware.
Hmmm, you're right. I generally think one or two sentences ahead of what I'm typing. I generally re-read what I type before sending or posting but apparently not this last time. Cheers mate!
Unless they use a fake visa (debit or check card) in which case the consumer has absolutely zero recourse.
Banks and credit unions are not held the same dispute structure as credit card companies (since the legislation concerning charge disputes was drafted and instituted during a more consumer-friendly congress than was legislation created for debit and check cards).
Slashdot Mirror
In Soviet Russia...we have Red Christmas!
Where the hell is "Redmond, Seattle"?
As a user I understand that most of the proprietary crap that MS dishes out for protocols is indeed "cruft" (Most slashdotter's could shit better protocols in their sleep). I've experienced more bizarre behavior than I care to admit, but what are some technical or design examples that could be cited as to why most of their protocols (exchange in particular) are so bad? I know their implementation of IMAP is very poor, I think it has to do with various connection and sync commands not being fully or at all implemented which can cause all sorts of weirdness on the client end and lost mail on the server.
No, it's not. The US Secret Service working out of DC that protects former PsOTUS and FLsOTUS for up to ten years upon exiting their respective offices (it used to be lifetime), candidates for president are covered under this as well.
They also had a number of duties that until only recently put them under direction of the US Treasury and oversaw most if not all of the investigations therein. Before their move to the DHS they were assigned to investigate federal computer crime laws, a jurisdiction not removed with their transfer of ownership, as it were. Although publicly perceived as only protecting the president they are much like a handful of other somewhat small federal law enforcement agencies that do many other things than just what the public thinks they do. They were originally created in 1865 to go after currency counterfeiting, only being given the duty to protect presidents-and only informally-in 1901.
Shit! I hate it when my Schwartz gets twisted!
Then we can't call it Hockey-Pux anymore!
"Onerous?"
You mean like...I don't know, dictionaries?
No, no, no.
Login: reiser
Password:
$ touch wife /dev/hills/body
touch: access denied
$ sudo touch wife
password:
touch: access denied
$ echo "wtf?"
wtf?
$ ps -aux | grep wife
wife 14589
$ sudo kill -9 14589
mv body
Some time later:
Login: cops
Password:
$ locate body /dev/hills/body
body not found
$ sudo usermod -g felon reiser
$ sudo updatedb
$ locate body
Same here. A total cockup. I'm considering canceling the order and telling them that's the reason, and that they just lost a sale to the cheaper Acer Aspire, even if it's a bitch to put memory into.
Li-Ion batteries work by placing anodes and cathodes next to each other, causing lithium ions to go to and from the anodes/cathodes. The resulting electro-chemical reaction "makes" electricity (this is over simplified!) When one of these things drops, is punctured or in any other way causes the two components to come into further contact with one another and then is "charged" the resulting energy can cause "expansion," excessive heat, fire and can even explode as we've seen previously.
This is a very simple explanation though. There are quite a few physical and electrical safeties on Li-Ion batteries but they aren't guarantees and as we've seen poor manufacturing or mis-use of these batteries can indeed be dangerous.
Something in your petri dish smells funny.
No designer in their right mind would use even an nth of the shit uploaded on Facebook everyday.
I had a friend once that put "I'm not tipping you" on his. If a clerk doesn't mention it, they don't get anything written on the tip line of the receipt.
Interesting. The entire reason we like Open Source is because we can change the code and fix bugs and make our lives better without being explicitly tied down to a vendor. But when I sign up with a vendor to provide support with things like this, I'm not able to fix those problems and worse off neither is the company that I signed up with.
What's the point then?
You mean, more so than Windows Mobile? Diebold machines work on the same security from obscurity concept, and are also based on the closed source Windows CE. Just because something is locked down or is closed source doesn't make it any easier to crack open. Many would argue the opposite. Please don't spread your anti-FOSS FUD.
You can screw with people on the phone very easily by going phonetic on them without saying "a as in."
Yes the name is, Delta India Tango Tango Oscar Bravo Oscar X-Ray.
Technically:
1. Search for useful features (history, cache, saved entries)
2. Patent the removal of said features
3. ???
4. Profit!
I see the point of removing or disabling histories in a browserâ"it makes senseâ"but these are just added features that some very old or very basic browsers don't have.
How can you patent the removal of features? It's not "making" anything, it's just tearing down something that already exists and only putting some parts back when you build it again. Obviously not everyone wants those parts, hence "privacy-aware" browsers exist, but you can't patent that!
As a designer this design makes me puke, crap and wee myself at the same time. While seizing.
Please make the text readable with black on white. I realize that there's plenty of pedantic crap that could be said about archaic hardware, 80 columns of text and green on black but we don't live in the 1980's anymore. ;)
That's the point. They don't have to support anyone else. They just shouldn't be able to legally tie down there OS to their hardware through DRM. It's fine when the underlying hardware is some exotic blend that really can't be purchased elsewhere but when we're talking about fairly run-of-the-mill Intel reference designs...the same ones that Dell and HP use. It's just white-box PC hardware. Only the Mac Pro line is "exotic" and even then it's a fairly standard Intel workstation reference design.
I'm typing all this on my Dell Precision which for all intents and purposes was nearly identical to what Apple was shipping with Mac Pros when I got it about a year and a half ago. The biggest difference was the fact that spec'ing out the same exact thing with Apple was almost 750USD more. IIRC Apple was even shipping bottom-of-the-barrel consumer GeForce cards with there Mac Pros at the time, mine came with a medium-level Quadro with a cheap upgrade path.
This is without Dell's on-site, next-day warranty which doesn't require me to lug in my box to a "Genius Bar." I call my 800 number and generally have the problem nailed down within 15 to 30 minutes, they send out a tech the next day with the replacements and we're ready to rock and roll. I've not had to take them up on it with this box but I have on several others and it's really simple.
I love OS X and I would love to use it day to day, but I refuse to get dicked into a poor warranty and over-priced, generic hardware.
That won't happen. SkyNet is British.
More to the point, we own them not the other way 'round. You know, Airstrip 101 and all.
[/sarc]
There, fixed that for you.
Hmmm, you're right. I generally think one or two sentences ahead of what I'm typing. I generally re-read what I type before sending or posting but apparently not this last time. Cheers mate!
Citations please. I'd love to know uses 1984 as a blueprint of sorts.
Unless they use a fake visa (debit or check card) in which case the consumer has absolutely zero recourse.
Banks and credit unions are not held the same dispute structure as credit card companies (since the legislation concerning charge disputes was drafted and instituted during a more consumer-friendly congress than was legislation created for debit and check cards).
Naw man. That's the sound lasers make: pew pew pew