Live data from Hacker News

Reahl – A Python-only web framework

reahl.org

71–80 of 108 posts

Re: Reahl – A Python-only web framework

#71
post #68

Earlier quoted context omitted.

I have always disliked the “GPL doesn’t prohibit commercial use” argument. You know well why it isn’t practical to use for commercial purposes. You basically make any project using it into an unlimited full featured free trial.

> I have always disliked the “GPL doesn’t prohibit commercial use” argument. You know well why it isn’t practical to use for commercial purposes. You basically make any project using it into an unlimited full featured free trial. I don't get it. What would be so wrong about making your source code available to everyone (including your competitors)? Remember, if your source code is AGPL and someone uses it, their sour…

It breaks the pay-per-copy model, which is realistically the only one that is viable for a lot of proprietary software.

Re: Reahl – A Python-only web framework

#72

Earlier quoted context omitted.

AGPL means you have to share any code you write using this framework. It makes no sense to me why a library would be AGPL licensed, LGPL is what I expect libraries to be, of course I'm not sure how the LGPL applies to Python, but I'm usually all in for MIT License.

More importantly it means you have to share any modifications you make to the library itself. This is good for us. Sharing is good.

sharing forced by license is not good.

Re: Reahl – A Python-only web framework

#73

Earlier quoted context omitted.

More importantly it means you have to share any modifications you make to the library itself. This is good for us. Sharing is good.

sharing forced by license is not good.

Why? It's worked pretty well so far. We wouldn't have free software at all without it.

Re: Reahl – A Python-only web framework

#74

Be careful. This is licensed under the AGPL, which basically makes it unusable. Or a commercial license can be purchased.

I'm surprised GitHub doesn't show this on the repository it just says "View License" but I guess they don't allow using AGPL when creating a repository.

They do support showing AGPL 3.0, but it has to be either in a LICENSE.txt or LICENSE.md. This project just has it in a file called LICENSE. https://help.github.com/articles/licensing-a-repository/

Re: Reahl – A Python-only web framework

#77
post #27

Be careful. This is licensed under the AGPL, which basically makes it unusable. Or a commercial license can be purchased.

"Unusable" seems quite strong. It's usable for open source projects.

Sort of. It's only really usable for those who want to apply the same restrictions to their users/contributors.

Re: Reahl – A Python-only web framework

#78
post #64

You took a declarative language (HTML) and mad it imperative (Python). Why is that a good thing?

I've been thinking about this sort of thing a lot recently in terms of our heavy use of Troposphere[1] which is a Python abstraction over AWS CloudFormation and how much better that abstraction is than just writing HTML (in the case of this library) or JSON/YAML (in the case of CloudFormation) directly. Ultimately, for me, it comes down to what makes sometimes complicated declarative code easier to reason about, read…

If you like troposphere, you'll love stacker:

https://github.com/cloudtools/stacker

Re: Reahl – A Python-only web framework

#79
post #6

Does APL here mean you can only use it ti build APL-licensed server code? Apparently it should be the case.

AGPL means you have to share any code you write using this framework. It makes no sense to me why a library would be AGPL licensed, LGPL is what I expect libraries to be, of course I'm not sure how the LGPL applies to Python, but I'm usually all in for MIT License.

In this case, AGPL seems to be an open source veneer on a free during development license.

Re: Reahl – A Python-only web framework

#80

Earlier quoted context omitted.

>But in the end, no one serious would ever consider using it. Why not? I would say it is the other way around. For any web application project of decent size there is almost always a transpilation step that converts whatever programming language your source code is in, into JavaScript (usually ES5). We also had very successful and widely used projects like GWT for years (GWT was first released in 2006!!!).

Transpiling to JavaScript is a bug on the web, not a feature. node and npm is a shit show. Having to deal with it a couple days ago. I wish that entire ecosystem would just die. I can make a sophisticated python web app with 20 packages. Or in JavaScript I'll need a few hundred that have massive vulnerabilities and conflicts. Hell npm reported the most modern packages I was installing had over 200 vulnerabilities. Ja…

Amen brother. It just baffles me that most people here in HN enjoy working with JavaScript and its derivatives. I feel bad for them, like when you see a 14 year old kid smoking and drinking
Post reply on HN