bertolo1988's comments

bertolo1988 | 8 years ago | on: Plain emails not only save time but work better (2016)

I have had a job where they tried to implement emails 4 times. The last attempt is still ongoing and in my opinion destined to fail.

They wanted to implement few dozen of auto generated emails with huge content.

The task was suspended 3 times, always because of the same thing: cost. Its insanely costly and hard to make a good looking cross platform email. After every suspension there were new design changes to implement so we ended up starting almost from scratch in every attempt.

I worked on it for a bit and i can assure you email clients are the biggest shit. Specially Gmail and Outlook.

A few highlights:

* Javascript not allowed.

* Outlook processes HTML and CSS with a specific engine which is also used in Microsoft Word.

* Outlook does not support paddings.

* Gmail requires the styles to be all inline.

* We followed Foundation Zurb recommendations and used tables all over. Still didn't work on all clients.

Humanity urgently needs to replace the emails with something else. Not only because the clients suck but because the protocol is outdated.

bertolo1988 | 8 years ago | on: Napa.js: A multi-threaded JavaScript runtime

> What if you have a large shared in-memory data structure that you want to update with lots of irregular translations in parallel

Use C++.

If you ever decide to scale and distribute it for real save the state in a database and orchestrate containers. For this solution i would recommend using Node.js or Go.

bertolo1988 | 8 years ago | on: Napa.js: A multi-threaded JavaScript runtime

1 - How is REST complex?

2 - That is only true if the your bottleneck is on communication somehow. Usually it is not.

And a huge advantage: You will write stateless and easy to scale apps that do not care how the machine resources are being handled.

bertolo1988 | 8 years ago | on: Napa.js: A multi-threaded JavaScript runtime

Its not up to me to know how to manage processes or threads. That's the SO task, not mine.

My app should be stateless and scale by replication. This is the most efficient solution in every possible way.

page 1