This is absolutely correct. There are meta elements you can add to the html payload which will force IE8 to run with specific rendering rules.
However, the *rendering* of the content isn't the biggest problem.... A *LOT* of internal applications were written without sandboxing and security in mind. So, in the early days of javascript/dhtml, it was the wild wild west, and bad code simply will not work. The security semantics of iframes also changed along the way.... and then there is the white elephant in the room.... ActiveX/OCX's in the browser... which enabled vb6 developers to get 'fat client' functionality running in a browser. In this case, many of the legacy control toolkits are marginally functional on Windows7.
The bottom line is that IE6, VB6 and IIS made it VERY easy for devs to develop solutions *quickly* for the enterprise. Now, they are reaping the harvest of bad security decisions, bad coding,
etc...
My experience differs.
My employer does on-campus interviews at around 50 schools nationwide, and over 70% of the potential recruits were equipped with macs.... according to the web logs from a site they were required to visit individually....
Our public web site has seen a marked increase in 'mac' traffic as well.... averaging around 10%, up from 3% a couple of years ago.
I would have like to have seen more information about _why_ they think this is a good idea...
1. develop cool single player game
2. add a pvp/arena/ranking system so when the user finishes the single player game, they keep coming back to zerg the n00bz.
3. profit!
I am going to summarize all the comments below
on
Safari vs. KHTML
·
· Score: 1
Statement: KHTML did Apple a favor by releasing the code.
Response: No, they didn't. It is LGPL licensed.
Statement: They should be required to submit their changes back as per the LGPL license.
Response: They are providing their changes.
Statement: It isn't easy to apply their changes to the originally source code.
Response: But the LGPL doesn't require the contributions to be in a 'ready to use' format.
Statement: But they should have given us patch logs so we can commit the changes equally.
Response: Apple isn't obligated to give you access to their patch logs, only the changes.
Statement: But they should have 'in the spirit of community'.
Response: LOL. So, the GPL isn't just a binding agreement now, but a moral mandate?
The bottom line is that Apple has fullfilled all their legal obligations to the KHTML community.. and then some.
My god, GPL advocates are annoying. Even when people comply fully with the GPL they are complaining about 'community' and 'spirit'.
To summarize: Apple is 'mean' because they aren't making the KHTML developer's lives easy, even if they have fullfilled all their legal obligations.
Re:Its only the bad things we head about?
on
Safari vs. KHTML
·
· Score: 3, Insightful
The thing is, the KDE guys did Apple a favor, and DID make it easy for them to get at the code
Ummm... no. The GPL gave apple the access to the code. Apple has been compliant with the GPL by giving the changes back to the community.
The fact that the changes are not in the prefered format is completely irrelevant.
AFAIK, the GPL doesn't dictate what format changes need to be submitted back to the project in. In fact, that would hypocritical, as mandating a specific patch format would be a limitation of our freedoms to use what software we want.
Apple is checkpointing their releases. They start with a block of code, make a buttload of changes and then run diff across it.
"People aren't flocking to work those fields in Idaho, do construction around Las Vegas, etc."
Do you know why citizens aren't flocking to those jobs? It is due to the fact that the illegal population drove down labor costs to a ridiculous level. A skilled carpenter, framer, drywaller, electrician, etc used to be able to pull in enough cash seasonally to feed his family and purchase a home.
This is no longer the case, especially in southern california, where day laborers are typically employed for less than $10 an hour to do what used to cost $15-40, depending on experience and skill.
The problem is compounded by the fact that these workers typically work under the table, meaning that they aren't paying medicare, social security, sdi, etc.
When that worker gets hurt, he goes to a county hospital, which costs the regular tax payer. When he has a child, the child attends the public school, and is considered a united states citizen.
It is a well known fact in southern california that the typical 'teen jobs' of fast food restaraunts, grocery stores, gas stations, car washes, etc are no longer available because 'undocumented' workers can give full time for minimum wage and the business doesn't have to deal with immature and unreliable teenagers.
These problems compound themselves time and time again, and the same tired arguments of 'we can't secure our borders' are played out with little basis in reality.
The fact is that it is politically incorrect to want to close the borders, as it is considered 'racist'.
A perfect example of this is the 'minuteman project' in southern arizona that is patrolling a formerly well trafficed section of the border. Recent statistics shown that there has been a substantial reduction in border crossing attempts. These are ordinary citizens, who regardless of media hype have committed no crimes.
However, Senor Bush and his goons have derided these citizens calling them 'vigilantes'.
The balance of power has shifted such that illegal immigrants have more political clout than law abiding citizens.
So, do me a favor and spout rhetoric somewhere else.
I have been a pretty vocal detractor in the mailing lists about the lackluster attention paid to the OS/X port, but this release is really a huge milestone for the team, and they deserve a round of applause.
Kudos to Miguel, Nat and the rest of the team for getting this shipped. The Linux port is rock solid.
Now, if I could only get monoDevelop to run under OS/X without having to jump through endless hoops, I would be a happy man...
With the advent of the DMCA and the lottery-like nature of the american legal system, an ISP who chooses to ignore copyright violation claims could be held accountable.
From an ISP's perspective, it costs less to shut the content (and/or account) down than to defend themselves in court.
Like it or not, it is simple business.
I have an older linksys BEFWS11 (4 port 10/100 switch, 802.11b, internet router/firewall).
I was having terrible issues getting *any* of my pcmcia and pci wireless cards to talk to this device. I was also having problems my custom settings getting reset to factory defaults, etc.
Calling tech support was useless.
They recommended that i *downgrade* to an earlier version of the firmware, which was known to contain a large number of security vulnerabilities. That wasn't gonna happen.
They also thought that I might want to send the unit in for testing and possible repair. Of course the warranty on the unit expired about a month earlier.
So, after purchasing a cheapo blitzz wireless internet router @ walmart for $40 (which works flawlessly I might add), I noticed that linksys had updated the firmware.
I installed the newest version, and whammo they fixed the wireless problem..... by disabling the wireless tranceiver entirely.
Another call to linksys tech support was fruitless, as they recommended that I just go and buy a WRT54G.
You clearly don't have much experience w/ Digital recording.
The noise floor of a typical low end audio card (audigy, SBLive!) is high enough where the benefits of having a solid-state workstation are meaningless.
In other words, your typical creative-labs sound card is inherently going to be noisy regardless of how many or few moving devices are present in the system. Even the new audigy boards support 24bit recording, but the noise floor, electronic isolation and DAC's of the device are so bad, that you would be better off recording @ 16 bit on a used pro-grade board.
With a mid/high end audio board (read: MAudio Delta 44), the sheer amount of data being processed for 'even a few tracks' will quickly consume this machine... period.
Raw wave data (24bit/96Khz stored as 32bit FP) consumes approximately 23MB/minute per mono track. If you figure 3 stereo pairs or six mono tracks, over a 3 minute song, that is 414MB.. which is clearly over the 300MB of usable RAM that you cited.
Six tracks is barely adequate to record any music, unless you are a singer with an acoustic guitar (read: no drums, bass, brass, synths, etc)
This doesn't even begin to address I/O and CPU bottlenecks, which I noted in a prior post.
Anyone who needs a 'silent' audio workstation for A/D recording it going to need gobs of persistent I/O and a heavy duty CPU.
Almost all digital recordings of value are done at 24bit/96Khz (usually stored as 32bit FP), which when recorded in stereo is ~ 1MB / second of just WRITE activity.
This doesn't even begin to factor in playback of existing tracks. I have yet to record anything useful that wasn't comprised 6-8 independent tracks. Assuming the same bitrate, in stereo, that is about 3-4 MB of constant, random access read activity.
Given the lack of RAM (512MB for those that didn't read the article), you can at best hope to cache about 90 seconds of music in RAM. No, I didn't figure in OS overhead (??? oh yeah, this is linux.. there is none).
Ok, next.. Audio mixing and digital effects. Throw in a compressor and software reverb/delay and that 'lil via CPU is hosed. God help you if you try to apply different effects to different tracks.
Lets also assume that you don't own a drum kit, keyboard, trumpet, etc. You will need software instruments, which are totally waveform driven, typically by the host CPU. The SB Live! has soundbank instruments, which are *very* good, but the author also stated that he was waiting for a delta 44, which AFAIK, does not support onboard soundbanks/instruments.
So, in a nutshell, you have a severely limited I/O bottlneck, a severely limited CPU and massive memory limimtations.
All to have a 'silent audio workstation'?
Bottom Line: If silent recording is so important (ie. CD quality mixing/overdubs/dynamic range), you will find this setup unusable.
Slashdot Mirror
This is absolutely correct. There are meta elements you can add to the html payload which will force IE8 to run with specific rendering rules. However, the *rendering* of the content isn't the biggest problem.... A *LOT* of internal applications were written without sandboxing and security in mind. So, in the early days of javascript/dhtml, it was the wild wild west, and bad code simply will not work. The security semantics of iframes also changed along the way. ... and then there is the white elephant in the room.... ActiveX/OCX's in the browser ... which enabled vb6 developers to get 'fat client' functionality running in a browser. In this case, many of the legacy control toolkits are marginally functional on Windows7.
The bottom line is that IE6, VB6 and IIS made it VERY easy for devs to develop solutions *quickly* for the enterprise. Now, they are reaping the harvest of bad security decisions, bad coding,
etc...
My experience differs. My employer does on-campus interviews at around 50 schools nationwide, and over 70% of the potential recruits were equipped with macs.... according to the web logs from a site they were required to visit individually.... Our public web site has seen a marked increase in 'mac' traffic as well.... averaging around 10%, up from 3% a couple of years ago.
I would have like to have seen more information about _why_ they think this is a good idea...
1. develop cool single player game
2. add a pvp/arena/ranking system so when the user finishes the single player game, they keep coming back to zerg the n00bz.
3. profit!
Welcome to slashdot....
Statement: KHTML did Apple a favor by releasing the code. Response: No, they didn't. It is LGPL licensed. Statement: They should be required to submit their changes back as per the LGPL license. Response: They are providing their changes. Statement: It isn't easy to apply their changes to the originally source code. Response: But the LGPL doesn't require the contributions to be in a 'ready to use' format. Statement: But they should have given us patch logs so we can commit the changes equally. Response: Apple isn't obligated to give you access to their patch logs, only the changes. Statement: But they should have 'in the spirit of community'. Response: LOL. So, the GPL isn't just a binding agreement now, but a moral mandate? The bottom line is that Apple has fullfilled all their legal obligations to the KHTML community .. and then some.
My god, GPL advocates are annoying. Even when people comply fully with the GPL they are complaining about 'community' and 'spirit'.
To summarize: Apple is 'mean' because they aren't making the KHTML developer's lives easy, even if they have fullfilled all their legal obligations.
The thing is, the KDE guys did Apple a favor, and DID make it easy for them to get at the code
Ummm... no. The GPL gave apple the access to the code. Apple has been compliant with the GPL by giving the changes back to the community.
The fact that the changes are not in the prefered format is completely irrelevant.
AFAIK, the GPL doesn't dictate what format changes need to be submitted back to the project in. In fact, that would hypocritical, as mandating a specific patch format would be a limitation of our freedoms to use what software we want.
Apple is checkpointing their releases. They start with a block of code, make a buttload of changes and then run diff across it.
Big deal, stop whining.
"People aren't flocking to work those fields in Idaho, do construction around Las Vegas, etc."
Do you know why citizens aren't flocking to those jobs? It is due to the fact that the illegal population drove down labor costs to a ridiculous level. A skilled carpenter, framer, drywaller, electrician, etc used to be able to pull in enough cash seasonally to feed his family and purchase a home.
This is no longer the case, especially in southern california, where day laborers are typically employed for less than $10 an hour to do what used to cost $15-40, depending on experience and skill.
The problem is compounded by the fact that these workers typically work under the table, meaning that they aren't paying medicare, social security, sdi, etc.
When that worker gets hurt, he goes to a county hospital, which costs the regular tax payer. When he has a child, the child attends the public school, and is considered a united states citizen.
It is a well known fact in southern california that the typical 'teen jobs' of fast food restaraunts, grocery stores, gas stations, car washes, etc are no longer available because 'undocumented' workers can give full time for minimum wage and the business doesn't have to deal with immature and unreliable teenagers.
These problems compound themselves time and time again, and the same tired arguments of 'we can't secure our borders' are played out with little basis in reality.
The fact is that it is politically incorrect to want to close the borders, as it is considered 'racist'.
A perfect example of this is the 'minuteman project' in southern arizona that is patrolling a formerly well trafficed section of the border. Recent statistics shown that there has been a substantial reduction in border crossing attempts. These are ordinary citizens, who regardless of media hype have committed no crimes.
However, Senor Bush and his goons have derided these citizens calling them 'vigilantes'.
The balance of power has shifted such that illegal immigrants have more political clout than law abiding citizens.
So, do me a favor and spout rhetoric somewhere else.
I have been a pretty vocal detractor in the mailing lists about the lackluster attention paid to the OS/X port, but this release is really a huge milestone for the team, and they deserve a round of applause.
Kudos to Miguel, Nat and the rest of the team for getting this shipped. The Linux port is rock solid.
Now, if I could only get monoDevelop to run under OS/X without having to jump through endless hoops, I would be a happy man...
The judge DENIED the DEFENDANT'S (NOVELL) motion to DISMISS the case.
The judge is clearly leaning in favor of Novell (as it should), but this fight is not totally over.
With the advent of the DMCA and the lottery-like nature of the american legal system, an ISP who chooses to ignore copyright violation claims could be held accountable. From an ISP's perspective, it costs less to shut the content (and/or account) down than to defend themselves in court. Like it or not, it is simple business.
I have an older linksys BEFWS11 (4 port 10/100 switch, 802.11b, internet router/firewall). I was having terrible issues getting *any* of my pcmcia and pci wireless cards to talk to this device. I was also having problems my custom settings getting reset to factory defaults, etc. Calling tech support was useless. They recommended that i *downgrade* to an earlier version of the firmware, which was known to contain a large number of security vulnerabilities. That wasn't gonna happen. They also thought that I might want to send the unit in for testing and possible repair. Of course the warranty on the unit expired about a month earlier. So, after purchasing a cheapo blitzz wireless internet router @ walmart for $40 (which works flawlessly I might add), I noticed that linksys had updated the firmware. I installed the newest version, and whammo they fixed the wireless problem..... by disabling the wireless tranceiver entirely. Another call to linksys tech support was fruitless, as they recommended that I just go and buy a WRT54G.
You clearly don't have much experience w/ Digital recording. The noise floor of a typical low end audio card (audigy, SBLive!) is high enough where the benefits of having a solid-state workstation are meaningless. In other words, your typical creative-labs sound card is inherently going to be noisy regardless of how many or few moving devices are present in the system. Even the new audigy boards support 24bit recording, but the noise floor, electronic isolation and DAC's of the device are so bad, that you would be better off recording @ 16 bit on a used pro-grade board. With a mid/high end audio board (read: MAudio Delta 44), the sheer amount of data being processed for 'even a few tracks' will quickly consume this machine... period. Raw wave data (24bit/96Khz stored as 32bit FP) consumes approximately 23MB/minute per mono track. If you figure 3 stereo pairs or six mono tracks, over a 3 minute song, that is 414MB.. which is clearly over the 300MB of usable RAM that you cited. Six tracks is barely adequate to record any music, unless you are a singer with an acoustic guitar (read: no drums, bass, brass, synths, etc) This doesn't even begin to address I/O and CPU bottlenecks, which I noted in a prior post.
Anyone who needs a 'silent' audio workstation for A/D recording it going to need gobs of persistent I/O and a heavy duty CPU.
Almost all digital recordings of value are done at 24bit/96Khz (usually stored as 32bit FP), which when recorded in stereo is ~ 1MB / second of just WRITE activity.
This doesn't even begin to factor in playback of existing tracks. I have yet to record anything useful that wasn't comprised 6-8 independent tracks. Assuming the same bitrate, in stereo, that is about 3-4 MB of constant, random access read activity.
Given the lack of RAM (512MB for those that didn't read the article), you can at best hope to cache about 90 seconds of music in RAM. No, I didn't figure in OS overhead (??? oh yeah, this is linux.. there is none).
Ok, next.. Audio mixing and digital effects. Throw in a compressor and software reverb/delay and that 'lil via CPU is hosed. God help you if you try to apply different effects to different tracks.
Lets also assume that you don't own a drum kit, keyboard, trumpet, etc. You will need software instruments, which are totally waveform driven, typically by the host CPU. The SB Live! has soundbank instruments, which are *very* good, but the author also stated that he was waiting for a delta 44, which AFAIK, does not support onboard soundbanks/instruments.
So, in a nutshell, you have a severely limited I/O bottlneck, a severely limited CPU and massive memory limimtations.
All to have a 'silent audio workstation'?
Bottom Line: If silent recording is so important (ie. CD quality mixing/overdubs/dynamic range), you will find this setup unusable.