This, that, and whatever

[iamlost]

Three quite different bits of fluff minutiae:
1. I'm something of a C++ hobbyist slash nutcase :) Almost two decades ago now I wrote a CMS in C++ however web server scripting was PHP. As of this week PHP is gone. C++ rules!

2. While I truly appreciate the power and utility of node.js it has some serious 'holes' and ongoing critical security issues are a concern.

As I also use Redis the development/addition of streams, is in my usage, a viable alternative. Currently in development/test but, depending in part on Redis version release, should be ready for production side by side test release in a few months.

Yes, iamlost.

3. A friend who retired to sunnier climes in the southwest Pacific/Indian oceans area was getting his digs in the other day: mid morning, his time, he was out in shorts and tee enjoying 34C (93F) while early evening, my time, I was just in from exercising dog in -34C (-29F). Wearing far more clothes.

Can one hire a snowball attack in the tropics?

[NickMNS]

1- I haven't started in C++ yet, I guess at some point I'll find some reason to, likely through Cython.
2.5 -I have just started using redis for message queuing seems pretty straight forward.

3.. I am not quite at -34C but heading in that direction, we are looking at about a 20 to 30 degree drop between now and tomorrow AM. It's currently 0C. Was your -34 including a wind chill factor?

[brotherhood of LAN]

I learnt C and try to avoid that fancy c++ stuff. I do love (trying) to code up stuff in it.

I've dabbled with nodejs. The thing I don't like with more modern day stuff is there's relatively simple things you want to do, see someone has wrote something... but it takes about a Gigabyte of slapped on dependencies to get it going. Along the same lines I purchased an HTML5/bootstrap template and the download was 100MB.

I also had a nodejs dev insist that node was the only way to do non-blocking IO... sometimes these new techs seem like the answer to everything, for some.

Redis, tried it but never made a good attempt at using it in production. I do really like libJudy, but it does require locking between read and writes. LMDB is supposed to be really good too.

[NickMNS]

node was the only way to do non-blocking IO...

Definitely not.
I am using Python for non-block IO. From what I read is that it is also doable in PHP but not as straight forward, as say node.js or Python.

[brotherhood of LAN]

Indeed. Pretty much any language can do it, just depends on the default nature of things and what you want to achieve.

PHP can do it just fine. [php.net...]

[graeme_p]

A lot of languages can do that. I wrote a non-blocking webserver in TCL years ago (TCL was the first language to really put much emphasis on it and is probably still the easiest to write it in).

You can do it is C, evidently, as several non-blocking web servers are written in C.

As Nick says Python can do it. I have not found it particularly enjoyable to do so far though - its not terrible (and from what I have read better than PHP) but I do not think its brilliant either. I have stuck with it because of Python's libraries.

The fragmentation will fix itself as asyncio has momentum now, and other issues will too. In the long term the community is building a lot around asyncio.

Every other language I have looked recently can either do it, or offer an equivalent like green threads - I like learning bits of new languages, so that includes Haskell, Erlang, Go, D, some Scheme implementations....... I only made an real effort to learn the first two, but I read up on several others.

[iamlost]

@NickMNS: that was -34C without windchill, was -42 with. It was the -34/+34 that caught my eye. Currently -25C, -35C with windchill and ice crystals. Canada, eh?!