Re: Obviously was not tested
Shows how unwise it is installing anything with a version number that ends in .0
26 posts • joined 21 Sep 2018
The problem with Algol68 was that Aad van Wijngaarden treated it as an academic exercise, valuing elegance over practicality. He regarded Algol68-R as unclean, it having compromised on some of the more esoteric features to make it actually usable for real work.
People who used it told me one great feature was that most bugs were detected at compile time, i.e. once you got your program to compile it usually worked (unlike C).
"We truly believe that this transaction is good for all stakeholders because it allows PIR to invest in the registry and expand services for the benefit of all registrants"
If you own a domain name, you need to know it's globally unique. And from a registry that's all you need. So what exactly are these new "services"?
The idea was to give UK companies a head start in developing applications that use the new services 5G provides. Problems include:
- they wanted the testbeds to be built using off-the-shelf equipment (which by definition isn't the latest technology) on the assumption it's cheaper
- there are precious few applications that can be done with the current (3GPP Release 15) version of 5G that can't be done with 4G
- the way the calls for proposals are structured locks out micro-enterprises with really innovative (and cheaper and less power-hungry) technology which could have got the UK into a position where it wouldn't be dependent on China and the US for the equipment that implements the really interesting features of 5G
ITU has a nice triangular diagram that shows three main use cases for 5G: faster Internet, IoT, and applications (remote surgery is often cited) where latency matters. The first of these is LTE with a few tweaks, and is the only one being delivered, or even really supported by the 3GPP standards, as of now.
The main problem for IoT is battery life in devices that are so cheap you can have lots of them in different places; IPv6 over LTE is the problem there, not the solution, because of the amount of data to be transmitted to upload a couple of bytes-worth of information.
Critical applications that need low latency need something more than just a bit less contention for a best-effort service, and no, slicing is not a viable way of achieving it.
Biting the hand that feeds IT © 1998–2020