Reahl – A Python-only web framework

Post by IanCal » Sun, Jan 20, 2019, 4:11 AM UTC

bayesian_horse wrote: post #25

eganist wrote: post #10

Earlier quoted context omitted.

> "one language only" if you don't count the javascript, html and css. My hunch is that you strove for making the First Comment considering that the point of this project is exactly what you said it isn't. https://www.reahl.org/layout , for instance, talks about how styling works. Taking this further, here's a comment from one of the maintainers on the relevant Google Group: > Hello. > We want casual users of Reahl t…

"One language only" is a marketing slogan. It's slightly misleading, since it doesn't look like you can implement meaningful applications in 100% Python or get away with zero knowledge of HTML and JS. But it may be close, like you can spend 90% of your development time on Python, and write JS components in the remaining 10%.

Post by saagarjha » Sun, Jan 20, 2019, 4:20 AM UTC

giancarlostoro wrote: post #30

nine_k wrote: 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.

Post by giancarlostoro » Sun, Jan 20, 2019, 4:32 AM UTC

saagarjha wrote: post #34

giancarlostoro wrote: post #30

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.

> It makes no sense to me why a library would be AGPL licensed > AGPL means you have to share any code you write using this framework I think you've found the reason?

Post by saagarjha » Sun, Jan 20, 2019, 4:42 AM UTC

giancarlostoro wrote: post #36

saagarjha wrote: post #34

Earlier quoted context omitted.

> It makes no sense to me why a library would be AGPL licensed > AGPL means you have to share any code you write using this framework I think you've found the reason?

But you're using this code in any application you make, so you can't use it commercially.. AGPL isn't made with libraries in mind...

Post by paulie_a » Sun, Jan 20, 2019, 5:03 AM UTC

macspoofing wrote: post #37

jaequery wrote: post #28

I feel bad about projects like these, I really do. I'm sure a lot of effort have been put in and it probably satisfies what OP wants to do. But in the end, no one serious would ever consider using it.

>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!!!).