And no offense, but it has been known for the last month at least that CS5 was getting ready to launch. If you went ahead and purchased CS4, and could have waited those few weeks, well, you have no one to blame but yourself.
It surprises me that in all of the discussions about how HTML5 is going to murder Flash, the one thing that everyone overlooks is the exact reason why Flash continues to be popular - Cross-browser consistency.
I mean, right now, you cannot expect any of the five browsers to display CSS2 consistently, and that spec has been around since 1998. Why is it that everyone expects HTML5 to be perfect out of the box on every platform?
Out of curiosity, do you not believe of the ice ages (http://en.wikipedia.org/wiki/Ice_age), which is a scientific theory that has been accepted since 1870s? Doesn't it stand to reason that the opposite occurs - periods where the temperature of the world is much higher on average? And so, there are periods of global cooling and warming.
The climate changes. It has long before we showed up, and it will continue long after we are gone. You may not agree that our industrial nature is impacting how the climate is changing, but you cannot dispute that the climate of the Earth changes regardless.
To do so, you put yourself in the same class of individuals who thought that the idea of the world revolving around the sun was "junk science."
This is only half right. Climate is changing, but humans are not responsible for it happening. We may be responsible for it accelerating, but the climate of the Earth has been changing for millions of years.
This is what irritates me about the whole argument from both the left and the right. What we need to be arguing is the human influence of climate change, not the fact of climate change.
You know, man-made global warming may be in dispute, and may fit every thing that you are saying, but climate change does not. The climate on this planet has swung from massively hot to incredibly cold hundreds of times throughout the life of this planet. And it will continue to do so long after we are gone. This is what this office is about - understanding what is going to happen next to the world's climate, and giving that information to people and local governments so they can plan better.
We have an office that tries to tell people what the weather is going to be like in 10 days. Sometimes it gets it right, some times it doesn't. Should we get rid of the Weather Service because it misses the mark? No, because the more it predicts - even when it gets it wrong - the better the predictions will be the next time.
You obviously missed the part where the Climate Service is going to be part of NOAA. What they are doing is taking the already existing, climate related offices in NOAA that are scattered about in different line offices, and putting them in to their own line office. The offices don't change what they are doing, or even where they are located. What happens is they can now more easily work with each other on a shared mission.
Whether you believe that we are impacting the climate or not, the climate has changed quite a bit in the past, from one extreme to another, and there is absolutely no reason to think that suddenly, after millions of years of both warming and cooling, it is going to stop changing now that we are around. This office exists to help people and governments plan for that change, in the exact same way that the Weather Service exists to help those same people plan for what is going to happen tomorrow.
The web stats of the sites you manage should be dictating your support of any browser, not just IE6. For instance, I work as the Lead Designer for a government agency, and - depending on the target audience of the site - IE6 ranges anywhere from 9 - 15% of our users.
As such, I just don't feel that we can drop IE6 support from our websites yet. And I would encourage you not to rely on what Slashdot tells you, but instead look at your web stats and go from there.
"...unfindable by search engines..." That is absolutely not true. Anyone who uses Google knows that the search engine can read PDFs, identify if any of the keywords are located within, and then provide a link both directly to the PDF as well as to an HTML version.
I have always thought that the best cure for traffic jams would be cars that drive themselves and that are in constant communication with the cars around them. Cars that drive themselves won't slow down to rubberneck, allow cars to merge properly, and in general will work to keep the flow moving.
You obviously don't do any work in the GIS arena. Flash/Flex API from ESRI is going to allow for some amazing mapping applications. They also have a Javascript API, though after testing it in our shop, we ran in to some cross browser concerns, so we opted for the Flex option, and haven't regretted it yet.
You missed part of the point of the article. Most of the time, folks who know how to design a good frontend have no idea how to program it. Saying "patches welcome" to a usability guru is like saying "Usability sucks, and you suck too!" to that person.
I am all for blowing off the dickheads who give you unconstructive criticism, but when someone offers legitimate suggestions, and it is obvious they have no idea on how to implement, you should listen instead of being a dickhead yourself.
The problem with that statement is that you assume a user will put up with a bad interface long enough to get used to it, which just isn't true. Users will avoid or completely abandon software that is difficult to learn.
And usability does not equal easy to use, it equals obvious to use. The distinction is subtle enough for most people who build apps to miss completely.
For instance, my wife was trying to burn a CD yesterday. She fired up the burner software, and, having never used it before, she sat there clicking things that weren't clickable to get it to copy a CD. I finally had to point out the overly large red button the bottom right hand corner of the app that said "Go."
It was easy, but not obvious (because of placement), and thus the user failed at the task. Now that she knows, she won't have any problem (your point), but if I hadn't been there, she would have just moved on to a different application to get it done (my point).
I second this. I have been using WiiFit for nearly a month now, and it is great. Of course, you have to set your routine, find exercises you like, and such, but it can be very effective once you get in to it.
My routine is get up early, quick glass of OJ, then WiiFit. My goal is to do at least 40 minutes of exercise, which - when coupled with navigating the system - usually results in an hour total. I used to do yoga at both the beginning and end to stretch out (8-10 minutes each), then 8-10 minutes of strength training, then 20 minutes of aerobics (once unlocked, the step program is awesome).
Lately, I have dropped the yoga in the beginning, and lengthened the time on strength training and yoga at the end. Some of the strength training exercises are just as good for stretching.
The biggest change is that it is starting to have an impact in other parts of my life. I have found myself wanting to eat better and eat less, because I want to see that downward trend on the scale every day. The best part, though, is that I am actually sticking to it. My next goal is to get up over four times a week to five. I am hoping that should have an impact on the speed of the loss.
1. Because DW has some great code hinting and completion options when writing HTML and CSS. 2. Actually, I still use tables...when formatting tabular data. That is what tables are for, so it is no where near dying out. 3. I doubt he is using split view to preview what the site is going to look like, since DW's rendering engine stinks. He is probably using it to quickly find places in the design, then adjust the code by hand. 4. DW will not rewrite your code unless tell it to.
"It's not a big deal to install Apache, mod_php, tomcat, database on a development server or even locally to be able to test things out in a real environment."
Depending on your corporate environment, it can be a huge deal.
Basically, it boils down to this: Some people like it, some people don't. There is no right or wrong way to create a site, as long as at the end of the day the code is clean, the design is effective, and the end user is happy.
But it isn't just about playing guitar. Its about playing guitar with a bad ass band behind you. And that certainly isn't easily obtainable, nor really that fun once you get bad ass.
"As for the Wii Remote, I'm sure they'll just require you to purchase a whole new guitar controller."
But they should be able to make a guitar controller that allows for the Wiimote to just plug in, meaning that the guitar itself should contain significantly less technology, and thus cheaper. For instance, plug the Wiimote in to the guitar, and it is instantly linked to the Wii. No extra wires or wireless components needed.
Sort of, but it would be a huge blow to the PS3. Sony was counting on the PS3 to drive Blu-Ray into homes. Incorporating Blu-Ray into the PS3 was the primary reason Sony was having in getting their product to market. Blu-Ray is one of the primary reasons the PS3 costs $600 instead of something more competitive, or, it is the primary reason Sony is losing money on every PS3.
If Blu-Ray fails, it will be because of a lack of market penetration. And if Blu-Ray doesn't have a large user base, then that directly correlates to the PS3 not having a large user base.
Re:The rest of the launch lineup can go to hell...
on
Two Weeks with the Wii
·
· Score: 1
My wife and I rented Monkey this weekend. It was okay, but definitely not a purchase game. From everything I am reading though, Rayman sounds like an excellent game. I would also recommend Trauma Center. This game rocks very hard, and my wife plays it more than I do. Excite Truck is also a good game (I love it), but I would suggest renting first, as it is most definitely a love it or hate it game.
"The problem I see is that CSS in its current form (even if it was fully supported), still has certain things that aren't quite doable. Or they ARE doable. With 15 nested div tags."
I know you are exaggerating, but any experienced CSS designer doesn't need anywhere near that many divs. In fact, the only div tags I use are to outline the larger block elements (header, content, footer), plus an extra "container" div, just to cover my bases. Everything else can usually be done just by manipulating the tags within those divs, or, on the rare occasion, using classes.
The fact that most people are missing is that this is Nintendo. The same company that released multiple versions of the the same GameBoy. The same company that released an upgrade to the DS about a year after it is launched.
I would not be surprised if we see a new version of the Wii in a couple of years outputting a higher res. I know we have never seen them do this in the console market, but I bet they feel they can get away with it, especially if the Wii takes off. And they would probably be right.
Slashdot Mirror
This isn't the first time. Remember the original Gameboy? It destroyed pretty much every color competitor that tried to go up against it.
This answer will probably get modded down into oblivion, but get Flash CS5, and you can write for both with the same code. See: http://blogs.adobe.com/cantrell/archives/2010/04/one_application_five_screens.html
I believe there are other code platforms that are write once run everywhere, in case you have an allergic reaction to Flash.
Were these the same regulators that were "inspecting" Deepwater Horizon?
Republicans = Party to support rich
Democrats = Party to support poor
? = Party to support middle class
And no offense, but it has been known for the last month at least that CS5 was getting ready to launch. If you went ahead and purchased CS4, and could have waited those few weeks, well, you have no one to blame but yourself.
It surprises me that in all of the discussions about how HTML5 is going to murder Flash, the one thing that everyone overlooks is the exact reason why Flash continues to be popular - Cross-browser consistency.
I mean, right now, you cannot expect any of the five browsers to display CSS2 consistently, and that spec has been around since 1998. Why is it that everyone expects HTML5 to be perfect out of the box on every platform?
Out of curiosity, do you not believe of the ice ages (http://en.wikipedia.org/wiki/Ice_age), which is a scientific theory that has been accepted since 1870s? Doesn't it stand to reason that the opposite occurs - periods where the temperature of the world is much higher on average? And so, there are periods of global cooling and warming.
The climate changes. It has long before we showed up, and it will continue long after we are gone. You may not agree that our industrial nature is impacting how the climate is changing, but you cannot dispute that the climate of the Earth changes regardless.
To do so, you put yourself in the same class of individuals who thought that the idea of the world revolving around the sun was "junk science."
This is only half right. Climate is changing, but humans are not responsible for it happening. We may be responsible for it accelerating, but the climate of the Earth has been changing for millions of years.
This is what irritates me about the whole argument from both the left and the right. What we need to be arguing is the human influence of climate change, not the fact of climate change.
You know, man-made global warming may be in dispute, and may fit every thing that you are saying, but climate change does not. The climate on this planet has swung from massively hot to incredibly cold hundreds of times throughout the life of this planet. And it will continue to do so long after we are gone. This is what this office is about - understanding what is going to happen next to the world's climate, and giving that information to people and local governments so they can plan better.
We have an office that tries to tell people what the weather is going to be like in 10 days. Sometimes it gets it right, some times it doesn't. Should we get rid of the Weather Service because it misses the mark? No, because the more it predicts - even when it gets it wrong - the better the predictions will be the next time.
You obviously missed the part where the Climate Service is going to be part of NOAA. What they are doing is taking the already existing, climate related offices in NOAA that are scattered about in different line offices, and putting them in to their own line office. The offices don't change what they are doing, or even where they are located. What happens is they can now more easily work with each other on a shared mission.
Whether you believe that we are impacting the climate or not, the climate has changed quite a bit in the past, from one extreme to another, and there is absolutely no reason to think that suddenly, after millions of years of both warming and cooling, it is going to stop changing now that we are around. This office exists to help people and governments plan for that change, in the exact same way that the Weather Service exists to help those same people plan for what is going to happen tomorrow.
The web stats of the sites you manage should be dictating your support of any browser, not just IE6. For instance, I work as the Lead Designer for a government agency, and - depending on the target audience of the site - IE6 ranges anywhere from 9 - 15% of our users.
As such, I just don't feel that we can drop IE6 support from our websites yet. And I would encourage you not to rely on what Slashdot tells you, but instead look at your web stats and go from there.
"...unfindable by search engines..."
That is absolutely not true. Anyone who uses Google knows that the search engine can read PDFs, identify if any of the keywords are located within, and then provide a link both directly to the PDF as well as to an HTML version.
I have always thought that the best cure for traffic jams would be cars that drive themselves and that are in constant communication with the cars around them. Cars that drive themselves won't slow down to rubberneck, allow cars to merge properly, and in general will work to keep the flow moving.
You obviously don't do any work in the GIS arena. Flash/Flex API from ESRI is going to allow for some amazing mapping applications. They also have a Javascript API, though after testing it in our shop, we ran in to some cross browser concerns, so we opted for the Flex option, and haven't regretted it yet.
You missed part of the point of the article. Most of the time, folks who know how to design a good frontend have no idea how to program it. Saying "patches welcome" to a usability guru is like saying "Usability sucks, and you suck too!" to that person.
I am all for blowing off the dickheads who give you unconstructive criticism, but when someone offers legitimate suggestions, and it is obvious they have no idea on how to implement, you should listen instead of being a dickhead yourself.
The problem with that statement is that you assume a user will put up with a bad interface long enough to get used to it, which just isn't true. Users will avoid or completely abandon software that is difficult to learn.
And usability does not equal easy to use, it equals obvious to use. The distinction is subtle enough for most people who build apps to miss completely.
For instance, my wife was trying to burn a CD yesterday. She fired up the burner software, and, having never used it before, she sat there clicking things that weren't clickable to get it to copy a CD. I finally had to point out the overly large red button the bottom right hand corner of the app that said "Go."
It was easy, but not obvious (because of placement), and thus the user failed at the task. Now that she knows, she won't have any problem (your point), but if I hadn't been there, she would have just moved on to a different application to get it done (my point).
I second this. I have been using WiiFit for nearly a month now, and it is great. Of course, you have to set your routine, find exercises you like, and such, but it can be very effective once you get in to it.
My routine is get up early, quick glass of OJ, then WiiFit. My goal is to do at least 40 minutes of exercise, which - when coupled with navigating the system - usually results in an hour total. I used to do yoga at both the beginning and end to stretch out (8-10 minutes each), then 8-10 minutes of strength training, then 20 minutes of aerobics (once unlocked, the step program is awesome).
Lately, I have dropped the yoga in the beginning, and lengthened the time on strength training and yoga at the end. Some of the strength training exercises are just as good for stretching.
The biggest change is that it is starting to have an impact in other parts of my life. I have found myself wanting to eat better and eat less, because I want to see that downward trend on the scale every day. The best part, though, is that I am actually sticking to it. My next goal is to get up over four times a week to five. I am hoping that should have an impact on the speed of the loss.
1. Because DW has some great code hinting and completion options when writing HTML and CSS.
2. Actually, I still use tables...when formatting tabular data. That is what tables are for, so it is no where near dying out.
3. I doubt he is using split view to preview what the site is going to look like, since DW's rendering engine stinks. He is probably using it to quickly find places in the design, then adjust the code by hand.
4. DW will not rewrite your code unless tell it to.
"It's not a big deal to install Apache, mod_php, tomcat, database on a development server or even locally to be able to test things out in a real environment."
Depending on your corporate environment, it can be a huge deal.
Basically, it boils down to this: Some people like it, some people don't. There is no right or wrong way to create a site, as long as at the end of the day the code is clean, the design is effective, and the end user is happy.
But it isn't just about playing guitar. Its about playing guitar with a bad ass band behind you. And that certainly isn't easily obtainable, nor really that fun once you get bad ass.
"As for the Wii Remote, I'm sure they'll just require you to purchase a whole new guitar controller."
But they should be able to make a guitar controller that allows for the Wiimote to just plug in, meaning that the guitar itself should contain significantly less technology, and thus cheaper. For instance, plug the Wiimote in to the guitar, and it is instantly linked to the Wii. No extra wires or wireless components needed.
"Blu-Ray can fail without the PS3 failing."
Sort of, but it would be a huge blow to the PS3. Sony was counting on the PS3 to drive Blu-Ray into homes. Incorporating Blu-Ray into the PS3 was the primary reason Sony was having in getting their product to market. Blu-Ray is one of the primary reasons the PS3 costs $600 instead of something more competitive, or, it is the primary reason Sony is losing money on every PS3.
If Blu-Ray fails, it will be because of a lack of market penetration. And if Blu-Ray doesn't have a large user base, then that directly correlates to the PS3 not having a large user base.
My wife and I rented Monkey this weekend. It was okay, but definitely not a purchase game. From everything I am reading though, Rayman sounds like an excellent game. I would also recommend Trauma Center. This game rocks very hard, and my wife plays it more than I do. Excite Truck is also a good game (I love it), but I would suggest renting first, as it is most definitely a love it or hate it game.
"The problem I see is that CSS in its current form (even if it was fully supported), still has certain things that aren't quite doable. Or they ARE doable. With 15 nested div tags."
I know you are exaggerating, but any experienced CSS designer doesn't need anywhere near that many divs. In fact, the only div tags I use are to outline the larger block elements (header, content, footer), plus an extra "container" div, just to cover my bases. Everything else can usually be done just by manipulating the tags within those divs, or, on the rare occasion, using classes.
The fact that most people are missing is that this is Nintendo. The same company that released multiple versions of the the same GameBoy. The same company that released an upgrade to the DS about a year after it is launched.
I would not be surprised if we see a new version of the Wii in a couple of years outputting a higher res. I know we have never seen them do this in the console market, but I bet they feel they can get away with it, especially if the Wii takes off. And they would probably be right.