Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #71291

Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues)

From Mark H Harris <harrismh777@gmail.com>
Newsgroups comp.lang.python
Subject Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues)
Date 2014-05-11 00:36 -0500
Organization Aioe.org NNTP Server
Message-ID <536F0C77.5030108@gmail.com> (permalink)
References <mailman.9870.1399764946.18130.python-list@python.org> <39c6fc1b-9720-4606-9879-bcb48aa9958b@googlegroups.com>

Show all headers | View raw


On 5/10/14 11:16 PM, Nelson Crosby wrote:
> I also believe in this more 'BSD-like' view, but from a business
> point of view. No one is going to invest in a business that can't
> guarantee against piracy, and such a business is much less likely
> to receive profit (see Ardour).
>
> Don't get me wrong - I love free software. It's seriously awesome
> to see what a community can do. But at the same time, some people want
> to earn a living from writing code. That is simply not possible
> without proprietary software.
>

That's just the point...

The twenty-first century is not going to be about making money by moving
bits around a network, nor about making money writing code. It is going
to be about making money|living (whatever that means) by leveraging free 
networking (think libre box) and by leveraging free (as in libre) 
software and libre software engineering.

In other words, no longer are coders going to make a living writing 
proprietary code; rather, coders are going to make a living leveraging 
their skill writing libre software (in the specialized problem domain 
needing their resources --- free agents, have skill, will travel, or 
connect).

So, I go to work for some technical scientific research outfit that just 
got a federal grant for yadda yadda... and I bring in my toolkit|toobox 
(julia, haskell, python, C++ &c whatever) and I make a living coding 
within that specialized domain.  I don't market the app (& they don't 
either).  The killer app in the 21st century IS the unix distro 
(gnu/linux), and the toolbox is (mine, or yours).

We are going to stop purchasing software across the board, and we are 
going to share. In the process we are going to make our livings with our 
skills, services, innovations towards specialized problem domains 
through leveraged technical specialty, and by working together to better 
the whole.

This is already occurring.


marcus

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Chris Angelico <rosuav@gmail.com> - 2014-05-11 09:35 +1000
  Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Nelson Crosby <nelsoncrosby@gmail.com> - 2014-05-10 21:16 -0700
    Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Rustom Mody <rustompmody@gmail.com> - 2014-05-10 21:48 -0700
    Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Mark H Harris <harrismh777@gmail.com> - 2014-05-11 00:36 -0500
    Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-11 07:13 +0000
  Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Mark H Harris <harrismh777@gmail.com> - 2014-05-11 01:25 -0500
  Re: Free vs proprietary (was Re: NumPy, SciPy, & Python 3X Installation/compatibility issues) Mark H Harris <harrismh777@gmail.com> - 2014-05-11 01:25 -0500

csiph-web