Slashdot Mirror


Stallman's Legacy Halts At Hardware (hackaday.com)

szczys writes: To say Richard Stallman had a profound effect on free software is not a bold enough statement. The power of the GPL, and his advocacy for software freedom have changed the world. But there is one frontier that has yet to hear this gospel. These days, no hardware is an island. Almost every type of electronics we use is running some type of code, and in almost every case some of that code is secret in more ways than one. From beefy processors to graphics controllers, boot ROMs and binary blobs run in the silicon we base our systems upon. The code is not published and in the rare case that you are able to view the source it is only under strict NDA. This represents one of the biggest barriers to true open hardware.

208 comments

  1. All in for transparency? by ArcWild · · Score: 5, Interesting

    Stallman has always had the right idea IMHO, but that 'ideal' put up against Corp Profit will never win sadly.
    "Those who don't understand code, will be owned by those who do"
    I'm all for a hardware manufacturer who creates and promotes 100% open hardware with public code provided.....................know any?

    1. Re:All in for transparency? by jellomizer · · Score: 2, Insightful

      The success of the GPL is in spite of Stallman not because of it.
      Most successful GPL program are "Infrastructure based" Operating Systems, Web Servers (the most popular one is under the Apache Open source license) , Programming Languages, Databases. These are software that people use as the backdrop to the real work they are trying to accomplish. Installing a Database will not solve any problems, but using the database to solve your problems may improve your success. These get a lot of action because these are tools people really want, there are enough of them to keep interest, and the fact that they are not solving any real business need, means a lot of people don't have interest on keeping it for themselves. Support in an Open Source Project means that your particular needs will have a say in a larger project.
      However GPL doesn't have too much in end use applications because they are solving rather narrow solutions. So they will not get a lot of support because their solution is very narrow. This means if someone is going to spend a lot of time/money working on a solution they will need to sell the software for money.

      The problem with Hardware manufactures is that they make money off their hardware. There code is specialized for their hardware. So they are not so willing to let it go.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:All in for transparency? by Anonymous Coward · · Score: 0

      The success is despite your personal vendetta, not because of it. The GPL is the GPL because of Stallman. End of story.

    3. Re:All in for transparency? by Anonymous Coward · · Score: 0

      You must be a greasy neckbeard just like Stallman.

    4. Re:All in for transparency? by tnk1 · · Score: 1

      Open code turns hardware into even more of a commodity where they start racing toward the bottom in price. No one in the hardware business really wants that. Inter-operability between products per some agreement? Sure. Open hardware. Good luck.

      They will need to be forced to allow open hardware by some means or development. It is not in their interests to do so otherwise, and so far they cannot be forced to.

    5. Re:All in for transparency? by Anonymous Coward · · Score: 0

      The problem with Hardware manufactures is that they make money off their hardware. There code is specialized for their hardware. So they are not so willing to let it go.

      Doesn't make sense to me. Manufacturers make money off the hardware - so they have no need for closed software. I need to actually buy a motherboard before I can use the bios code that go with it. The code is no use without the hw it was made for. If that bios is open-source, chances are it is in better shape. (And being a programmer, I can add my own improvements/fixes if I feel a need.)

      So open software gets more hw sales to programmers who know how sw/hw works. In turn the sw gets the occational improvement - this gives the manufacturer an edge over other hw manufacturers. win-win & profit too.

    6. Re:All in for transparency? by lkcl · · Score: 1

      I'm all for a hardware manufacturer who creates and promotes 100% open hardware with public code provided.....................know any?

      yeah, that'll be me.
      http://rhombus-tech.net/commun...
      https://www.crowdsupply.com/eo...

      i also have an RYF / FSF-Endorseable CPU Card under development:
      http://rhombus-tech.net/ingeni...

      just so you know, i currently have a sponsor for the 15.6in laptop, i've been working on it for 14 months now. sponsorship works well for two reasons: firstly, investment is usually profit-driven, so the priority is on maximising the investor's profits instead of getting the product - and even more importantly the modular standard - right. secondly, sponsorship is absolutely fair and honest. i receive what i need to do the job, and the sponsor(s) get to be able to buy (or in the case of my main sponsor, sell) the end product(s).

      so if you'd like to sponsor the development of these products, do contact me ok? love to hear from you.

  2. Soap == Stallman's kryptonite by Anonymous Coward · · Score: 2, Funny

    His legacy also stopped at bathing as well.

    1. Re:Soap == Stallman's kryptonite by Anonymous Coward · · Score: 1
  3. Wrong... by LynnwoodRooster · · Score: 2, Informative

    The biggest barrier to true open hardware is the fact someone has to pay for a tangible good, and that tangible good - hardware - is designed for a specific purpose. The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon as you desire. The block is silicon that does what you want to do in the first place. And that carries with it costs beyond just software creation.

    --
    Browsing at +1 - no ACs, I ignore their posts. So refreshing!
    1. Re:Wrong... by Anonymous Coward · · Score: 0

      The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon as you desire.

      huh? So I can plug 12 hard drives into an IDE controller even though it only supports two, just because I desire?

    2. Re:Wrong... by Anonymous Coward · · Score: 0

      That basically amounts to "hardware is expensive". Software can be expensive as well but we've found ways to bring that cost down to a level where the barrier to entry is quite small. The open source hardware movement should fix this problem. Once we can fab processors in our bedrooms or in the basement then the tinkering will start and the knowledge will flow.

      We're not there yet.

    3. Re:Wrong... by xxxJonBoyxxx · · Score: 0

      >> Once we can fab processors in our bedrooms or in the basement then the tinkering will start and the knowledge will flow. We're not there yet.

      You'll never get there. See all the pending rules about OMGDrones! for an example.

    4. Re:Wrong... by Anonymous Coward · · Score: 0

      I guess you haven't heard about PCB printers and ASICs, have you?

    5. Re:Wrong... by OrangeTide · · Score: 1

      You can plug and unplug your IDE drives as frequently as you desire, up until the insertion rating of the connectors.

      --
      “Common sense is not so common.” — Voltaire
    6. Re:Wrong... by fuzzyfuzzyfungus · · Score: 2

      I wish that this were more often true; but firmware appears to be getting bigger and uglier(even on systems where 'firmware' means only the BIOS-or-equivalent stuff, not the entire embedded OS), rather than more unobtrusive over time.

      Sure, the PC BIOS was pretty lousy; but we went and replaced with with UEFI, which is essentially an always-on secondary OS designed by the people who thought that ACPI wasn't a dubious plan. That's not exactly progress.

      It's also false that firmware doesn't limit you from using silicon as you prefer: Since it's often cheaper to reduce the number of different SKUs than it is to shave every last transistor off the size, it's quite common to find parts that are feature-differentiated by firmware enforced locks(and, with a competent implementation of 'verify against the key burned into silicon', not something you can reasonably expect to just hack around). The Rasberry Pi, for instance, is based on a chip with a variety of supported codecs; but Broadcom will sell you versions with some enabled or disabled(so that you can avoid paying license fees for codecs you have no intention of using; but they don't need to spin a variant for every last possible combination of codecs). The rPi people attempted to square this particular circle by arranging so that you can buy unlock codes individually as needed; and I don't blame them for a situation largely beyond their control; but they are a good example of hardware whose exposed capabilities are directly controlled by firmware.

      More broadly, the delightful 'crypto bootloader' phenomenon has cut a fairly broad swath through hardware openness. Tivoization is not a new thing; but it seems to be more popular than ever; and techniques for moving enforcement directly onto the die, where attacks are difficult and almost always uneconomic, has proceeded apace. If you can't even boot something not blessed by the vendor, the hardware could be 100% open and it still wouldn't do you a bit of good without the necessary private key.

    7. Re:Wrong... by maligor · · Score: 1

      The biggest barrier to true open hardware is the fact someone has to pay for a tangible good, and that tangible good - hardware - is designed for a specific purpose. The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon as you desire. The block is silicon that does what you want to do in the first place. And that carries with it costs beyond just software creation.

      I think the point where GPL fails in hardware currently is tooling, and assosiacted low level designs/operations to make ASICs. There's plenty of hardware model designs under (L)GPL, including the OpenRISC. It's not that the materials in the chips is expensive, it's just expensive to start making them.

      Realistically something like this could be kickstarted - aka, making a large batch of OpenRISC SoC's, but it would be quite risky, in many areas like performance or having a completely failed batch due to a issue in the asic design. I'd probably give money, but there'd need to be a huge pool to make it feasible.

    8. Re:Wrong... by Bert64 · · Score: 1

      That is a hardware limitation not a software one...
      The Amiga only supported hard drives up to 4GB due to software limitations even tho neither IDE nor SCSI had such hardware limitations. By replacing the software it was possible to use much larger drives.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    9. Re:Wrong... by Anonymous Coward · · Score: 0

      since i can control the silicon as i desire, why can't I get hdmi video signals from a commodore 64? i guess i'm not desiring hard enough

    10. Re:Wrong... by lkcl · · Score: 5, Interesting

      The biggest barrier to true open hardware is the fact someone has to pay for a tangible good, and that tangible good - hardware - is designed for a specific purpose. The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon as you desire. The block is silicon that does what you want to do in the first place. And that carries with it costs beyond just software creation.

      i'm designing Libre Hardware, right now. i've been on this task for the past five years, since the embarrassing time when i encouraged 20 software libre developers to join me in buying one of the very first ARM netbooks to come out (back in 2010) that turned out to be GPL-violating. i had to spend a frantic 3 weeks reverse-engineering the hardware in order to provide those people with a GPL-compliant linux kernel.

      this example just on its own demonstrates that what you have said is simply untrue in a very profound and subtle way. you claim "The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon" - how can you load a kernel into memory using the BIOS's bootloader (if there is one) if you do not know how the BIOS *actually works*? how can you load a kernel into memory if you don't have the hardware's documentation? what if the proprietary bootloader (if there is one) has some sort of checksum or DRM where you are not provided the keys?

      another example is the IBM / Lenovo laptops, where the BIOS had the PCIe device and MAC address of the WIFI adapter *burned into EEPROM*. quite literally the only way for people to replace the WIFI adapter was to *replace the entire BIOS*. that required a *massive* reverse-engineering effort and we now have coreboot support for many Lenovo laptops.

      time and time again i have had to cut certain SoCs and ICs from the list of products because i cannot get the SDK, cannot get the Datasheet, cannot get *any* information about how the SoC or IC works.

      so you claim "the block is silicon that does what you want to do" - it only does what you want to do via a hardware API which requires an extremely comprehensive bit-level and timing-critical software-driven understanding of that "block". without that, the hardware is LITERALLY useless. [remember NDISWRAPPER for WIFI cards?]

      can you see, therefore, through these examples, that you've fundamentally misunderstood the complexity of the issue, and why there are such severe barriers to entry in the hardware arena?

      i *do* understand this, so it's why i have been working for the past five years on creating Libre-compliant eco-conscious hardware, where the hardware - all of it - will be vetted for GPL-compliance before putting it into production. sounds mad? but it's the only way, i feel, that instead of waiting for someone else to tackle this, i'm *actively* taking responsibility for ensuring that there exists Libre-compliant Hardware.

    11. Re:Wrong... by Dputiger · · Score: 1, Insightful

      You'll never get there because you need 99.9999999% purity and precisely balanced climate controls to do cutting-edge semiconductor fabbing. Government regulation has nothing to do with it. You can't build semiconductors of modern quality or capability in a bedroom, any more than Chinese peasants could build backyard steel furnaces during the Great Leap Forward.

    12. Re:Wrong... by Dputiger · · Score: 1

      You can fab some *extremely* simple boards and designs this way, yes. You're not going to build anything approaching the computing power of the last 15-20 years on that kind of equipment.

    13. Re:Wrong... by AmiMoJo · · Score: 0

      The GPL v3's anti tivoization clause does a lot to protect your right to do what you want with your silicon. Stallman has opened a lot of hardware for us.

      In fact, without the free software movement he started would the companies that do provide somewhat open, hackable hardware do so?

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    14. Re:Wrong... by Anonymous Coward · · Score: 0

      You can plug them into an IDE controller, your ass, or pretty much anything else you like. Whether or not it works... that's a different story. But yeah, you can probably find a way to connect them.

    15. Re:Wrong... by Anonymous Coward · · Score: 0

      Sure, you can't make a processor equivalent to the one intel produces in your home (you could, technically, if you had a VERY expensive ASIC, but it would run at 1 Mhz).
      But, there is still A LOT of stuff that you can make with it that people simply don't bother to do.
      If you need more complicated pcbs, you can always order them from your local pcb fab, or from china.
      You wouldn't get much better turnaround times in a corporate enviroment.

    16. Re:Wrong... by Anonymous Coward · · Score: 0

      You don't have a fucking clue how to handle the pinouts.

      Even a Sega Genesis can output over HDMI with a bit of modification.

    17. Re:Wrong... by Anonymous Coward · · Score: 0

      >> Once we can fab processors in our bedrooms or in the basement then the tinkering will start and the knowledge will flow. We're not there yet.

      You'll never get there. See all the pending rules about OMGDrones! for an example.

      You will never get there because you don't have 4-10 Billion dollars to build a fab. And because you thing regulations are the problem, you obviously don't have the technical knowledge either.

    18. Re:Wrong... by unixisc · · Score: 1

      The biggest barrier to true open hardware is the fact someone has to pay for a tangible good, and that tangible good - hardware - is designed for a specific purpose. The BIOS and bootloaders and such are immaterial, and do not limit you from using a piece of silicon as you desire. The block is silicon that does what you want to do in the first place. And that carries with it costs beyond just software creation.

      Yes & no! It's true that if I take a piece of 'truly open hardware', it would be at the expense of YOU getting it. However, the issue here would be the 'freedom' to fix, replicate the hardware, just like the 4 freedoms of GNU.

      Talking just about electronic hardware - stuff that can be done in silicon - you would normally have HDL models of anything you design. Let's say you had a VHDL model of a chip, and wanted to share it. You could send the model to someone else, without giving that someone the actual chip itself. It would be up to that other person to get an FPGA which he could burn w/ this code, or if he had the appropriate CAD software, he could go ahead and tape out the design. Of course, involving entities like fabs, simulation software and all those other things makes it too expensive to be done at an individual level. But on an organizational level, people could take such open hardware specs and models and replicate or improvise such designs, and also distribute them downstream.

    19. Re:Wrong... by sbaker · · Score: 4, Insightful

      What is being discussed is not "free" (as in "free-beer!") chunks of physical hardware, Indeed, that would be tough to do because physical objects are made of atoms - and atoms are not generally zero cost items - so they cannot be copied and distributed for free. We're talking about "free" (as in freedom) hardware that can be understood for $0 and (at some cost/difficulty) copied. The design of the hardware is free (as in beer and as in freedom) but the hardware itself is only free as in freedom.

      To look at it another way - if I design and build a house - I can offer the plans for free under a GPL-like license. You can then look at my plane, improve them and you can use the plans to build yourself a house - all without without paying me a cent...but you still have to buy the bricks and pay the builder. You *do* have to pay for your own "copying". That's actually the same with software - if I want a copy of emacs, even though it's GPL'ed, I have to pay for the bandwidth and disk space to make myself a copy of it (the GPL even allows the author to charge me a reasonable amount for making that copy - which is something that almost never happens!) The distinction between copying GPL'ed emacs and copying my GPL'ed house is in the cost of copying the item (fractions of a penny versus hundreds of thousands of dollars). That's not a conceptual difference - it's just a matter of scale - and it's not even necessarily larger. I've downloaded hundreds of Gigabytes of stuff that cost me many dollars worth of disk space to store - and I've downloaded the open-hardware design for a bracket for my "lasersaur" laser cutter that cost pennies to manufacture.

      The problem we're discussing with hardware that depends on "binary blobs" is in no way different from writing software that requires an external library for which you don't have source code.

      The issue is whether the software library is free (as in beer) or not. If you have to link some GPL'ed program to DirectX in order to run it under Windows - the software can still usefully be GPL'ed because even though DirectX is a closed source "binary blob" - people who run Windows all have a copy of it already. So it's effectively free-as-in-beer. However, if you write your own closed-source middle-ware package and charge people $100 to license it - then creating some GPL'ed application that requires that middle-ware isn't a very constructive thing to do. Of course we'd prefer that all of the libraries we use are also GPL'ed - but that's not an absolute requirement - and it's not a particularly reasonable one out here in the "real world".

      OpenHardware that requires use of a binary blob is no different from software that requires some complicated library. If the binary blob is legally copyable (free as in beer) - we can still usefully make our own copy of the hardware. But if the binary blob is either not legally copyable or requires a license fee to copy - then we're in the same situation we were in with software that needs a pay-to-license middleware library.

      Viewed in this way, OpenHardware is no different at all from OpenSoftware - EXCEPT that the cost of copying it is higher because it's made of atoms instead of bits.

      --
      www.sjbaker.org
    20. Re:Wrong... by Anonymous Coward · · Score: 0

      So true, UEFI BIOSes suck big time....and saying you can just use a piece of silicon as your heart desires is just bullshit as well as incredibly stupid.

    21. Re:Wrong... by Anonymous Coward · · Score: 0

      Thank you for working on this.

    22. Re:Wrong... by erapert · · Score: 1

      Do you have a website for your project, your team, etc?

    23. Re:Wrong... by Anonymous Coward · · Score: 0

      FPGA. ASICs are what you can't make in your bedroom.

    24. Re:Wrong... by fustakrakich · · Score: 1

      On the Phoneblocks site linked from yours:

      We believe that all our electronics should be built like this, modular. With one universal platform for the whole world....

      *Ahem* Do you really want this?

      --
      “He’s not deformed, he’s just drunk!”
    25. Re:Wrong... by nateman1352 · · Score: 1

      i'm designing Libre Hardware, right now. i've been on this task for the past five years, since the embarrassing time when i encouraged 20 software libre developers to join me in buying one of the very first ARM netbooks to come out (back in 2010) that turned out to be GPL-violating.

      So you have a GPL ARM netbook somewhere? Can you please provide me the URL to download the RTL for that ARM chip you have in that netbook? Also, please send me the URL to download the silicon layout files? Which foundry did you contract with to build that chip? TSMC?

      All commercial contract silicon foundries with any semi-recent process node (32nm or lower) require you to sign an NDA before they provide you with the transistor models for their manufacturing process. If your ARM chip design is under a GPL license, how do you deal with the fact that it is impossible to distribute your layout file without also distributing the layout for your foundry's transistor design which is under NDA?

      Even if your CPU design is fully synthesizable and you only distribute the RTL (which by the way will make your design a bit slower than if you had VLSI engineers custom design some of the critical paths in the CPU layout)... wouldn't running the synthesis tool be the same as running the compiler on software source code, so wouldn't the layout files that result from the synthesis be considered a derived work which also must be GPL licensed? Also, last time I checked there isn't any open source synthesis tools and both Synopsis and Cadence charge 6-figures to license their closed source synthesis tools. Are you addressing the lack of open source design tools? Do you have a cluster somewhere with some of that software available?

      In other words... I'm 100% sure that your ARM silicon design is not GPL, in fact I'm 100% sure that it's not open source because ARM Limited Inc. only provides ARM licenses under NDA. You bought that ARM chip from some company with a closed source silicon design. The only thing you are focused on is designing an open source PCB to put a closed source CPU on top of. You make the incorrect assumption that just because you can send your PCB to any PCB manufacturer and get the same result back, the same thing can be applied to chips. PCBs are easy, chips are hard. The OP is right. There is a fundamental difference when you are talking about manufacturing something that requires billions of dollars worth of capital expense in order to create the factory necessary to build the device. Nobody spends billions to create the capability to manufacture modern silicon and then gives away their factory's transistor design in today's world. Until open source foundry exists and open source silicon design exists... your obsession over firmware binary blobs is penny wise and dollar dumb.

      If you want to actually change something, you should be pitching open source foundry... honestly I think its a rather hard sell :) The much more feasible thing for you to do would be to start developing open source silicon design software. Just like how GCC was a prerequisite to an open source UNIX, open source silicon design tools are a prerequisite to open source hardware.

    26. Re:Wrong... by DrVxD · · Score: 1

      You will never get there because you don't have 4-10 Billion dollars

      Speak for yourself.

      you obviously don't have the technical knowledge either.

      Ah, I see that you were.

      --
      Not everything that can be measured matters; Not everything that matters can be measured.
    27. Re:Wrong... by AmiMoJo · · Score: 1

      Actually, the Broadcom decoder situation is a little different to how you describe it. The Broadcom decode is a binary blob that you need a licence to use. You could however implement your own hardware accelerated decode if you had complete documentation for the chip and weren't worried about patent issues. So really the problem is not that the chip has features disabled by firmware, it's that there isn't enough documentation for a free implementation of the firmware and possible patent issues.

      This highlights a way in which hardware has actually become more open recently, in a sense. Firmware is often not fixed or even loaded into chips any more, but rather loaded by the driver at run time. Thus, the firmware can be replaced - it's not stored in ROM and usually not required to be signed. Many CPUs work that way, so in theory with the right information you could re-write a lot of the microcode on your Intel Core i7.

      Of course in practice a lack of documentation prevents this from happening, but there are examples of modifications and hacks which hopefully one day will evolve into more complete replacements for the original firmware.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    28. Re:Wrong... by david_thornley · · Score: 1

      You can try, just as you can try using gcc to compile Haskell or Lisp code. Success is not guaranteed.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    29. Re:Wrong... by david_thornley · · Score: 1

      The really interesting part is not that hardware is expensive to duplicate, but that software isn't. If you have a CPU and want another, and don't want to pay Intel or AMD for one, you need an extremely expensive fab. If you have an operating system and want another, you send it over cheap digital communications cables or burn a DVD or something inexpensive like that.

      I could cheaply provide you with an entire high-quality operating system with lots of additional software, and it wouldn't take that long. As long as I give you a Free OS and Free software, it's all legal. I can't do that with hardware.

      This screws up perceptions about software engineering. Most people are used to a design phase and a production phase for stuff, and therefore tend to think of writing the software as production rather than the low-level design it is.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    30. Re:Wrong... by david_thornley · · Score: 1

      Lots of computers were pretty much open and hackable before Stallman started the Gnu project. I don't know if Free Software helped or not.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    31. Re:Wrong... by Anonymous Coward · · Score: 0

      THIS, you hit it right on the head! The problem is not right licence that IMO is more of a self evolving thing. It is lack of synthesis & verification tools like gcc which was a huge enabler. Stallman's biggest contribution to oss is gcc NOT GPL. I touched upon that in my other AC remark http://hardware.slashdot.org/c...

    32. Re:Wrong... by so.dan · · Score: 1

      Thank-you very, very much for your work. I appreciate it a huge amount.

  4. Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0, Insightful

    In the long run, the real legacy of the GPL will be that it proved that developers and users don't want lengthy, highly-restrictive licenses that claim to be "open" and claim to support "freedom".

    Instead, they want concise licenses like the BSD and MIT licenses that go out of their way to promote openness and freedom for all: for developers, for users, and for those who wish to use open source code without contributing back any changes.

    That's the thing about freedom that the GPL crowd just doesn't get. It's not freedom when you force somebody else to contribute back changes they made to software; it's tyranny.

    True freedom is when you get to choose what you do with changes you made to open source software. If you want to contribute them back, then you can do it. If you don't want to distribute the modified source code, then you don't have to. It's real freedom at work: you choose what you want to do, without somebody else dictating anything to you.

    The BSD and MIT licenses offer true freedom. The GPL offers restriction and the elimination of freedom.

    1. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0, Flamebait

      Nice trill, shill. GPL is by far the most popular license on the planet, and it's growing. Whaaa whaaa, BSD, whaaa whaa, MIT. Nope. GPL is the code you'll find in just about every non-Apple consumer electronics device; even though the manufacturers could take vanity-ware licensed projects and keep quiet about them. They don't, though. Wonder why?

      If you want to steal another's code, and pass it off as your own, hunt out the substandard and abandoned BSD equivalents.

    2. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 1

      I remember a lot of people back in the 90s and 2000s that tried to use public domain or BSD, MIT, ISC license and where extremely upset when their software was used commercially without anything given in return. The code was often warped and hacked until it was a bug ridden mess, and totally out of control of the original authors.

      I'm fine with this, I use an ISC license on things I write, but I know first hand that someone can take the software and never give anything back. And for some programmers, this is their worst nightmare and hugely demotivating to them. Many of those old projects forked into more restrictive licenses, often as GPL. (wine being the most famous)

    3. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 1

      Nice trill, shill. GPL is by far the most popular license on the planet, and it's growing. Whaaa whaaa, BSD, whaaa whaa, MIT. Nope. GPL is the code you'll find in just about every non-Apple consumer electronics device; even though the manufacturers could take vanity-ware licensed projects and keep quiet about them. They don't, though. Wonder why?

      If you want to steal another's code, and pass it off as your own, hunt out the substandard and abandoned BSD equivalents.

      Manufacturers only use GPL code when it pretty much already does what they need it to do. GPL and other open-source software is nothing more than the commoditization of software.

      Which is why software that isn't a commodity - small user bases with stringent requirements that make "good enough" not good enough - is still mostly closed-source. Such as truly redundant highly-available shared-storage databases or WORM archiving for SOX compliance.

      Commodity software works like commodity hardware. How often do you have to reboot your Android phone?

    4. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      I sort of feel this way too; however, I wonder if something like the Linux kernel would have been as successful if not for the GPL. Say a company like Freescale makes a chip, and then ports linux to it so a tablet manufacturer can buy it and run Android on it. Were it not for the GPL, I wonder if those ports to their chip would ever make it back into the mainline kernel.

    5. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 2, Informative

      Uhhh...no, it's not the most popular:
      https://www.blackducksoftware.com/resources/data/top-20-open-source-licenses

      And no, it's not growing:
      http://osswatch.jiscinvolve.org/wp/files/2015/02/figure2.png

    6. Re:Why are so many moving away from the GPL? by Bert64 · · Score: 4, Insightful

      It's not freedom that in todays society we are not free to kill anyone we want, or take anything we want from anyone else...
      Sometimes you have to give up freedoms which would allow you to harm others, and thats what the GPL does... You are given a limited set of freedoms by the GPL, and the primary limitation is that you must grant the same level of freedom to anyone else, you're not free to limit someone else's use of the software.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    7. Re:Why are so many moving away from the GPL? by fonos · · Score: 5, Insightful

      Nothing in the GPL forces you to contribute back changes. You can download GPL'd code, change it however you want, and use it on your own systems to your heart's desire, without having to contribute anything.

      However, if you download GPL'd code, modify it, and distribute a binary, you must distribute your code changes under the GPL. If you don't want to do that, write your own damn code from scratch. None of this is forced upon you.

    8. Re:Why are so many moving away from the GPL? by AmiMoJo · · Score: 5, Insightful

      Without the GPL we wouldn't have much of the freedom we now enjoy. Would Linux be so popular, would it get as much contribution from private companies if they were able to release their own proprietary versions? Look at BSD. It doesn't benefit much from Sony using it on their games consoles and in their smart TVs, because they don't have to give anything back.

      Without GPL software, software that wouldn't exist in the way it does without the GPL, we would be much more reliant on non-free products. We would be less free to compute.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    9. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      It's real freedom at work: you choose what you want to do, without somebody else dictating anything to you.

      So, let me get this straight, you want to choose to do what you want without somebody else dictating something at you...
      ...but you're dictating to somebody else how they should license code that they wrote?

      And if they don't license their code exactly like you dictated to them to do, it's 'tyranny'?

      Let me ask you: Do hypocrites understand irony or not?

    10. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 1

      If you want to contribute them back, then you can do it. If you don't want to distribute the modified source code, then you don't have to.

      You have that freedom with the GPL! It's only if you distribute copies of your compiled binaries to others that you're required to supply the source code. And in that instance, not supplying them with the source code is restricting *their* freedom.

      The only freedom the GPL restricts is the freedom to restrict the freedom of others.

    11. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      You can download GPL'd code, change it however you want, and use it on your own systems to your heart's desire, without having to contribute anything.

      You can do that every time the master branch is updated, which is of course tiresome. So people want their patches in the master branch, which is often good for everyone. Sadly all projects under the FSF umbrella are controlled by Stallman and he made it clear that he considers current programming trends such as clean software design and easy re-factoring the antithesis of free software and that he or his flunkies will not only refuse any such patches but also go out of their way to break APIs in every new update if they are found to be used for such. In the end you are free to do what Stallman wants you to do or suffer the consequences.

    12. Re:Why are so many moving away from the GPL? by lkcl · · Score: 5, Insightful

      The BSD and MIT licenses offer true freedom. The GPL offers restriction and the elimination of freedom.

      this is a very subtle and dangerous perspective that has one extremely large software project which has ended up in complete chaos, causing headaches for many people, including misunderstandings and ignorance by vendors who assume that because the majority of the software is BSD/MIT, the linux kernel's GPL license is somehow magically transmuted to a BSD/MIT license as well.

      that software is android.

      the only reason why we have things like cyanogen, thank god, is because there is one last bastion of fundamental GPL code left in android devices: u-boot and the linux kernel. without that, the smartphone industry would be viewed with extreme hostility. it's *already* bad enough in cases where companies such as Mediatek blatantly and continuously violate the GPL.

      look at what happened with Fairphone, for example. great product, yes? envisioned as being sustainable, yes? and after 2 years, what happened? well, there turned out to be some security vulnerabilities in the version of android that was supplied (by Mediatek). it was *critical* that the users upgrade. but, because Fairphone had naively bought a binary-only GPL-violating OS from a 3rd party OEM company that *DIDN'T EVEN HAVE THE SOURCE CODE*, there was no way to provide updates of *ANY KIND*. the buyers therefore had to abandon their products for security reasons. bear in mind that this is supposed to be eco-conscious *sustainable* hardware that's supposed to be re-usable. it was extremely embarrassing for Fairphone, and a very hard lesson for them.

      so that's even when there's a GPL kernel. imagine what it would be like - imagine the situation if the linux kernel *wasn't* GPL? you would end up with the exact same situation as with apple. apple _used_ to release the kernel source code (based on FreeBSD) back to the community... they stopped recently. the end result: people no longer actually own their own hardware.

      the GPL is, at its heart, a recognition that collaboration is better than competition and secrecy. the BSD and MIT licenses were developed when everybody released source code *anyway*. the licenses were therefore more about fighting the liability that is inherent in releasing code as "Public Domain". everyone *trusted* that the code modifications would be released.... and then suddenly they weren't [did you even *know* for example that Windows 95's TCP/IP stack is actually BSD-licensed?]

      google's insistence on using BSD licenses - to the point of re-implementing entire GPL-based pre-existing libraries - has resulted in untold very subtle harm to end-users and to software freedom in general - harm that is very difficult to quantify and explain because it's long-term, and the consequences are ongoing.

      the one thing that really really stinks about what google did with android is summed up in this simple question: they replicated dozens of critical low-level libraries and applications that had perfectly-functional GPL versions that were proven and had stable communities based around them (that could really have done with the financial support of google).... so why did they not replicate the Linux Kernel as a BSD-based project as well? that hypocrisy - that they did not also re-create the Linux Kernel as a BSD/MIT project - tells you everything that you need to know.

    13. Re:Why are so many moving away from the GPL? by DRJlaw · · Score: 1

      So, let me get this straight, you want to choose to do what you want without somebody else dictating something at you... ...but you're dictating to somebody else how they should license code that they wrote?

      And if they don't license their code exactly like you dictated to them to do, it's 'tyranny'?

      Let me ask you: Do hypocrites understand irony or not?

      How did GP "dictate" to somebody else how they should license code? Are there legal consequences if they chose to ignore the instructions? Jail? Fines? A refusal to fulfill some obligation that is owned unless the licensor bows GP's will?

      Or have you simply decided that advocacy is a dictat because you need it to be one?

      I think you have no real understanding of the meaning of the words dictate, hypocrite, and irony. I thkn that you are merely throwing those words around because you have no better argument to make.

    14. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      It's not freedom when you force somebody else to contribute back changes they made to software; it's tyranny.

      There's nothing in the GPL that forces you to contribute back your changes to GPL software unless you distribute binaries.

    15. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Be honest about wine, they only went gpl because no one liked Transgaming.

    16. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Explain why BlackDuck ranks MIT as the most popular license in use, with GPL v2 trailing a few points behind?

      https://www.blackducksoftware....

      From that chart, the only way GPL is "the most popular license on the planet" is if you add GPL2 and GPL3 together, and since they're very different licenses, that'd be more than a little disingenuous of you.

    17. Re:Why are so many moving away from the GPL? by exomondo · · Score: 1

      Would Linux be so popular

      If Linux were GPL it would most definitely not be so popular, it's popularity stems from some of the clauses in the GPLv2 combined with the explicit exclusion of GPL provisions in the license preamble. The GPL is good in some respects and bad in others. Linux would also not have been anywhere near as popular had the GPLv3 provisions regarding Tivoization existed in the GPLv2.

      As Linus has repeatedly said, Linux isn't about Free Software ideals, it is about "tit-for-tat" code contributions (hence the reason he sees Tivoization as a good thing) and the GPLv2 offers that.

    18. Re:Why are so many moving away from the GPL? by iMadeGhostzilla · · Score: 1

      Argue the principles all you want, reality is people are moving away from GPL (esp. v3). Maybe GPL did help spread Linux and all the great tools better than MIT-style license would have, maybe it didn't, impossible to tell. Question is what do you do now. If you have too many people leaving, something is likely in need of a fix.

    19. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Without the GPL we wouldn't have much of the freedom we now enjoy. Would Linux be so popular, would it get as much contribution from private companies if they were able to release their own proprietary versions? Look at BSD. It doesn't benefit much from Sony using it on their games consoles and in their smart TVs, because they don't have to give anything back.

      Without GPL software, software that wouldn't exist in the way it does without the GPL, we would be much more reliant on non-free products. We would be less free to compute.

      FreeBSD seems to be getting support from EMC Isilon, Netflix, NetApp, Nginx, etc. from the commit messages I'm seeing. Let's also not forget Sendmail, BIND, and many other infrastructure software, especially in the early days of the Internet, were generally BSD/MIT licensed. Also, X11.

      Where you say "It doesn't benefit much from..." is telling. Perhaps it's not a matter of people thinking "what can I get back", but rather "what can give to the world". Perhaps people that like to the the BSD/MIT/X11 license are more generous in their giving. :)

    20. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Manufacturers only use GPL code when it pretty much already does what they need it to do.

      total bullshit, look at how oracle, facebook, amazon, etc. have modified linux to fit their needs and then contributed back their changes

    21. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Nice trill, shill. GPL is by far the most popular license on the planet, and it's growing.

      Actually it is waning. The most popular open source projects are permissively licensed, even Linux isn't pure GPL (it has specific omissions in the license that override the GPL and allow you to link to it with proprietary software).

      If you want to steal another's code, and pass it off as your own

      Nobody does that, he is talking about the additions. Even permissive licenses dont permit you to pass code off as your own. So the original remains free as the author of it wanted and the terms of the additions are decided by the author of those additions.

    22. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      The only freedom the GPL restricts is the freedom to restrict the freedom of others.

      That's a common (though often intentional) misrepresentation. The even permissive licenses don't allow you to restrict the freedoms of others, if I give you a binary I am not restricting you, do as you wish. Unless of course you want to play the MPAA/RIAA game of imagining that you have lost something you didn't have on the basis that I didn't give it to you so you then conflate that to mean I took it from you, which is obviously wrong.

    23. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      If the GPL doesn't force anything on anyone, then neither do proprietary licenses.

      If I don't like a clause in the GPL I can reject it, and the same is true of a proprietary license. Yet somehow GPL advocates somehow argue that thus isn't true...

    24. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      By telling them they were restricting the rights of others and bitching about their choice and insisting that the GPL should be ignored.

      Try reading next time.

    25. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Nothing in the GPL forces you to contribute back changes.

      Ahh, yes, but it's zealotry behind GPL that's the problem.

    26. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      Yes they do. They force you to pay. AND sign over rights. Remember that EULA?

      But apart from me here right now showing how you can be wrong, who is saying that propriatory licenses force other developers to be less free? Yet here you are, along with the other retards from the reject bin, complaining that the GPL is "less free".

      The BSD is *less free* because it doesn't stop slavery. Your freedom has to be defended from those who would remove it, and without that, you don't have freedom. The GPL is the Constitution for software. BSD is the Communist manifesto: from each of you writing BSD code to those that need it most, the companies who can close it up if they want and make you pay for it.

    27. Re:Why are so many moving away from the GPL? by KGIII · · Score: 1

      Not to quibble but I feel that this is essential to having a discussion along these lines.

      The fact of the matter is that I am free to kill you. I am not at liberty to do so. If you are trying to take my freedom then I have a right to kill you.

      Freedom is taken by force, more or less. Assuming you are not physically prevented from doing so, you're free to kill any one you want. There will be penalties for doing so and you shouldn't do it - but that's what freedom is all about. That's why they say, "Give me liberty, or give me death."

      Carry on then... I just figured it salient and of moderate importance.

      --
      "So long and thanks for all the fish."
    28. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      That's the thing about freedom that the GPL crowd just doesn't get. It's not freedom when you force somebody else to contribute back changes they made to software; it's tyranny.

      So you think if I pay you to mow my lawn, it's now *your* lawn, and you can just set up a lemonade stand or whatever?

      No, it's still my lawn. And if you don't like my rules, you can get off it.

    29. Re:Why are so many moving away from the GPL? by Anonymous Coward · · Score: 0

      I'm surprised more BSD/MIT/ISC licensed projects don't get the Transgaming treatment.

      X Consortium released MIT licensed code for years, and dozens of vendors picked it up and turned it into proprietary products. But it managed to sort of work because the vendors would frequently contribute small bits of code for the next release. Back then most of the X Servers were binary-only proprietary software. I think XFree86 / X386 was where things really started to change, and a fully working X server became part of every X11 Release after that.

  5. Also, the sky is blue, and water is wet by Anonymous Coward · · Score: 0

    This is all obvious. Why post an "article" which is simply clickbait?

  6. You know you're getting old. by Lead+Butthead · · Score: 4, Insightful

    When you start missing the days when every piece of hardware you bought came with schematics and firmware listings, instead of six page license agreement printed in four point fonts and written in incomprehensible legaless (and indeed, demanding adherence to reprehensible terms.)

    --
    ELOI, ELOI, LAMA SABACHTHANI!?
  7. It eould be nice, but... by ChrisMaple · · Score: 1

    What's the point? CPUs have hardware interface and instruction set specifications that allow reverse engineering. Sure, some things are microcoded, but microcode is slower than hardwiring and is mostly useful for working around design flaws.

    GPUs, on the other hand, are clouded in secrecy and there would be a benefit from opening them up much more than they are now.

    --
    Contribute to civilization: ari.aynrand.org/donate
    1. Re:It eould be nice, but... by Arnold+Reinhold · · Score: 2

      The big problem is security. There are too many places for exploitable bugs, deliberate back doors, key loggers, side channels and other forms of pwnware to hide in modern processors. Do you know where all the components in your PC were fabricated?

    2. Re:It eould be nice, but... by sbaker · · Score: 1

      The big problem is security. There are too many places for exploitable bugs, deliberate back doors, key loggers, side channels and other forms of pwnware to hide in modern processors. Do you know where all the components in your PC were fabricated?

      That's "security by obscurity" - which is no security at all. If you want to avoid all of those exploits, you have to allow the good guys to find, report and fix them before the bad guys find, hide and exploit them.

      --
      www.sjbaker.org
  8. Patents ... by gstoddart · · Score: 2, Insightful

    I think patents are why this can never work.

    Pretty much EVERY industrial process is patented by someone. That patent is guarded by a corporation who wants to ensure they get paid ... either through sales, or licensing the patent.

    IBM makes a zillion patent applications every year.

    There's simply no way you can bypass the sheer quantity of "intellectual property" which encumbers the world. And since pretty much every aspect of the hardware is probably covered under a patent, you're not going to get it.

    Hell, even with software, Microsoft used to insinuate that Linux violated a bunch of their patents, but wouldn't ever name them.

    The modern world has been structured to serve the needs to greedy corporations. They're not going to allow you to sufficiently change the rules of the game to take that away.

    Which is why every treaty these days is having the intellectual property pushed even harder, because governments are on the payroll of entities which want to further entrench their rights as superseding ours.

    Keep dreaming.

    --
    Lost at C:>. Found at C.
    1. Re:Patents ... by xtronics · · Score: 1

      It is NOT patents - it is everything to do with policy to prevent coreboot. They don't want hardware under the owners control.

    2. Re:Patents ... by gstoddart · · Score: 1

      Such vanity. Such utter vanity.

      Which do you think is more likely ... decades of greedy corporate behavior resulting in a "patent everything" mentality ... or some giant conspiracy to stop your pet project?

      Companies have been doing this crap since before coreboot. They're sure as hell not doing it because of coreboot.

      They want to block everybody, because they want control. They didn't get together and say "ZOMG! teh coreboot is teh enemy".

      It's just another bug on the windshield of the inexorable creep of corporate power; all of which started long before Linux.

      --
      Lost at C:>. Found at C.
    3. Re:Patents ... by erice · · Score: 1

      Strictly speaking, patents are not a problem for making software open. Open source reveals patented techniques but then, so does the patent application. The competition can see what you are doing but it doesn't matter because they can't use the information.

      Which means it is not an excuse for binary blobs. If it source was open, it still would not be free because of the patents but that's another problem.

      Binary blobs serve to protect trade secrets including elements are could be but are not yet patented.

      The real problem is that hardware development world is insanely protective of IP. So much productivity is lost is due to stifled communication to protect IP that isn't all that unique or useful.

    4. Re:Patents ... by Anonymous Coward · · Score: 0

      No. This has nothing to do with patents and everything to do with trade secrets. Libre software does not prevent patents at all, it prevents trade secrets.

    5. Re:Patents ... by Anonymous Coward · · Score: 0

      The consumer did it to themselves. You included. If you really cared that much about IP and how it's handled you could have made changes that would have left the titans of IP in the cold but instead you bought into them and likely still are but comforting yourself with moans of "oh me, oh my."
       
      Bugger off.

    6. Re:Patents ... by Anonymous Coward · · Score: 1

      Patents are only good for 20 years max before their teachings enter the public domain. In real life, patents often last for considerably less time. Part of the deal to get a patent is to disclose to the public what you're doing. This is pretty much of opposite of closed/secret firmware/hardware.

      "Pretty much EVERY industrial process WAS patented by someone" /FTFY

      There are two reasons for closed/secret firmware/hardware:
      1. The improvements are small efficiency gains and therefore not patentable or not deemed worth the cost of a patent. So the next best protection is to keep it secret.
      2. The owner of the tech figures they can get >20 years exclusivity by keeping it secret thereby bypassing the benefit of the patent system.
      2a. By the same token, the owner of the tech would have to spend crazy $$ reverse engineering competing products to see if competitors implemented the patented tech before enforcing the patent.

      I realize I'm trying to piss up a rope supporting patents here, but look at the system this way: Companies voluntarily pay large amounts of money into the public purse for the privilege of disclosing their confidential information to the public with the express understanding that the public will own that information after 20 years. They do this unconditional of the grant of the limited monopoly that allows them to spend millions of dollars to go to court to try to stop competitors from adopting the technology before the 20 years is up.

    7. Re:Patents ... by david_thornley · · Score: 1

      Open Source, in discussions like this, is normally used in the sense of the Open Source Initiative. Their definition of Open Source is very similar to the FSF's definition of Free. (And once more we see how Stallman was right when he objected to the term "Open Source".)

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  9. nsa backdoors by Anonymous Coward · · Score: 0

    well DUH! if people started publishing firmware code they'd end up like snowden... ;-)

  10. Make your own by Richard_at_work · · Score: 2, Insightful

    Nothing is stopping you making and using your own hardware, rather than putting expectations on other peoples products. Of course, making your own hardware isnt cheap or trivial, whereas putting expectations on other people is both of those things.

    1. Re:Make your own by Anonymous Coward · · Score: 0

      Nothing is stopping you making and using your own hardware,

      except maybe that YOU are not capable of manufacturing transistors at a density that makes computing practical

      feel free to solder up your computers from TTL chips while the rest of us move on

    2. Re:Make your own by Richard_at_work · · Score: 2

      I take it that

      a. you didnt finish reading my post, and
      b. entirely missed the point of it.

  11. As Challenger Deep said to the kettle... by Pseudonymous+Powers · · Score: 1

    Say what you want about Richard Stallman, no one's ever accused him of being too willing to compromise on his principles in the name of pragmatism and expediency.

    Oh, wait, they totally just accused him of that.

    1. Re:As Challenger Deep said to the kettle... by Anonymous Coward · · Score: 0

      Say what you want about Richard Stallman, no one's ever accused him of being too willing to compromise on his principles in the name of pragmatism and expediency.

      Stallman is too willing to compromise on his principles in the name of pragmatism and expediency.

      Until now.

  12. Stallman's open-source-everwhere view blinds him by Da+w00t · · Score: 5, Informative

    Source: e-mail exchange with him, based on my shmoocon presentation on hacking USB flash drives.

    In short: I said there's no way you can have open source firmware for a proprietary undocumented ASIC, that has to keep track with new developments in flash memory every 3 months.

    He want on to ask if there was a way to buy a USB flash drive that wasn't field-reprogrammable, or to "convince a company to make USBs [sic] that way". I'm not aware of any, and it's impossible as-is to A) ask a vendor "What chips are you using?" and B) have the vendor use the same controller/flash chips on the same device.

    Dude wouldn't listen, and I gave up trying to educate him.

    --

    da w00t. mtfnpy?
  13. a simple but short lived advantage may explain it by nimbius · · Score: 1

    the reason a legacy of GPL can be attributed ot stallman is because of the egregious error of computing in capitalism. Namely, the means of production of code were given to coders themselves and in doing so they were empowered to construct the terms of that softwares use.

    Hardware has enjoyed this luxury for quite some time, however its days may be numbered. open source firmware for routers and mp3 players has existed for a while, and open source chip design and hardware is slowly coming to fruition with the open hardware laptop by bunny huang and programmable keyboards from input.club.

    expect a future of open hardware to seem eerily familiar to the future of open source software. First its ignored, then its laughed at, then its attacked as inferior and dangerous, and finally its either embraced by hackers and business or outlawed through a combination of DMCA style legislative chicanery and thoughtcrime akin to aaron schwartz.

    --
    Good people go to bed earlier.
  14. Isn't he alive? by Anonymous Coward · · Score: 0

    Why does TFS talk about Stallman like he's dead?

    1. Re:Isn't he alive? by cloud.pt · · Score: 1

      I just made the exact same remark in my comment :D

    2. Re:Isn't he alive? by Hognoxious · · Score: 0

      The author is downwind of him.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  15. amd & lenovo should do their own linux by Anonymous Coward · · Score: 0

    just a thought... help bring us out of the '80s sooner

  16. Scope Problem by cloud.pt · · Score: 1

    I guess whatever device we're talking about here has had limited scope until this wearable/beacon/smart bubble started. We effectively have known that specific devices (think: a clock, a fridge, an AC unit) did and still do very specific things, and until now we see them doing those things clearly, not transparently, because they are usually one-task devices. So what point was there really in open-sourcing that stuff or requiring any form of software-bound compliance? Not much really.

    Now that we're getting super smart watches that are basically computers, with a lot more IO into and from our immediate lives, we need to start caring what they run and who they share with, but to me this is just the smartwatch getting closer to the router in effective "influence" on our privacy, security, and other GPL-centered concerns. Whatever has been said about software for computers, that started applying to servers, routers, set-top-boxes at some point, can now apply to all "hardware", because, well, that hardware runs and does what a generic-purpose personal computer runs and does. And then some, if you add all those sensors, it gets access to a lot more stuff than those Spring Break pictures you're embarrassed about. Richard Stallman needs not say one thing

    Off-topic: why is this article's tone sound like RMS is no longer alive or active?

  17. They got flights going to Russia weekly by Anonymous Coward · · Score: 0

    Get On the Plane. Literally.

  18. Open Source Soap by Anonymous Coward · · Score: 1

    Unfortunately Open Source Soap, http://opensourcesoap.com/ , is only OSS and not GPL or LGPL.

    1. Re:Open Source Soap by Anonymous Coward · · Score: 0

      All soap is open source. Soap makers have to list their ingredients and you can't copyright a recipe.

      I think Stallman's problem is that the water company in his area uses non-GPL software to operate their equipment so he boycotts them by having poor hygiene.

    2. Re:Open Source Soap by Anonymous Coward · · Score: 0

      Recipes can be covered under trade secrets. Hence why you see things like "natural and artificial flavors". Also they aren't required to spell out the exact amounts of the recipe ingredients either.

    3. Re:Open Source Soap by Anonymous Coward · · Score: 0

      It is illegal for a company to not either state their ingredients on the package or by request. They would be liable for any allergic reactions caused by not doing so.

      And no, recipes are considered lists and not covered by any kind of copyright or trade secret law.

  19. What's good about GPL? by mi · · Score: 3, Insightful

    Stallman has always had the right idea IMHO

    How was it a "right" idea? The society — and generations of programmers — were spending considerable efforts on software, which could not be used by all. This caused a substantial duplication of efforts and repulsed a substantial body of programmers, who preferred the truly free BSD-license instead. Instead of cooperating, people and groups ended up competing. And when the original GPL proved to not be "enough" — for example, it was still possible to use GPL2-licensed gcc in a BSD-project, Stallman doubled down with GPL3, forcing FreeBSD, for example, to switch from gcc to BSD-licensed clang.

    put up against Corp Profit will never win sadly

    Yep, these denunciations of "profit" is the very core of the problem. Generations of young idiots do not realize, that profit is simply a reward for doing something people want. There is nothing wrong or shameful about it and all efforts to "fight" it are misguided and destructive.

    --
    In Soviet Washington the swamp drains you.
    1. Re:What's good about GPL? by Anonymous Coward · · Score: 2, Interesting

      How was it a "right" idea? The society - and generations of programmers - were spending considerable efforts on software, which could not be used by all. This caused a substantial duplication of efforts...

      It was the right idea at the time. What you describe is precisely what was happening in the 1980s. GPL was a drastic medicine for this; since the source could not be re-closed, its sole target was to avoid just that duplication. For achieving this, I applaud GNU, no question.

      Fast forward 20 years. People have become accustomed that software is free. From OS to $EDITOR, compiler & desktop. And now the liberty of GPL starts to become a hindrance at times. People want to use GPL stuff for work, and can't because $REASON. BSD/MIT software gets more popular again.
      My argument here is that the BSD/MIT software would not be so popular now, if it wasn't for GPL. E.g. LLVM would never have gotten its Apple blessing as an opensource compiler if it wasn't for GCC. Heck, it isn't even now. Just compare the quality difference between opensource and Apple clang.

      GPL did its duty in the 1980's, 1990's and 2000's. We can afford the luxury of dispensing with it for now, because it was successful, not because it is bad. Sure BSD/MIT software can achieve more than GPL because it can get industry money to support it easier then GPL software. But only because there always is an implied threat that such BSD/MIT projects can re-license to GPL. It keeps the industry at bay.

      Stallman doubled down with GPL3,

      Not going to start an argument here. Just noting that GPL3 is the logical fallout from what I describe above.

    2. Re:What's good about GPL? by Bradmont · · Score: 5, Insightful

      Saying BSD-style licenses are "truly free" and the GPL isn't is like saying that you're only truly free if you have the right to use a gun to hold others captive. The ability to revoke freedoms from others does not make one more free in any logical sense.

    3. Re:What's good about GPL? by mi · · Score: 3, Insightful

      you're only truly free if you have the right to use a gun to hold others captive

      Actually, being unable to hold somebody — like a thief caught in your home — captive would be a violation of freedom. But your analogy is flawed and let's not use it.

      The ability to revoke freedoms from others does not make one more free in any logical sense.

      BSD revokes no freedoms from anyone.

      Whatever is released under BSD remains so for ever. A new development may be made under a different license, but that can happen with GPL too. Heck, it did happen with GPL! The last gcc, for example, that's available under GPL2, is 4.2.1 — beyond that it is all GPL3.

      --
      In Soviet Washington the swamp drains you.
    4. Re:What's good about GPL? by mi · · Score: 0

      If i forge an actual wrench out of metal, and drop it on the ground, any human can then come along and use it.

      Only with your permission and only one at a time.

      If you build software that is designed to only reap profit then yes that is WRONG AND SHAMEFUL.

      False. The only "shameful" kind of profit, is when it is derived from people forced by your efforts to either pay you or work for you. I struggle to imagine an example of software (or hardware), that would be "designed to only reap profit" without doing something people actually want done.

      Software should be a tool in the hand, not a leash around the neck.

      Huh? What do you have against leashes? My dog has 5 different ones, we willingly paid for them all, which, no doubt, allowed the manufacturers to make profit.

      Profit is fine, its the extremes of profit

      Define "extreme"... Try to avoid comparisons to your own income and success...

      the walled gardens

      1990-ies called, asking for the anti-AOL rhetoric back. But, now that you mention it, GPL software is an example of a walled garden. BSD code be used in a GPL project, but not the other way around. That GPL is not even making any profit off such a situation, only makes it worse...

      Stallman says no profit because there are legions of people just like you who refuse to condemn commercial software's alchemist methods.

      A less coherent sentence is a rarity indeed. Thank you very much!

      --
      In Soviet Washington the swamp drains you.
    5. Re:What's good about GPL? by Anonymous Coward · · Score: 2, Insightful

      Saying BSD-style licenses are "truly free" and the GPL isn't is like saying that you're only truly free if you have the right to use a gun to hold others captive. The ability to revoke freedoms from others does not make one more free in any logical sense.

      A comparison:
      * GPL: use the code for whatever you want, but you must share changes
      * BSD: use the code for whatever you want

      Seems to me that the latter has one less restriction on what you're able to do. Isn't having fewer restriction equivalent to being more free?

    6. Re:What's good about GPL? by Anonymous Coward · · Score: 1

      And someone comes along and embraces and extends it, then once it's adopted en masse, pulls the rug out from under everyone...sure, you can go back to the latest version that has openly available source code, but you're wasting your time as far as providing an alternative many use...the enslavement via inertia (and everyone trying to remain compatible with that new de facto, binary-only standard) is cemented. They profitted off the work of others, then locked you in...

    7. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      Stallman says no profit because there are legions of people just like you who refuse to condemn commercial software's alchemist methods.

      Because in the vast majority of cases the software that commercial vendors produce is far superior overall to what the free software ideology produces. You can crow "software freedom" all you like but the fact is users do not care about that. Free software hasnt innovated, it has merely imitated...usually poorly and very late.

      Let me tell you that I would be more than willing to accept the free software ideology absolutely if it were proven, I can see that the methodology behind it has its place in certain areas and I feel that you don't need to religiously follow one or the other, rather they can co-exist. We have plenty of DIY hardware that could have been used to innovate and produce a free software blackberry or iphone or ipad or wearable but free software just isnt innovative, even the desktop is still a mess. There is no decent CAD/CAM/CAE, professional photo (no not GIMP), audio and video production software for example, LibreOffice only exists because it was built atop the once-proprietary StarOffice, Linux (brilliant as it is) is an imitation of UNIX.

      Free software is great but it most certainly is not for everything.

    8. Re: What's good about GPL? by Anonymous Coward · · Score: 0

      Yeah umm that's not true at all, at least for media production.

        Blender was freed and then vastly improved by professional animators for their jobs. Pixar has an open source render pipeline. While I'll grant you I use Photoshop over GIMP, that's mainly due to inertia. Most of the professional shops I've been in use Audacity in some capacity. I have never been in *any* type of shop that didn't make extensive use of MySQL.

      There's places where what you say is accurate, but media production is not one of them.

    9. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      A comparison:

      GPL: You have the right to life, liberty and the pursuit of happiness
      BSD: You have the right to keep slaves

    10. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      Yep, these denunciations of "profit" is the very core of the problem. Generations of young idiots do not realize, that profit is simply a reward for doing something people want. There is nothing wrong or shameful about it and all efforts to "fight" it are misguided and destructive.

      That's a retarded view. The weasel word is apparent when you ask HOW MUCH PROFIT? The truth is that tech companies gouge their customers by monopolistic practices which result in prices that are many times higher than reasonable, and result in stratospheric profits each year.

      Stallman's philosophy isn't against profit, it is merely causing a much needed competition with commercial software, which would be otherwise even more expensive than it is now.

      There is nothing wrong with profit, provided the profit is a tiny amount. When people become the richest men on Earth for selling bits on a plastic disc costing 50 cents to make, that's when profit has jumped the shark.

    11. Re:What's good about GPL? by Dagger2 · · Score: 1

      Nope, it's not. You need to consider the consequences of the licenses too. "You have the ability to place restrictions on other people" means, in practice, that other people will place restrictions on you. (Remember that there's a lot more of them than there are of you.)

      Seems to me that having more restrictions placed on you makes you less free.

    12. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      Generations of young idiots do not realize, that profit is simply a reward for doing something people want.

      Doing something people do not want can sometimes be just as profitable, if not more.

    13. Re:What's good about GPL? by tomxor · · Score: 1

      And someone comes along and embraces and extends it, then once it's adopted en masse, pulls the rug out from under everyone...

      I'm possibly historically ignorant on this but when has this happened? (and how significant was it)

      I can't think of large projects that had a "rug" to begin with when using BSD style licences... and if it was truly that open and suddenly became closed then forking is easy enough... if some company is building their proprietary empire around it and forking causes incompatibility then what do you expect? it was never truly open to begin with.

    14. Re:What's good about GPL? by tomxor · · Score: 1

      A comparison:

      GPL: You have the right to life, liberty and the pursuit of happiness BSD: You have the right to keep slaves

      Saying "Use the code for whatever you want" === "You have the right to keep slaves" is as missleading as politicians saying "encryption" === "terrorist"

      Did it ever occur to you that maybe they are both good at different things? maybe you don't have to ascribe to a single ideology like a religious extremist.

      In other words: take your straw man absolutist interpretations of two equally good licences and go fuck yourself troll coward.

    15. Re:What's good about GPL? by AmiMoJo · · Score: 1

      The GPL was never supposed to prevent duplication of effort if people wanted to try different approaches or use different licences. The idea was simply to create a way for people creating software to protect their work and ensure that others would not use it to build systems that were hostile to them. It gives developers assurances that are essential for projects like Linux.

      BSD is nice and all, but Linux is clearly the more popular OS. The fact that it is GPL licensed has not prevented large corporations using it in their products. Generations of young idiots do not realize that the GPL isn't anti-commercial or anti-corporation.

      You have what I'd call a US-centric view of freedom. Freedom to own a gun, mainly so you have the option of pointing it at other people and exerting power over them, forcing them to do what you want (e.g. leave your property). Your idea of freedom is having the power to take away other people's freedom when you deem it necessary, e.g. for a corporation to make software proprietary and prevent others from modifying the device it is installed on. The GPL takes a more European view, where freedom is protected not by the individual with their gun, but by the law. The GPL, enforced by the law, says you can't take certain freedoms away once the creator of that software has granted them to the world. That's true freedom.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    16. Re:What's good about GPL? by Lonewolf666 · · Score: 1

      A semi-applicable example would be Android and its applications.

      Originally it was pretty much free as in speech, but in recent years Google licenses the newer, proprietary versions of the apps only under the condition that the phone manufacturer does not make "competing" phones outside the android ecosystem.
      One instance is reported here: http://www.reuters.com/article/us-acer-alibaba-google-idUSBRE88C0HW20120913
      Semi-applicable example because the "rug" is not the open source project itself, but the proprietary apps running on it.

      --
      C - the footgun of programming languages
    17. Re:What's good about GPL? by david_thornley · · Score: 1

      What makes you think gcc can't be used for a BSD project? You can use it on any sort of project. Nothing that is output from GPLed software is automatically under the GPL. Compilers do put their own prewritten stuff into output, which is why gcc has special permission.

      If gcc could only be used to write GPLed software, it would never have caught on.

      Profit isn't a reward for doing something people want. It's related, in that you are unlikely to make a profit on something nobody wants, but just doing something people want is often unprofitable, and there are things that can't be made profitable, like love, that people want.

      Right now, anyone with a computer and a net connection can install a high-quality operating system with a very large range of software available, without spending additional money. Someone with a computer can download language implementations for free, which did not happen before the FSF and BSD. That is very valuable for people all over the world, since it means that an interested person can learn and implement software without many financial barriers. It encourages quality, since few people will buy a C++ compiler unless it's at least as good as g++.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    18. Re: What's good about GPL? by Anonymous Coward · · Score: 0

      Yeah umm that's not true at all, at least for media production.

      I didnt say media production doesnt use open source. Audacity is not even in the same ballpark as Logic or ProTools. Blender is one of the *very few* places where FOSS is competitive for an end user product though it still is a minor player compared to Maya and MAX, but of course that is why I didn't call out 3D modeling software as a place where FOSS is deficient.

      Pixar has an open source render pipeline.

      No, Pixar uses Renderman which is *not* open source.

    19. Re:What's good about GPL? by KGIII · · Score: 1

      Hmm... Not sure if serious? Some free software is industry leading software, innovative and dynamic. You use it, perhaps indirectly, just to make the post you made in this thread. You connect through it, you store your data on it, you might not notice it but it is ubiquitous. The tools you use were made with it. Your email runs on it, your website thrives on it, your banking is done with it, and even your phone has it (probably).

      You touch free software almost everywhere you go. That's a good thing.

      --
      "So long and thanks for all the fish."
    20. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      Hmm... Not sure if serious?

      Perfectly serious.

      Some free software is industry leading software, innovative and dynamic.

      Certainly some is industry-leading, nowhere did I say it was not. Very little of it is innovative or original though.

      The tools you use were made with it. Your email runs on it, your website thrives on it, your banking is done with it, and even your phone has it (probably).

      It certainly does, there are little bits of it everywhere. Did you get the impression somewhere there that I am anti-Free Software? I am not, it has its place.

      You touch free software almost everywhere you go. That's a good thing.

      If you bothered to read the post my suggestion is that one ideology over the other is pointless, they should continue to co-exist.

    21. Re:What's good about GPL? by Anonymous Coward · · Score: 0

      > BSD revokes no freedoms from anyone.

      Incorrect, it *grants* rights that are automatically reserved by copyright law.

      GPL grants some rights, and some conditionally, but it's copyright law restricting your so-called "freedom," not the license itself.

  20. Balance by iamacat · · Score: 1

    I don't think it's possible or even desirable for every piece of software to be open source. That would result in a lot of useful software not being written, as many smaller developers will not figure out how differentiate themselves from legal copycats.

    Nevertheless, FSF made a huge positive contribution by making compelling critical mass of free software available and forcing commercial companies to share improvements that they make to Linux kernel, compilers and other key infrastructure. We can't even imagine how sucky and insecure commercial products would be today if they were not built on shared community foundation. GPL essentially helped overcome tragedy of the commons where it's better for everyone if there is, say, a good OS kernel available for everyone to build their own UI on top, but it's in immediate interest of any one company to withhold improvements from competitors.

    I can see a similar need in hardware - a set of copyleft hardware, firmware and 3D printer designs that anyone can use as a base for an innovative product while sharing improvements to reusable components.

    It's an important secondary benefit that people will be able to run 100% open systems to learn, because of concern about government backdoors or just because of philosophical objections to not having source, like RMS. I just don't see it as a primary motivating factor for most people in the position to actually contribute code.

    1. Re:Balance by Anonymous Coward · · Score: 0

      We can't even imagine how sucky and insecure commercial products would be today if they were not built on shared community foundation.

      Oh come on, you know damn well we end up with sucky and insecure shared community code distributed all over the place. Take OpenSSL for example, in just the past year we have had MAJOR critical bugs get out and distributed, there was heartbleed, FREAK, the DoS bug, the bug with ChangeCipherSpec spec that was introduced in 199fucking6! And this is a MAJOR project, one of the most widely used open source projects in the world and it is an insecure mess with decades old critical issue cropping up. Quite clearly the "shared community" is not the answer.

    2. Re:Balance by Hognoxious · · Score: 1

      I can see a similar need in hardware - a set of copyleft hardware, firmware and 3D printer designs that anyone can use as a base for an innovative product while sharing improvements to reusable components.

      That would definitely be a game shifting paradigm change.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    3. Re:Balance by Perky_Goth · · Score: 1

      And you had a small group of people fixing it instead of multiplying that for every product that needed the functionality.

  21. So.... he's NOT dead? by Anonymous Coward · · Score: 0

    Very strange wording for someone who is still alive :/

  22. Re:a simple but short lived advantage may explain by ADRA · · Score: 1

    Well, open hardware is pretty crippled. When you consider patents, almost across the board hardware innovation patents are a non-started for a small-ish open hardware company trying to cook their own gear. If you're successful enough, someone will sue you into the ground. Software on the other hand can be served from countries which don't have software patents and still get downloaded everywhere. Would x264/ffmpeg exist today if purely developed under US laws? Probably not, but who's to say...

    Its hard to shut down an individual sending a scrap of code over the web vs. a small hardware shop shipping their devices through the mail. If anywhere 'open' hardware flourishes, it'll be China which has historically been more or less indifferent of patents in general.

    --
    Bye!
  23. It halts at personal hygiene by Anonymous Coward · · Score: 0, Insightful

    https://www.youtube.com/watch?v=I25UeVXrEHQ

  24. incorrect by Gravis+Zero · · Score: 4, Insightful

    From beefy processors to graphics controllers, boot ROMs and binary blobs run in the silicon we base our systems upon. The code is not published and in the rare case that you are able to view the source it is only under strict NDA. This represents one of the biggest barriers to true open hardware.

    this is incorrect! the giant barrier that prevents people from having true open hardware is the obscene cost of having your design made into a silicon chip. if you could suddenly get a one-off chip made for $100, we would all be running much different systems and few of them would be related to x86.

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:incorrect by Anonymous Coward · · Score: 1

      Indeed.

      Also, I rather think that what RMS (and many others, including myself) actually wants isn't necessarily open-source programmable hardware, but transparent hardware.

      I don't _want_ to program my own IDE controller firmware or graphics card RAMDAC, but I do want it to not be reprogrammable by anyone else without my knowledge, and I do want it to be certified by some trusted third party to not contain any fatal flaws, vulnerabilities, or user-harmful features.

      I guess you could say we never had that, but in the old days of fixed-function hardware we were a lot closer, if for no other reason than because it would have been impractical to implement spyware and ad-ware in an ASIC, and too expensive to make a lot of mistakes..

  25. Linux won over BSD by nvm_my_comment · · Score: 0

    I think (hope) no one will disagree when I state that Linux won over BSD, at least in popularity. But what made it won? Was it Torvald charisma alone? The lawsuit that hit BSD? Simply the software quality? I think many would disagree about that, BSD was still more mature no matter what. Timing? yep sorry it seems gpl did had a big impact. Or a larger amount of programmer liked the idea.

    1. Re:Linux won over BSD by 110010001000 · · Score: 1

      Linux was the first Unix like OS that I could download for my PC for free that just worked. "Just working" is a rare quality of software.

    2. Re:Linux won over BSD by unixisc · · Score: 1

      It was Linux being out there while BSD was still locked in that AT&T lawsuit. Once BSD 4.4 derivatives - FreeBSD and NetBSD were out, they were just as available to anyone interested.

    3. Re:Linux won over BSD by Anonymous Coward · · Score: 0

      And everyone dropped Linux and swarmed en masse to BSDs (nope)...inertia...de fact standards compatibility...this is why embrace and extend/dominate works and why the GPL is important...

    4. Re:Linux won over BSD by unixisc · · Score: 1

      Nobody did due to inertia, as you point out. But what standards compatibility? Linux made quite a few departures from both SVR4 and BSD Unix, but that didn't matter, since there wasn't a real standard as far as the market went. At that time, GPL won by virtue of being the only game in town: there wasn't an FOSS BSD license, that came later. Everything Linux adapted was new - be it bash (as opposed to bourne or C shell), X11 (as opposed to X) and KDE (as opposed to Motif and OpenLook). Not that it hurt Linux

  26. Open Source vs. GPL by mi · · Score: 1, Interesting

    Most successful GPL program are "Infrastructure based" ... the most popular one is under the Apache Open source license

    APL is very different from GPL. The most successful GPL-program is gcc — which is waning now that there is clang, to which the evil KKKorporations can contribute without fear. You seem to conflate all open-source licenses together — and that's a mistake.

    However GPL doesn't have too much in end use applications because they are solving rather narrow solutions

    The MIT-licensed X11 is very "end user", Mozilla-licensed Libreoffice — even more so (do I need to mention firefox?) No, it is perfectly possible to have a popular open-sourced software offering. But adoption of GPL is a kiss of death.

    What Stallman must've hoped for 30 years ago was the thinking like: "Ok, they use GPL, so we'll do so too to be able to use their code." What happened instead is: "Oh, they use GPL, so we'll have to implement the same functionality ourselves."

    GPL is a failure, open source is not.

    --
    In Soviet Washington the swamp drains you.
    1. Re:Open Source vs. GPL by The-Ixian · · Score: 1

      GPL is a failure, open source is not.

      It is interesting you should say this. Whenever I look at the licenses in proprietary devices, I always find a GPL cut and paste job.

      The second most common license I see is BSD and almost never see APL.

      This is purely anecdotal but it seems odd to make a statement like that when it is clear that GPL is used very extensively.

      --
      My eyes reflect the stars and a smile lights up my face.
    2. Re:Open Source vs. GPL by mi · · Score: 1, Insightful
      GPL is a failure in what it set out to achieve, which was nothing less than world domination. It also harmed the software projects, that adopted it because a number of programmers refused to participate in them. And, I might add, these were the more mature developers. People, who programmed for the pleasure of it, rather than to spite KKKorporations... It also turned off those KKKorporations themselves. A lose-lose approach.

      Whenever I look at the licenses in proprietary devices, I always find a GPL cut and paste job.

      That's not a useful datum, even if it weren't anecdotal. How do you compare the "success" of GPL as evidenced by its presence in embedded devices with "success" of Mozilla license, for example, as evidenced by firefox or LibreOffice? You can't...

      And if you compare the licenses by the sheer number of projects — useful and otherwise — using them, then MIT-license is the clear winner these days.

      --
      In Soviet Washington the swamp drains you.
    3. Re:Open Source vs. GPL by tepples · · Score: 2

      The most successful GPL-program is gcc

      It depends on how you define "success". I'd bet there are more Android devices running Linux than developer PCs running GCC.

    4. Re:Open Source vs. GPL by dbIII · · Score: 1

      GPL is a failure in what it set out to achieve, which was nothing less than world domination

      I didn't think you could get more ridiculous than your earlier posts.
      Somewhere in yehaw moonshine county a community is missing a ...

    5. Re:Open Source vs. GPL by mi · · Score: 1

      Sigh... Haters gonna hate...

      --
      In Soviet Washington the swamp drains you.
    6. Re:Open Source vs. GPL by Anonymous Coward · · Score: 0

      GPL is a failure in what it set out to achieve, which was nothing less than world domination.

      This is ahistorical bullshit. Basically, in the "old days" all software was MIT licensed (well actually three clause BSD, but we didn't know the difference then). The manufacturers took it and closed it. Exactly as Apple has done with FreeBSD (creating OS/X). This meant that the software could never become mainstream because there would always be some software company that broke off soon before success and created a proprietary version, sucking developers and interest from the main version.

      Stallman created the GPL as an attempt to solve this problem. He was so successful in this that his GPL license has even created a protected environment which has allowed software like clang and OpenBSD to exist. Remember, all of this software, including clang, relied on the GNU build tools to get anywhere.

      The reason why Linux succeeded in creating the "cloud" was because of the GPL.

    7. Re:Open Source vs. GPL by terjeber · · Score: 0

      When adults converse they use arguments, when children converse they don't. Talk to an adult so that they can help you. Remember, it is better to sit quietly in a corner having everybody think you are a moron than to open your mouth and remove any doubt.

    8. Re:Open Source vs. GPL by AmiMoJo · · Score: 1

      Utter nonsense. The GPL never set out to achieve "world domination", it set out to protect open source developers and users. Stallman had seen where the industry was going, with DRM locking everything down and the ability to program your own devices removed. Operating systems were already locking people out, vendors were already acting like asshats.

      He realized that the iPhone was the ultimate goal of many corporations. A locked down platform that only runs code they authorize, which you are forced to pay whatever they charge for, and which is designed to take away your freedom to use your device as you choose. Imagine if you bought a car, tried to turn the wheel to the right and a message appeared on the dash saying "For your safety, right turns are disabled with this edition of Steering. Upgrade to Steering Pro to enable this feature." You would think such a car would never sell, but the many millions of iPhone users prove you wrong.

      Even if the GPL itself isn't used by ever bit of popular open source software, the fact that it takes a hard and principled line sets a standard for everything else to be measured by. I very much doubt that the other licences you mention would be as popular if the GPL didn't exist, and I really doubt that the GPL has any major effect on the popularity of GCC vs. clang. Can you cite any specific examples?

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    9. Re:Open Source vs. GPL by Anonymous Coward · · Score: 0

      You worship a man that ingests his own toe-jam. You have no ground to stand on, sir.

    10. Re:Open Source vs. GPL by silentcoder · · Score: 1

      Except of course that the scenario you claim was an unrealized hope has happened numerous times.
      There is an entire stable of free programs and libraries which were GPL'd only because it would be too much effort to reimpliment the GNU readline library.

      That library being GPL'd rather than LGPL'd has by itself led to hundreds of other projects also being GPLd and that's just one library.

      On the other hand - the C-library would not have such an effect, a C-library must implement a well known common set of functions and anybody could write one with some patience, and it's all fairly basic stuff - to GPL the GNU C-library would have only led to dozens of competing, incompatible non-free c-libraries having to co-exist to run various programs - so glibc is LGPLd instead. And as a result there are really only two c-libraries in the GNU/Linux world even today - glibc which almost every distro runs and mulc which is extremely minimalistic and deliberately built ultra-tiny for very small distros.

      Also note how nobody has seriously ported or replaced the GNU utlities with non-gpl'd versions. It would not be very hard to port the BSD utils to all run on Linux and make a distro out of it (quite a lot of BSD utils are in Linux already where GPLd ones weren't available), yet nobody has bothered to do that. There are only really two core-utils sets that work with the Linux kernel - the GNU utilities and busybox (again - targeted at ultra-tiny use-cases like embedded systems) and busybox is also GPL'd.
      Busybox being GPL'd has been a massive boon to the community. More than any other project busybox has challenged companies who violated the GPL and the fact that it exists, works fantastically and is GPLd has directly led to hundreds of devices having their firmware source available that otherwise would not be - mostly consumer devices like routers. There are any number of consumer router replacement-software projects adding features like advanced firewalling, all possible because the busybox and linux licenses forced the router-makers to make their changes GPLd which allowed other developers to use those to create custom firmware products.

      There is some thought that goes into this stuff you know...

      --
      Unicode killed the ASCII-art *
    11. Re:Open Source vs. GPL by tomxor · · Score: 1

      The most successful GPL-program is gcc

      It depends on how you define "success". I'd bet there are more Android devices running Linux than developer PCs running GCC.

      There are more users than developers so it would make sense, but then again "use" is ambiguous here because GCC is in a way used by both developers and users... but there is no sound metric for such an ambiguous criteria, the effect of GCC is perhaps so far reaching that it doesn't matter.

    12. Re:Open Source vs. GPL by david_thornley · · Score: 1

      I'm sorry to hear that the Linux kernel has become unsuccessful. Can I keep running a Linux distro anyway? Unless you're using Android, you are likely using a lot of GPLed software as userland, if you're running Linux.

      What you attribute to Stallman is indeed what he planned, and for a long time it worked fairly well. One case is GNAT, the GNu Ada Translator, which became Free software because it had to be GPLed because it built on GPLed software.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    13. Re:Open Source vs. GPL by dbIII · · Score: 1

      Remember, it is better to sit quietly in a corner having everybody think you are a moron than to open your mouth and remove any doubt.

      All that for quoting someone and pointing out how ridiculous the quoted text is, let alone his very political sig.

    14. Re:Open Source vs. GPL by terjeber · · Score: 1

      All that for not being able to formulate an argument and only being able to contribute vitriol. As I mentioned, when you finish Kindergarten, and start mingling with adults that are not solely your shepherds, you will find that in those circles, using reasoned arguments are considered rational and are usually thought of as a requirement for participating in polite exchange of opinion.

      Until then watching Sesame Street will still be fun for you.

    15. Re:Open Source vs. GPL by dbIII · · Score: 1

      Read your own post above and apply the same standard to it :)
      It's good for a laugh if nothing else.

    16. Re:Open Source vs. GPL by terjeber · · Score: 1

      Read your own post above and apply the same standard to it :)

      I always do. If you don't know what is meant by: "When adults converse they use arguments", just ask an adult for help.

    17. Re:Open Source vs. GPL by dbIII · · Score: 1

      You do not understand how utterly hilarious it is hearing something like that from a person that is probably thirty or more years younger than me :)
      Here's a clue kid - Apollo inspired me to go into engineering.

  27. Oh please by Anonymous Coward · · Score: 0

    just shut up!

  28. Re:Stallman's open-source-everwhere view blinds hi by Anonymous Coward · · Score: 0

    At the same time, many confidential information about chips protected by NDAs is often not justified.

    Does giving all the details about a flash chip, its durability, sequences of operations for obtaining good data really help competitors ?

    It is a bit like 3D chips, vendor swore for years that it was impossible to disclose programming information, because it would reveal
    too much. Bullshit. Important features are patented anyway.

    The only compelling reason for not disclosing anything is when you have something to hide, for example using a competitor's patented technology.

    As much as I understand that complete hardware information will not be available for everything, pushing for more openness is legitimate.
    Having provably secure USB flash drives would be great.

  29. Re:Stallman's open-source-everwhere view blinds hi by chispito · · Score: 1

    Dude wouldn't listen, and I gave up trying to educate him.

    I was under the impression that sums up his particular strength and weakness. He isn't interested in the particulars of his grand vision that are impractical or impossible. With RMS it's always a "Damn the torpoedoes..." mentality.

    --
    The Daddy casts sleep on the Baby. The Baby resists!
  30. Right Idea but wrong details by Anonymous Coward · · Score: 0

    Its true that Stallman's legacy is limited to hardware only but the causation is entirely wrong [bear with me]. The reason opensource flourished so well is that only partly because of GPL/other licenses. The real enabler IMO was availability of uncontrollable compiler collection that allowed developers unencumbered ability to code and publish. Not many people know this but Stallman was the guy behind creation of GCC. With the open source (& free as in speech) compiler the community had an ability to improve upon proprietary compilers that focus their support on whatever the monetary interests of the provider happens to be. Once ability to build your own code without the key chokepoint of 'agreements' is there, the rest of opensource movement became more plausible.

    THIS critical piece is missing in h/w development. Almost anything semi decent [I know open source eda tools exist, but..] on EDA front costs 6 figures. Also the fact that there is a huge non recurring expense when making chips that requires a certain volume production to be profitable, also, this expense gets worse as geometries shrink. This is the root cause behind patents & other barriers to openness. the NRE costs can be reduced by sharing wafers and using legacy nodes but synthesis & verification still costs money. IMO the real solution to open hardware is community (or some deep pocketed neutral investor like Page/Musk) investing some effort in creating these tools in fully open manner.

    The other path [I really hope] is as the geometries shrink the Fabs (TSMC/GloFo/etc) realize that the chip development costs are going to be so high that their market with shrink to a handful of big players. So to rekindle the silicon work they may start funding these open EDA tools thereby serving their own interests.
    Just my 2 cents.

  31. Dirty hippie extremist by Anonymous Coward · · Score: 2, Insightful

    I respect what Stallman has contributed to free software, but at the same time, his views are ridiculous. He is to FLOSS what fundamentalists are to religion. His untenable ideals and overwrought goals drive people away, and do more to hurt the more reasonable open source options than to help free software.

    1. Re:Dirty hippie extremist by JDLazarus · · Score: 1

      My opinion on software licensing has always been that it should be the choice of the developer whether they want to use an open license or not. Stallman's is that all software should be open, regardless of the desires of the developer, because only when the license is open is the consumer free to do whatever.

      The thing is, as a consumer, you have the ability to choose which software you use (whether it be licensed closed or open) - If you don't like closed licenses, don't use them, but taking the rights of the developer *and* consumer away seems unacceptable.

      The reason projects like LibreOffice exist is because people wanted open alternatives to closed projects, which is great - I'm a fan of LibreOffice; however, that doesn't mean that anyone else should be forced to accept the same license as LibreOffice. People are welcomed to use either application, and the interchangeability of file formats available means that it doesn't matter which one you're using, you get access to the file. What people like Stallman (and his zealots) don't seem to get is that lots of consumers will simply choose whichever works best because they give exactly zero cares for the source. They can't code, they don't want to learn to, they often don't even care if they hit a bug, they just want the software.

      Freedom is the ability to choose. Optimal freedom comes from having the ability to choose whether a developer wants to use one license or another AND for a consumer to choose whether to use between software packages, which likely have different licenses. Trying to force your vision of freedom on someone else is not freedom.

    2. Re:Dirty hippie extremist by Anonymous Coward · · Score: 0

      He says "should," not "must." He's not forcing anyone to use GPL software, but for those who agree to do so, they have to honor the terms under which they have been granted such a license. He wishes it wasn't necessary, that the freedoms he envisions would inherently exist. It's what he can do to ensure the existence of such software under current copyright law.

    3. Re:Dirty hippie extremist by Anonymous Coward · · Score: 0

      Well he should shut the fuck up then. If he's not going to say anything, say nothing rather than whinge about the choices others have made.

      GPL doesn't restrict your freedom.

      Unless you're a parasite.

    4. Re:Dirty hippie extremist by Anonymous Coward · · Score: 0

      Stop trolling. As a GPL developer you get to use other people's work for free instead of having to sit down yourself and write everything from scratch. You're not allowed to prevent other people from using your work for free instead of having to sit down themselves and write everything from scratch. That's trrue freedom, if you disagree you're just a greedy hipocrite for wanting the get the free code and not let anyone else have yours.

  32. Re: Stallman's open-source-everwhere view blinds h by Anonymous Coward · · Score: 0, Interesting

    No, RMS is straight fucking ignorant about hardware, and that whole e-mail exchange proves it.

    How about you get Stallman's unwashed cock out of your mouth for a minute so you can possibly have a chance to smell his bullshit?

  33. Proprietary Math Libraries by tommeke100 · · Score: 1

    You would be amazed at some of the 'low level' libraries that GPU manufacturers have and license to other such companies. These companies have Math Phd's still trying to get better precision and faster computation at Sine and Cosine functions, etc... I'm sure they are not in a hurry to open source this type of research which took plenty of money and time.

  34. Re:Stallman's open-source-everwhere view blinds hi by Anonymous Coward · · Score: 0

    I think it;s that he decided you wouldn't listen and gave up trying to educate you.

  35. ixnay on the own-phay by PopeRatzo · · Score: 1

    This doesn't affect me because I always talk in code anyway.

    --
    You are welcome on my lawn.
  36. Good! by Anonymous Coward · · Score: 0

    Open source is just about ego--like you can debug any problem by looking at the source (in under ten seconds, of course).

  37. Re:Stallman's open-source-everwhere view blinds hi by Anonymous Coward · · Score: 0

    Digitally signed flash firmware on flash drive:
    https://www.kanguru.com/storage-accessories/kanguru-flashtrust-secure-firmware.shtml

  38. He certainly wasn't shy about promoting Lemote by Anonymous Coward · · Score: 0

    Now he apparently uses a ThinkPad.

    I use a Thinkpad X60 computer, in which the FSF installed a free initialization program (libreboot) and a free operating system (Trisquel GNU/Linux.) This is the first computer model ever to be sold commercially with a free initialization program and a free operating system, and thus the first computer product the FSF could endorse. (It was not sold that way by Lenovo, however.)

    Before that, I used the Lemote Yeeloong for several years. At the time, it was the only laptop one could buy that could run a free initialization program and a free operating system. But it was never sold with a free operating system.

    Sauce: https://stallman.org/stallman-computing.html

  39. Re:Cowardly GPL apologists by Anonymous Coward · · Score: 2, Insightful

    This reminds of labor unions claiming credit for us not working on weekends... Bullshit, in other words.

    Sometimes I read a thread here and just spot the most amazing, untrue bullshit - like this line.

    I've been in the office Monday through Saturday for the past 3 months - involuntarily. The project manager just had to send a simple email requesting additional resources when the goals on his timeline started slipping. HR and my direct boss walk over to me and tell me that I'm expected to be at work Monday through Saturday from 8am to 6pm. I don't get paid extra for the extra hours. I don't get comp time. I'm not allowed to use vacation days during crunch time. The contract I signed when I started here said nothing whatsoever about involuntary unpaid OT. My recourse is to find a new job (it's hard to interview on a Sunday) or initiate legal action which will end badly for me.

    My neighbor is a UAW worker in a Ford plant. He gets Saturdays and Sundays off - except when they allow him to volunteer for weekend OT at 1.5x rate or even higher. I'm willing to bet his annual salary is higher than mine when you factor in his OT pay.

    Please hop on the clue bus when it comes to unions. Please, I'm begging you.

  40. Re: Stallman's open-source-everwhere view blinds h by Anonymous Coward · · Score: 0

    "No, RMS is straight fucking ignorant about hardware, and that whole e-mail exchange proves it."

    Not at all. Pay attention to the details:

    Da Woot: "[T]here's no way you can have open source firmware for a proprietary undocumented ASIC."

    RMS: "Okay. Is there a way to buy a USB flash drive that isn't field-reprogrammable, or to convince a company to make such a USB flash drive?"

    Da Woot: "Fuck you dude, you're asking for the impossible and are clearly a moron."

    It's clearly a reasonable thing to produce USB flash drives that are not field-reprogrammable. RMS has *long* held the opinion that devices that are not field-reprogrammable can reasonably run closed-source software, because they can then be viewed as single-purpose appliances. (Think of your microwave. It has non-field-upgradable software, too!) What's more, if you make it impossible to field-reprogram a device, you make it impossible to have that device's firmware changed from something that *might* be malicious, to something that is *definitely* malicious.

    Another thing:

    We've heard the "You can't make open-source drivers for $HARDWARE because that field moves way too quickly!" song for decades. In every case, the singer has been lying to us. Do you *honestly* think that gongkai somehow doesn't apply to the manufacturers of USB mass storage devices? I certainly don't. :)

  41. Re:Stallman's open-source-everwhere view blinds hi by spire3661 · · Score: 0

    This is a feature, not a bug. SOMEONE has to stand out at the extreme edge. I take the position that all IP should be abolished because the opposing force is so powerful, its the only logical counter to it. Someone somewhere has to stand up to greed and profit, no matter how Quixotic it may appear to be or the width of the spectrum shrinks and the extremes get much closer to each other.

    --
    Good-bye
  42. The biggest barrier is not lack of access to code by fustakrakich · · Score: 1

    It is lack of access to * the means of production*. Gee, where have I heard that before? But in this context it is true. And since it won't be given to us, we have to create our own. Uh oh... there's that 3D printing nonsense again. But... it is the only way to "democratize" things.

    --
    “He’s not deformed, he’s just drunk!”
  43. Re:Stallman's open-source-everwhere view blinds hi by Hognoxious · · Score: 1

    He want on to ask
    USBs [sic]

    I gave up trying to educate him.

    Perhaps you should focus your efforts closer to home?

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  44. USL v. BSDi left door open for GNU/Linux by tepples · · Score: 2

    BSD existed since 1970-ies.

    But was it free in 1984? Wikipedia says it didn't start to become free software until 1991. And was it a complete free operating system, entirely free of AT&T encumbrances, in 1992? Once Linux was combined with what the GNU project had produced by the early 1990s, it succeeded in part because of the legal uncertainty surrounding BSD prior to the 1993 settlement.

    1. Re:USL v. BSDi left door open for GNU/Linux by mi · · Score: 0

      But was it free in 1984? Wikipedia says it didn't start to become free software until 1991

      "Free" is not the point. Your software came with the source-code, not "binaries only", that's all that matters. Incidentally, GPL does not mean free of charge either — it is Ok to charge money for GPL-software, you just have to provide source-code with it. In this regard the two licenses aren't different.

      Once Linux was combined with what the GNU project had produced by the early 1990s, it succeeded in part because of the legal uncertainty surrounding BSD prior to the 1993 settlement

      That uncertainty was surrounding BSD as in "Berkley Software Distribution" — a particular body of code, not BSD-license — a legal document. Maybe, one didn't want to use Berkley's code because of the lawsuits — and had to reimplement it — but it did not mean, the reimplementation had to have a different license.

      If gcc and other tools incorporated into Linux in those early 1990ies used BSD-license, a vast duplication of effort would've been avoided. Sadly, the influence of Stallman-the-gifted-programmer allowed Stallman-the-activist to lure people into using GPL instead... Our world today is slightly worse because of it.

      --
      In Soviet Washington the swamp drains you.
    2. Re:USL v. BSDi left door open for GNU/Linux by Anonymous Coward · · Score: 0

      BSD is chump change/niche in open-source OS's...there wasn't much duplication of effort...far fewer worked on it...

    3. Re:USL v. BSDi left door open for GNU/Linux by Anonymous Coward · · Score: 0

      "Free" is not the point. Your software came with the source-code, not "binaries only", that's all that matters.

      No, that is NOT all that matters. I was fucking there.

      Because BSD was based on AT&T Unix, you had to have an AT&T source licence (about $40k as I recall) to have the source code. When the computer to run it on cost $100k, that might not have been such a big deal; anybody who had access to the machine probably had access to the source.

      When computers became cheap enough that just anybody could buy one, it was a Big Fucking Deal. It meant that you couldn't just do something as a hobby, or in a garage. And, in software, hobbies turn into garage companies and sometimes those turn into big companies.

      Even in a big company, you might or might not have been authorized for Source Access(TM), so if you felt like playing with something on a "skunk works" basis, you might or might not have a base to work from. You had to go through a bunch of procedural hurdles and start a formal project.

      And for people who DID have source access, it was a huge pain in the ass to share any changes or improvements. People would email diffs around, and everybody would compile things for themselves. There was no such thing as a "distribution" or a "repository".

      That was directly caused by the fact that somebody could and would prevent you from distributing the changed source code... and wanted to get paid. Paying for things has an overhead. In theory, you could have negotiated with AT&T to come up with some kind of better distribution system, where everybody got paid somehow in proportion to their contribution. In practice, that was not going to happen; the negotiating and license tracking and fee collection overhead would have been many times more than anybody could support, and the work of setting them up would have been uncompensated.

      Innovation was the absolute opposite of permissionless, it slowed the hell out of everything, and making it free-as-in-gratis was absolutely essential to breaking down those barriers and improving the software base.

    4. Re:USL v. BSDi left door open for GNU/Linux by Anonymous Coward · · Score: 0

      If gcc and other tools incorporated into Linux in those early 1990ies used BSD-license, a vast duplication of effort would've been avoided. Sadly, the influence of Stallman-the-gifted-programmer allowed Stallman-the-activist to lure people into using GPL instead... Our world today is slightly worse because of it.

      No, if gcc and other tools had used BSD licenses they would have been picked up by large corporations who would have reclosed them again, sapping energy and resources from the open source offering. Our world is much better because of it.

    5. Re:USL v. BSDi left door open for GNU/Linux by Anonymous Coward · · Score: 0

      > BSD is chump change/niche in open-source OS's...

      BSD is in every device Apple sells containing OS X or iOS.

      Until Android pulled ahead, OS X was by far the most prolific Unix-like OS on the planet.

  45. How to turn C64's S-Video into HDMI by tepples · · Score: 1

    You control the silicon that postprocesses the signal.

    The Commodore 64 computer's VIC-II GPU outputs S-Video signals using a 90/11 = 8.18 MHz pixel clock, which is 16/7 times the frequency of the color subcarrier. Put code on an FPGA that samples the luma and chroma signals at twice this rate, and it should be able to guess which color the VIC-II is producing. Then store lines of pixels in a circular buffer in block RAM feeding a line tripler circuit on the same FPGA. Kevin Horton did something like this for the NES.

    Or clone the VIC-II. (If you dare.)

    1. Re:How to turn C64's S-Video into HDMI by Anonymous Coward · · Score: 0

      how does one do that with the existing silicon, which is what I desire, and supposedly I can get what i desire

    2. Re:How to turn C64's S-Video into HDMI by tepples · · Score: 1

      You get what you desire by adding silicon.

    3. Re:How to turn C64's S-Video into HDMI by Rakarra · · Score: 1

      how does one do that with the existing silicon, which is what I desire, and supposedly I can get what i desire

      You're being intentionally obtuse to make a shitty point. Please stop.

  46. FPGA is not a pro golf league by tepples · · Score: 1

    Then get an FPGA development board and write your CPU in Verilog.

  47. But the BSD license impinges on my freedoms! by Anonymous Coward · · Score: 0

    The horrible, evil, freedom-hating BSD license does not allow me to redistribute the code without acknowledging who wrote it!

    As the sainted Ayn Rand often said, only absolute freedom is freedom. If you can't commit genocide without some dirty stinky BSD hippies whining about it, you're not really free, are you? Down with BSD's freedom-hampering restrictions! Public domain (and CRELM® toothpaste) is the only true free license!

  48. Why is it all about computers? by AndreyFilippov · · Score: 1

    The sales of computers are going down last years, and there are more other devices in the age of "Internet of Things" that are harmful for the freedom of the users. Even simple climate control is not your device, but is designed to spy on your family habits, "phone home" - all in the name of optimizing your utility bills. In the US the practical disadvantage of this unfreedom can likely be just unsolicited junk mail, in other countries with higher corruption levels this data can be sold to burglars who will visit your home when the heating/AC is set on "vacation" level. Freedom of the users of the devices (including all 4 classic components) is much broader then just that of the computer operators, and the choice if free/non-free is not only about your philosophy, but be a matter of survival.

    As for Richard Stallman - I just can not see, where is that his one mistake. For years there are continuing attempts by others to create "hardware GPL" but there is no universal solution (we use exactly the combination mentioned in the article: GPLv3 for software/firmware/FPGA and CERN OHL for the hardware) caused by fundamental differences of the software and hardware. His last year article http://www.wired.com/2015/03/r... provides a lot of practical instructions how to build free hardware in a not-yet-so-free hardware world, there are "levels of design".

  49. Find and support the good hardware by AHuxley · · Score: 1

    Find the cpu thats fully understood.
    Buy the motherboard thats been fully examined and found to be open and usable for a developers needs.
    Tell the world about it on the web and grow a user community.
    Move away from the devices and brands that expose IP's while selling an expensive VPN related product.
    Stop buying tame and junk crypto turn key products that have trap doors and backdoors design in as sold and shipped.
    Secure and understand what can be as a user and developer.
    The cpu, motherboard, OS can still be secure, fully documented and developer ready.

    --
    Domestic spying is now "Benign Information Gathering"
  50. At least AOSP is going further GPL(ish) by Phil+Urich · · Score: 1

    With Google's switch from Apache Harmony-based runtime libraries to GPL-with-Classpath-exception-based code, we have an ever-so-slight uptick in the copyleft nature of AOSP. True, the Classpath exception is a huge exception that makes it arguably lesser than the LGPL (Bradley Kuhn apparently half-seriously argued at the time of its creation for it to be called the "Least GPL"), but even if it's a slight shift, at least it's in the right direction. And it shows that Google at very least isn't actively working to diminish any further the usage of GPL code in Android.

    But, yeah. The use of a new software stack rather than a standard glibc-based one has seriously rather counterproductively bifurcated the Linux world.

    --
    I remember sigs. Oh, a simpler time!
    1. Re:At least AOSP is going further GPL(ish) by exomondo · · Score: 1

      True, the Classpath exception is a huge exception

      The most popular GPL-based projects have exceptions rather than a proper GPL license. gcc has the gcc runtime library exception, Linux has the preamble in the COPYING file about linking proprietary binaries and Android's runtime with the classpath exception.

  51. Stallman does this for personal gain. by Anonymous Coward · · Score: 0

    Stallman gets his bank account padded every time someone picks Libre software for her computer. By expanding into the Libre hardware realm, Stallman's bank account will grow even fatter. Can't you people wake up and see through Stallman's motives? He does not care about us or society. Microsoft and Apple has done more for the user than a thousand Stallman's in an ideal world ever could. Right now is a crucial time to lobby our schools, public sectors, and institutions to embrace Apple and Microsoft and stop supporting Stallman's profiteering. It's sickening. The man has no decency, he just cares about the bottom line while feeding us the illusion of choice and getting what we want. The day I see people choose Libre hard/software is the day our free market economy has died and gone to greed and delusion. If Libre software is embraced, that is the death of our freedom.

  52. BSD allows freedom to screw you over by mx+b · · Score: 1

    Generations of older idiots do not realize, that corporations are shafting you and laughing all the way to the bank based on *your* hardwork, and you just accept it. There is nothing wrong or shameful about asking for higher compensation, and joining a union to strength your demands by putting workers and executives on an even playing field, and all efforts to "fight" it are misguided and destructive.

    FTFY.

    Look, I don't mean to be rude in the above statement, but it really irritates me when people refer to younger generations as idiots, just because we have a different philosophy than you do.

    In my view, BSD allows corporations to fork the code and never contribute back. They can essentially take everyone's hard work, say "So long and thanks for all the fish", and package up a proprietary version of it and sell it for oodles of money. They don't owe you a thing. They don't owe the open source project a thing. Just because some of them currently do contribute code/effort doesn't mean they will indefinitely. Once they have obtained what they want, what incentive do they have to keep working with the community?

    The GPL, meanwhile, protects your hardwork. If you write free software (in RMS's terms; or open source if you prefer), you can still build a community around it and have anyone contribute, including corporations. You can use it for whatever you want, including commercial software (i.e., you can sell software that is GPL, that's not against the license). HOWEVER, there is one important exception: any changes/add-ons MUST be available under GPL license for others. While you can sell GPL software, you can't make it solely proprietary, ever. I look at it as demanding compensation -- if you worked hard (for free in most cases) to develop some open source library, and a corporation takes it to use in some product they sell, why should they solely profit off your work? Requiring them to give back to you and community -- so you can turn around and sell too if you wish -- keeps an even playing field. Everyone contributed so everyone gets it. No one can unilaterally decide they're done contributing back; it's a requirement of the license.

    Imagine being the author of a library that becomes used in OS X, and then Apple says "Sorry, that's proprietary, you can't reverse engineer our code" -- they took your code, the code you wrote 99% of, and effectively removed your freedom to use your own library just because they made a few changes and reissued under a new license. BSD allows this; GPL doesn't.

    The only thing GPL really requires is that changes also be released GPL, so everyone can use it. Otherwise, it's the same as BSD. How is that taking away freedom? You can do anything you want with GPL, including launch a commercial company and sell it, EXCEPT screw people over by taking your ball and going home. Does it not occur to you as being a little suspicious that corporations, after years working with GPL software, are starting to turn to BSD in some cases? You use it as an example of GPL's "failure", but I see it as an impending crisis among BSD software, where in a few years corporations will fork and close these libraries and leave BSD'd software to decay. Remember that old "extend-embrace-extinguish" memo? Did you not learn from history? BSD can't prevent that, but GPL can because of its viral nature.

    Now if you really think corporations getting to take your code for proprietary stuff is important, then by all means pick BSD. I'm not going to sit here and tell you what to do with your own hard work. It's a free country. But stop spreading such lies about the GPL. The GPL protects your freedom by preventing others from taking away your freedom.

  53. Re:Stallman's open-source-everwhere view blinds hi by Anonymous Coward · · Score: 0

    SOMEONE has to stand out at the extreme edge.

    No, they don't. Extremists always do more harm than good.

  54. LGPL as a middle-ground. by sbaker · · Score: 1

    Stallman is indeed a fundamentalist. His goals are just fine - but he's about as remote from what a typical software engineer is as it's possible to be. That's OK, he's the idealist - and that lets the rest of us be pragmatists.

    GPL is great for complete software packages - emacs, gcc...that kind of thing. But for libraries, it sucks. That's why we have LGPL. Sadly, there is a lot of anti-LGPL rhetoric out there https://www.gnu.org/licenses/w...

    I think we need something like that for OpenHardware. The ability to use a piece of OpenHardware design in a closed-hardware ensemble without hiding the open part of the design...putting a BeagleBone inside my (commercial) 3D printer perhaps.

    Keep that in mind - while I consider why LGPL is a good thing for *parts* of systems.

    I get paid for writing software - I need that money to by food, clothing, housing, transport, etc. When I put something out into the public domain it's because I expect to get a fair trade out of it - I give you my software - some of you give me back bug fixes, improvements, etc. My gift to you is repaid to me - possibly in just a small way - but possibly many, many times over...it's a fair trade for some kinds of software - but not for others.

    Yet when I open-source a game (I've actually done this) - I got 300,000 downloads in the first month - a lot of thanks and ego-boosting praise - but almost zero actual tangible benefits in return (one guy - a musician - sent me a new, original music track). But if I open-source a library (and I've done that too, on many occasions), then with only a tenth the number of downloads - for years to come, my library was polished, fixed and improved - for free! That's because users of libraries are software engineers, and they are capable of helping out - players of games are typically not.

    I learned my lesson - and I mostly OpenSource library code - or complete applications that programmers are likely use the most - these things give me a return on my work.

    With a library, we need to allow the maximum number of people to use it in order to get constructive input. If I use GPL, it effectively causes all users of my library to have to license their application via GPL (or similar) too. That cuts out 100% of all commercial users and a large chunk of potential OpenSource users. The only people who can use my code are those who are working on GPL'ed applications - and those are a small minority. With LGPL, I can force the library sources to remain free - while allowing the maximum possible number of users to want to help with the maintenance. This gives me my best return on investment.

    So it makes sense to have an LGPL-like license for hardware components - the BeagleBone inside my 3D printer design, for example. Keep the BeagleBone "open" and "free" while allowing me to use it in some larger project that I can sell to keep the lights on.

    But for Stallman, this is a religious matter - he's trying to get me to use GPL on my library in an effort to leverage more GPL'ed applications out there. That's a nice goal - but it not one that a typical working programmer can rationally cope with. Closed source code pays the rent.

        -- Steve

    --
    www.sjbaker.org
  55. Re:All in for transparency? IBM PC Tech. Ref. by dakra137 · · Score: 1

    If I recall correctly, the Assembler source code listing for the original PC BIOS was included in the IBM Personal Computer Technical Reference, but not the source code for the ROM BASIC, licensed from Microsoft.

  56. Re:Stallman's open-source-everwhere view blinds hi by chispito · · Score: 1

    SOMEONE has to stand out at the extreme edge.

    No, they don't. Extremists always do more harm than good.

    You're either saying RMS isn't an extremist or he has done more harm than good. I disagree with both views. He's pretty crazy on some things. But without him there is no (GNU/) Linux, and probably no free software movement as we know it today. Sure open source would exist, but not the legally binding licensing that has helped to keep open source open.

    --
    The Daddy casts sleep on the Baby. The Baby resists!
  57. Re:All in for transparency? IBM PC Tech. Ref. by Anonymous Coward · · Score: 0

    Yep, you can see for yourself if you're interested in that sort of detail.

  58. Re: Cowardly GPL apologists by Anonymous Coward · · Score: 0

    Is crap like that actually legal in the USA? No wonder your country's fucked.

    Here in socialist Europe, as well as basic essentials for a civilised society such as universal health care, free at the point of delivery, and meaningful regulation of lethal weapons, we have a maximum 48 hour working week, seven weeks paid holiday a year, a right to a year's maternity/paternity leave and protection against being sacked for no reason. We have these things because worker's unions fought for them then people elected governments who made them universal.