View Single Post
Old 01-02-2014, 01:05 PM   #32
sirmaru
Wizard
sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.sirmaru ought to be getting tired of karma fortunes by now.
 
sirmaru's Avatar
 
Posts: 2,426
Karma: 6561538
Join Date: Nov 2007
Device: Kindle PW 2013, HDX 2013, Galaxy S5 2014
Source code to Object code is routine.

Quote:
Originally Posted by PeterT View Post
You are of course aware that Computers have NEVER run BASIC or COBOL programs; instead, the textual source code was compiled into machine code.

In fact, languages such as BASIC and COBOL came a lot later in the computing business than machine code, as a means of making programmers more productive.

Nowadays very little development is done in machine-code; it's all done in high-level languages, and we rely on the compilers and their knowledge of computer architectures to efficiently create the machine code.
Most software is now written in Source code and then compiled to Object code which happens to be Machine code. I believe C++ is one language used a lot today. eBooks, now sold in accessible Source code, could easily be converted to Object code (Machine code) before sale.

Why it has not yet happened is because no one up until now has had a decisive edge in eBook sales and had to conform to common industry standards (ePub and its derivatives). Amazon now may be moving into a decisive edge and may start conversion of their eBook inventory.

Some software like encryption modules and cookies are written directly in machine code. Thus, it would be quite easy to insert a cookie to detect alteration of an eBook and then either self destruct the file or send a message to the seller via the internet. Even if the internet was disconnected, a delayed message could be created and then sent once the internet was activated. Updates of all our software happens like that now taking place when the computer is inactive and the internet is connected.

By the way, Amazon now sells songs without any DRM. However, they insert a serial number which identifies the customer and song. If that serial number is removed, the file becomes illegal. If a customer, not being the buyer, ends up with that file with the serial number, then he as well can be identified.

Its possible that Amazon may strip all DRM from eBooks and insert serial numbers as they do now with the songs. If that happens, Calibre would still work fine but Apprentice Alf would become obsolete.

So far as I know, there was only one major crackdown on DRM stripping and that had to do with songs. Technology enabled song publishers to identify names and addresses of violators and mailed thousands of subpoenas out. That move proved very unpopular with customers and was never repeated. Thus, there is little likelihood that it will ever be repeated with eBooks.

Frankly, I believe only a small minority of eBook purchasers from Amazon even know about Calibre and Apprentice Alf. Most probably just buy the eBook to read it just as most just buy songs to listen and don't bother with metadata alterations or any other technical maneuvers.

Last edited by sirmaru; 01-02-2014 at 01:21 PM.
sirmaru is offline   Reply With Quote