Um... When they suddenly need to use an old version of windows and are forced to use command.exe, where the tab button does not auto-complete things for them?
Perhaps people should think a little more before they open their mouths, or in this case, apply their fingers to their keyboards. Which is exactly what the summary/article mentioned as being bad:
"Afraid how our words and actions may be perceived years later and taken out of context, the lack of forgetting may prompt us to speak less freely and openly." I actually do find myself speaking less freely and openly precisely because I know it's all likely to still be on the internet someday long after I'm dead. I see that as a problem.
Someone mentioned that we could use nicknames, so yeah, I use a nickname. The trick comes when I try to continually separate my nickname-self from my real-self, in order to protect my privacy. It's hard work!
So, I'm sad that I feel the need to censor what I say on the internet. But what's worse is that I tend to carry that tendency over into real life. I find myself not divulging information about myself to other people, in real-life conversations, because the hesitancy to do so is so ingrained in me now... I've somehow come to a point of thinking that it's not anyone's right or business to know anything about me, unless I'm feeling particularly benevolent. But this is to the detriment of real-life relationships.:(
Does anyone else experience this issue? Does anyone have useful tips on resolving it?
People can forgive (and perhaps we should learn to do it more often) but machines do not. Computers also can't differentiate between the truth and a lie, either. (And people post a lot of both, on the internet.) That very fact makes it sound really ridiculous (in my opinion) for any business to depend upon data-mined and computer-analyzed internet posts to make any business decisions for them.
That's the spirit! You've just got to unsay what you said before, then, when they look up your past, they'll pay more attention to the more recent comments. Er...hopefully. But I suppose actually meaning the "unsaid" comment might help...;)
"00:01 would be correct in a 24-hour clock, but not in a 12-hour clock."
Interestingly, JK Rowling actually stated (http://www.jkrowling.com/textonly/en/news_view.cf m?id=97): Harry Potter and the Deathly Hallows will be published on Saturday 21st July 2007 at 00:01 BST in the UK and at 00:01 in the USA. It will also be released at 00:01 BST on Saturday 21st July in other English speaking countries around the world.
I might have been confused, too, had I not read the news from her site first. I'm not a fan of the 24-hour clock, but I do think we should call the first hour of the day 0:whatever AM, instead of 12:whatever AM. It definitely stops the confusion (for me, at least) before it even starts.
So... Is the quad core considered 4 processors? or just one?
I ask because the Vista EULA says:
2. INSTALLATION AND USE RIGHTS. Before you use the software under a license, you must
assign that license to one device (physical hardware system). That device is the "licensed device."
A hardware partition or blade is considered to be a separate device.
a. Licensed Device. You may install one copy of the software on the licensed device. You may
use the software on up to two processors on that device at one time. Except as provided in the
Storage and Network Use (Ultimate edition) sections below, you may not use the software on any
other device.
Q: Will systems running Wine pass WGA validation?
A: Wine is an implementation of the Windows 3.x and Win32 APIs on top of X and Unix. When WGA validation detects Wine running on the system, it will notify users that they are running non-genuine Windows, and it will not allow genuine Windows downloads for that system. Users of Wine should consult the Wine community for Wine updates. It is important to note that Wine users, and other users of non-genuine Windows, can continue to download updates for most Microsoft applications from Microsoft application-specific sites, such as Office Update.
And another question I had: how often will Vista try to Validate itself? What if you don't have the internet on that machine? Would Validating involve calling MS every so often?
For me, at least, one of the reasons I "arbitrarily" click on nothingness (it's actually on purpose, but if you weren't inside my head, you wouldn't know why--but, here I'm about to tell you!) is because I want to make sure that the "nothingness" is the active part of the page, rather than some form that I forgot I had been typing in (try searching in firefox when a form is the active element in a web page. You end up typing the word you were intending to search for into the form, rather than actually searching), or worse, a combobox. (I use the scroll wheel a lot, and when you have a combobox active, it scrolls through the combobox, not the webpage. Sometimes, a change in the selection of a combobox actually results in a refresh or reload of some of the data on the page, so that gets really annoying.)
The other reason I click on nothingness is just habit, because of the above reason.
But... It's not exactly easy to find EVERY bug that there could be. A software tester is a software tester, not a typical user. Programmers are programmers, not typical users. They/We don't even always think to do things the way a user would do them.
I'm a programmer, and I know that I definitely (Firefox, I love your spell checker!) don't use the program the way our users would. If I want to get to a certain point in the program, I typically use the fastest route to get there, not always the most probable route that a user would take. After writing some code, I try to be thorough in testing the results, but since I don't use the program the way the user would use it, I don't always think of the scenarios where a bug might have crept up. (That's why software testers are so important, but I think we need to cut them a little slack, sometimes, too.)
true. I mean, maybe it's just me, but I sort of expected to learn something about zune by going to the website... um... but I did see some birds go psycho and dance around while on fire! can't say I expected to ever see that, in life.
But while I DID like the psycho bird video, I still don't know anything more about zune.
I just got a free laptop from someone that's about 7 or 8 years old. It had windows 98 (first edition) on it. So I reformatted and installed Slax (URL:http://www.slax.org/forum/viewtopic.php?t=132 96) - the KillBill edition, because I wanted to run a windows executable on it (and the KillBill version of Slax has Wine already on it. But I guess since the computer only had 64 meg of ram, it couldn't even install my executable. It was too slow, I guess.:( So I pretty much have a useless machine and a program I can't run, because I can't think of how else to solve the problem. I think the problem was KDE (and I love KDE, so this is a sad admission, to me).
Can Wine run in fluxbox? I haven't tried it since I'm a big KDE person, but is it worth a shot? I think Slax comes with fluxbox too. I'm not sure what the system requirements of this windows executable are, but if it requires more than 64 mb of RAM, am I out of luck? Or would just upping the size of the swap partition help?
Does anyone have any other solutions for me?
Hardware:
7-8 year old Compaq laptop
64 MB RAM
3 and a half GB of hard drive
Need:
a GUI interface, and wine because I want to run a windows executable
I'm from Iowa, too, so I thought the class action anti-trust lawsuit mentioned was worth reading up on (since I actually have purchased Microsoft stuff).
Microsoft's Predatory Response to GNU/Linux
142. GNU/Linux is an "open source" operating system that runs on Intel-compatible
PCs. Microsoft has targeted the competing operating system by pressuring Intel, as well as
various major OEMs such as Dell and Compaq, to boycott Linux. In late 2000, for instance,
Microsoft executive Joachim Kempin described his plan of retaliation and coercion to shut down
competition from Linux: "I am thinking of hitting the OEM harder than in the past with anti-
Linux actions" and will "further try to restrict source code deliveries where possible and be less
gracious when interpreting agreements - again without being obvious about it," continuing "this
will be a delicate dance."
Then it mentions Lindows/Linspire, and after that, it talks about the OEMs.
Here's a part I found interesting, from page 49:
Microsoft also used its MDAs ("Market Development Agreement") to lock OEMs in and competitors out by offering a
discriminatory price to the OEM in a later year provided (a) the OEM reached Microsoft's
imposed goal of Windows sales over competitive sales in the prior year and (b) renewed its
exclusionary contract with Microsoft for,the later year. This placed the OEM on a perpetual
treadmill, eliminating competition indefinitely. Microsoft continued these exclusionary terms at
least past April 2002.
(Please forgive spelling mistakes in the quotes. It's a weird PDF copy/paste thing, I think.)
Anyways, I'm particularly irked at those OEM's these days, because of a motherboard tattoo issue, but this sheds some light on the relationship between OEM's and Microsoft for me.
Personally, something about Microsoft and the OEM's really bugs me, but I can't put my finger on it. Is it the Monopoly issue people debate? or is it something else? I'm not sure. I guess it's good that there seems to be a standard (windows, and office), but I don't love that there's only one company that achieves that standard (Microsoft). I wish there could be a standard, but many companies and programs that achieve that standard. Then the people could really have a free choice about which company/program to go with. (Which is why I like linux, and the choices it gives me, so much.)
Whatever the issue is, though, it's enough to make me seriously consider building my next computer from scratch... So that I actually have a choice of whether to have a Microsoft Operating System on it or not (among other reasons).
I recently came across this exact issue. Some capacitors on the mobo leaked (definitely what I'd call a defect!), and I had to replace it. The thing that annoys me is that no one tells you ahead of time that the license for the OS is tied to the mobo, when you have a OEM version of the OS. (Sure, maybe something was said in the original agreement (and I'm the paranoid type who actually reads those things), but did I understand that the OS was tied to the motherboard it at the time? Obviously not. They need to be more explicit about that fact.) Why do they do that, anyways? Does the OEM distributor (HP, in my case) work with MS to give you a discounted price on the OS for these OEM versions in exchange for only being able to use it with that mobo? If so, I'd like to suggest that they let you pay MS the amount that the OEM'ers originally got as a discount in order to "free/release" that copy of the OS from that mobo, instead of having to pay full price for a new one altogether (or having to waste your money and several weeks (time wasn't a luxury for me in this case) on sending the computer in to the OEM people to get the motherboard re-tattooed).
In the end, after switching out the mobo, windows told me to reactivate. When that didn't work, I wasn't even given an option to talk to a real person. In near desperation, I clicked the "change product key" button (uh, you know, the one that says something like, "ONLY push this button if the MS person on the phone tells you to..."), and saw that the edit box was pre-populated with a key that was different than the product key that was on the side of my box. That was weird... I assume it was because the mobo had changed... Anyways, I just typed in the "real" product key that was on the sticker on the side of the box, and called the MS number again. Again, it didn't work, but this time I actually got to talk to a real person, and they gave me a new installation ID which worked fine.
What does it all mean? It means that that installed copy of XP is on it's last leg, because the installation CD's from HP don't work since the mobo still isn't "tattooed" (it's not in warranty anymore, so it probably would have costed some outrageous price, plus, I didn't have the luxury of time to do that, as I mentioned above). So the OEM's and MS win after all. I'll either have to buy a new OS sooner or later, or else send the machine in to HP to get the motherboard tattooed. But I still wish there was such a thing as a "release" fee which would untie a copy of the OS from the OEM so that you can install it on whatever machine you like.
For my next computer, I might have to build it from scratch so that I actually feel like I own all of MY OWN hardware and software, and I'm not chained to an OEM or MS like a slave (I'm not bitter... Really.) (Plus, then I won't have to pay the Microsoft tax if I decide to just put linux on it.)
all uppercase text slows reading by as much as half.
Very interesting... I think that's why I subconsciously skip over the ALL CAPS part of those EULA's... You'd think that someday the EULA writers would figure out that writing in all caps is counter productive. ALL CAPS sort of signifies that the text is important, but if it's too long, I'll just give up on reading it... Hence, I probably miss the most important parts of the agreements.
I use togglekeys specifically because I don't like Caps Lock. When I first started working where I do now, someone told me *never* to use caps lock. I didn't understand why until I started using Vim (which the aforementioned person uses all the time) a lot, where the uppercase and lower case letters mean something different. The beep that togglekeys gives me tells me if I've just accidentally bumped caps lock so that I can quickly remedy the situation before it causes annoyances for me in Vim.
Consequently, I've gotten quite good at typing entire sentences while holding down the shift key.
Some day I might try the remap of the escape key to the caps lock...
Shouldn't we hope that it doesn't leak? I don't really know much about it, but I'd imagine that Microsoft has patents and such all over their stuff. If it gets out, and similar looking code appears elsewhere (i.e. in open source code projects), couldn't there be lawsuits and accusations flying everywhere?
I agree that the curve should be the same for the gray stories as the green stories.
I like that the gray stories clump together, though, if there are more than one of them in a row. It's a good way to save space.
I feel like there are two ways to list the articles: by the time the story was submitted, or by the section the story comes from. If you want to keep the stories listed by time, I would suggest switching the curve on the gray stories to be like the curve on the green stories.
But if you were to leave the gray bar like it is now, it definitely seems like a footnote to me. In that case, you could list the articles by section, and each section gets one green start bar, and one gray end bar. The most important story could get the full description, whereas the less important ones could be in the gray underneath. Then you could bump that section block to the top when a new "most important" story gets added. The previous most important story could be bumped into a less important story....but I suppose then, you'd have to have a set number of "less important stories" in the gray section....and if it's a section that doesn't get many stories, you could have really old ones still listed....ok, so it's an idea, at least. I didn't say it was a good one or even a very well thought out idea...
It [our loftiest goal] should be to make the profession available to anybody who cares to pursue it. If that means that only 1/4 to 1/3 of the profession is composed of women, as long as that reflects the actual number of women who wants to do it, there's nothing wrong with that.
I agree. I'm also glad that my employer attained the lofty goal of making the profession available to me (a female computer programmer).
I know I went to an unusual (and small) college, as far as the ratio of guys to girls is concerned (about half of us CS majors were female), and I often heard that we were an unusual CS department, but it didn't truly phase me until after I graduated and was looking for a job. Finally I came to the realization that I was in the minority, but thankfully, I never suffered because of it. The first place I interviewed at hired me--which I'm very grateful for, but I still think is weird, because I'm the only girl in a department of 14 of us.
Some days, I think to myself, "Wow. If I didn't REALLY like what I do, I'd probably be miserably lonely."
(Other days, I think to myself, "I'm glad I'm the only female, because then I don't have to compete with anyone."--And I'm NOT talking about competing for the guys (I'd never date/marry anyone I work with), I'm talking about competing with any other girls in the sense of annoying competitions regarding appearances and other sorts of materialism. It's very freeing, sometimes, to be the only girl.)
I think one of the things I really liked about my college was that I didn't feel like I had to be a geek/nerd (take your pick) in order to be a CS major (although, I felt like I could be, if I wanted to be). I think (but I'm not sure, since I'm just speculating) that I would have felt more pressure to be geek/nerd-ish if I had gone to a bigger, more gender-lopsided school.
I think it mostly comes down to personality type (I'm an INTP personality type), and perhaps girls are less inclined to be of the personality type that enjoys things like programming.
Oh well. *shrug* I just enjoy doing what I do. And I'm glad my employer is ok with the fact that I'm a girl.
They would love a way to make it easy for content filters to block access for children.
. ..
It has to be voluntary.
My personal hope is that the pornography sites will voluntarily register at.xxx domains, and voluntarily remove themselves from.com domains. It would make it much easier for me to filter out the porn.
The fact that I get a lot of spam concerning porn, however, tells me that they (whoever "they" is... certainly not all porn sites, but some of them, for sure) don't really care that much about keeping their porn away from children or anyone else who doesn't want to deal with it.
My fear is that as long as it's voluntary, the porn sites will register at.xxx domains, *and* keep their.com domains. That would make it easier for people who want to view the porn to find their sites, and it would also make it easier for the porn sites to keep their sites within the search results of everyone else--thus hopefully still being able to exploit (or whatever it is "they" are trying to do) everyone else even though they conduct searches that filter out.xxx sites.
Slashdot Mirror
Um... When they suddenly need to use an old version of windows and are forced to use command.exe, where the tab button does not auto-complete things for them?
Someone mentioned that we could use nicknames, so yeah, I use a nickname. The trick comes when I try to continually separate my nickname-self from my real-self, in order to protect my privacy. It's hard work!
So, I'm sad that I feel the need to censor what I say on the internet. But what's worse is that I tend to carry that tendency over into real life. I find myself not divulging information about myself to other people, in real-life conversations, because the hesitancy to do so is so ingrained in me now... I've somehow come to a point of thinking that it's not anyone's right or business to know anything about me, unless I'm feeling particularly benevolent. But this is to the detriment of real-life relationships.
Does anyone else experience this issue? Does anyone have useful tips on resolving it?
That's the spirit! You've just got to unsay what you said before, then, when they look up your past, they'll pay more attention to the more recent comments. ;)
Er...hopefully. But I suppose actually meaning the "unsaid" comment might help...
I agree, wholeheartedly! :)
"00:01 would be correct in a 24-hour clock, but not in a 12-hour clock."
f m?id=97):
Interestingly, JK Rowling actually stated (http://www.jkrowling.com/textonly/en/news_view.c
Harry Potter and the Deathly Hallows will be published on Saturday 21st July 2007 at 00:01 BST in the UK and at 00:01 in the USA. It will also be released at 00:01 BST on Saturday 21st July in other English speaking countries around the world.
I might have been confused, too, had I not read the news from her site first. I'm not a fan of the 24-hour clock, but I do think we should call the first hour of the day 0:whatever AM, instead of 12:whatever AM. It definitely stops the confusion (for me, at least) before it even starts.
What if you wanted to sell the movie to someone else? Or even just give it to them? Now it still has your name on it...
Vista will solve that little "problem"
W indows%20Vista_Ultimate_English_36d0fe99-75e4-4875 -8153-889cf5105718.pdf
So... Is the quad core considered 4 processors? or just one?
I ask because the Vista EULA says:
2. INSTALLATION AND USE RIGHTS. Before you use the software under a license, you must assign that license to one device (physical hardware system). That device is the "licensed device." A hardware partition or blade is considered to be a separate device.
a. Licensed Device. You may install one copy of the software on the licensed device. You may use the software on up to two processors on that device at one time. Except as provided in the Storage and Network Use (Ultimate edition) sections below, you may not use the software on any other device.
From http://download.microsoft.com/documents/useterms/
(Emphasis added by me.)
Yay! That was my main objection to Vista, so far.
p x#Question3Label):
While I'm posting, does anyone know what this means (from http://www.microsoft.com/genuine/downloads/faq.as
Q: Will systems running Wine pass WGA validation?
A: Wine is an implementation of the Windows 3.x and Win32 APIs on top of X and Unix. When WGA validation detects Wine running on the system, it will notify users that they are running non-genuine Windows, and it will not allow genuine Windows downloads for that system. Users of Wine should consult the Wine community for Wine updates. It is important to note that Wine users, and other users of non-genuine Windows, can continue to download updates for most Microsoft applications from Microsoft application-specific sites, such as Office Update.
And another question I had: how often will Vista try to Validate itself? What if you don't have the internet on that machine? Would Validating involve calling MS every so often?
For me, at least, one of the reasons I "arbitrarily" click on nothingness (it's actually on purpose, but if you weren't inside my head, you wouldn't know why--but, here I'm about to tell you!) is because I want to make sure that the "nothingness" is the active part of the page, rather than some form that I forgot I had been typing in (try searching in firefox when a form is the active element in a web page. You end up typing the word you were intending to search for into the form, rather than actually searching), or worse, a combobox. (I use the scroll wheel a lot, and when you have a combobox active, it scrolls through the combobox, not the webpage. Sometimes, a change in the selection of a combobox actually results in a refresh or reload of some of the data on the page, so that gets really annoying.)
The other reason I click on nothingness is just habit, because of the above reason.
Exactly!
But... It's not exactly easy to find EVERY bug that there could be. A software tester is a software tester, not a typical user. Programmers are programmers, not typical users. They/We don't even always think to do things the way a user would do them.
I'm a programmer, and I know that I definitely (Firefox, I love your spell checker!) don't use the program the way our users would. If I want to get to a certain point in the program, I typically use the fastest route to get there, not always the most probable route that a user would take. After writing some code, I try to be thorough in testing the results, but since I don't use the program the way the user would use it, I don't always think of the scenarios where a bug might have crept up. (That's why software testers are so important, but I think we need to cut them a little slack, sometimes, too.)
Heh. I can see this going terribly wrong, if we're forced to return the hardware to wherever we bought it.
I agree that this hardware is licensed, not purchased.
X_________________ (sign here)
*oh wait! I mean, "license it", rather than buy it...
true. I mean, maybe it's just me, but I sort of expected to learn something about zune by going to the website... um... but I did see some birds go psycho and dance around while on fire! can't say I expected to ever see that, in life.
But while I DID like the psycho bird video, I still don't know anything more about zune.
that'd be nice, but can/does it run wine?
Can Wine run in fluxbox? I haven't tried it since I'm a big KDE person, but is it worth a shot? I think Slax comes with fluxbox too. I'm not sure what the system requirements of this windows executable are, but if it requires more than 64 mb of RAM, am I out of luck? Or would just upping the size of the swap partition help?
Does anyone have any other solutions for me?
Hardware:
7-8 year old Compaq laptop
64 MB RAM
3 and a half GB of hard drive
Need:
a GUI interface, and wine because I want to run a windows executable
Of particular interest to me was the mentions about linux and the OEMs in the complaint (http://www.iowasoftwaresuit.com/pdfs/Complaint.pd f).
From page 47:
Microsoft's Predatory Response to GNU/Linux
142. GNU/Linux is an "open source" operating system that runs on Intel-compatible PCs. Microsoft has targeted the competing operating system by pressuring Intel, as well as various major OEMs such as Dell and Compaq, to boycott Linux. In late 2000, for instance, Microsoft executive Joachim Kempin described his plan of retaliation and coercion to shut down competition from Linux: "I am thinking of hitting the OEM harder than in the past with anti- Linux actions" and will "further try to restrict source code deliveries where possible and be less gracious when interpreting agreements - again without being obvious about it," continuing "this will be a delicate dance."
Then it mentions Lindows/Linspire, and after that, it talks about the OEMs.
Here's a part I found interesting, from page 49:
Microsoft also used its MDAs ("Market Development Agreement") to lock OEMs in and competitors out by offering a discriminatory price to the OEM in a later year provided (a) the OEM reached Microsoft's imposed goal of Windows sales over competitive sales in the prior year and (b) renewed its exclusionary contract with Microsoft for ,the later year. This placed the OEM on a perpetual
treadmill, eliminating competition indefinitely. Microsoft continued these exclusionary terms at
least past April 2002.
(Please forgive spelling mistakes in the quotes. It's a weird PDF copy/paste thing, I think.)
Anyways, I'm particularly irked at those OEM's these days, because of a motherboard tattoo issue, but this sheds some light on the relationship between OEM's and Microsoft for me.
Personally, something about Microsoft and the OEM's really bugs me, but I can't put my finger on it. Is it the Monopoly issue people debate? or is it something else? I'm not sure. I guess it's good that there seems to be a standard (windows, and office), but I don't love that there's only one company that achieves that standard (Microsoft). I wish there could be a standard, but many companies and programs that achieve that standard. Then the people could really have a free choice about which company/program to go with. (Which is why I like linux, and the choices it gives me, so much.)
Whatever the issue is, though, it's enough to make me seriously consider building my next computer from scratch... So that I actually have a choice of whether to have a Microsoft Operating System on it or not (among other reasons).
I recently came across this exact issue. Some capacitors on the mobo leaked (definitely what I'd call a defect!), and I had to replace it. The thing that annoys me is that no one tells you ahead of time that the license for the OS is tied to the mobo, when you have a OEM version of the OS. (Sure, maybe something was said in the original agreement (and I'm the paranoid type who actually reads those things), but did I understand that the OS was tied to the motherboard it at the time? Obviously not. They need to be more explicit about that fact.) Why do they do that, anyways? Does the OEM distributor (HP, in my case) work with MS to give you a discounted price on the OS for these OEM versions in exchange for only being able to use it with that mobo? If so, I'd like to suggest that they let you pay MS the amount that the OEM'ers originally got as a discount in order to "free/release" that copy of the OS from that mobo, instead of having to pay full price for a new one altogether (or having to waste your money and several weeks (time wasn't a luxury for me in this case) on sending the computer in to the OEM people to get the motherboard re-tattooed).
In the end, after switching out the mobo, windows told me to reactivate. When that didn't work, I wasn't even given an option to talk to a real person. In near desperation, I clicked the "change product key" button (uh, you know, the one that says something like, "ONLY push this button if the MS person on the phone tells you to..."), and saw that the edit box was pre-populated with a key that was different than the product key that was on the side of my box. That was weird... I assume it was because the mobo had changed... Anyways, I just typed in the "real" product key that was on the sticker on the side of the box, and called the MS number again. Again, it didn't work, but this time I actually got to talk to a real person, and they gave me a new installation ID which worked fine.
What does it all mean? It means that that installed copy of XP is on it's last leg, because the installation CD's from HP don't work since the mobo still isn't "tattooed" (it's not in warranty anymore, so it probably would have costed some outrageous price, plus, I didn't have the luxury of time to do that, as I mentioned above). So the OEM's and MS win after all. I'll either have to buy a new OS sooner or later, or else send the machine in to HP to get the motherboard tattooed. But I still wish there was such a thing as a "release" fee which would untie a copy of the OS from the OEM so that you can install it on whatever machine you like.
For my next computer, I might have to build it from scratch so that I actually feel like I own all of MY OWN hardware and software, and I'm not chained to an OEM or MS like a slave (I'm not bitter... Really.) (Plus, then I won't have to pay the Microsoft tax if I decide to just put linux on it.)
all uppercase text slows reading by as much as half.
Very interesting... I think that's why I subconsciously skip over the ALL CAPS part of those EULA's... You'd think that someday the EULA writers would figure out that writing in all caps is counter productive. ALL CAPS sort of signifies that the text is important, but if it's too long, I'll just give up on reading it... Hence, I probably miss the most important parts of the agreements.
I use togglekeys specifically because I don't like Caps Lock. When I first started working where I do now, someone told me *never* to use caps lock. I didn't understand why until I started using Vim (which the aforementioned person uses all the time) a lot, where the uppercase and lower case letters mean something different. The beep that togglekeys gives me tells me if I've just accidentally bumped caps lock so that I can quickly remedy the situation before it causes annoyances for me in Vim.
Consequently, I've gotten quite good at typing entire sentences while holding down the shift key.
Some day I might try the remap of the escape key to the caps lock...
Shouldn't we hope that it doesn't leak? I don't really know much about it, but I'd imagine that Microsoft has patents and such all over their stuff. If it gets out, and similar looking code appears elsewhere (i.e. in open source code projects), couldn't there be lawsuits and accusations flying everywhere?
I agree that the curve should be the same for the gray stories as the green stories.
...but I suppose then, you'd have to have a set number of "less important stories" in the gray section. ...and if it's a section that doesn't get many stories, you could have really old ones still listed. ...ok, so it's an idea, at least. I didn't say it was a good one or even a very well thought out idea...
I like that the gray stories clump together, though, if there are more than one of them in a row. It's a good way to save space.
I feel like there are two ways to list the articles: by the time the story was submitted, or by the section the story comes from. If you want to keep the stories listed by time, I would suggest switching the curve on the gray stories to be like the curve on the green stories.
But if you were to leave the gray bar like it is now, it definitely seems like a footnote to me. In that case, you could list the articles by section, and each section gets one green start bar, and one gray end bar. The most important story could get the full description, whereas the less important ones could be in the gray underneath. Then you could bump that section block to the top when a new "most important" story gets added. The previous most important story could be bumped into a less important story.
I agree. I'm also glad that my employer attained the lofty goal of making the profession available to me (a female computer programmer).
I know I went to an unusual (and small) college, as far as the ratio of guys to girls is concerned (about half of us CS majors were female), and I often heard that we were an unusual CS department, but it didn't truly phase me until after I graduated and was looking for a job. Finally I came to the realization that I was in the minority, but thankfully, I never suffered because of it. The first place I interviewed at hired me--which I'm very grateful for, but I still think is weird, because I'm the only girl in a department of 14 of us.
Some days, I think to myself, "Wow. If I didn't REALLY like what I do, I'd probably be miserably lonely."
(Other days, I think to myself, "I'm glad I'm the only female, because then I don't have to compete with anyone."--And I'm NOT talking about competing for the guys (I'd never date/marry anyone I work with), I'm talking about competing with any other girls in the sense of annoying competitions regarding appearances and other sorts of materialism. It's very freeing, sometimes, to be the only girl.)
I think one of the things I really liked about my college was that I didn't feel like I had to be a geek/nerd (take your pick) in order to be a CS major (although, I felt like I could be, if I wanted to be). I think (but I'm not sure, since I'm just speculating) that I would have felt more pressure to be geek/nerd-ish if I had gone to a bigger, more gender-lopsided school.
I think it mostly comes down to personality type (I'm an INTP personality type), and perhaps girls are less inclined to be of the personality type that enjoys things like programming.
Oh well. *shrug* I just enjoy doing what I do. And I'm glad my employer is ok with the fact that I'm a girl.
. .
It has to be voluntary.
My personal hope is that the pornography sites will voluntarily register at .xxx domains, and voluntarily remove themselves from .com domains. It would make it much easier for me to filter out the porn.
The fact that I get a lot of spam concerning porn, however, tells me that they (whoever "they" is... certainly not all porn sites, but some of them, for sure) don't really care that much about keeping their porn away from children or anyone else who doesn't want to deal with it.
My fear is that as long as it's voluntary, the porn sites will register at .xxx domains, *and* keep their .com domains. That would make it easier for people who want to view the porn to find their sites, and it would also make it easier for the porn sites to keep their sites within the search results of everyone else--thus hopefully still being able to exploit (or whatever it is "they" are trying to do) everyone else even though they conduct searches that filter out .xxx sites.