Group items tagged

Everyone will benefit, even the Java community: Now that there's competition again, new constructs are—surprise!—again being considered for Java

Do languages have to sacrifice anything?

.NET goes much further: A routine written in a language L1 may call another routine written in a different language L2. A module in L1 may declare a variable whose type is a class declared in L2, and then call the corresponding L2 routines on that variable. If both languages are object oriented, a class in L1 can inherit from a class in L2. Exceptions triggered by a routine written in L1 and not handled on the L1 side will be passed to the caller, which—if written in L2—will process it using L2's own exception-handling mechanism. During a debugging session, you may move freely and seamlessly across modules written in L1 and L2. I don't know about you, but I've never seen anything coming even close to this level of interoperability.

Your server should serve OpenSearch plugins using the MIME type application/opensearchdescription+xml. Be sure that your Search Plugin XML is well formed. You can check by loading the file directly into Firefox. Ampersands in the template URL need to be escaped with & and tags need to be closed with a trailing slash or matching end tag. The xmlns attribute is important, without it you could get an error message indicating that "Firefox could not download the search plugin from: (URL)". Note that you must include a text/html URL — search plugins including only Atom or RSS URL types (which is valid, but Firefox doesn't support) will also generate the "could not download the search plugin" error. Remotely fetched favicons must not be larger than 10KB

Once you have a key you need to add its public part to your add-on's install.rdf file. The simplest way to do this is to select the key then click the Install toolbar button. You must then locate your install.rdf for McCoy and the public part of the key will be added directly to the file. The file will be overwritten so take a backup if you need to.

You need to use McCoy to sign this file so that the application can verify that it really came from you. Simply select the key you originally added to the add-on's install.rdf, then click the "Sign" toolbar button, select your update.rdf file and the data in it will be signed. It's important to note that if you change any information in the update file then it must be signed again.

The guys and gals who show up every day eager to hone their craft, who are passionate about building stuff that matters to them, and perhaps in some small way, to the rest of the world -- those are the people and projects that will ultimately succeed.

Everything else is just noise.

If you want to move your project forward, the only reliable way to do that is to cultivate a deep sense of software craftsmanship and professionalism around it.

Comment 36 by agl@chromium.org, Apr 06 (45 hours ago) You can remove the SSE2 specific flags from the build and you'll still end up with a working browser. However, you can't run pixel-tests with such a browser because your outputs will be different. For everything else, it should be fine. Comment 37 by evan@chromium.org, Apr 06 (45 hours ago) There is no reason we really need SSE2; it's just a temporary workaround for bug 8475.

. Let's assume that this application does storage and retrieval of large media files; the required infrastructure is: A firewall appliance for connecting to the Internet A private network connecting the firewall to other systems A Linux web server running a LAMP stack A Solaris database machine running MySQL for application persistence A WebDAV server for the media files