Sidechains And Lightning, The New New Bitcoin

chain-gang The great thing about Bitcoin, for a tech columnist like me, is that it’s simultaneously over-the-top cinematic and technically dense. Richard Branson recently hosted a “Blockchain Summit” at his private Caribbean island. There’s a Bitcoin Jet. At the same time, 2015 has seen the release of a whole slew of technically gnarly–and technically… Read More

Original URL:  

Original article

Why did Borland fail?

Borland lost its way when executive management decided to change the company to pursue a different market.

The company was founded on the idea of making mass-market software – products that can be used by a large number of people in a variety of different scenarios, and at reasonable prices.  Turbo Pascal did not become a worldwide sensation just because it compiled thousands of times faster than other compilers – it was also priced hundreds of dollars less than other compiler products, and provided a level of developer tool integration never before seen.

A few years after Borland went public, founder and CEO Philippe Kahn began to have increasing disagreements with the Borland board of directors. Kahn wanted to continue building products for the mass market, but the board of directors wanted to shift gears and pursue the “enterprise” software market. I get the impression that this difference of opinion simmered for years. Ultimately the board fired Kahn and threw the company headlong into the pursuit of the enterprise market.

I’m sure there were several motivations for this change of company direction. In the early 90’s, Microsoft had a firm foothold in mass market software, but was still relatively unknown in the enterprise market. Was the board solely drawn to the high price tags of the enterprise market?  Or were they also attempting to run away from Microsoft’s shadow?

In the height of the enterprise transformation, I asked Del Yokam, one of many interim CEOs after Kahn, “Are you saying you want to trade a million loyal $100 customers for a hundred $1 million customers?”  Yokam replied without hesitation “Absolutely.”

And that, in my opinion, was the core of Borland’s downfall. The executive team decided to take a talented development team with lots of experience building innovative consumer products and retask them to build enterprise software. On paper this may seem like a fairly minor adjustment, if you have the attitude (as Borland executive management had) that developers are a dime a dozen and any developer can be applied to any product or problem space. That may work for technical programming skills but it doesn’t work for passion.

The reality is that the enterprise market is a radically different beast from the consumer market. “Turning the ship” to pursue enterprise customers requires a lot more than just changing the project requirements given to the development teams. It requires a different skillset and mindset in the development teams, a different sales force, and ultimately a different corporate culture.

For many of Borland’s talented developers, enterprise software was the antithesis of their interests and passions. Hot rodders, hackers, and modern day makers were tasked with making things they had no passion for – building the software analogs of sewer systems, utility poles, or synthetic hairballs for ceramic cats.

Borland’s long slow death spiral began when it turned away from what it knew best to chase a unicorn it knew nothing about.

Original URL:  

Original article

Why Open Source Misses the Point of Free Software

by Richard Stallman

When we call software “free,” we mean that it respects
the users’ essential freedoms:
the freedom to run it, to study and change it, and to redistribute
copies with or without changes. This is a matter of freedom, not
price, so think of “free speech,” not “free

These freedoms are vitally important. They are essential, not just
for the individual users’ sake, but for society as a whole because they
promote social solidarity—that is, sharing and cooperation. They
become even more important as our culture and life activities are
increasingly digitized. In a world of digital sounds, images, and words,
free software becomes increasingly essential for freedom in general.

Tens of millions of people around the world now use free software;
the public schools of some regions of India and Spain now teach all
students to use the free GNU/Linux
operating system
. Most of these users, however, have never heard of
the ethical reasons for which we developed this system and built the free
software community, because nowadays this system and community are more
often spoken of as “open source”, attributing them to a
different philosophy in which these freedoms are hardly mentioned.

The free software movement has campaigned for computer users’
freedom since 1983. In 1984 we launched the development of the free
operating system GNU, so that we could avoid the nonfree operating systems
that deny freedom to their users. During the 1980s, we developed most
of the essential components of the system and designed
the GNU General Public License (GNU GPL)
to release them under—a license designed specifically to protect
freedom for all users of a program.

Not all of the users and developers of free software
agreed with the goals of the free software movement. In 1998, a part
of the free software community splintered off and began campaigning in
the name of “open source.” The term was originally
proposed to avoid a possible misunderstanding of the term “free
software,” but it soon became associated with philosophical
views quite different from those of the free software movement.

