4 ms·

2.6.19 will be forked and a community-driven Akka will emerge eventually.

jsiepkes 4y ago
Has a champion risen to the task yet? Forking a project is no easy feat. Certainly not one the size of Akka. You need a corporate backer who is going to put at least one person full time on it. I've seen plenty of forks start out with the best of intentions only to slowly fade in to nothing.
- halfmatthalfcat 4y ago
  It's only been a week since the announcement, I'd expect it'll take a while.
- Test0129 4y ago
  https://www.theregister.com/2022/09/08/open_source_biz_sick_of/ https://www.theregister.com/2022/09/08/open_source_biz_sick_... Here's an article on it. Their logic actually makes sense. Not that I support gouging customers, but when you consider how there are massive billion dollar companies with expensive lawyers figuring out how to end-around OSS (via SaaS, etc) this is the logical conclusion. A lot of companies make a lot of money on OSS and give little to nothing in return. This isn't in the spirit of OSS but company men don't really care. So it seems like Akka finally got sick of it and is now coming to collect its (without question) overdue paycheck from these people. It's just unfortunate they went so aggressive with it. $2000/vCPU/year will do a lot of damage to smaller projects in the process of sinking the billion dollar open source leeches in the process.
  - azemetre 4y ago
    If you’re making $25mil in revenue why is it out of the question to pay for licenses?
    - Test0129 4y ago
      Why would you? License requisition is a real pain, they have to be factored into the budget, depreciated, etc. If you can instead simply pull in OSS and hide it behind a SaaS implementation (thereby complying with licenses) you can leverage it to make money. I don't think Stallman saw this coming. Some companies do better than others. For example, FAANG level companies typically have teams that do give back. In some cases several orders of magnitude more than they take from popular projects. It's the in-betweens, the other companies that don't do anything other than leech.
      - svnpenn 4y ago
        > pull in OSS and hide it behind a SaaS implementation (thereby complying with licenses) sorry, but you can do that shit anymore: https://wikipedia.org/wiki/Open_Software_License#Network_deployment_is_distribution https://wikipedia.org/wiki/Open_Software_License#Network_dep...
        bhuber 4y ago
        My interpretation of that clause is it applies to distributing code over a network. The most common example of this is serving javascript to a web browser. I'm pretty sure putting an API in front of a server that happens to run open source software doesn't count as "distribution", which is what we're talking about here with SAAS providers and Akka. If it does, then every site that is backed by servers running linux and not distributing their GPL license to clients is also in violation.
        svnpenn 4y ago
        I would disagree with your assessment. OSL was specifically crafted, to close this exact loophole: > Most other open source licenses treat such network uses of software as internal to the company that runs the server, and they don't require disclosure of source code. That is seen by many nowadays as a loophole that permits large online companies to avoid their reciprocal source code obligations. http://rosenlaw.com/OSL3.0-explained.htm#_Toc187293088 http://rosenlaw.com/OSL3.0-explained.htm#_Toc187293088
afpx 4y ago
Given that thousands of projects are dependent on it, I would hope so. https://mvnrepository.com/artifact/com.typesafe.akka/akka-actor/usages https://mvnrepository.com/artifact/com.typesafe.akka/akka-ac...

Has a champion risen to the task yet? Forking a project is no easy feat. Certainly not one the size of Akka. You need a corporate backer who is going to put at least one person full time on it. I've seen plenty of forks start out with the best of intentions only to slowly fade in to nothing.

halfmatthalfcat 4y ago
It's only been a week since the announcement, I'd expect it'll take a while.
Test0129 4y ago
https://www.theregister.com/2022/09/08/open_source_biz_sick_of/ https://www.theregister.com/2022/09/08/open_source_biz_sick_... Here's an article on it. Their logic actually makes sense. Not that I support gouging customers, but when you consider how there are massive billion dollar companies with expensive lawyers figuring out how to end-around OSS (via SaaS, etc) this is the logical conclusion. A lot of companies make a lot of money on OSS and give little to nothing in return. This isn't in the spirit of OSS but company men don't really care. So it seems like Akka finally got sick of it and is now coming to collect its (without question) overdue paycheck from these people. It's just unfortunate they went so aggressive with it. $2000/vCPU/year will do a lot of damage to smaller projects in the process of sinking the billion dollar open source leeches in the process.
- azemetre 4y ago
  If you’re making $25mil in revenue why is it out of the question to pay for licenses?
  - Test0129 4y ago
    Why would you? License requisition is a real pain, they have to be factored into the budget, depreciated, etc. If you can instead simply pull in OSS and hide it behind a SaaS implementation (thereby complying with licenses) you can leverage it to make money. I don't think Stallman saw this coming. Some companies do better than others. For example, FAANG level companies typically have teams that do give back. In some cases several orders of magnitude more than they take from popular projects. It's the in-betweens, the other companies that don't do anything other than leech.
    - svnpenn 4y ago
      > pull in OSS and hide it behind a SaaS implementation (thereby complying with licenses) sorry, but you can do that shit anymore: https://wikipedia.org/wiki/Open_Software_License#Network_deployment_is_distribution https://wikipedia.org/wiki/Open_Software_License#Network_dep...
      - bhuber 4y ago
        My interpretation of that clause is it applies to distributing code over a network. The most common example of this is serving javascript to a web browser. I'm pretty sure putting an API in front of a server that happens to run open source software doesn't count as "distribution", which is what we're talking about here with SAAS providers and Akka. If it does, then every site that is backed by servers running linux and not distributing their GPL license to clients is also in violation.
        svnpenn 4y ago
        I would disagree with your assessment. OSL was specifically crafted, to close this exact loophole: > Most other open source licenses treat such network uses of software as internal to the company that runs the server, and they don't require disclosure of source code. That is seen by many nowadays as a loophole that permits large online companies to avoid their reciprocal source code obligations. http://rosenlaw.com/OSL3.0-explained.htm#_Toc187293088 http://rosenlaw.com/OSL3.0-explained.htm#_Toc187293088

afpx 4y ago

Given that thousands of projects are dependent on it, I would hope so. https://mvnrepository.com/artifact/com.typesafe.akka/akka-actor/usages https://mvnrepository.com/artifact/com.typesafe.akka/akka-ac...