There is No Such Thing as Proprietary Client-side JavaScript. We Recommend These Resources About 3 years ago, I launched my first product.
I built it with two fabulous partners, who continue to produce awesome things. It was a little app, and a tool I thought made for better web. It is no longer online, due to costs, it was a URL aggregator called bundl.it. It was a big deal for me, as it was something I made, and put online for others to use. A year or so later an established website in the same industry launched a feature that was doing the exact thing that my app was made for. When the news hit I was flooded with emails from friends and folks that had happened upon my site. At the time I was disappointed, not because my idea had been "stolen," or "copied" by a larger company. Another lesson I learned, is that people seem to think they own ideas on the internet. We have seen a lot of arguing back and forth about these issues as the landscape of the web is starting to be sheriff'd.
However, in the midst of it all, lies client side JavaScript.
Firefox. Microsoft CEO surprised at Yahoo deal reception. Eight Evil Things Microsoft Never Showed You in the ClickOnce De. LickOnce is a powerful and easy-to-use deployment technology that offers a relatively hassle-free experience for end users, when properly configured.
Unfortunately, the developer story for ClickOnce varies from super simple to maddeningly complicated, depending on what you are trying to accomplish. I recently wrapped up a project where ClickOnce was a large part of the release strategy, and also responsible for a lot of the headaches that went with it. When you use ClickOnce as it was intended, it's remarkably effective. But knowing that most of you reading this article probably don't use stuff "as intended," I'd like to offer you the benefit of my experience: ClickOnce is a "non-impactful" deployment mechanism. C:\Program Files\Microsoft Visual Studio 8\ SDK\v2.0\BootStrapper\Packages Or like this: C:\Program Files\Microsoft SDKs\Windows\ v6.0A\Bootstrapper\Packages.
Una tazza di caff. In a couple of recent posts Roman and David summarise some of the issues of running stupidly conceived wanna be OS (interesting article, especially when they say that "it is not only possible to execute Windows 1.0 binary programs on current versions of Windows to a large extent but also to recompile their source code into an equally functional "modern" application with just limited modifications", which is basically true, and you can really feel this when using windows!).
Yesterday I was at work, and needed to send to mauve a patch to fix an invalid test case. So far so good… Because I basically gave up on using evolution as mail client, because it does everything but let you read the mails nicely (especially if you‘re over imap), I started to use thunderbird. To my great surprise, although I consider thunderbird generally better than evolution, I stumbled upon a funny bug.
US Federal Judge Affirms Key FOSS Developer Rights. A crucial battle over the legal provisions for free and open source software in the US has finally ended today.
Following a recent ruling by a US Federal District Court judge in favor of several key FOSS developer rights, a settlement was reached. The settlement documents are now available to the public. The landmark case of Jacobsen v. Katzer was fought over, of all things, a piece of model railroad software. The plaintiff was Robert Jacobsen, a member of the Java Model Railroad Interface (JMRI) project - a free and open source software project. The most important issue at stake in this case was whether a developer of free software could collect damages for copyright infringement.
The case of Jacobsen v. After the ruling, Katzer decided to settle, and although the judge did not grant Jacobsen's request for an injunction, Katzer and Jacobsen's lawyers agreed on one in the settlement.