Some of the supporters of open source considered the term a
“marketing campaign for free software,” which would appeal
to business executives by highlighting the software’s practical
benefits, while not raising issues of right and wrong that they might
not like to hear. Other supporters flatly rejected the free software
movement’s ethical and social values. Whichever their views, when
campaigning for open source, they neither cited nor advocated those
values. The term “open source” quickly became associated
with ideas and arguments based only on practical values, such as
making or having powerful, reliable software. Most of the supporters
of open source have come to it since then, and they make the same

The two terms
describe almost the same category of software, but they stand for
views based on fundamentally different values. Open source is a
development methodology; free software is a social movement. For the
free software movement, free software is an ethical imperative,
essential respect for the users’ freedom. By contrast,
the philosophy of open source considers issues in terms of how to make
software “better”—in a practical sense only. It
says that nonfree software is an inferior solution to the practical
problem at hand. Most discussion of “open source” pays no
attention to right and wrong, only to popularity and success; here’s
typical example

For the free software movement, however, nonfree software is a
social problem, and the solution is to stop using it and move to free

“Free software.” “Open source.” If it’s the same
software (or nearly so),
does it matter which name you use? Yes, because different words convey
different ideas. While a free program by any other name would give you the
same freedom today, establishing freedom in a lasting way depends above all
on teaching people to value freedom. If you want to help do this, it is
essential to speak of “free software.”

We in the free software movement don’t think of the open source
camp as an enemy; the enemy is proprietary (nonfree) software. But
we want people to know we stand for freedom, so we do not accept being
mislabeled as open source supporters.

Practical Differences between Free Software and Open Source

In practice, open source stands for criteria a little weaker than
those of free software. As far as we know, all existing free software
would qualify as open source. Nearly all open source software is free
software, but there are exceptions. First, some open source licenses
are too restrictive, so they do not qualify as free licenses. For
example, “Open Watcom” is nonfree because its license does
not allow making a modified version and using it privately.
Fortunately, few programs use such licenses.

Second, and more important in practice, many products containing
computers check signatures on their executable programs to block users
from installing different executables; only one privileged company can
make executables that can run in the device or can access its full
capabilities. We call these devices “tyrants”, and the
practice is called “tivoization” after the product (Tivo)
where we first saw it. Even if the executable is made from free
source code, the users cannot run modified versions of it, so the
executable is nonfree.

The criteria for open source do not recognize this issue; they are
concerned solely with the licensing of the source code. Thus, these
unmodifiable executables, when made from source code such as Linux
that is open source and free, are open source but not free. Many
Android products contain nonfree tivoized executables of Linux.

Common Misunderstandings of “Free Software” and
“Open Source”

The term “free software” is prone to misinterpretation:
an unintended meaning, “software you can get
for zero price,” fits the term just as well as the intended
meaning, “software which gives the user certain freedoms.”
We address this problem by publishing the definition of free software,
and by saying “Think of ‘free speech,’ not ‘free
beer.’” This is not a perfect solution; it cannot completely
eliminate the problem. An unambiguous and correct term would be better, if
it didn’t present other problems.

Unfortunately, all the alternatives in English have problems of
their own. We’ve looked at many that people have
suggested, but none is so clearly “right” that switching
to it would be a good idea. (For instance, in some contexts the
French and Spanish word “libre” works well, but people in India
do not recognize it at all.) Every proposed replacement for
“free software” has some kind of semantic problem—and
this includes “open source software.”

The official definition of
“open source software”
(which is published by the Open
Source Initiative and is too long to include here) was derived
indirectly from our criteria for free software. It is not the same;
it is a little looser in some respects. Nonetheless, their definition
agrees with our definition in most cases.

However, the obvious meaning for the expression “open source
software”—and the one most people seem to think it
means—is “You can look at the source code.” That
criterion is much weaker than the free software definition, much
weaker also than the official definition of open source. It includes
many programs that are neither free nor open source.

Since the obvious meaning for “open source” is not the
meaning that its advocates intend, the result is that most people
misunderstand the term. According to writer Neal Stephenson,
“Linux is ‘open source’ software meaning, simply,
that anyone can get copies of its source code files.” I don’t
think he deliberately sought to reject or dispute the
official definition. I think he simply applied the
conventions of the English language to come up with a meaning for the
term. The state of Kansas published a similar definition:
“Make use of open-source
software (OSS). OSS is software for which the source code is freely
and publicly available, though the specific licensing agreements vary
as to what one is allowed to do with that code.”

