emixam

Hello, author here. It is actually possible to use return instead with a different set of decorators: check out the first "tip" block on this page: https://hyperflask.github.io/sqlorm/sql-functions/

Some of the sub-projects of hyperflask can be re-used elsewhere but most of it is Flask specific.

Notable sub-projects that could be used with Django:

- https://github.com/hyperflask/jinja-super-macros

- https://github.com/hyperflask/jinjapy

It is for now. Hoping to rally others !

sqlorm is a new orm developed as part of hyperflask.

I use sqlalchemy daily, it's an amazing library, but I wanted something more lightweight and straightforward for this project. I find the unit of work pattern cumbersome

I would be glad having some users on this project but that would definitely kill it !

It's in sync with the Locality of Behavior [0] principle that htmx follows.

It's inspired by Astro Pages [1] which are the same thing in the javascript world. I really liked the developer experience working with them.

[0] https://htmx.org/essays/locality-of-behaviour/ [1] https://docs.astro.build/fr/basics/astro-pages/

Thank you so much ! Great work with htmx, I'm a fan. This project is the culmination of a lot of concepts I like from many different stacks coming together.

I knew of unpoly but didn't know about alpine-ajax. My choice was set on htmx since the beginning. I feel it's a more mature solution with more flexibility.

There is Flask-Admin but it's more bare bone than Django Admin. I plan to tackle the problem in the future.

Thanks ! I've introduced a lot of stuff with this project and I'm glad someone noticed :D

I've also submitted SQLORM on HN if it's of interest to others: https://news.ycombinator.com/item?id=45607688

I've built SQLify with it: https://sqlify.me

Hello, author of hyperflask here. I'm happy to finally announce this project as I've been working on it for quite some time.

I made an announcement post here: https://hyperflask.dev/blog/2025/10/14/launch-annoncement/

I love to hear feedback!

The framework is composed from many extensions indeed. You can use them independently though!

The component system is not fully independent because it depends on multiple other extensions but it mostly is as this extension: https://github.com/hyperflask/flask-super-macros

On the GitHub organization there is a list of all the extensions that are built as part of the project: https://github.com/hyperflask

From what I understand, there is no limitation regarding the type of company when it comes to the French Tech Visa (as long as it qualifies on the other requirements which focus more on the innovation aspect). (my coop would be eligible for example)

Starting a coop is like starting any other kind of company so same rules apply. (You must be at least 2 people of course!)

The problem really comes from the capacity for a coop to raise funds. A coop is a non-capitalistic company so very few investors are interested.

There is no valuation other than amount of shares x value of share. Voting power is not dependent on share (1 person = 1 vote).

Making an exit is thus not a possibility. Investors have little interest to finance a traditional company that would only yield dividends (if it does, which is not mandatory).

The problem of speed is also often cited: democracy takes more time. While I think that's true, I haven't felt that was a limiting factor. Financing is a much bigger one.

Not necessarily (the coop I work for is one though). There are 3 possible types of coops in France: SCOP, SCIC and CAE. To make it short:

- SCOP: adheres to the international definition of coops

- CAE: a coop of freelancers. You are an employee of the structure (with a work contract) but you have to bring in your own revenue to pay your salary. A percentage of your revenue goes towards the coop budget for shared services (accounting, hr, ...) and cash reserve

- SCIC: a multi-party coop. A good use case would be platforms where you could have multiple groups of stakeholders: employees of the platform, users and service providers. (eg. with a Uber like coop: employees, users and drivers could all be separate groups of owners). Each group has a voting percentage. No group can have more than 50% ownership.

I see great potential for the 2 other types of coops that France has in the context of tech. I do not know of any equivalent elsewhere (but would be happy to learn it exists!)

Happy to see this list here on which our coop startup appears! (https://kantree.io) It is very challenging to raise funds as a coop indeed but we have managed to do it on small amounts (a few hundreds of thousands). We are one of the few product based coop and not service based.

France (where we are based) is actually a very interesting market for coops. There is a very good legal framework around coops and a growing percentage of them. There's even an investment fund of tech coop as of recently! https://coopventure.fr/

I think coops are a great ownership model for the future and for a more responsible economy. It is too bad that there is still very little support and recognition around it.

I'm one of the co-founder of Digicoop, a worker cooperative based in France. We develop Kantree, a work management platform as SaaS or on-prem solution.

We are a small team, all employees are associates and we are remote first. New employees must become associate after 1 year.

The hardest part for us is funding as no investors are interested in worker coops.

We had quite a few hurdles on the way and the startup scene mostly rejects outliers like us as we have no true funding story to tell. But we really believe in this model and fight hard to keep going.

We have written about our company on kantree's blog if you want more details.

I've been working on a tiny vanilla js lib focused around web components: https://github.com/maximebf/gousse.js. It includes a set of components using Bootstrap: https://github.com/maximebf/gousse.js/blob/master/examples/u...

Indeed, their Android app is amazing and we hope to offer something of the same level in the future. Right now, Kantree is responsive and will adapt to smaller screens. The experience should be good on tablets. Unfortunately, we're still having a few touch and performance issues on larger projects which we are working on.

We are starting beta testing the self-hosted version this month among a limited number of testers. We're integrating with LDAP at first. Pricing starts at 150$/user/year with discounts the more seats you get. We will adjust the pricing as customers enroll. If you're interested in joining the beta, contact us at [email protected]

Thanks! The Github integration is already available under your project's settings in the "Service Integrations" tab.

We wouldn't have used such a headline but we were not the one submitting this. We contacted the admins to change it.

Hi, co-founder of Kantree here. We were not the one submitting and hadn't plan this for today but we're here to answer any questions you may have :)