ttty

Let’s say with your optimised settings your ROI is 20%. With Google settings is 15%.

An end user might say 15% is pretty good and don’t touch it.

Google just earned 5% by giving you worst ROI.

If you start comparing with other ad providers you’l you might notice you’re being screwed. But low spenders rarely do proper checks.

So you rather write your app twice: once in react and once in go? And keep it in sync, including css and styles and dom… ? For real?

I'm building a simple page. Ok let's do simple html. Now I need popup for email capture, ok add a bit of hacky js. Now add a menu, could potentially be done with css only.

Now add responsive images. Good luck. You need to process then on server side, then handle them on client side etc...

Now add some customer area...

Add a few more features and it becomes complex.

Why would you want to now throw away all this and rewrite in react when you could just start with react.

In addition I can even migrate my old app to the new one and sometimes I can just copy paste certain components and css styles (thanks to css in Js) and it just works.

Honestly I don’t want to write responsive images manually. I just wrote a system once, now any app reuses the same thing. Same for other stuff. Plus I only need to know react and I can build anything.

You telling me now to learn htmlx syntax and use it sometimes, then use react other times just because… it’s simpler. The benefit is minimal, but now I need to know 2 worlds: react and htmlx.

Refactor any js code to typescript. You’ll see how many bugs are discovered and how many wtfs!

It’s the 2nd comment mentioning this issue

Image resizing can’t be done statically. That’s a big issue if you want to serve things from cdn property.

Tailwind is to styled components .... Like jQuery is to react.

Popular now, huge pile of mess in a few years.

> My Google cal emails me notifications

Until you get locked out/banned by Google.