The New York Times
run an article that stretches the meaning of the term
to refer to
user beta testing—letting a few users try an early version and
give confidential feedback—which proprietary software developers
have practiced for decades.

Open source supporters try to deal with this by pointing to their
official definition, but that corrective approach is less effective
for them than it is for us. The term “free software” has
two natural meanings, one of which is the intended meaning, so a
person who has grasped the idea of “free speech, not free
beer” will not get it wrong again. But the term “open
source” has only one natural meaning, which is different from
the meaning its supporters intend. So there is no succinct way to
explain and justify its official definition. That makes for worse

Another misunderstanding of “open source” is the idea
that it means “not using the GNU GPL.” This tends to
accompany another misunderstanding that “free software”
means “GPL-covered software.” These are both mistaken,
since the GNU GPL qualifies as an open source license and most of the
open source licenses qualify as free software licenses. There
are many free software
aside from the GNU GPL.

The term “open source” has been further stretched by
its application to other activities, such as government, education,
and science, where there is no such thing as source code, and where
criteria for software licensing are simply not pertinent. The only
thing these activities have in common is that they somehow invite
people to participate. They stretch the term so far that it only
means “participatory” or “transparent”, or
less than that. At worst, it
become a vacuous buzzword

Different Values Can Lead to Similar Conclusions…but Not Always

Radical groups in the 1960s had a reputation for factionalism: some
organizations split because of disagreements on details of strategy,
and the two daughter groups treated each other as enemies despite
having similar basic goals and values. The right wing made much of
this and used it to criticize the entire left.

Some try to disparage the free software movement by comparing our
disagreement with open source to the disagreements of those radical
groups. They have it backwards. We disagree with the open source
camp on the basic goals and values, but their views and ours lead in
many cases to the same practical behavior—such as developing
free software.

As a result, people from the free software movement and the open
source camp often work together on practical projects such as software
development. It is remarkable that such different philosophical views
can so often motivate different people to participate in the same
projects. Nonetheless, there are situations where these fundamentally
different views lead to very different actions.

The idea of open source is that allowing users to change and
redistribute the software will make it more powerful and reliable.
But this is not guaranteed. Developers of proprietary software are
not necessarily incompetent. Sometimes they produce a program that
is powerful and reliable, even though it does not respect the users’
freedom. Free software activists and open source enthusiasts will
react very differently to that.

A pure open source enthusiast, one that is not at all influenced by
the ideals of free software, will say, “I am surprised you were able
to make the program work so well without using our development model,
but you did. How can I get a copy?” This attitude will reward
schemes that take away our freedom, leading to its loss.

The free software activist will say, “Your program is very
attractive, but I value my freedom more. So I reject your program. I
will get my work done some other way, and support a project to develop
a free replacement.” If we value our freedom, we can act to
maintain and defend it.

Powerful, Reliable Software Can Be Bad

The idea that we want software to be powerful and reliable comes
from the supposition that the software is designed to serve its users.
If it is powerful and reliable, that means it serves them better.

But software can be said to serve its users only if it respects
their freedom. What if the software is designed to put chains on its
users? Then powerfulness means the chains are more constricting,
and reliability that they are harder to remove. Malicious features,
such as spying on the users, restricting the users, back doors, and
imposed upgrades are common in proprietary software, and some open
source supporters want to implement them in open source programs.

