fruiapps

Printing a hello world over kubernetes cluster is an overkill, so are multiple microservices when you do not need them. I loved monolithic django, but with the advent of microservices architecture and modern JS libraries react, vue, and the likes, here is what you got to do

Create a DRF Backend

Take care of authentication at both ends

Build your SPA in a modern JS framework.

The good is modularity, maintainability, better UX controls, super interactive UIs, and the likes, the bad is you need to write more code. In simple cases the good old django templates is good enough. Is anyone still doing them? I love the organised new age FE framework code, the imports that come with ES6.

Is anyone still doing monolith with django template and ES6. If so, mind sharing your workflow, and libraries?

Apple attempted to levy a 30% App Store fee on Hey subscriptions, despite the fact that Hey doesn’t actually allow in-app purchases (payments happen on the web). While Apple’s actions were not necessarily in response to the competition, they do call out Apple’s incredible power over app developers.

Last January, the entrepreneur took his Twitter rants directly to Congress, testifying in front of the House Antitrust Committee:

“A small company like ours simply has no real agency to reject or resist the rules set by big tech. And neither do consumers. The promise that the internet was going to cut out the middleman has been broken”

This dictatorial nature is not limited to big-tech, but in my recent experience, while submitting an integration to Zapier, here is what I discovered.

1. Do the API integrations as per them - which is fair and expected.

2. Create a blog-post and documentation about your submission.

3. Send this to your subscribers.

4. It does not stop here. Create Zap templates on Zapier and then embed it on your website.

5. As if this was not enough, now they want you to bring them 50 customers. Unless you do that, your app is in beta.

If not dictatorial, what is this? If you want to submit your app

1. Give me free backlink 2. Give me a blog post 3. Give me a website embed. 4. Give me an email shout-out to your subscribers. 5. Well that is not enough, I want 50 of your customers to sign up with us.

What do you think about it?

Facebook recently came up with a new license.

My understanding is that you're only at jeopardy of losing your license to React if you sue facebook over patent infringement. AKA, facebook implements a feature that you feel infringes on a patent you hold, and you actively sue facebook, then you lose your license.

The overly broad terms are the main problem. I have read across and found it difficult to interpret the clauses.

We thought of migrating to Preact[1] and were advised the following :

    what most people don't realize is that at least react contains a patent grant for 
    react related patents for you. Preact comes with no such guarantees and most likely 
    infringes a lot of those same patents -- without you having any kind of promise that 
    facebook won't sue you.

    You're more likely to get sued for patents if you use preact (or inferno etc).

What are the general understanding people over here have, in terms of using and not using React JS, not technically but from a legal perspective.

[1] - https://preactjs.com/