I think that Peter M. at Lionhead still makes his games to be works of art. Small tightly knit team and their current games looked cool even when they were demo'ing the AI with stick figures.
After reading thru the patent (very briefly) I noticed a trend that most everything talked about was client side.
So, if my company makes more than $1mil/year, and I have an.asp script on my page that spews out some HDML to cell users can get a bite sized info chunk, I have to pay the royalty fee? Is this $1mil/year from services extracted from the wireless network or all services?
I don't get it. It doesn't seem right that I should have to pay royalties to spewing out HDML pages. I didn't even need phone.com's SDK for that. They're easy enough to reverse engineer.
That's what I get for reading and writing too early in the morning.
We've only started "officially" doing it recently. People have been hired on that used it before and various internal projects were used to test with.
But, until I work with it on different types of projects, I'm going to hold back any judgement. Right now, it's fun and interesting. Next year, who knows. Maybe my lackluster view is due to the empty food hole in my stomach right now.;)
After doing "normal" coding for the past 7 years, I thought I had it down pretty good. We started switching over to "XP" about 12 weeks ago and our company is on it's 2nd project using it. One difference, we split our teams out into 3 week chunks. The teams are small and we work tight. After 6 months of this, each programmer really has a feel for the system and because they work on each piece for 3 weeks, they're not leaving a mess of bugs for the next team. This "XP" thing isn't as bad as it seems. When run side by side with a "normal programming", the XP team always comes in under budget, ahead of schedule, and with fewer bugs. And the constant client feedback on each 3 week iteration is a lot better than the old school "design sessions" and "requirements gathering" phases, which left out a lot of developer/client contact.
The whole MP3 -> MD thingie Sharp is toutine has been around for years. I bought a Sharp MS702 a few years ago and there was an option to buy a linkup to my PC that would allow a digital dump. The ad at the time was throwing it as your "internet music" tool and when I talked to a rep he told me that it did more than dump MP3's out, it would dump all audio out. I'm assuming that it was all audio that was processed by the CPU since a lot of the CD drives have the direct link to the sound card.
What I think is new is the voice thing. I don't ever remember hearing about that one before today.
MD is selling like crazy in Japan. I'm not too sure about the European market, but I never am sure with them on any product. It's failing in the states because it was kind of shoved into a niche market. It is better than tape, but too expensive. Worse than CD, and still too exensive. I won't buy production MD's because there is no reason to. I have a CD player with digital outs and can dump a CD down to MD easier than I can rip it to MP3. As far as sound goes, MD started as "almost CD" quality but after a couple generations of reworking, it is now "close to perfect CD". I love them and hope that Sony finishes the HD-MD soon so it may get a good push. Sharp is also working on theri own version of a HD-MD that stores 740 megs of data. I use my MD all the time, it's just too cool. Editing your CD? Never thought I would miss it until I had it. I also use MD instead of DAT for music performances. Try doing random track jumps with a DAT player.
When I found out about WSH earlier this year, I thought it was the best thing since sliced bread. And as soon as I found out you could slap a COM interface onto a JS file, it just went neat from there. Sad thing is, there wan't much use for it after the initial "oooooh" and "ahhhh". Although, I am still waiting for the change to use dynamic code generation... as soon as I find something of value to use it on.
Slashdot Mirror
I think that Peter M. at Lionhead still makes his games to be works of art. Small tightly knit team and their current games looked cool even when they were demo'ing the AI with stick figures.
After reading thru the patent (very briefly) I noticed a trend that most everything talked about was client side.
.asp script on my page that spews out some HDML to cell users can get a bite sized info chunk, I have to pay the royalty fee? Is this $1mil/year from services extracted from the wireless network or all services?
So, if my company makes more than $1mil/year, and I have an
I don't get it. It doesn't seem right that I should have to pay royalties to spewing out HDML pages. I didn't even need phone.com's SDK for that. They're easy enough to reverse engineer.
Does this cover HDML as well?
I'm not actually worried... I make zero from my site. I'm just curious.
That's what I get for reading and writing too early in the morning.
;)
We've only started "officially" doing it recently. People have been hired on that used it before and various internal projects were used to test with.
But, until I work with it on different types of projects, I'm going to hold back any judgement. Right now, it's fun and interesting. Next year, who knows. Maybe my lackluster view is due to the empty food hole in my stomach right now.
-j
After doing "normal" coding for the past 7 years, I thought I had it down pretty good. We started switching over to "XP" about 12 weeks ago and our company is on it's 2nd project using it. One difference, we split our teams out into 3 week chunks. The teams are small and we work tight. After 6 months of this, each programmer really has a feel for the system and because they work on each piece for 3 weeks, they're not leaving a mess of bugs for the next team. This "XP" thing isn't as bad as it seems. When run side by side with a "normal programming", the XP team always comes in under budget, ahead of schedule, and with fewer bugs. And the constant client feedback on each 3 week iteration is a lot better than the old school "design sessions" and "requirements gathering" phases, which left out a lot of developer/client contact.
The whole MP3 -> MD thingie Sharp is toutine has been around for years. I bought a Sharp MS702 a few years ago and there was an option to buy a linkup to my PC that would allow a digital dump. The ad at the time was throwing it as your "internet music" tool and when I talked to a rep he told me that it did more than dump MP3's out, it would dump all audio out. I'm assuming that it was all audio that was processed by the CPU since a lot of the CD drives have the direct link to the sound card.
What I think is new is the voice thing. I don't ever remember hearing about that one before today.
MD is selling like crazy in Japan. I'm not too sure about the European market, but I never am sure with them on any product. It's failing in the states because it was kind of shoved into a niche market. It is better than tape, but too expensive. Worse than CD, and still too exensive. I won't buy production MD's because there is no reason to. I have a CD player with digital outs and can dump a CD down to MD easier than I can rip it to MP3. As far as sound goes, MD started as "almost CD" quality but after a couple generations of reworking, it is now "close to perfect CD". I love them and hope that Sony finishes the HD-MD soon so it may get a good push. Sharp is also working on theri own version of a HD-MD that stores 740 megs of data. I use my MD all the time, it's just too cool. Editing your CD? Never thought I would miss it until I had it. I also use MD instead of DAT for music performances. Try doing random track jumps with a DAT player.
When I found out about WSH earlier this year, I thought it was the best thing since sliced bread. And as soon as I found out you could slap a COM interface onto a JS file, it just went neat from there. Sad thing is, there wan't much use for it after the initial "oooooh" and "ahhhh". Although, I am still waiting for the change to use dynamic code generation... as soon as I find something of value to use it on.