True mate

You know who sucks at developing APIs?

Facebook.

I mean, how are so high paid guys with so great ideas manage to come up with apis THAT shitty?

Let's have a look. They took MVC and invented flux. It was so complicated that there were so many overhyped articles that stated "Flux is just X", "Flux is just Y", and exactly when Redux comes to the stage, flux is forgotten. Nobody uses it anymore.

They took declarative cursors and created Relay, but again, Apollo GraphQL comes and relay just goes away. When i tried just to get started with relay, it seemed so complicated that i just closed the tab. I mean, i get the idea, it's simple yet brilliant, but the api...

Immutable.js. Shitload of fuck. Explain WHY should i mess with shit like getIn(path: Iterable<string | number>): any and class List<T> { push(value: T): this }? Clojurescript offers Om, the React wrapper that works about three times faster! How is it even possible? Clojure's immutable data structures! They're even opensourced as standalone library, Mori js, and api is great! Just use it! Why reinvent the wheel?

It seems like when i just need to develop a simple react app, i should configure webpack (huge fuckload of work by itself) to get hot reload, modern es and jsx to work, then add redux, redux-saga, redux-thunk, react-redux and immutable.js, and if i just want my simple component to communicate with state, i need to define a component, a container, fucking mapStateToProps and mapDispatchToProps, and that's all just for "hello world" to pop out. And make sure you didn't forget to type that this.handler = this.handler.bind(this) for every handler function. Or use ev closure fucked up hack that requires just a bit more webpack tweaks. We haven't even started to communicate to the server! Fuck!

I bet there is savage ass overengineer sitting there at facebook, and he of course knows everything about how good api should look, and he also has huge ass ego and he just allowed to ban everything that he doesn't like. And he just bans everything with good simple api because it "isn't flexible enough".

"React is heavier than preact because we offer isomorphic multiple rendering targets", oh, how hard want i to slap your face, you fuckface. You know what i offered your mom and she agreed?

They even created create-react-app, but state management is still up to you. And react-boierplate is just too complicated.

When i need web app, i type "lein new re-frame", then "lein dev", and boom, live reload server started. No config. Every action is just (dispatch) away, works from any component. State subscription? (subscribe). Isolated side-effects? (reg-fx). Organize files as you want. File size? Around 30k, maybe 60 if you use some clojure libs.

If you don't care about massive market support, just use hyperapp. It's way simpler.

Dear developers, PLEASE, don't forget about api. Take it serious, it's very important. You may even design api first, and only then implement the actual logic. That's even better.

And facebook, sincerelly,

Fuck you.

There you are, fiddling with next.js webpack settings, because your isomorphic JS-in-CSS-in-JS SSR fallback from react-native-web to react-dom throws a runtime error on your SSR prerendering server during isomorphic asynchronous data prefetching from Kubernetes backend-for-frontend edge-server with GraphQL.

You have all that tech to display a landing page with an email form, just to send spam emails with ten tracking links and five tracking beacons per email.

Your product can be replaced by an Excel document made in two days.

It was developed in two years by a team of ten developers crunching every day under twelve project managers that can be replaced with a parrot trained to say “Any updates?”

Your evaluation is $5M+. You have 10,000 dependency security warnings, 1000 likes on Product Hunt, 500 comments on Hacker News, and a popular Twitter account.

Your future looks bright. You finish your coffee, crack your knuckles and carry on writing unit tests.

yeah we use isomorphic async hydrated SSR pseudo-rendering with edge-server chunked ES module CSS-in-JS-in-CSS ESNext TypeScript interop through GraphQL in react-native-web transpilation to react-dom in NextJS isomorphic rendering context React hooks

You call it “gay”, I call it “isomorphic” 👩‍🦰🌱

I actually want to rant and pitch a product idea here:

So I am furious when i found out Gravit Designer made offline mode premium only, seriously what the fuck. And Figma is getting no progress for the offline mode either - even lacking grids that I need (I might do isomorphic and I also need grids to keep things aligned).

To be honest I liked Figma more now than Gravit (screw you Corel for fucking up a great platform). So that's why I want to do something similar to Gravit Designer, universal and all, works in browsers, without the forced paywall in my face.

I always forsee premium as a way to add features to products when you need it, and as a way to let a developer know they're doing a good job. I want to make this kind of model stick, and it seems with the money-hungry fuckwits of Corel on Gravit, it ain't happening.

So that's why I want to build an designer app that does what Gravit does, except, I want premium to be more ethical, giving all the core features, add more customizabilty to the interface, and actually make the designer workbench yours. Heck, if its possible we can have Google Drive/Nextcloud integration as well for those who want cloud saves.

I badly want to do this because I believe someone out there shares my sympathy. Gravit was a nice product but was ruined by Corel's greedy paywall system. I won't be paying 99 monthly just to get offlline mode. Affinity and Figma's model is better.

Corel you fucking suck

If you are able to integrate React Router with SSR for an isomorphic app you are not human.

I'd like to make an android Git client eventually. I tried React Native because I already know React and Isomorphic-git would have been a godsend, but the hello world example has a splash screen. Can you recommend an android dev toolkit with the following constraints?

1. Are accessible to a mobile dev newbie
2. Launch very quickly
3. Hopefully accommodate an existing mutable Git implementation