Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment I cloned IBM's APIs in the late 1960s. (Score 1) 210

Back in the late 1960s and early 1970s, many of IBM's mainframe APIs were public and cloned regularly. One of the first reasons was to perform Job Accounting, i.e., charge for the run of batch programs based on some combination of userid, account number, CPU time and clock time used, etc. For instance, if a Job card was processed by an API in module jobctla.exe, we would rename that IBM module to jobctlx.exe, and write our own jobctla.exe. In our module, we would simply pass on the the API calls we didn't want to process in any way and for those we did want to process, we would do our own processing and then hand the call off to the renamed module. Rewriting APIs was an easy way to do pre-processing of commands.

Comment Re: Oracle (Score 1) 146

Back in the early 1970s, as an IBM mainframe systems programmer, I copied APIs to add functionality. E.g., the program that read JOB cards was JOBCTLA. If I wanted to extract accounting info from the job card, I would rename the IBM module to JOBCTXA and replace the original with my own version. It would do what I wanted, and then call the IBM version.

Comment Prior Art goes back to the 1960s (Score 1) 303

FWIW, in the late 1960s and early 1970s is was common to replicate some of IBM's APIs in its DOS and OS operating systems. That was a standard for modifying system behavior. A simple example that I remember was writing renaming IBMs main job control routine JOBCTRLA to something like JOBCTLA2 and writing your own JOBCTRLA which would usually call JOBCTLA2 after it was done with its additional processing but might not. This was how job accounting was first implemented, i.e., reading additional info off job cards to determine who was to be charged for the job.

Comment A Very Old Reason to Copy APIs (Score 1) 198

Most APIs are not unique. In most cases, the same API structure is used for many other purposes in other programs. But back in the late 1960s there was another reason to copy APIs, and that was to replace the module using it. In a simple example, assume a program called jobctla.dll that has a single API. I might have renamed jobctla.dll, with it's single API, to jobctlax.dll, and then replaced the original with my own jobctla.dll that did something new and eventually passed the same API parameters to the old jobctlax.dll. One common example of this was in early job accounting routines, where I would parse out additional account numbers, user ids and other info in a job card before it was passed on to the original job control processor.

Comment Wallingford's Perspective Might Not Be Right (Score 1) 735

Around 1983, in a meeting with Dr. Ted Hoff, the architect of the first microprocessor at Intel, the 4004, he gave me a perspective on ideas that has stayed with me. He said. "Everyone has ideas. It's only the people who can make something of them that count." From 1989-1999 I ran a software company and my employees used to come to me with great ideas for what the company should do next. Most of these were software developers. I told them that I couldn't commit the resources the idea needed, but I would give them all the leeway I could to make something of the idea themselves. And they hardly ever did. Programmers have software ideas. Non-programmers have software ideas. Some of each group will succeed in implementing them, but very few.

Submission + - Best IT-infrastructure for a small company 2

DiniZuli writes: I've been imployed by a small NGO to remake their entire IT-infrastructure from scratch. It's a small company counting 20 employees. I would like to ask the /.-crowd and gather some experience and knowledge from you — what worked out best for you and why? I came up with a small list:
Are there any must have books on building the IT infrastructure?
New desktops: should it be laptops (with dockingstations), regular desktop machines or thin clients? A special brand? Ubuntu, Windows or?
Servers: We need a server for authentication and usermanagement. We also need an internal mediaserver (we have thousands of big image and videofiles, and the archive grows bigger every year). Finally we would like to have our webserver in house. Which hardware is good? Which setup, software and OS'es have worked the best for you?
Network: We are redoing everything: routers, schwitches, wireless, authentication — even the wiring. Which setup do you think is the best for a small company?
Which backup solutions do you use?
Since we are remaking everything, this list is not exhaustive, so feel free to comment on anything important not on the list.

Submission + - apple being culturally insensitive ?

lampernisse writes: every iTunes user regularly gets to accept new 'terms and conditions' — usually with each new version. now, i live in belgium, where we have a two thirds majority of dutch speakers (to which i belong) and a one third minority of french speakers, but in belgium iTunes presents the new conditions only in french — with a (non working) link to an hypothetical dutch version. many mail exchanges with apple over several months could not correct this situation. i would like to know if apple is behaving in such a culturally insensitive way in other countries, and — for instance — what would US customers think of being forced to accept binding legal terms in a minority or foreign language they don't understand ? and are such terms and conditions even legally binding if offered only in an unknown language ?

Submission + - Is Google Polluting the Internet?

Pickens writes: "In 1998, Larry Page and Sergey Brin made a promise: "We believe the issue of advertising causes enough mixed incentives that it is crucial to have a competitive search engine that is transparent and in the academic realm." Now Micah White writes in the Guardian that the vast library that is the internet is flooded with so many advertisements that this commercial barrage is having a cultural impact where users can no longer tell the difference between content and advertising and the omnipresence of internet advertising constrains the horizon of our thought. And at the center of it all with ad space on 85% of all internet sites is Google, the world's largest online advertising company. In the gleeful words of Google CEO Eric Schmidt, "We are an advertising company." The danger of allowing an advertising company to control the index of human knowledge is too obvious to ignore, writes White. "The universal index is the shared heritage of humanity. It ought to be owned by us all. No corporation or nation has the right to privatize the index, commercialize the index, censor what they do not like or auction search ranking to the highest bidder." Google currently makes nearly all its money from practices its founders once rightly abhorred. "Now it is up to us to realise the dream of a non-commercial paradigm for organising the internet. Only then will humanity find the wisdom it needs to deal with the many crises that threaten our shared future." We have public libraries. We need a public search engine."

Submission + - Google Wave creator joins Facebook (

daria42 writes: Looks like the Sydney-based creator of Google Wave wasn't too happy with Google after the search giant canned his project in July. Lars Rasmussen, who also created Google Maps, has quit Google and is now rumoured to have joined Facebook. Wonder what he'll be doing there?

Comment Patent should never have been awarded (Score 1) 76

Acacia's patent examiner never looked at the Object View Broker technology from 1994. That in turn was based on an object-oriented semantic modeling tool called Open Books, released by Open Books, Inc, in Cambridge, MA around 1990. That was written in C and released for the OS/2 platform. It wasn't successful in the market because it came out much too early, but it was a brilliant piece of technology that most prospects didn't understand at that time. And Open Books itself was based on the Camps Planning Architecture, a LISP-based technology developed by Mitre Corporation for NASA and DOD in the 1980s. If I remember correctly, it was the basis for some of the early space shuttle mission planning system tools because of the way it could tie together different relational databases.

Slashdot Top Deals

Life would be so much easier if we could just look at the source code. -- Dave Olson