Xref: utzoo news.admin:10193 comp.sources.d:5711 Path: utzoo!attcan!uunet!decwrl!fernwood!oracle!news From: nhess@gumby.us.oracle.com (Nate Hess) Newsgroups: news.admin,comp.sources.d Subject: Re: [from comp.emacs: Imagine if you couldn't use compress any more] Message-ID: <1990Jul31.142102.8291@oracle.com> Date: 31 Jul 90 14:21:02 GMT References: <31666@eerie.acsu.Buffalo.EDU> <1990Jul28.061540.25261@looking.on.ca> <&F5$J3^@masalla.fulcrum.bt.co.uk> Sender: news@oracle.com Reply-To: nhess@gumby.us.oracle.com (Nate Hess) Followup-To: comp.sources.d Organization: Oracle Corporation, Belmont, CA Lines: 19 In article <&F5$J3^@masalla.fulcrum.bt.co.uk>, I.G.Batten@fulcrum (Ian G Batten) writes: >brad@looking.on.ca (Brad Templeton) writes: >> If you have such a big problem, write your own program. There are >> algorithms that compress more, you know. Although few do it as quickly. >Yes, but how would we know if it was patented? If I set down with my >collegues and confect a compression (or whatever) algorithm, and then >implement it, and then distribute it, what protection do I have? Well, you could always sit down, write up your new, wild'n'wooly compression algorithm, run off and patent it, and then never take legal recourse against "patent violaters." --woodstock -- "What I like is when you're looking and thinking and looking and thinking...and suddenly you wake up." - Hobbes nhess@oracle.com or ...!uunet!oracle!nhess or (415) 598-3046