⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 opinion_03.html

📁 关于ARM汇编的非常好的教程
💻 HTML
字号:
<!doctype html public "-//W3C//DTD HTML 3.2//EN"><html><head><title>Opinion - A call for code</title><meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /><meta http-equiv="content-language" content="en" /><meta name="resource-type" content="document"><meta name="copyright" content="This document copyright 2001 by Richard Murray. Use for non-profit and education purposes explicitly granted."><meta name="author" content="Richard Murray"><meta name="rating" content="general"></head><!--  /assembler/opinion_03.html         --><!--                                     --><!--  (C) Copyright 2000 Richard Murray  --><!--  Designed by Richard Murray         --><!--  rmurray@heyrick.co.uk              --><!--                                     --><body bgcolor="#f0f0f0" text="#000000" link="#0022dd" vlink="#002288"><table border = "0" width="100%">  <tr>    <td align=center width=100>      <img src="arm3.gif" width=79 height=78 align = middle>    </td>    <td>      <h1 align="center"><font color="#800080">Opinion<br>A call for code</font></h1>    </td>    <td align=center width=100>      <img src="arm3.gif" width=79 height=78 align = middle>    </td></table><p>&nbsp;<p><font size = "1"><i>The views expressed in this article are purely the opinions of theauthor, Richard Murray, and should not be taken as truth, fact, or resembling anythingwhatsoever. So there.</i></font><p>&nbsp;<p>&nbsp;<p><div align="right">29th October 2000</div><p>&nbsp;<p>I have often said that it is a terrible shame to let hard work coding be dropped. I won'tsay &quot;<i>go to waste</i>&quot; because sometimes the coding is a commercial success.<br>However, when a person or company stops developing for the RISC OS platform for whateverreasons they may have, they often take with them the code. A notable exception here is<i>Webite</i> (DoggySoft), which is a basic HTML 2.0 web browser written entirely inassembler (oh wow!) and sources are available from this site! (example 101)<br>But consider another example. Computer Concepts.<br>I, personally, did not click with <i>Impression</i>'s way of working, but I have seen thesystem in use, and would never claim that it didn't have style and power. The same goes forArtWorks. But now Computer Concepts have gone on with bigger better things (like Xara) anddo not actively develop for RISC OS any more. A number of people still use their software,and I really do think it is a shame to just say &quot;okay, let's call it a day&quot; andstop. Really stop.<br>What I would like to see, and what I will put to various companies/individuals if I cantrack them down, is to have the source code publically released.<br>After all, if it is now a piece of Acorn history, what does the person concerned have tolose?<br><ul>  <li> That others might laugh at their code?<br>       If that was a valid excuse, nobody would ever release code.       <br>&nbsp;<br>  <li> That others might change the copyright and try <i>selling</i> the program?<br>       Well, yes, that is always a possibility. But I rather think that the size of the       RISC OS market, and the fact that the RISC OS magazine editors do remember, I think       it would be <i>highly</i> unlikely that anybody would get far by renaming       <i>Impression</i> to, say, <i>PagePro</i>, and flogging it.       <br>&nbsp;<br>  <li> That users will be downloading untested code?<br>       That is always something to be wary of. When I was discussing the viability of making       the <i>Voyager</i> code open source, I said that the open source version should not       be heavily publicised to newbie users. If a person understands the whole concept,       then using untested code won't bother them. But for 'normal' users, it can cause       unwanted headaches.<br>       But, should that mean that code should not be made open source just because it might       upset somebodies system if they install a bunch of untested things? That logic is       akin to &quot;some kid might shoot his classmates, so we won't broadcast any Quentin       Tarantino movie...ever...&quot;. It just doesn't deal with the real issue.       <br>&nbsp;<br>  <li> How about code management?<br>       Well, I do not wish to take on the role of code manager, primarily due to the time I       spend abroad in the Summer, with no internet connection.<br>       However, the code <i>does</i> need to be managed, so that <i>one</i> release is       available, and modifications are incorporated into the main code release; rather than       loads of different versions all over the web.<br>       But please, don't think I'm trying to duck out. If nobody else is willing to take on       the job of code manager, then I <i>will</i> do it. It'll just mean that it is       possible that little happens during the summer.       <br>&nbsp;<br>  <li> What about royalities? Or payment for the time we spend updating the code?<br>       I'm afraid if you are asking those sorts of questions, then you have missed the       driving force here...       <br>&nbsp;<br>  <li> So this means we'll get once-commercial software as a freebie?<br>       Well, yes and no.<br>       Essentially, yes. Although you <i>will</i> most likely need to recompile it       yourself. However the point here is not so much freebie software, but in keeping       something alive. There will be people we don't code who will benefit, no doubt, but       is that such a bad thing?       <br>&nbsp;<br>  <li> But the original author loses!<br>       How? The original programmer(s) no longer develop and support the code. Only under       very exceptional circumstances would I even dream about asking for a currently       developed project to be made open source. As for the rest, I will be trying to get       old source code released. It is something that, as far as the programmer is concerned,       is out of the picture.<br>       So they don't really have anything to lose.<br>       But, conversely, they do stand to gain a little. They stand to gain a good reputation       from the geeks for actually releasing the code; and they stand to gain from the       end-users who benefit from patches and modifications, whether necessary to make the       code work on a newer system or simply wish-list requests.</ul>Think about it.<p>Surely, you'll agree that this can only be a Good Thing for practically everybody concerned?<p>&nbsp;<p>&nbsp;<p>I will be looking through back-issues of various RISC OS magazines, and looking to see whatgood software we had, but is unfortunately no longer in active development. And, if I cantrack down those concerned, I will put this question to them. I am hoping to secure thereleasal of some good source code, so that we may pool together and get some goodapplications back into development. But all this depends upon many factors. So, at thismoment in time, all I can do is hope - and try to write something really convincing.<p>&nbsp;<p><hr size = "3"><a href="index.html#16">Return to assembler index</a><hr size = "3"><address>Copyright &copy; 2000 Richard Murray</address></body></html>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -