It works great for me
I replaced fibre with it:
Not bad for a 30-day rolling contract for £28 pm.
464 publicly visible posts • joined 13 Jun 2009
> it results in exclusion of those who don't keep their browser "up to date" with the latest execution capabilities.
Indeed, yesterday there was a submission to HackerNews about some scandal in the Scala community. Every browser I used on my admittedly old iPad to view the medium.com article would show the text for a few seconds before rendering a completely white screen.
Redis is great, I like Redis and use it a lot.
We're better off running Redis as a standalone instance rather than through Elasticache. We run an instance on each core and shard requests to each core (from the client, not server), this saves a ton of money. We can also then use modules. There is a multi-threaded version of Redis, KeysDB, that we'll soon take a look at.
I recently moved to Edinburgh from London and am using the Huawei device as a replacement for fibre. The SIM is Vodafone's pay monthly unlimited data one and is working nicely so far. 90Mbps is average so far, but should hopefully go up once I can get a 5G signal. The cost is slightly cheaper than my previous Virgin Media 100Mbps fibre deal. It remains to be seen how it holds up in stormy weather.
There is an underlying assumption here that people invovled in software are largely a) American, and b) speak English natively.
The first is just American Privilege pure and simple.
The second negatively affects anyone who has to use a dictionary or online translation service to contribute to a project. They're not likely to be aware of the nuances of certain words.
C++ is unfortunately doomed. A lot of fantasic work went in to C++11 and beyond but it's a dying language. Memory safety issues aside (which should have been largely solved by RAII), it's too complex (there are 5 ways to initialise a variable, xvalues, glvalues, prvalues, lvalues, rvalues), its networking framework is too much but also too little and there's zero mention of unicode. I get the feeling that companies like MS, Google and Mozilla are of the opinion that trying to fix their broken C++ code is too much effort when they could just rewrite in Rust.
I'm not a fan of the visual look of Rust source code but I think it'll become a desired skill if not by its merits, but by the herd wanting to use it.
Our server code is written in C++ and I can't remember the last time we had a crash or a memory leak. I'm not saying we're perfect but C++ has come on leaps and bounds since C++03. Rust protects you from this unless you go 'unsafe', and the devs that can still make modern C++ crash and leak will probably get to do the same in Rust.
That said, what will get Rust more widely used is the 3rd party libraries / source code. With C++ it's a pain and that random HTTP parser you cloned from github may not be the best quality.
Also, networking. C++'s ASIO stuff is a headache, I'd be surprised if Rust is in a similar boat. I'm considering dropping ASIO altogether and going straight to using io_uring.