Under pressure from the movie and record companies, software for
individuals to use is increasingly designed specifically to restrict
them. This malicious feature is known as Digital Restrictions
Management (DRM) (see and is
the antithesis in spirit of the freedom that free software aims
to provide. And not just in spirit: since the goal of DRM is to
trample your freedom, DRM developers try to make it hard, impossible,
or even illegal for you to change the software that implements the DRM.

Yet some open source supporters have proposed “open source
DRM” software. Their idea is that, by publishing the source code
of programs designed to restrict your access to encrypted media and by
allowing others to change it, they will produce more powerful and
reliable software for restricting users like you. The software would then
be delivered to you in devices that do not allow you to change it.

This software might be open source and use the open
source development model, but it won’t be free software since it
won’t respect the freedom of the users that actually run it. If the
open source development model succeeds in making this software more
powerful and reliable for restricting you, that will make it even

Fear of Freedom

The main initial motivation of those who split off the open source
camp from the free software movement was that the ethical ideas of
“free software” made some people uneasy. That’s true: raising
ethical issues such as freedom, talking about responsibilities as well as
convenience, is asking people to think about things they might prefer
to ignore, such as whether their conduct is ethical. This can trigger
discomfort, and some people may simply close their minds to it. It
does not follow that we ought to stop talking about these issues.

That is, however, what the leaders of open source
decided to do. They figured that by keeping quiet about ethics and
freedom, and talking only about the immediate practical benefits of
certain free software, they might be able to “sell” the
software more effectively to certain users, especially business.

This approach has proved effective, in its own terms. The rhetoric
of open source has convinced many businesses and individuals to use,
and even develop, free software, which has extended our
community—but only at the superficial, practical level. The
philosophy of open source, with its purely practical values, impedes
understanding of the deeper ideas of free software; it brings many
people into our community, but does not teach them to defend it. That
is good, as far as it goes, but it is not enough to make freedom
secure. Attracting users to free software takes them just part of the
way to becoming defenders of their own freedom.

Sooner or later these users will be invited to switch back to
proprietary software for some practical advantage. Countless
companies seek to offer such temptation, some even offering copies
gratis. Why would users decline? Only if they have learned to value
the freedom free software gives them, to value freedom in and of itself
rather than the technical and practical convenience of specific free
software. To spread this idea, we have to talk about freedom. A
certain amount of the “keep quiet” approach to business can be
useful for the community, but it is dangerous if it becomes so common
that the love of freedom comes to seem like an eccentricity.

That dangerous situation is exactly what we have. Most people
involved with free software, especially its distributors, say little about
freedom—usually because they seek to be “more acceptable to
business.” Nearly all GNU/Linux operating system distributions add
proprietary packages to the basic free system, and they invite users to
consider this an advantage rather than a flaw.

Proprietary add-on software and partially nonfree GNU/Linux
distributions find fertile ground because most of our community does
not insist on freedom with its software. This is no coincidence.
Most GNU/Linux users were introduced to the system through “open
source” discussion, which doesn’t say that freedom is a goal.
The practices that don’t uphold freedom and the words that don’t talk
about freedom go hand in hand, each promoting the other. To overcome
this tendency, we need more, not less, talk about freedom.

“FLOSS” and “FOSS”

The terms “FLOSS” and “FOSS” are used to
be neutral between free
software and open source
. If neutrality is your goal,
“FLOSS” is the better of the two, since it really is
neutral. But if you want to stand up for freedom, using a neutral
term isn’t the way. Standing up for freedom entails showing people
your support for freedom.

Rivals for Mindshare

“Free” and “open” are rivals for mindshare.
“Free software” and “open source” are
different ideas but, in most people’s way of looking at software, they
compete for the same conceptual slot. When people become habituated
to saying and thinking “open source,” that is an obstacle
to their grasping the free software movement’s philosophy and thinking
about it. If they have already come to associate us and our software
with the word “open,” we may need to shock them intellectually
before they recognize that we stand for something else.
Any activity that promotes the word “open” tends to
extend the curtain that hides the ideas of the free software

Thus, free software activists are well advised to decline to work
on an activity that calls itself “open.” Even if the
activity is good in and of itself, each contribution you make does a
little harm on the side. There are plenty of other good activities
which call themselves “free” or “libre.” Each
contribution to those projects does a little extra good on the side.
With so many useful projects to choose from, why not choose one
which does extra good?


As the advocates of open source draw new users into our community,
we free software activists must shoulder the task of bringing the issue
of freedom to their attention. We have to say, “It’s
free software and it gives you freedom!”—more and louder
than ever. Every time you say “free software” rather than
“open source,” you help our cause.


<!– The article is incomplete (#793776) as of 21st January 2013.

Joe Barr’s article,
“Live and
let license,”
gives his perspective on this issue.


Lakhani and Wolf’s
paper on the motivation of free software developers
says that a
considerable fraction are motivated by the view that software should be
free. This is despite the fact that they surveyed the developers on
SourceForge, a site that does not support the view that this is an ethical

Original URL:  

Original article

Hack4Detroit’s indemnification clause

Fair warning that I’m not a lawyer and I may not fully understand the contract. It’s included inline for your reference.

TL, DR; #hack4detroit requires a contract be signed on the day of the event that was not previously mentioned before registration fees. The contract states that participants are liable (unlimited personal liability) to pay for any lawyer fees and lawsuit damages if the City of Detroit is ever sued for the submitted software [clause 17]. The contract also states that all IP is transferred to ownership of the City of Detroit (which I think is reasonable) and the City is granted a perpetual, royalty-free license to “use” any derivative software (which I think is unreasonable). Wired aptly elaborates on the hackathon “indemnification” liability situation perfectly here (great read).

This weekend Automation Alley from Troy, Michigan pulled a quick one on a lot of software developers that were just trying to have fun making some cool apps for Michigan. I wanted to take part, but I ended up signing up for the 24-hour hackathon, paying $20, donating my weekend for the event, driving 40-minutes downtown, parking, walking to the event, and then leaving after an hour to drive home.

#hack4detroit is a hackathon where participants can come to make cool software to help Detroit and possibly win a $5K prize. :) Pretty cool, right? I thought so, because when I heard of the event I signed up right away! It’s fun to get together with other software developers at hackathons and I’ve been in the Code Michigan events before and that is always a blast.

My problem arose when I entered the 4th floor of Grand Circus (Detroit’s tech epicenter) and there was a registration table. The registration table is where you get your t-shirt and sign some documents – harmless. The first document was a 1-page release form for allowing the event to use pictures of you so when they take pictures of the event they can publish them freely – cool. :)

But then then the second document was an 8-page contract between Automation Alley, the City of Detroit, and the Participant. When I took a look at the contract I thought to myself “Hm, why am I seeing this for the first time at the registration table on the day of the event, 10 minutes before the event starts?” They could have had this on their website before I’d even signed up weeks ago. If it was on the online registration page I would have had a chance to go over it in detail without time-pressure.

I let the greeter know that that I’ll need some time to read over the 8-page document and she replies “Alright, just bring it back when you want to sign it because I need to witness you sign it”. It seems to be a serious document.

Now here’s the problem. I’m not a lawyer, and neither are any of the other participants in this event (I’m assuming). And we’ve been given 30 minutes to review a document that may include unknown liabilities (which this contract does).

It made me wonder who organizes an event to put participants in this situation, and do I really want to sign a contract that they’ve pressured me into? I was especially surprised because my expectations for Automation Alley were high, as it is self-advertised goal is “[…] enhancing the region’s reputation around the world“.

Here is the contract in its entirety. The most important parts is page 3, clause 17: Indemnification: it states in “non-legalese” that I agree to take responsibility for claims against the City’s use of hackathon code.

What if I accidentally infringed on a patent? I’m liable. What if there’s a bug that causes somebody harm? I’m liable. What if anything? I’m liable. Liable in the sense that they can clear out my bank account and take everything I own.


It took me 40 minutes to read and re-read this document four times and afterward, I was faced with a dilemma: This is going to be a fun event with really smart, fun people, do I want to be the only person that is a stick-in-the-mud about a contract? Everybody else signed the document, am I silly for even taking this so seriously? I consulted with an event organizer Beth Niblock (CIO of Detroit) and she informed us that “You’re probably thinking about it too hard”. Yikes! That made me even more concerned.

I’ve been taught the hard way to never sign anything I don’t fully understand, and the Indemnification clause alone made the $5K prize money seem tiny compared to the unlimited liability I’d be exposing myself to.

So after I spent an hour reading the contract and thinking, I decided not to submit an app to the City of Detroit.

I packed up my things and left. What a shame.

I wanted to make an awesome app.

How could they fix this in the future?

  1. Most importantly, put the contract online before registration so that we can read it before we register for the event.
  2. Take out the one-way indemnification clause from the contract or limit total cost to Participant to Participant’s prize winnings.
  3. Remove the perpetual, royalty-free license for derivative work from the contract.
  4. Remove the waiver of jury trial.
  5. Remove the waiver of right to sue (is this even enforcable? I suspect no)
  6. Include reasoning for each clause so that the non-lawyer participants can understand why clauses have been included.

So I’m still not sure if I made the right decision, but I couldn’t sign that document and feel good about it. Was I taking the indemnification clause too seriously or was I right to go with my gut?

Original URL:  

Original article

How IBM Watson apps are changing 7 industries

Watson transforms industries
0 watson intro title

Since IBM opened IBM Watson to the world last year, it has been building a developer and entrepreneur community around the development platform. The community now consists of more than 280 commercial partners, as well as tens of thousands of developers, students, entrepreneurs and other enthusiasts that are generating up to 3 billion monthly API requests on Watson.

To read this article in full or to leave a comment, please click here

Original URL:  

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: