If you are on a public street, then there is no expectation of privacy. If you don't have a sign displaying your name, then it's a bit hard to map the image to you unless you're listed in the yellow pages, which in that case, defeats the idea of privacy.
The same way we have gotten used to ads on websites, the same way we will get used to ads in RSS feeds.
We will train ourselves to ignore that ad above that says "Test your skills with Java(TM) and win an Ipod. Take the challenge for Java(TM)". Ads are a must for many, if many bloggers didn't have some type of revenue coming in to support their sites, then many would not exist. Financial support is a necessity for many. So, we will get over that as we have gotten over the RSS feeds.
And if it's in XML, I'm sure someone will write a stylesheet to parse it out.
VR gear. A headmount display that puts you literally into the gameplay. All you see is the world around you and the gyroscopes can be mounted in the headgear, so you turn more with your head and body, than the controller, and the controller could be used for activating weapons and forward/backward movement. It falls in line to what he said "revolutionary, but nothing technically new". VR gear has been around for over a decade, I believe, and have seen it used in the big arcades as far back as 1997 (I used to work at XS New York). I just hope they have resolved the cooling issues by the time it's launched.
Other ideas, some other simpler force feedback device.
staring Christopher Lambert with short blonde hair, set in a post-apocalypitic world. Now that was a bad movie, and the overly used sex scenes didn't add to the movie, though were enjoyable for there moments of interlude.
At a small company I worked at with 3 other developers, and 2 designers we did not use a version control system because: * we didn't think of installing one, even though a number of negative things happened as a result of not having one. * had difficulty installing CVS. After reading the docs to install CVS, I still had trouble getting the thing to work and skipped it completely. * we were naive. not everyone who is programming, especially those new to the scene, know about version control.
I'm not saying these are legitimate reasons, these are excuses for a poor development environment. I have learned from this and have made changes to make my developing better.
The problems with Javascript doing form validation are: * that it can be turned off, so you NEED server side validation anyway, * the interactiveness is not necessarily helpful if the developers do not denote locations for users to plainly see, which requires more work to implement, but can be easily setup server-side,
Though I do agree with your assumption on it, it's best to deal with just one form of validation.
You say web designer, so I will assume you want to go for a more visual development, than a programming/scripting side of it.
With that in mind I would suggest the following:
HTML/CSS as you're doing now. There's no way around this.
Javascript You should learn this and as other have said already, use it sparingly. Form validation is one example where it's been used heavily, and should probably not be used. But javascript has other uses such as pull down menus,floating content, image rollovers and other things. At this point in 2005, most of the code you will need is available on many sites you can download from. The most you need to do is understand the code and modify as needed.
Flash, and maybe Director There's plenty of Flash on the web, most of it is useless especially when it's used for splash pages. What you need to do is learn when to use it or more so when NOT to use it.
Now for the theory. This seperates the person who was good with crayons as a kid from someone who can seriously understand what a website means. You need to learn concepts beyond just simple design. You need to understand how web interfaces work and how users relate to them. Read the articles at use-it.com to get a initial understanding of this. You should understand concepts like the "page fold" and how does it relate to content on the page, how much time should a page take to load, most common page dimensions, what actions people commonly do under certain situations and what link colors people are used to and how should links look like. All of this mainly falls under Visual Information design. You have to know how to communicate what the information is trying to say. If you're the type who likes to go for the big flashy images, then you missed the whole point. If you start off your introduction with "I'm a print designer" or "I come from the print industry" then you need to stop, turn around and go back to the books.
Now for the tougher part. Adding in the developer side of things.
If you want to become well rounded, the main questions to ask are:
What do you expect to gain from doing or learning the developer aspect of it?
Do you want to do backend development or at least just have an understanding of the development?
Do you want to do complex development or just simple development?
This is not to discourage but to at least ask the basic questions
If you want to at least have an understanding, then I would suggest...
...read a number of the websites dedicated to web design and development like webmonkey.com, devshed.com, sitepoint.com, and others.
...learn basic programming concepts. Pick up a book like Programming for Dummies. Great way to learn if you're not a programmer.
...pick a language to play with.
If you want to do development, then I would suggest...
...the same that was suggested above for understanding.
...learn PHP because it has a lower learning curve than Perl, and less syntax mistakes you will encounter. (Don't flame me, it's just my personal opinion from personal experience with both languages.) The main issue some developers will have with PHP is the number of functions available in the core language. Perl has 200+ functions, and PHP has well over 3000 functions. That's where the documentation comes in handy to have. I used the Windows CHM doc when developing PHP for quick reference.
If you want to have a more Microsoft background, you could learn ASP.NET. If you want to get into some more serious programming with more potential, then Java is another option.
...learn some SQL and some Database Design concepts. A number of books talk about simple theory that can be implemented quite easily if you're a smart enough person. It's also good to look at the example data they have and build basic applications that do simple tasks. Mak
The idea of switching applications for people can be a task no one wants to undertake for many two reasons.
Comfort level: It's like having designers switch from Photoshop to The GIMP, or MS Word to OO Writer. Granted, the apps accomplish the same thing, but it's not the *same* program. People will resist the change because they know how to use the first program, and the reason for the change isn't a concern for them.
Dominance: Going vendor neutral when the major still use vendor specific requires you to see if your users use vendor specific features that are not available in the neutral. If those features aren't there, then what do you do? Write code to compenstate for the feature, or get plugins, or do nothing if there's nothing you can do. Are there tools that can do as good a job as the old tools, to work in this neutral envirnoment?
It would help more if you stated your case in more detail.
The points brought up in the site you link are valid. It's one thing is someone were merely spatting out nonsense, but when they have valid points they can demonstrate, it's good to make note of it.
The tail from the Yellow Lion broke on day one! I was pissed, and almost swapped my Voltron with another kid I didn't like. I would have played it off too as "I had nothing to do with it". hehehhe,
when the reason people switch to Linux and FOSS is due to * Financial reasons * Freedom of software choices * The ability to make alterations to code * The ability to review the code you are running on your hardware.
If apache, php, mysql runs on Windows (which it does), would I switch back to Windows as my main development/production environments for the web work I do? No. I'm quite happy with Linux. I save money with Linux. I pay no licenses, and I deal with less software updating and vulnerabilities.
I agree the level of fuss that might be associated with the game because OSS was used in the entire development process. It's not the key point I personally look for in a RPG.
But, that the development of the game using OSS is good for those looking for a real-world example on how someone used OSS to create and publish a piece of work.
The reference isn't to say that Red Hat is the owner/maker of Linux, but more of a distinction in the plethora of linux options, as Red Hat stands out as the main company who is selling an O/S package, that uses the Linux kernel to Enterprises.
As a result, MS, Sun and RH would be looked at as competiting for the same or similar enterprise markets. That's where I see the reference of "Red Hat's Linux"
Also when someone is talking about enterprises and OSes, distros like Debian, Gentoo, Fedora, and others will not come to mind because of the lack of support the way someone who works for an enterprise would expect. A company would want something like a server contract where they can pick up a phone with the company who makes the product, and not necessarily have to dig through a list of consultants found on a simple listing provided on the OS's website. That's not to say the consultants are no good in anyway, but you have to think they way someone who works for an enterprise would.
If I order a product from Microsoft, Sun, or Red Hat, they offer support with that product. I go to Debian, I don't get that directly from Debian.
As for it being an OS war, it IS. Ultimately, you would have to pick a distro to install, and for many, it will be Red Hat. Remember it's not the company people are only picking, it's the product they sell as well.
As for Apple being an option in this, it has a small market share compared to the others. You won't find "many" setups with Apple being used for enterprise server applications (I know there are few, so don't attack me you Mac zealots). Apple is not competiting in the enterprise areas as much as the other three.
I have a PC and a PS2, and use both for gaming. Ratchet and Clank (which I love playing) gets alot of time on my PS2. Trust me, I know what games don't run on the PC but when you measure it all up the Mac is the platform with the smallest amount of games. PCs have the widest game selection out there. Some games are only console based so if you want Halo, then you have to get an Xbox. If you want "Ratchet and Clank" or Jak, then you have to have a PS2.
But staying on topic to the original post, the Mac is limited in software options, that's all I'm saying.
No really, it's the price stopping me from getting a Mac. Why spend $1500 when I can spend $500-750 for a new machine?
Any why is it ever time I say something like that to a Mac person, they always get offended. sheesh. It's just my opinion. You can place my comments in the "Trash can".
Sorry for double posting, forget to rebuttle in the first post.
My comments weren't to say that the Mac is a limited piece of trash, it's a machine limited by it's lack of popularity, and that anyone buying, should at the very least consider the limitation in software options before buying a machine.
You don't buy software based on the hardware, you buy the hardware based on the software you want/need to run. Seriously speaking, without the initial sarcasm of my original post, I hope those who are causally making the switch realize that the range of options they will have on the PC, will not be there on the Mac for a number of things.
They will quickly learn what you CAN'T get with a Mac.
If it's a gamer, they will learn what games DON'T run on a Mac, versus what does.
If it's a song swapper, they will learn what P2P DOESN'T run on the Mac.
Granted, they can shell out more money for the emulation software.
I have yet to get a Mac, and the only reason why I want one is for web development testing, to make sure it works for that 3-5% market share of Safari users using a browser that might still have bugs or features not yet implemented. The main thing stopping me from getting a Mac... Price.
House or a Mac.... hmmmm I chose the house.;=) My home directory can't protect me from hurricanes.
When I first played the game, I experienced nausea. Same for Quake and a few others. The main thing that worked to alleviate the nausea was being in a room cool enough to keep me comfortable. That was the ONLY thing to offset nausea for me.
So if I experienced nausea as far back as Doom 1, does that make me cooler, or just more weaker when it comes to FPS playing?
Slashdot Mirror
If you are on a public street, then there is no expectation of privacy. If you don't have a sign displaying your name, then it's a bit hard to map the image to you unless you're listed in the yellow pages, which in that case, defeats the idea of privacy.
So short answer, "no".
The same way we have gotten used to ads on websites, the same way we will get used to ads in RSS feeds.
We will train ourselves to ignore that ad above that says "Test your skills with Java(TM) and win an Ipod. Take the challenge for Java(TM)". Ads are a must for many, if many bloggers didn't have some type of revenue coming in to support their sites, then many would not exist. Financial support is a necessity for many. So, we will get over that as we have gotten over the RSS feeds.
And if it's in XML, I'm sure someone will write a stylesheet to parse it out.
VR gear. A headmount display that puts you literally into the gameplay. All you see is the world around you and the gyroscopes can be mounted in the headgear, so you turn more with your head and body, than the controller, and the controller could be used for activating weapons and forward/backward movement. It falls in line to what he said "revolutionary, but nothing technically new". VR gear has been around for over a decade, I believe, and have seen it used in the big arcades as far back as 1997 (I used to work at XS New York). I just hope they have resolved the cooling issues by the time it's launched.
Other ideas, some other simpler force feedback device.
staring Christopher Lambert with short blonde hair, set in a post-apocalypitic world. Now that was a bad movie, and the overly used sex scenes didn't add to the movie, though were enjoyable for there moments of interlude.
At a small company I worked at with 3 other developers, and 2 designers we did not use a version control system because:
* we didn't think of installing one, even though a number of negative things happened as a result of not having one.
* had difficulty installing CVS. After reading the docs to install CVS, I still had trouble getting the thing to work and skipped it completely.
* we were naive. not everyone who is programming, especially those new to the scene, know about version control.
I'm not saying these are legitimate reasons, these are excuses for a poor development environment. I have learned from this and have made changes to make my developing better.
I guess sex does sell software, even if it's done by a very thin, nerding looking little boy in a knit sweater and khakis.
You can never be too sure, even on slashdot.
The tsunami was in the Pacific Ocean, and this thing was found in the Atlantic Ocean more north of Maine... I highly doubt it's due to the tsunami.
And it didn't wash up on shore, it was caught in the traps they use.
Well if it is a hermaphrodite, then it has the traits of a gay man from soho. "Honey I'm here to conquer the world" *two snaps*
The problems with Javascript doing form validation are:
* that it can be turned off, so you NEED server side validation anyway,
* the interactiveness is not necessarily helpful if the developers do not denote locations for users to plainly see, which requires more work to implement, but can be easily setup server-side,
Though I do agree with your assumption on it, it's best to deal with just one form of validation.
You say web designer, so I will assume you want to go for a more visual development, than a programming/scripting side of it.
With that in mind I would suggest the following:
Now for the theory. This seperates the person who was good with crayons as a kid from someone who can seriously understand what a website means. You need to learn concepts beyond just simple design. You need to understand how web interfaces work and how users relate to them. Read the articles at use-it.com to get a initial understanding of this. You should understand concepts like the "page fold" and how does it relate to content on the page, how much time should a page take to load, most common page dimensions, what actions people commonly do under certain situations and what link colors people are used to and how should links look like. All of this mainly falls under Visual Information design. You have to know how to communicate what the information is trying to say. If you're the type who likes to go for the big flashy images, then you missed the whole point. If you start off your introduction with "I'm a print designer" or "I come from the print industry" then you need to stop, turn around and go back to the books.
Now for the tougher part. Adding in the developer side of things. If you want to become well rounded, the main questions to ask are:
This is not to discourage but to at least ask the basic questions
If you want to at least have an understanding, then I would suggest...
If you want to do development, then I would suggest...
The idea of switching applications for people can be a task no one wants to undertake for many two reasons.
Comfort level:
It's like having designers switch from Photoshop to The GIMP, or MS Word to OO Writer. Granted, the apps accomplish the same thing, but it's not the *same* program. People will resist the change because they know how to use the first program, and the reason for the change isn't a concern for them.
Dominance:
Going vendor neutral when the major still use vendor specific requires you to see if your users use vendor specific features that are not available in the neutral. If those features aren't there, then what do you do? Write code to compenstate for the feature, or get plugins, or do nothing if there's nothing you can do. Are there tools that can do as good a job as the old tools, to work in this neutral envirnoment?
It would help more if you stated your case in more detail.
The points brought up in the site you link are valid. It's one thing is someone were merely spatting out nonsense, but when they have valid points they can demonstrate, it's good to make note of it.
The tail from the Yellow Lion broke on day one! I was pissed, and almost swapped my Voltron with another kid I didn't like. I would have played it off too as "I had nothing to do with it". hehehhe,
when the reason people switch to Linux and FOSS is due to
* Financial reasons
* Freedom of software choices
* The ability to make alterations to code
* The ability to review the code you are running on your hardware.
If apache, php, mysql runs on Windows (which it does), would I switch back to Windows as my main development/production environments for the web work I do? No. I'm quite happy with Linux. I save money with Linux. I pay no licenses, and I deal with less software updating and vulnerabilities.
I agree the level of fuss that might be associated with the game because OSS was used in the entire development process. It's not the key point I personally look for in a RPG.
But, that the development of the game using OSS is good for those looking for a real-world example on how someone used OSS to create and publish a piece of work.
I think you missed the COO's point.
The reference isn't to say that Red Hat is the owner/maker of Linux, but more of a distinction in the plethora of linux options, as Red Hat stands out as the main company who is selling an O/S package, that uses the Linux kernel to Enterprises.
As a result, MS, Sun and RH would be looked at as competiting for the same or similar enterprise markets. That's where I see the reference of "Red Hat's Linux"
Also when someone is talking about enterprises and OSes, distros like Debian, Gentoo, Fedora, and others will not come to mind because of the lack of support the way someone who works for an enterprise would expect. A company would want something like a server contract where they can pick up a phone with the company who makes the product, and not necessarily have to dig through a list of consultants found on a simple listing provided on the OS's website. That's not to say the consultants are no good in anyway, but you have to think they way someone who works for an enterprise would.
If I order a product from Microsoft, Sun, or Red Hat, they offer support with that product. I go to Debian, I don't get that directly from Debian.
As for it being an OS war, it IS. Ultimately, you would have to pick a distro to install, and for many, it will be Red Hat. Remember it's not the company people are only picking, it's the product they sell as well.
As for Apple being an option in this, it has a small market share compared to the others. You won't find "many" setups with Apple being used for enterprise server applications (I know there are few, so don't attack me you Mac zealots). Apple is not competiting in the enterprise areas as much as the other three.
Ok I was wrong about the P2P software options.
I apologize to all the Macians.
I'm sorry.
I have a PC and a PS2, and use both for gaming. Ratchet and Clank (which I love playing) gets alot of time on my PS2. Trust me, I know what games don't run on the PC but when you measure it all up the Mac is the platform with the smallest amount of games. PCs have the widest game selection out there. Some games are only console based so if you want Halo, then you have to get an Xbox. If you want "Ratchet and Clank" or Jak, then you have to have a PS2.
But staying on topic to the original post, the Mac is limited in software options, that's all I'm saying.
No really, it's the price stopping me from getting a Mac. Why spend $1500 when I can spend $500-750 for a new machine?
Any why is it ever time I say something like that to a Mac person, they always get offended. sheesh. It's just my opinion. You can place my comments in the "Trash can".
Sorry for double posting, forget to rebuttle in the first post.
My comments weren't to say that the Mac is a limited piece of trash, it's a machine limited by it's lack of popularity, and that anyone buying, should at the very least consider the limitation in software options before buying a machine.
You don't buy software based on the hardware, you buy the hardware based on the software you want/need to run. Seriously speaking, without the initial sarcasm of my original post, I hope those who are causally making the switch realize that the range of options they will have on the PC, will not be there on the Mac for a number of things.
I seriously have no spyware problems on my machine. I run 2 machines at home, a Windows 2000 and Red Hat Linux 9.0
"So baby, what are you doing tonight? baaaaaaaaaah
They will quickly learn what you CAN'T get with a Mac.
;=) My home directory can't protect me from hurricanes.
If it's a gamer, they will learn what games DON'T run on a Mac, versus what does.
If it's a song swapper, they will learn what P2P DOESN'T run on the Mac.
Granted, they can shell out more money for the emulation software.
I have yet to get a Mac, and the only reason why I want one is for web development testing, to make sure it works for that 3-5% market share of Safari users using a browser that might still have bugs or features not yet implemented. The main thing stopping me from getting a Mac... Price.
House or a Mac.... hmmmm I chose the house.
When I first played the game, I experienced nausea. Same for Quake and a few others. The main thing that worked to alleviate the nausea was being in a room cool enough to keep me comfortable. That was the ONLY thing to offset nausea for me.
So if I experienced nausea as far back as Doom 1, does that make me cooler, or just more weaker when it comes to FPS playing?