The GDI Scan tool from ISC reveals that after all of the latest patches for Windows and Office, I am still left with vunerable.dll files within office.
Further... the version of the GDI redistributable on the MSDN site still includes a vunerable version of the GDI.dll dated May 2004.
On this fully patched Windows XP system GDI Scan reveals the following information:
What you can do now to limit the spread: * Update all of your virus checkers and make sure that they are fully active (auto, not just on-demand). * Disable images in your email applications, just use text only. * Switch your primary browser to Firefox or another browser whose latest version is immune from this specific attack. If you have to still use IE, then do so only for sites you truly trust.
Adobe
Systems has today announced a new unified public format for raw digital
camera files and a free software tool, Adobe DNG Converter, for
translating raw photo formats into the new.DNG format, which is
compliant with the Digital Negative Specification. There is no standard
format for raw files, which vary between manufacturers and cameras.
Digital Negative Specification will introduce a single format that can
store information from a diverse range of cameras. An updated Adobe RAW
File Converter adds support for DNG as well as several other cameras.
Adobe Unifies Raw Photo Formats with Introduction of Digital Negative Specification
Free Converter Tool Kick Starts New Digital Negative File Format by
Translating Raw Formats into Easy-to-Use, Archive-Ready Files
SAN JOSE, Calif. -- Sept. 27, 2004
-- Adobe Systems Incorporated (Nasdaq:ADBE) today introduced the Digital
Negative Specification, a new unified public format for raw digital
camera files. The company also launched a free software tool, Adobe DNG
Converter, which translates many of today's popular raw photo formats
into the new.DNG file format, compliant with the Digital Negative
Specification.
Raw files, which contain the original
information captured by a camera sensor prior to any in-camera
processing, have become popular due to their promise of greater
flexibility and image quality. Until today there has been no standard
format for these files, which vary between manufacturers and individual
cameras. The Digital Negative Specification solves this problem by
introducing a single format that can store information from a diverse
range of cameras. Technology leaders, major customers, and professional
photographers today also endorsed the new specification (see separate
quote sheet).
"Professional photographers and other
creative professionals are moving to raw camera workflows because of
the outstanding creative control they get over digital images," said
Bryan Lamkin, senior vice president of Digital Imaging and Digital
Video products at Adobe. "However, clients and publishers have
difficulty working with disparate raw file formats and nobody can be
sure that today's raw formats will be supported ten years from now.
Adobe customers asked us to work on a unified, public format for raw
files and that's what we've delivered with the new Digital Negative
Specification."
Serious photographers want to store
raw files in long-term image archives, because -- unlike standard JPEG's
and TIFF's -- these files represent the pure, unaltered capture. Current
raw formats are unsuitable for archiving because they are generally
undocumented and tied to specific camera models, introducing the risk
that the format will not be supported over time. The unified and
publicly documented Digital Negative Specification ensures that digital
photographs can be preserved in original form for future generations.
The new.DNG file format also simplifies digital imaging workflows for
creative professionals who today have to juggle multiple file formats
as they bring raw images, from different cameras, into print and
cross-media publishing projects.
New Specification Built on Existing Standards
The Digital Negative Specification is based on the TIFF EP format, an
accepted standard, and already the basis of many proprietary raw
formats. The power of.DNG format lies in a set of metadata that must
be included in the file to describe key details about the camera and
settings..DNG-compliant software and hardware can adapt on the fly to
handle new cameras as they are in
"No more broken windows because the kid down the street hits a baseball at your house."
Delightful.
Just imagine that you have a fire in your house blocking access to your exit, now you could go for the window... but your window locks do their job quite well.
If there are as many people out there with fresh copies of Doom 3 in their hands or winging their way to them as I suspect, then this will be slashdotted veerrryy soon.
So here's the content:
In last week's conference call ( http://www.corporate-ir.net/ireye/ir_site.zhtml?ti cker=NVDA&script=2100 ), NVIDIA CEO Jen Hsun Huang confirmed reports that NVIDIA would be launching a new shader model 3.0 mainstream card shortly: "In a few days we're going to turn up the heat another notch. At Quakecon in Texas, a mecca for gamers and truly a phenomenon to witness, we will officially unveil our newest mainstream member of the GeForce 6 family".
Jen Hsun went on to say:
This mainstream GeForce 6 will be the only shader model 3.0 GPU in its class and deliver performance well beyond that of the competition. PCI Express support is native and AGP support will be provided through HSI, once again showing the versatility of the HSI strategy...sampling started in June, production is in full steam on TSMC's 110 nanometer process, with shipments to OEMs soon.
Price points and product names weren't discussed, but Jen Hsun also confirmed SLI support for this upcoming card, and also mentioned by the end of the year NVIDIA will have a top-to-bottom family of shader model 3.0 cards. In fact, he mentions "we're ramping 110 on two GeForce 6 families right now at TSMC, and very shortly we'll start a third...and this quarter we'll have five GeForce 6 GPUs in production, and that ought to cover us from top to bottom."
Because it prevents the installation of the Express copies at home and using the full VS2003 at work.
Which means that I will have to carry on lugging the laptop around.
It also means that if you have a large development team (especially with people spread out geographically) that any updates now have to be synchronised across all users to ensure no loss in working time.
And when it comes down to it, it is unacceptable. It's an XML file! They could at least make a schema to describe a basic project and extend from that, with older versions using basic nodes, and newer version using extended nodes. Afterall, XML should follow the KISS line of thought, whereas if you've looked at the Project files you'll see that they tried to be clever, failed, and now nuke their work in each iteration.
It's just bloody frustrating.
Oh, I long for the days of being a Java developer again.
Intellij IDEa, now THAT was what an IDE should be.
Quote: "When you open a Visual Studio.NET 2003 Web project in Visual Web Developer 2005 Express Edition, the project is converted to the new, simpler project layout used with Visual Studio 2005. The conversion process also converts existing.aspx pages,.ascx files and other files into a new format; for example,.aspx pages are converted to use the new code-behind model. You can therefore work with existing projects using Visual Web Developer 2005 Express Edition, but the conversion process is one-way and you will not be able to continue work with them in Visual Studio.NET 2003. Note that the conversion process creates a backup of your project before the conversion begins."
I think this is precisely what the problem may be... I generally am downloading what people call 'world music' and it's not as widely seeded as your usual porn, bootlegged britney and what not and troublesome to find.
Hence I've seldom managed to retrieve an entire file.
I only persevere because you lot keep raving about it:)
if this is to work on a television, maybe torrents should start to be paired with PAR files to create a far more robust method of fetching large files.
sure these might need to be seeded and torrent files too, but as the PAR files could be dramatically smaller (i.e. 15% of size depending on size of parity) than the full torrent file, they could be published on the sites of the copyright owner (in the case of legit works where the company is using torrents to save bandwidth).
simply put, user expectations when they use simple devices like a TV is that it just works... how many times have you NOT got a complete torrent and/or had trouble getting torrent working efficiently. PAR's could help bring in the robustness that dumb users would need.
So on one side we have the RIAA representing their interests in "reducing piracy" by trying to stop people time-slipping radio.
On the other we have companies like Clearchannel, who benefit from advertising revenues the more listeners they get.
Clearchannel are sucked up to by record labels who want to get their output out there and promoted.
So now we have this problem... do the labels want to be represented by the views of the RIAA, when those views will cause one of the greatest ways of promoting music to turn against them.
Especially, when companies like Clearchannel have so much control.
However this pans out, it's going to get messy and very interesting before it calms down.
This is the time to pull up a seat and relish the spot the RIAA have put themselves in (between a rock (the labels) and a hard place (radio)).
The headline doesn't make it clear, whilst it is a good thing that migrations to Linux happen from all other OS's, it should be highlighted before the anti-MS crowd jump in too fast:
This is a move FROM Sun Solaris TO Linux.
Oracle never used Windows for development because of portability issues to other OS's;)
Of course the initial response is to think that those who have pirated copies must not receive updates.
As with all things though it's seldom that simple.
When a company such as Microsoft gain a significant share of the market (yes... monopoly), then the damage that saying no could be could actually threaten the stability of that society were their software to fail sigificantly.
i.e. If machines cannot be patched with at least the bare security updates, and those machines then assist in the even wider propagation of a virus or worm such that it affects the infrastructure of the Internet as a more general thing.
Then in those cases, would it not have been a civic duty upon the company to protect the wider Internet and society (of their original shortcomings in allowing the vunerability to exist) regardless.
So I'm more of the opinion that No should be the answer for all bells and whistles things... such as Media Player. But that all security patches should be installed on every machine possible... regardless of whether that is a machine without a legit key or not.
Interesetingly, this is probably opposite Microsofts view. As to be able to manipulate market forces they need critical mass in areas suh as Media Player. So I think from their perspective they would probably wish to allow the whistles, but to encourage/force the upgrade to a legal version would probably wish to disallow stability patches (read: security) so that legit systems are more stable.
Yes, as their Red Hat Enterprise product (which uses their custom 2.4 kernel) is widely deployed at hosting companies such as The Planet.
If datacentres and hosting companies are deploying this widely, then you can be sure that there are many sysadmins out there who are creeping up the learning curve and are unaware of precisely what they run on or what it means (2.6 kernel performance with MySql should prompt many to upgrade, but it doesn't).
So the 2.4 kernel is far more widely deployed than you may initially suspect. This is where Red Hat are making their money and why it matters to use.
I've worked on some very large sites with concurrent users running into the hundreds of thousands... these range from http://www.btopenworld.com/ through to the UK's Football League clubs and premium content video sites.
In my experience, Java was not the wisest choice, it was bloated, difficult to maintain (that's one that will rile the pro-Java camp), required too much focus on non-business focus areas (i.e. creating things like session pools and encryption when we should have been focusing on getting the actual business requirements fulfilled), created a object model bureacracy (pure OO with respect to encapsulation? or break the purity of the model because you know in advance that you want 27 objects and you could get them all from one piece of SQL, but this would have presumed knowledge on the internals of the object and thus have broken the rules of encapsulation).
All in all, Java proved to be the most substantial factor in late deliveries of projects, limited scaleability... and expense (you wouldn't run Java on Windows, and we were running it on some very sizeable Sun boxes). We had several major works at performance improvements, memory caching, singletons to persist seldom-modified data, re-working SQL, etc. But this didn't help dig us out of the hole that we were in.
As a comparison, we also ran some Windows boxes with ASP 3 code on it... used prolific file system caching, and because of poor OO support abandoned hope of properly creating encapsulation and objects purely... we did use re-usable components in DLL's, and we did do extensive work to cache page parts in both memory and on disk according to the predicted frequency of use.
Both systems were behind reverse proxy caches... but the Java had the benefit of all pages being cached (as authentication ran in an NSAPI plugin on the proxy), whereas the ASP did not have its pages cached (just the images, styles, etc) as authentication code ran in the pages (it had not moved behind the plugin when I had left the company).
Yet of these... the ASP consistently performed better on page generation times, concurrent users, etc... even though the ASP boxes were just cheap Compaq servers and the Java boxes were very over-specced Sun servers.
My experience of all of this led me to the following conclusions... which were ever obvious but merely got re-inforced.
1) Right tool for the right job. And at the moment that means considering things like PHP, Perl, ASP for web pages... not Java. String manipulation languages and those that are lower overhead are performing better on web sites.
2) If you do use Java, be prepared to dilute the purity of the object model you create to favour performance. DO NOT get caught in the trap that the object model purity is more important than total performance/maintenance... OO purity does not necessarily equate to maintenance increase... documentation and commenting achieves that more.
3) Cache everywhere! Parts of pages, generated pages, the images and styles used on pages, the queries in the database.
4) Control your cache flushing fiercely! Do not allow apps to ever flush anything that you are not sure has to be flushed... wild-card flushing should never occur. If you stay in Java, implement the Observer pattern and persist and serialise data everywhere.
Ultimately it comes down to architecture... but I have witnessed that Java encourages really strange architecture as everyone starts running after a holy grail of a pure object model.
I would generally favour not using Java and going for the re-write. Other languages encourage pure string manipulation and control of what you're doing at a far more approachable level.
That wouldn't apply here as the sample data you've suggested is too little.
For statistical translations to work, you would need a substantial set of data, already translated, from which you could do the comparisons and create your database of phrases and words.
In the example you've given you would need to have pre-populated this database in advance for the statistical engine to understand how to do the translation.
What you've got to do is stop thinking that this is actually performing a translation... it's not... it's performing a cost-based replacement where the costs have been calculated from statistics gathered from a large pool of sample data.
Once you have the sample data... then you will have the translation.
The Sony Ericssons use the same interface as all prior Ericsson phones, and whilst they haven't updated the site accordingly, I do have my old accessories for my T29 running smoothly on my T610... namely my old data transfer cable (for syncing contacts with Outlook).
I believe that the chat keyboard above should work fine with the P800... thus solving the input method.
Does anyone have the keyboard? Can you confirm if the extra keys are on it? Maybe the developers can use key combinations (if the interfaces expose them) to emulate the CTRL and ESC keys.
Because this one will be slashdotted under minor load:
July 25, 2003 - Imagine your kitchen blender conks out the day you're hosting a
large cocktail party. You search an online catalog, decide on a model, and click
the "buy" button. But instead of waiting three days for the appliance to be
shipped to your door, a new kind of printer on your desk springs into action.
Layer by layer, the miraculous machine squirts out various materials to form the
chassis, the electronics, the motors - literally building the blender for you
from the bottom up in a matter of hours.
Call it desktop manufacturing. For gadget geeks in need of instant
gratification, it's a miracle. For designers deep in the iterative prototyping
process, it's a revolution in product development. And thanks to small tech,
it's becoming a reality.
University of California, Berkeley engineering professor John Canny and his
colleagues are building such a printer. They call the technology "polymer
mechatronics" or, more simply, flexonics. The revolutionary approach to desktop
manufacturing is enabled by recent advances in 3-D printers, organic electronics
and polymer actuators.
Three-dimensional printers are commonly used to make prototypes of new
product designs. For example, a designer may load a digital design into a Fused Deposition Modeling machine. The FDM then extrudes thin
beads of ABS plastic in.01-inch layers, until you have a completed passive
functional part or device. While the printers are dropping in price, the leap
from producing passive to active devices is monumental. That's where organic
electronics come into play.
Organic electronics were born in the 1970s when researchers discovered that
chemically doping organic polymers, or plastics, increases their electrical
conductivity. Since then, researchers have worked to develop the most effective
and inexpensive organic compounds that can be patterned on flexible substrates
to create useful circuits. In the private sector, companies ranging from Bell
Labs to IBM to UK startup Plastic Logic are also working to develop quality organic
transistors that are fabricated far more cheaply than silicon circuits. Organic
semiconductors will most likely first hit the market in the form of inexpensive
radio-frequency identification (RFID) tags and flexible display screens.
Canny's co-investigator in Berkeley's flexonics effort, Vivek
Subramanian, is one of many researchers harnessing the microfluidic
precision of inkjet printing technology to deposit organic semiconductors in
desired patterns. The key ingredient in Subramanian's organic circuits is
"liquid gold." Synthesized in his laboratory, liquid gold consists of gold
nanocrystals that are only 20 atoms across and melt at 100 degrees Celsius, 10
times lower than normal.
The gold nanocrystals are encapsulated in an organic shell of an alkanethiol
(an organic molecule containing carbon, hydrogen and sulphur) and dissolved in
ink. As the circuit is printed on plastic, paper or cloth using inkjet
technology, the organic encapsulant is burned off, leaving the gold as a
high-quality conductor.
Combining Subramanian's circuit printing technology with a 3-D printer
enables electronics to be embedded within the housing of the device being
printed. The chassis and the electronics are fabricated as one single structure.
The next step is to add the actuators that provide electromechanical
capabilities to the devices - for instance, a mechanism that causes the
blender's blades to spin when switched on. For this, Canny plans to fill inkjet
cartridges with electroactive polymers that contract when zapped with a voltage,
enabling components to flex in desired directions. Additionally, the polymers
generate a voltage when compressed, so buttons and switches can also be embedde
They'd probably try and get a few publishers on board so that they can be supplied with digital versions of the text. I can't imagine that they would OCR everything... so they'd negotiate what they could from the outset.
This would be very easy for publishers to accomodate, and they would do so more willingly if the book was old (e.g. Origin Of Species, etc).
Slashdot Mirror
Very good point... mod parent up
As this register article (from today) shows:_ music_pirates/
http://www.theregister.co.uk/2004/10/01/uk_to_sue
The GDI Scan tool from ISC reveals that after all of the latest patches for Windows and Office, I am still left with vunerable .dll files within office.
.dll dated May 2004.
x s.dlll ll ln dows.GdiPlus_65 95b64144ccf1df_1.0.0.0_x-ww_8d353f13\GdiPlus.dll
Version: 5.1.3097.0 -- Possibly vulnerable (Windows Side-By-Side DLL)P lus_65 95b64144ccf1df_1.0.10.0_x-ww_712befd8\GdiPlus.dll P lus_65 95b64144ccf1df_1.0.2600.1360_x-ww_24a2ed47\GdiPlus .dll
Further... the version of the GDI redistributable on the MSDN site still includes a vunerable version of the GDI
On this fully patched Windows XP system GDI Scan reveals the following information:
Scanning Drive C:...
C:\Program Files\Common Files\Microsoft Shared\Office10\MSO.DLL
Version: 10.0.3501.0 -- Possibly vulnerable (Under OfficeXP only)
C:\Program Files\Common Files\Microsoft Shared\OFFICE11\MSO.DLL
Version: 11.0.6360.0
C:\Program Files\Common Files\Microsoft Shared\VGX\vgx.dll
Version: 6.0.2800.1106 -- Possibly vulnerable (Win2K SP2 and SP3 w/IE6 SP1 only)
C:\Program Files\Microsoft Office\OFFICE11\GDIPLUS.DLL
Version: 6.0.3264.0
C:\Program Files\Microsoft Works\GDIPLUS.DLL
Version: 5.1.3102.1360
C:\WINDOWS\$NtUninstallKB833998$\s
Version: 5.1.2600.1106 -- Possibly vulnerable (Backup for uninstall purposes)
C:\WINDOWS\$NtUninstallKB839645$\sxs.d
Version: 5.1.2600.1336 -- Possibly vulnerable (Backup for uninstall purposes)
C:\WINDOWS\system32\dllcache\sxs.dll
Version: 5.1.2600.1515
C:\WINDOWS\system32\dllcache\vgx.d
Version: 6.0.2800.1106 -- Possibly vulnerable (Win2K SP2 and SP3 w/IE6 SP1 only)
C:\WINDOWS\system32\sxs.dll
Version: 5.1.2600.1515
C:\WINDOWS\WinSxS\x86_Microsoft.Wi
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Gdi
Version: 5.1.3101.0 -- Possibly vulnerable (Windows Side-By-Side DLL)
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Gdi
Version: 5.1.3102.1360
Scan Complete.
What you can do now to limit the spread:
* Update all of your virus checkers and make sure that they are fully active (auto, not just on-demand).
* Disable images in your email applications, just use text only.
* Switch your primary browser to Firefox or another browser whose latest version is immune from this specific attack. If you have to still use IE, then do so only for sites you truly trust.
Adobe Systems has today announced a new unified public format for raw digital camera files and a free software tool, Adobe DNG Converter, for translating raw photo formats into the new .DNG format, which is
compliant with the Digital Negative Specification. There is no standard
format for raw files, which vary between manufacturers and cameras.
Digital Negative Specification will introduce a single format that can
store information from a diverse range of cameras. An updated Adobe RAW
File Converter adds support for DNG as well as several other cameras.
Click here for more information on Adobe DNG
Press Release:
Adobe Unifies Raw Photo Formats with Introduction of Digital Negative Specification Free Converter Tool Kick Starts New Digital Negative File Format by Translating Raw Formats into Easy-to-Use, Archive-Ready Files
SAN JOSE, Calif. -- Sept. 27, 2004 -- Adobe Systems Incorporated (Nasdaq:ADBE) today introduced the Digital Negative Specification, a new unified public format for raw digital camera files. The company also launched a free software tool, Adobe DNG Converter, which translates many of today's popular raw photo formats into the new .DNG file format, compliant with the Digital Negative
Specification.
Raw files, which contain the original information captured by a camera sensor prior to any in-camera processing, have become popular due to their promise of greater flexibility and image quality. Until today there has been no standard format for these files, which vary between manufacturers and individual cameras. The Digital Negative Specification solves this problem by introducing a single format that can store information from a diverse range of cameras. Technology leaders, major customers, and professional photographers today also endorsed the new specification (see separate quote sheet).
"Professional photographers and other creative professionals are moving to raw camera workflows because of the outstanding creative control they get over digital images," said Bryan Lamkin, senior vice president of Digital Imaging and Digital Video products at Adobe. "However, clients and publishers have difficulty working with disparate raw file formats and nobody can be sure that today's raw formats will be supported ten years from now. Adobe customers asked us to work on a unified, public format for raw files and that's what we've delivered with the new Digital Negative Specification."
Serious photographers want to store raw files in long-term image archives, because -- unlike standard JPEG's and TIFF's -- these files represent the pure, unaltered capture. Current raw formats are unsuitable for archiving because they are generally undocumented and tied to specific camera models, introducing the risk that the format will not be supported over time. The unified and publicly documented Digital Negative Specification ensures that digital photographs can be preserved in original form for future generations. The new .DNG file format also simplifies digital imaging workflows for
creative professionals who today have to juggle multiple file formats
as they bring raw images, from different cameras, into print and
cross-media publishing projects.
New Specification Built on Existing Standards
The Digital Negative Specification is based on the TIFF EP format, an accepted standard, and already the basis of many proprietary raw formats. The power of .DNG format lies in a set of metadata that must
be included in the file to describe key details about the camera and
settings. .DNG-compliant software and hardware can adapt on the fly to
handle new cameras as they are in
http://www.alienware.com/ALX_pages/area51_alx.aspx
"No more broken windows because the kid down the street hits a baseball at your house."
Delightful.
Just imagine that you have a fire in your house blocking access to your exit, now you could go for the window... but your window locks do their job quite well.
Don't you wish your window could break now?
No, to cool a prescott you need to use the water around glaciers.
If there are as many people out there with fresh copies of Doom 3 in their hands or winging their way to them as I suspect, then this will be slashdotted veerrryy soon.
i cker=NVDA&script=2100 ), NVIDIA CEO Jen Hsun Huang confirmed reports that NVIDIA would be launching a new shader model 3.0 mainstream card shortly: "In a few days we're going to turn up the heat another notch. At Quakecon in Texas, a mecca for gamers and truly a phenomenon to witness, we will officially unveil our newest mainstream member of the GeForce 6 family".
So here's the content:
In last week's conference call ( http://www.corporate-ir.net/ireye/ir_site.zhtml?t
Jen Hsun went on to say:
This mainstream GeForce 6 will be the only shader model 3.0 GPU in its class and deliver performance well beyond that of the competition. PCI Express support is native and AGP support will be provided through HSI, once again showing the versatility of the HSI strategy...sampling started in June, production is in full steam on TSMC's 110 nanometer process, with shipments to OEMs soon.
Price points and product names weren't discussed, but Jen Hsun also confirmed SLI support for this upcoming card, and also mentioned by the end of the year NVIDIA will have a top-to-bottom family of shader model 3.0 cards. In fact, he mentions "we're ramping 110 on two GeForce 6 families right now at TSMC, and very shortly we'll start a third...and this quarter we'll have five GeForce 6 GPUs in production, and that ought to cover us from top to bottom."
Don't feed the trolls... it's a badger campaign... only marginally better than a goatsx or gay niggers ones.
RTFA! It's Assembler not a script.
Because it prevents the installation of the Express copies at home and using the full VS2003 at work.
Which means that I will have to carry on lugging the laptop around.
It also means that if you have a large development team (especially with people spread out geographically) that any updates now have to be synchronised across all users to ensure no loss in working time.
And when it comes down to it, it is unacceptable. It's an XML file! They could at least make a schema to describe a basic project and extend from that, with older versions using basic nodes, and newer version using extended nodes. Afterall, XML should follow the KISS line of thought, whereas if you've looked at the Project files you'll see that they tried to be clever, failed, and now nuke their work in each iteration.
It's just bloody frustrating.
Oh, I long for the days of being a Java developer again.
Intellij IDEa, now THAT was what an IDE should be.
Quote: "When you open a Visual Studio
So here starts the next layer of conversion hell!
Thank you VERY much for this explanation :)
:)
:)
I think this is precisely what the problem may be... I generally am downloading what people call 'world music' and it's not as widely seeded as your usual porn, bootlegged britney and what not and troublesome to find.
Hence I've seldom managed to retrieve an entire file.
I only persevere because you lot keep raving about it
I'll look into Azureus
Cheers
have always failed to get complete large files.
/or had trouble getting torrent working efficiently. PAR's could help bring in the robustness that dumb users would need.
if this is to work on a television, maybe torrents should start to be paired with PAR files to create a far more robust method of fetching large files.
sure these might need to be seeded and torrent files too, but as the PAR files could be dramatically smaller (i.e. 15% of size depending on size of parity) than the full torrent file, they could be published on the sites of the copyright owner (in the case of legit works where the company is using torrents to save bandwidth).
simply put, user expectations when they use simple devices like a TV is that it just works... how many times have you NOT got a complete torrent and
just my 2c!
So on one side we have the RIAA representing their interests in "reducing piracy" by trying to stop people time-slipping radio.
On the other we have companies like Clearchannel, who benefit from advertising revenues the more listeners they get.
Clearchannel are sucked up to by record labels who want to get their output out there and promoted.
So now we have this problem... do the labels want to be represented by the views of the RIAA, when those views will cause one of the greatest ways of promoting music to turn against them.
Especially, when companies like Clearchannel have so much control.
However this pans out, it's going to get messy and very interesting before it calms down.
This is the time to pull up a seat and relish the spot the RIAA have put themselves in (between a rock (the labels) and a hard place (radio)).
The headline doesn't make it clear, whilst it is a good thing that migrations to Linux happen from all other OS's, it should be highlighted before the anti-MS crowd jump in too fast:
;)
This is a move FROM Sun Solaris TO Linux.
Oracle never used Windows for development because of portability issues to other OS's
Of course the initial response is to think that those who have pirated copies must not receive updates.
As with all things though it's seldom that simple.
When a company such as Microsoft gain a significant share of the market (yes... monopoly), then the damage that saying no could be could actually threaten the stability of that society were their software to fail sigificantly.
i.e. If machines cannot be patched with at least the bare security updates, and those machines then assist in the even wider propagation of a virus or worm such that it affects the infrastructure of the Internet as a more general thing.
Then in those cases, would it not have been a civic duty upon the company to protect the wider Internet and society (of their original shortcomings in allowing the vunerability to exist) regardless.
So I'm more of the opinion that No should be the answer for all bells and whistles things... such as Media Player. But that all security patches should be installed on every machine possible... regardless of whether that is a machine without a legit key or not.
Interesetingly, this is probably opposite Microsofts view. As to be able to manipulate market forces they need critical mass in areas suh as Media Player. So I think from their perspective they would probably wish to allow the whistles, but to encourage/force the upgrade to a legal version would probably wish to disallow stability patches (read: security) so that legit systems are more stable.
If datacentres and hosting companies are deploying this widely, then you can be sure that there are many sysadmins out there who are creeping up the learning curve and are unaware of precisely what they run on or what it means (2.6 kernel performance with MySql should prompt many to upgrade, but it doesn't).
So the 2.4 kernel is far more widely deployed than you may initially suspect. This is where Red Hat are making their money and why it matters to use.
Perens really should've put a page up if he wanted it to be user friendly ;)
I've worked on some very large sites with concurrent users running into the hundreds of thousands... these range from http://www.btopenworld.com/ through to the UK's Football League clubs and premium content video sites.
/., we all love it, and it's on Perl!
In my experience, Java was not the wisest choice, it was bloated, difficult to maintain (that's one that will rile the pro-Java camp), required too much focus on non-business focus areas (i.e. creating things like session pools and encryption when we should have been focusing on getting the actual business requirements fulfilled), created a object model bureacracy (pure OO with respect to encapsulation? or break the purity of the model because you know in advance that you want 27 objects and you could get them all from one piece of SQL, but this would have presumed knowledge on the internals of the object and thus have broken the rules of encapsulation).
All in all, Java proved to be the most substantial factor in late deliveries of projects, limited scaleability... and expense (you wouldn't run Java on Windows, and we were running it on some very sizeable Sun boxes). We had several major works at performance improvements, memory caching, singletons to persist seldom-modified data, re-working SQL, etc. But this didn't help dig us out of the hole that we were in.
As a comparison, we also ran some Windows boxes with ASP 3 code on it... used prolific file system caching, and because of poor OO support abandoned hope of properly creating encapsulation and objects purely... we did use re-usable components in DLL's, and we did do extensive work to cache page parts in both memory and on disk according to the predicted frequency of use.
Both systems were behind reverse proxy caches... but the Java had the benefit of all pages being cached (as authentication ran in an NSAPI plugin on the proxy), whereas the ASP did not have its pages cached (just the images, styles, etc) as authentication code ran in the pages (it had not moved behind the plugin when I had left the company).
Yet of these... the ASP consistently performed better on page generation times, concurrent users, etc... even though the ASP boxes were just cheap Compaq servers and the Java boxes were very over-specced Sun servers.
My experience of all of this led me to the following conclusions... which were ever obvious but merely got re-inforced.
1) Right tool for the right job. And at the moment that means considering things like PHP, Perl, ASP for web pages... not Java. String manipulation languages and those that are lower overhead are performing better on web sites.
2) If you do use Java, be prepared to dilute the purity of the object model you create to favour performance. DO NOT get caught in the trap that the object model purity is more important than total performance/maintenance... OO purity does not necessarily equate to maintenance increase... documentation and commenting achieves that more.
3) Cache everywhere! Parts of pages, generated pages, the images and styles used on pages, the queries in the database.
4) Control your cache flushing fiercely! Do not allow apps to ever flush anything that you are not sure has to be flushed... wild-card flushing should never occur. If you stay in Java, implement the Observer pattern and persist and serialise data everywhere.
Ultimately it comes down to architecture... but I have witnessed that Java encourages really strange architecture as everyone starts running after a holy grail of a pure object model.
I would generally favour not using Java and going for the re-write. Other languages encourage pure string manipulation and control of what you're doing at a far more approachable level.
Remember that you're only creating web pages:
1) Query database
2) Concat string
3) Echo string
4) ???
5) Profit!
It really isn't hard, and doesn't need rocket science. Look at
That wouldn't apply here as the sample data you've suggested is too little.
For statistical translations to work, you would need a substantial set of data, already translated, from which you could do the comparisons and create your database of phrases and words.
In the example you've given you would need to have pre-populated this database in advance for the statistical engine to understand how to do the translation.
What you've got to do is stop thinking that this is actually performing a translation... it's not... it's performing a cost-based replacement where the costs have been calculated from statistics gathered from a large pool of sample data.
Once you have the sample data... then you will have the translation.
... so providing you wear a looser necked shirt and tie... there's no reason to actually not wear a tie.
not quite the strength of argument for me to bash my boss with health and safety law!
This is a fantastic idea, but as the developers pointed out... it's a bit frustrating without the ability to CTRL + ESC.
So... the chat keyboard should work:
Chat Keyboard @ Sony Ericsson
The Sony Ericssons use the same interface as all prior Ericsson phones, and whilst they haven't updated the site accordingly, I do have my old accessories for my T29 running smoothly on my T610... namely my old data transfer cable (for syncing contacts with Outlook).
I believe that the chat keyboard above should work fine with the P800... thus solving the input method.
Does anyone have the keyboard? Can you confirm if the extra keys are on it? Maybe the developers can use key combinations (if the interfaces expose them) to emulate the CTRL and ESC keys.
July 25, 2003 - Imagine your kitchen blender conks out the day you're hosting a large cocktail party. You search an online catalog, decide on a model, and click the "buy" button. But instead of waiting three days for the appliance to be shipped to your door, a new kind of printer on your desk springs into action. Layer by layer, the miraculous machine squirts out various materials to form the chassis, the electronics, the motors - literally building the blender for you from the bottom up in a matter of hours.
Call it desktop manufacturing. For gadget geeks in need of instant gratification, it's a miracle. For designers deep in the iterative prototyping process, it's a revolution in product development. And thanks to small tech, it's becoming a reality.
University of California, Berkeley engineering professor John Canny and his colleagues are building such a printer. They call the technology "polymer mechatronics" or, more simply, flexonics. The revolutionary approach to desktop manufacturing is enabled by recent advances in 3-D printers, organic electronics and polymer actuators.
Three-dimensional printers are commonly used to make prototypes of new product designs. For example, a designer may load a digital design into a Fused Deposition Modeling machine. The FDM then extrudes thin beads of ABS plastic in .01-inch layers, until you have a completed passive
functional part or device. While the printers are dropping in price, the leap
from producing passive to active devices is monumental. That's where organic
electronics come into play.
Organic electronics were born in the 1970s when researchers discovered that chemically doping organic polymers, or plastics, increases their electrical conductivity. Since then, researchers have worked to develop the most effective and inexpensive organic compounds that can be patterned on flexible substrates to create useful circuits. In the private sector, companies ranging from Bell Labs to IBM to UK startup Plastic Logic are also working to develop quality organic transistors that are fabricated far more cheaply than silicon circuits. Organic semiconductors will most likely first hit the market in the form of inexpensive radio-frequency identification (RFID) tags and flexible display screens.
Canny's co-investigator in Berkeley's flexonics effort, Vivek Subramanian, is one of many researchers harnessing the microfluidic precision of inkjet printing technology to deposit organic semiconductors in desired patterns. The key ingredient in Subramanian's organic circuits is "liquid gold." Synthesized in his laboratory, liquid gold consists of gold nanocrystals that are only 20 atoms across and melt at 100 degrees Celsius, 10 times lower than normal.
The gold nanocrystals are encapsulated in an organic shell of an alkanethiol (an organic molecule containing carbon, hydrogen and sulphur) and dissolved in ink. As the circuit is printed on plastic, paper or cloth using inkjet technology, the organic encapsulant is burned off, leaving the gold as a high-quality conductor.
Combining Subramanian's circuit printing technology with a 3-D printer enables electronics to be embedded within the housing of the device being printed. The chassis and the electronics are fabricated as one single structure.
The next step is to add the actuators that provide electromechanical capabilities to the devices - for instance, a mechanism that causes the blender's blades to spin when switched on. For this, Canny plans to fill inkjet cartridges with electroactive polymers that contract when zapped with a voltage, enabling components to flex in desired directions. Additionally, the polymers generate a voltage when compressed, so buttons and switches can also be embedde
They'd probably try and get a few publishers on board so that they can be supplied with digital versions of the text. I can't imagine that they would OCR everything... so they'd negotiate what they could from the outset.
This would be very easy for publishers to accomodate, and they would do so more willingly if the book was old (e.g. Origin Of Species, etc).