Working for a large print company I can assure you that is not the intent. The paperless office will come regardless of what the dying print companies attempt to do.
Some of the better print companies are trying to standardize on XML-based formats rather than relying solely on PDF and/or PostScript.
PDF-like documents, where the layout and text are "frozen", will always be needed as long as marketing and sales folks want their electronic documents to "look nice" and stay that way.
I have been a professional Java devloper for 4 years now. I started on a C# project with my company 2.5 months ago. I would say the biggest hurdles that I have had to overcome are:
1) no checked exceptions in C#
2) dotNET API is not as well organized as JavaDoc
3) getting used to applying hotfixes and security updates weekly
I definitely like the C# IDE. It is nice to spend more time coding and less time waiting for a slow Java IDE to respond.
Slashdot Mirror
Working for a large print company I can assure you that is not the intent. The paperless office will come regardless of what the dying print companies attempt to do.
Some of the better print companies are trying to standardize on XML-based formats rather than relying solely on PDF and/or PostScript.
PDF-like documents, where the layout and text are "frozen", will always be needed as long as marketing and sales folks want their electronic documents to "look nice" and stay that way.
I have been a professional Java devloper for 4 years now. I started on a C# project with my company 2.5 months ago. I would say the biggest hurdles that I have had to overcome are:
1) no checked exceptions in C#
2) dotNET API is not as well organized as JavaDoc
3) getting used to applying hotfixes and security updates weekly
I definitely like the C# IDE. It is nice to spend more time coding and less time waiting for a slow Java IDE to respond.