I tried to get a hold of you by email, but it's hidden? Anyway, I was curious about how this 'eldercare consulting' works. How you actually got involved in the industry, how you found your first client, how you charged people, what kinds of things did you run across, and what not.
I've actually managed to lose weight at my current job. Of course, I had to make it a focus point. I planned my meal for the whole day so I know what I could or couldn't eat. I barely keep any food in my house, expect for the food stuff I needed to make said meals with. And I still eat out a lot. Definitely a lot more than I did even in college. I just make sure that it fits into my food 'budget'.
It's doable to lose weight, even in IT, it just requires some small changes to your habits and a little bit of will.
But there is no official NASA business in Mississippi. As far as I know, FAA does not have any extra offices in Mississippi. So why station the first 'space' law school in Mississippi?
Why the University of Mississppi? Isn't that like studying oceanography in Colorado? Wouldn't it be more prudent to study in Florida, Texas? Hell, even Alabama is a better choice.
The GPL enforces what it considers 'freedom'. It traps whatever gets into its license, like a venus flytrap. That is not freedom.
It's like holding someone hostage at Buckingham Palace and then stating it's not a hostage situation since the palace is so big and nice and extravagant. It may be a nicer situation than being held hostage than in someone's basement, but it's still a hostage situation. That's the GPL.
Not the greatest analogy, but close.
GPL - Basically, as basically as it can be stated, if you modify the code source, " . ..However, nothing other than this License grants you permission to propagate or modify any covered work." If you start in gpl, you're stuck in gpl. http://www.gnu.org/copyleft/gpl.html/
Because I have. I had this idea two years ago, and started reading Myspace, Livejournal, Facebook, Xanga, etc., TOS to see what actually is and isn't allowed on their networks. IANAL, but according to what I have read/seen, most have rules against automatically posting and receiving information without directly logging in through their particular sites. I remember one TOS actually stating that screen scraping and scripting of sites would not be permitted.
So,what's the business plan, then? Ignore the TOS, under the belief of better to ask for forgiveness than permission, or hope that their lawyers aren't as good as the ones you'll be needing?
So, the whole point is to treat operating environments and systems like files? Interesting. But I'm not sure that is any better than just making an image of the system you want and installing it directly to the hardware itself, than go through virtualization. Though, it would be useful if it virtualizes radically different enviroments.
I'm sorry. I'm feeling really slow today, so maybe that's why I don't get it. How does one make a virtual application? I mean, isn't the whole point of virtualization is that it emulates a layer of computing so that changes to the applications aren't needed?
I mean, I read the how to and the examples, and it doesn't seem to be any different than from developing on a non-virtual environment. Somebody, please help me make sense of this!
I just looked over the list again, and while it doesn't necessarily feel like a US-specific list, the editors were lazy enough forming the list I don't know what their point is. About 10 to 20 items listed all came out in 2004. Granted, the tail end of 2004, but still 2004.
Security and correctness are things you cannot ignore except in extreme cases. Security is particularly important to nail down, because it can result in your customers losing data (even data not pertaining to your app), which is the first no-no of software.
Yes, you are correct, if you are still writing the software, and you notice the security and correctness are being compromised. If you're doing final testing (say, 3 weeks before gold cd goes out), or if you've already sent the software out, you can't just rush out a fix, especially without seriously sitting down and thinking things through.
In this case, I'd say proper fix is to disable hyperthreading by default, and make sure the user is aware of the hardware bug/consequence of using HT when they decide to turn it on. You need to let the user decide if they're willing to accept the security risk or not.
The Linux Kernel Developers may decide otherwise, but that's how I'd call it if it was in my shop. It's a hardware problem and the software fix is not obvious.
That's pretty much what I've been saying. Linus is doing the correct thing and Colin Percival is being too hasty with things.
... that's developped a product for a decade and got spooned by a new OSS product in less than 2 years in marketshare has so many things to its advantage.
Marketing. That's basically why FireFox has more downloads than Opera right now. It's not necessarily a sign of one product being better than another.
Firefox is what, less than a year or two in age? Give'em a break!
Firefox is older than 2 years, it's just had the name Firefox for about 2 years. It existed in Mozilla. It just got spun out.
Opera 8 reached, what, a tad over a million downloads? That's less than a tenth of the firefox 1.0 downloads. So it might be better in some areas, but they don't make enough noise to really be noticed by the public...
You seem to be forgetting other venues besides the desktop. Opera does quite while on mobile applicances (PDA, Cellphones), something Firefox just got started on, and is having a bit of trouble with at the moment.
He also doesn't mention the HIGHLY obnoxious "best guess" rendering - Opera STARTS to render a page as soon as it has any data at all, then re-renders as more data comes in. Net result? You can play tag with the page elements as they move around your screen. In my experience, Firefox starts to render pages a tick or two after Opera, but tends to finish rendering a tick or two before Opera.
That's actually changable. You can change when the page is rendered in the Windows tab under Preferences.
By your reasoning, Y2K shouldn't have been addressed until after the fact.
Please carefully reread what I said. I said
I would think that would only be adviseable only if you (internally) found the bug/security problem. I would put up a notice saying I've heard of this situation, and maybe even come up with an idea for the fix, but definitely wouldn't implement it until I could prove or see proof that said problem exists.
If you internally find the bug/hole, fix it. If you can proof to myself said security bug/hole is there, fix it. I never said wait until it's too late. Perhaps I should have made myself more clear on this point.
I'm sorry. I don't know who modded me funny, but I wasn't actually trying to be funny.
From the little bit I understand from the paper (which, when this story was first posted on Slashdot May 13th, wasn't publicly available), it's an extremely low level attack that depends on certain process switching back and forth, without emptying cache. (I think that's the base of it.)
From what I've learned in software writing, is that it's preferrable to wait and see how much and how bad your software runs or has problems before you start charging into the situation to fix it. Especially something as low level as this, which could have unseen side effects. Especially since this (to me, at least) seems to be more of a hardware problem than software, per se. (But, of course, I could be wrong.)
Its better to just fix it and be safe than wait and see if something happens later.
I would think that would only be adviseable only if you (internally) found the bug/security problem. I would put up a notice saying I've heard of this situation, and maybe even come up with an idea for the fix, but definitely wouldn't implement it until I could prove or see proof that said problem exists.
p.s. Microsoft's reaction is slightly different than what you describe. Microsoft didn't seem to care about bug fixes to IE, period, only fixing them when the griping got too loud and the public started paying more attention to Firefox. There was no motivation to fix IE, not just a 'wait and see' type attitude.
If I remember correctly, there hasn't been a shown exploit for this yet. It's better to wait and see before fixing something that may not matter later.
Wrong.
Nintendo actually did backwards compatibility before Sony did, with the Gameboy line! This, however, is the first time Nintendo could do with their main console, as nobody wanted to continue to develop for cartileges anymore (it's expensive to do so.)
Responding to a trollish post, but I'll bite:
If you ever get the chance to speak to Mark Cuban personally, he'd be the first person to tell you how lucky he was to get bought out by Yahoo. I know this because he's said/written it before!
And that's why Paul Graham basically states this in his article that about 90% of startups fail, because of various reasons. He's just merely stating that, for most recent grads, it's not as riskly/potentially damaging now than later in life.
Your argument is right, your examples are a bit wrong, however. The Magneto you're referring to is an elseworld one, one of the more well-known elseworld called 'The Age of Apolcaypse'.
However, since Magneto is such a hardliner that even though his intentions are alright, his actions to achieve his beliefs makes him a villian.
http://en.wikipedia.org/wiki/Magneto_(comics) wiki link for info on magneto
I was thinking the exact same thing. This thing would be killer at museums and other open floors. It seems portable enough to just rent one or two to install in cases of increased traffic at certain venues.
Slashdot Mirror
I'm partial to Eureka myself. But it really isn't hardcore sci-fi, but more like sci-fi comedy.
My googling fu is weak today. I can't find the lawsuit you're talking about. Mind providing a link or general timeline when this happened?
I tried to get a hold of you by email, but it's hidden? Anyway, I was curious about how this 'eldercare consulting' works. How you actually got involved in the industry, how you found your first client, how you charged people, what kinds of things did you run across, and what not.
I've actually managed to lose weight at my current job. Of course, I had to make it a focus point. I planned my meal for the whole day so I know what I could or couldn't eat. I barely keep any food in my house, expect for the food stuff I needed to make said meals with. And I still eat out a lot. Definitely a lot more than I did even in college. I just make sure that it fits into my food 'budget'. It's doable to lose weight, even in IT, it just requires some small changes to your habits and a little bit of will.
Sorry. I thought that was in Lousiana. Close, though.
But there is no official NASA business in Mississippi. As far as I know, FAA does not have any extra offices in Mississippi. So why station the first 'space' law school in Mississippi?
Why the University of Mississppi? Isn't that like studying oceanography in Colorado? Wouldn't it be more prudent to study in Florida, Texas? Hell, even Alabama is a better choice.
The GPL enforces what it considers 'freedom'. It traps whatever gets into its license, like a venus flytrap. That is not freedom.
It's like holding someone hostage at Buckingham Palace and then stating it's not a hostage situation since the palace is so big and nice and extravagant. It may be a nicer situation than being held hostage than in someone's basement, but it's still a hostage situation. That's the GPL.
Not the greatest analogy, but close.
In what universe is the BSD license less free than the GPL, of any version???
BSD - Basically, do whatever you want, just include the credits of previous contributors. http://www.freebsd.org/copyright/license.html/
GPL - Basically, as basically as it can be stated, if you modify the code source, " . . .However, nothing other than this License grants you permission to propagate or modify any covered work." If you start in gpl, you're stuck in gpl. http://www.gnu.org/copyleft/gpl.html/
Which one is more free?I still go to the arcade and we still stack quarters/change to indicate who is next on DDR and Tekken. Whatever is he talking about?
Because I have. I had this idea two years ago, and started reading Myspace, Livejournal, Facebook, Xanga, etc., TOS to see what actually is and isn't allowed on their networks. IANAL, but according to what I have read/seen, most have rules against automatically posting and receiving information without directly logging in through their particular sites. I remember one TOS actually stating that screen scraping and scripting of sites would not be permitted.
So,what's the business plan, then? Ignore the TOS, under the belief of better to ask for forgiveness than permission, or hope that their lawyers aren't as good as the ones you'll be needing?
So, the whole point is to treat operating environments and systems like files? Interesting. But I'm not sure that is any better than just making an image of the system you want and installing it directly to the hardware itself, than go through virtualization. Though, it would be useful if it virtualizes radically different enviroments.
I'm sorry. I'm feeling really slow today, so maybe that's why I don't get it. How does one make a virtual application? I mean, isn't the whole point of virtualization is that it emulates a layer of computing so that changes to the applications aren't needed?
I mean, I read the how to and the examples, and it doesn't seem to be any different than from developing on a non-virtual environment. Somebody, please help me make sense of this!
I just looked over the list again, and while it doesn't necessarily feel like a US-specific list, the editors were lazy enough forming the list I don't know what their point is. About 10 to 20 items listed all came out in 2004. Granted, the tail end of 2004, but still 2004.
The DS came out in 2004.
Yes, you are correct, if you are still writing the software, and you notice the security and correctness are being compromised. If you're doing final testing (say, 3 weeks before gold cd goes out), or if you've already sent the software out, you can't just rush out a fix, especially without seriously sitting down and thinking things through.
In this case, I'd say proper fix is to disable hyperthreading by default, and make sure the user is aware of the hardware bug/consequence of using HT when they decide to turn it on. You need to let the user decide if they're willing to accept the security risk or not. The Linux Kernel Developers may decide otherwise, but that's how I'd call it if it was in my shop. It's a hardware problem and the software fix is not obvious.
That's pretty much what I've been saying. Linus is doing the correct thing and Colin Percival is being too hasty with things.
Marketing. That's basically why FireFox has more downloads than Opera right now. It's not necessarily a sign of one product being better than another.
Firefox is what, less than a year or two in age? Give'em a break!
Firefox is older than 2 years, it's just had the name Firefox for about 2 years. It existed in Mozilla. It just got spun out.
Opera 8 reached, what, a tad over a million downloads? That's less than a tenth of the firefox 1.0 downloads. So it might be better in some areas, but they don't make enough noise to really be noticed by the public...
You seem to be forgetting other venues besides the desktop. Opera does quite while on mobile applicances (PDA, Cellphones), something Firefox just got started on, and is having a bit of trouble with at the moment.
That's actually changable. You can change when the page is rendered in the Windows tab under Preferences.
Please carefully reread what I said. I said
I would think that would only be adviseable only if you (internally) found the bug/security problem. I would put up a notice saying I've heard of this situation, and maybe even come up with an idea for the fix, but definitely wouldn't implement it until I could prove or see proof that said problem exists.
If you internally find the bug/hole, fix it. If you can proof to myself said security bug/hole is there, fix it. I never said wait until it's too late. Perhaps I should have made myself more clear on this point.
From the little bit I understand from the paper (which, when this story was first posted on Slashdot May 13th, wasn't publicly available), it's an extremely low level attack that depends on certain process switching back and forth, without emptying cache. (I think that's the base of it.)
From what I've learned in software writing, is that it's preferrable to wait and see how much and how bad your software runs or has problems before you start charging into the situation to fix it. Especially something as low level as this, which could have unseen side effects. Especially since this (to me, at least) seems to be more of a hardware problem than software, per se. (But, of course, I could be wrong.)
Its better to just fix it and be safe than wait and see if something happens later.
I would think that would only be adviseable only if you (internally) found the bug/security problem. I would put up a notice saying I've heard of this situation, and maybe even come up with an idea for the fix, but definitely wouldn't implement it until I could prove or see proof that said problem exists.
p.s. Microsoft's reaction is slightly different than what you describe. Microsoft didn't seem to care about bug fixes to IE, period, only fixing them when the griping got too loud and the public started paying more attention to Firefox. There was no motivation to fix IE, not just a 'wait and see' type attitude.
If I remember correctly, there hasn't been a shown exploit for this yet. It's better to wait and see before fixing something that may not matter later.
Wrong.
Nintendo actually did backwards compatibility before Sony did, with the Gameboy line! This, however, is the first time Nintendo could do with their main console, as nobody wanted to continue to develop for cartileges anymore (it's expensive to do so.)
If you ever get the chance to speak to Mark Cuban personally, he'd be the first person to tell you how lucky he was to get bought out by Yahoo. I know this because he's said/written it before!
And that's why Paul Graham basically states this in his article that about 90% of startups fail, because of various reasons. He's just merely stating that, for most recent grads, it's not as riskly/potentially damaging now than later in life.
However, since Magneto is such a hardliner that even though his intentions are alright, his actions to achieve his beliefs makes him a villian. http://en.wikipedia.org/wiki/Magneto_(comics) wiki link for info on magneto
I was thinking the exact same thing. This thing would be killer at museums and other open floors. It seems portable enough to just rent one or two to install in cases of increased traffic at certain venues.