Browsers are like car stereos: some people will always go out-of-the-way to install an aftermarket car stereo; others will only install an aftermarket car stereo when it has a tangible feature that their existing one doesn't have. My parents just wait until they buy a new car!
Yes, if they don't use any Linux/Unix-specific features. User-space part of FUSE, however, will have be modified (because there's no fork() in Windows).
Have you ever played with Cygwin? Back when I was in college, (about 5 years ago,) all of my assignments had to run on my school's Unix system. I would develop on Windows using my favorite IDE, and compile & run locally under Cygwin. When the program was complete, running it on the school's Unix system was a trivial matter.
I think Cygwin has a Unix-style fork(), but I'm not 100% sure. I didn't know about Cygwin until after I programmed with fork(). (On a side note, after my experience with fork(), I thank Bill Gates every day I use threading in.Net.)
Consider seeking a sizable "career company." These companies often put a priority on existing for the sake of providing their employees jobs, and like having a few greybeards who are very familar with their codebase. As long as you realize that your job is to get things done, you'll always be considered valuable. (Just don't become someone who's attitude is "My job is to keep my job.")
I had breakfast with Crunch last Sunday. The thing he wants most is a job where his employers won't cheat him, and can overlook his past. IMO, this also requires an employer that has the patience for his eccentricities. Even though he's over-the-hill, he still has the mind of a young person.
Both excellent escape routes, provided of course that cracking DRM isn't regarded as a felony in itself (whether there's a content-owner present or not), and if the escrow outfit itself doesn't go tits-up.
Trouble is, there's really no foolproof way to ensure that DRM both can and WILL be expired. Even so, it'd be better than DRM-forever.
I agree with you. Consider the following: The escrow agency could be controlled by the government. With regard to cracking encryption; as computers become faster, the time needed to brute-force is reduced.
Such a system is impossible; how does it know if the CD I burn is for personal use? Likewise, what if I have a legitimate use for 100,000 liscensed playback devices?
It is impossible to objectivly judge the intent of a consumer; thus content creators need to build a trust-based relationship with their sponsors. DRM inheritly breaks such a trust relationship.
We're not talking about zunes that let you share a song which expires after a few plays or a few days (which ever comes first.) Or windows media devices that require regular docking otherwise the music will cease to function. We're talking about the ability to legally download music and literally give it to any of 5 computer users. Or burn copies and spread them infinitely. Some kids use maybe two of their 5 licenses on other computers in the house, the rest usually go to their friends. (Legal or not, it still lets you.)
I'd rather see expiring DRM. For example, the DRM is uber-restrictive the first month the song is released, then slowly grants additional freedoms. After 2-3 years, the DRM expires and you can do what you want.
The fault, for the vast majority of PHP security problems, is completely Zend's. Zend needs to give security priority over backwards compatibility, and get rid of all of their problems that developers repeatedly trip up on.
The above reason is why I gave up on PHP. I see it as insecure and difficult to maintain.
As a result, I decided to make my own web development platform. It's easier then you think!
If this rule is allowed to take effect (translation: a bunch of cableco lobbists don't pop up and stop it) soon hooking up digital cable will be as easy as hooking up analog cable. The converter box can be built into the TV the same way we transitioned from having to get a box from the cable company twenty years ago to having "cable ready" TV's. It would help clear the way for people to not have to pay "per box" for their service. DVR recorders can be built that can tune all the channels themselves.
I think we're more likely to see net neutrality; while the cable company is off fighting CableCard, we'll all go buy cheap HTPCs.
Heck, if the Daily Show were on iTunes as soon as it broadcasted; I'd cancel my Comcast TV subscription NOW.
I assume you're using a catch-all email account, like I do. I get about 100 SPAMs/bounces a day. Here are techniques that I use:
My reply-to address doesn't go to my catch-all. This way, all undeliverable bounces in my catch-all are only from SPAM.
Almost everyone who I email on a regular basis figures out my REAL email address, thus the special account for my reply-to address has very little SPAM.
I use Apple's mail program instead of Microsoft's mail programs. It's much easier to see what's SPAM because Apple displays the "TO" and "FROM" addresses without me having to open the email.
There's a reason for this! They don't want to completely close the door to making an offer to you someday in the future, should various circumstsances change.
It's still rude to not send a response. A better approach is what happened with a friend of mine; the company informed him that they were planning on interviewing other candidates and might contact him in 3-5 months. 4 months later, he got the job.
What's funny is that the one company that didn't send me a response later hired (and fired) my college's big-time drug dealer who was caught cheating on a major assignment! Karma is such a bitch.
The flip side of this coin is, part of the interview may have been finding out whether or not you do due diligence when receiving a new project.
The hiring manager may not be able to train his customer base to give a complete specification, but he can always try to hire people who make a habit of getting a complete specification before they begin working. You may have lost the job because you failed to ask what kind of code the manager wanted, not because you failed to read his mind or guess his intent.
In both cases it wasn't a manager. I do treat interviews as two-way streets and am incredibly selective about who I work for.
In the first case, the developer interviewing me was still under the assumption that "all good code must be as fast as possible, at all costs." I prefer not to work within such constraints, as my time is valuable. The company also had a condesending attitude; in another discussion a senior employee was condescending to a junior employee; later, the founder also indicated that he spent a significant amount of time arguing with other employees.
In the second case, we established that I was writing pseudocode where error checking wasn't needed. Afterwards, he then dinged me for not performing null checks.
Your problem is that you never *asked* in the first place. I *always* ask first what are the trade-offs (eg. performance, reliability, whatever else that may seem relevant to the problem) that they want to see in my answer. In the real world, users never really tell you what they want (and often they don't know themselves). IMHO, it's part of the job. By asking first, it shows that you think first, before acting.
My problem? Do not forget that interviews are two-way streets; I am quite selective about who I work for! In both cases the people interviewing me were unprofessional.
I'll never forget the manager who told me that she was having trouble keeping people, then immediatly offered me a starting salary less then my first internship!
I've been on both sides of the interview table and there are as many idiots hiring as there are looking for jobs. The worst interviewers are the ones who are convinced of their own omniscience and feel the need to prove it. Then there are the ones who feel threatened by the possibility that you might be better than they are, definitely don't expect a job from these clowns. And the ones who put you on the spot by asking you to solve a stupid mensa riddle, give me a break. It's a tough exercise either way and it's disappointing when you know that you could do the job but also know that it's not going to happen.
I find in those cases I'm better off working for someone else. Why should I work for someone who has a superiority complex? It'll just end up being a situation where I can do no right.
Consider that the problem could be you. When I've been "corrected" on coding problems in the past; it typically indicated that the interviewer was asking the wrong questions. Don't expect people to write perfect error-checking, choose your favorite algorithm, naming convention, ect.
For example, I once had to write an algorithm that had to handle money. I chose a slow and reliable algorithm, and the interviewer chastised me to not writing the fastest once possible. (He never told me he was looking for speed.) When I politley explained that I always choose a reliable algorithm that can be replaced with a fast one, as needed, he refused to listen to me, and probably thought that I was a risk to his code base.
In another internview, I was chastised for not performing extensive (and redundant) input checking. Typically, in whiteboard coding where the goal is to demonstrate an algorithm, one does not worry about minor details. Again, the interviewer probably though that I was a risk to his code base because my first reaction to his problem wasn't to follow his error-checking style.
So, perhaps instead of correcting someone's code, ask them why they wrote it the way they did. The answer to, "Why did you choose a slow algorithm?" or "Why aren't you performing null checking?" could be valid because the interviewer thinks you're looking for something else.
Hasn't the supreme court tossed out everyone of the laws passed in states that old Jackie boy worked on?
When I turned 18, I was living in MA. Around that time, a friend's father was an exec for a local theater chain. Their clerks were giving us trouble whenever we'd try to buy tickets for R-rated movies.
I complained to my friend's father about the amount of difficulty that we were having legally buying R-rated tickets. It turns out that in MA, people DO call the police when they see underage people sneaking into R-rated movies.
My guess is that there is a desire to make an equivilent rules for volient video games. Frankly, if someone's able to get theaters to enforce R-rated movies, someone else will get stores to enforce restrictions on violent video games.
My guess is that the bug was "planted" by the coin being placed directly in the contractor's pocket. This could occur when someone casually bumps into the contractor. As a result, the bug is hard to detect. Let's face it, if you found a coin in a random pocket, would you suspect that it's a bug?
After a disaster, you need something that's quick to set up, and very reliable. Solar, as altruistic as it sounds, is just going to be a distraction from actually helping people in need. You have to wait for batteries to charge, wait for sunlight, aim the panels...
Why not use a diesel generator? It's cheap, safe to store, proven technology, and can be "solar" if you choose to use bio-fuels. Besides, when you use diesel instead of solar, you'll have something that "just works."
Slashdot Mirror
Browsers are like car stereos: some people will always go out-of-the-way to install an aftermarket car stereo; others will only install an aftermarket car stereo when it has a tangible feature that their existing one doesn't have. My parents just wait until they buy a new car!
Have you ever played with Cygwin? Back when I was in college, (about 5 years ago,) all of my assignments had to run on my school's Unix system. I would develop on Windows using my favorite IDE, and compile & run locally under Cygwin. When the program was complete, running it on the school's Unix system was a trivial matter.
I think Cygwin has a Unix-style fork(), but I'm not 100% sure. I didn't know about Cygwin until after I programmed with fork(). (On a side note, after my experience with fork(), I thank Bill Gates every day I use threading in .Net.)
Consider seeking a sizable "career company." These companies often put a priority on existing for the sake of providing their employees jobs, and like having a few greybeards who are very familar with their codebase. As long as you realize that your job is to get things done, you'll always be considered valuable. (Just don't become someone who's attitude is "My job is to keep my job.")
There's no stairs to get to the second floor!
I had breakfast with Crunch last Sunday. The thing he wants most is a job where his employers won't cheat him, and can overlook his past. IMO, this also requires an employer that has the patience for his eccentricities. Even though he's over-the-hill, he still has the mind of a young person.
Which is why I chose to buy a smaller 16x9 TV instead of a larger 4x3; widescreen DVDs end up being bigger and looking better.
I agree with you. Consider the following: The escrow agency could be controlled by the government. With regard to cracking encryption; as computers become faster, the time needed to brute-force is reduced.
Two ways: Either there's no one to sue for releasing a DRM-cracker; or the key is stored in an industry-wide escrow.
Such a system is impossible; how does it know if the CD I burn is for personal use? Likewise, what if I have a legitimate use for 100,000 liscensed playback devices?
It is impossible to objectivly judge the intent of a consumer; thus content creators need to build a trust-based relationship with their sponsors. DRM inheritly breaks such a trust relationship.
I'd rather see expiring DRM. For example, the DRM is uber-restrictive the first month the song is released, then slowly grants additional freedoms. After 2-3 years, the DRM expires and you can do what you want.
The above reason is why I gave up on PHP. I see it as insecure and difficult to maintain.
As a result, I decided to make my own web development platform. It's easier then you think!
I think we're more likely to see net neutrality; while the cable company is off fighting CableCard, we'll all go buy cheap HTPCs.
Heck, if the Daily Show were on iTunes as soon as it broadcasted; I'd cancel my Comcast TV subscription NOW.
I assume you're using a catch-all email account, like I do. I get about 100 SPAMs/bounces a day. Here are techniques that I use:
How long do you think it'll be until MS makes their own PC?
It's still rude to not send a response. A better approach is what happened with a friend of mine; the company informed him that they were planning on interviewing other candidates and might contact him in 3-5 months. 4 months later, he got the job.
What's funny is that the one company that didn't send me a response later hired (and fired) my college's big-time drug dealer who was caught cheating on a major assignment! Karma is such a bitch.
The iPhone is technology, it's price will drop just like all other phones and computers. Frankly, if it had a hard drive, I'd buy one.
In both cases it wasn't a manager. I do treat interviews as two-way streets and am incredibly selective about who I work for.
In the first case, the developer interviewing me was still under the assumption that "all good code must be as fast as possible, at all costs." I prefer not to work within such constraints, as my time is valuable. The company also had a condesending attitude; in another discussion a senior employee was condescending to a junior employee; later, the founder also indicated that he spent a significant amount of time arguing with other employees.
In the second case, we established that I was writing pseudocode where error checking wasn't needed. Afterwards, he then dinged me for not performing null checks.
My problem? Do not forget that interviews are two-way streets; I am quite selective about who I work for! In both cases the people interviewing me were unprofessional.
I'll never forget the manager who told me that she was having trouble keeping people, then immediatly offered me a starting salary less then my first internship!
I find in those cases I'm better off working for someone else. Why should I work for someone who has a superiority complex? It'll just end up being a situation where I can do no right.
Every year or so I find a Canadian coin in my pocket. A lot of people just pass of their loose pocket change when returning to the states.
Consider that the problem could be you. When I've been "corrected" on coding problems in the past; it typically indicated that the interviewer was asking the wrong questions. Don't expect people to write perfect error-checking, choose your favorite algorithm, naming convention, ect.
For example, I once had to write an algorithm that had to handle money. I chose a slow and reliable algorithm, and the interviewer chastised me to not writing the fastest once possible. (He never told me he was looking for speed.) When I politley explained that I always choose a reliable algorithm that can be replaced with a fast one, as needed, he refused to listen to me, and probably thought that I was a risk to his code base.
In another internview, I was chastised for not performing extensive (and redundant) input checking. Typically, in whiteboard coding where the goal is to demonstrate an algorithm, one does not worry about minor details. Again, the interviewer probably though that I was a risk to his code base because my first reaction to his problem wasn't to follow his error-checking style.
So, perhaps instead of correcting someone's code, ask them why they wrote it the way they did. The answer to, "Why did you choose a slow algorithm?" or "Why aren't you performing null checking?" could be valid because the interviewer thinks you're looking for something else.
When I turned 18, I was living in MA. Around that time, a friend's father was an exec for a local theater chain. Their clerks were giving us trouble whenever we'd try to buy tickets for R-rated movies.
I complained to my friend's father about the amount of difficulty that we were having legally buying R-rated tickets. It turns out that in MA, people DO call the police when they see underage people sneaking into R-rated movies.
My guess is that there is a desire to make an equivilent rules for volient video games. Frankly, if someone's able to get theaters to enforce R-rated movies, someone else will get stores to enforce restrictions on violent video games.
My guess is that the bug was "planted" by the coin being placed directly in the contractor's pocket. This could occur when someone casually bumps into the contractor. As a result, the bug is hard to detect. Let's face it, if you found a coin in a random pocket, would you suspect that it's a bug?
After a disaster, you need something that's quick to set up, and very reliable. Solar, as altruistic as it sounds, is just going to be a distraction from actually helping people in need. You have to wait for batteries to charge, wait for sunlight, aim the panels...
Why not use a diesel generator? It's cheap, safe to store, proven technology, and can be "solar" if you choose to use bio-fuels. Besides, when you use diesel instead of solar, you'll have something that "just works."
I'd buy one if it had a hard drive... I prefer carrying my entire music collection in an 80-gig player then resynching every few days.