* Posts by bazza

3501 publicly visible posts • joined 23 Apr 2008

Tesla batteries went from fully charged to fully disabled after botched patch, lawsuit claims

bazza Silver badge

Re: Taxes

The problem with ANPR based charging is that it makes it trivial to evade. Just get a cloned plate. People already do that, and never seem to get caught.

Energy taxation at source is a good way of taxing usage. You can't get the petrol without paying the tax. As soon as they try things like ANPR, or a special meter for the car charger at home, or GPS logging in the car, you're handing opportunities to those minded to evade paying and you have very few means of stopping them. The sneaky thing to do would be to introduce GPS logging based taxation, but the government has shares in the company that sells GPS jammers (which are commonly available anyway...).

bazza Silver badge

Re: Everybody throttles

They're written off so far as the customer is concerned. That's a fraudulent way to do business.

bazza Silver badge

Re: Everybody throttles

The software may well be the thing that makes it look like the battery has only so much capacity, but it's also the thing that stops you driving the car... And you can't drive a car with an utterly inaccurate energy-remaining meter.

bazza Silver badge

Re: Yet Another Needless Distraction

And at present, it looks like current stock holders are clinging to a vision of beauty that wasn't there, and increasingly being revealed to be something of a monster... That has all the hallmarks of a sudden stock price collapse in the making!

bazza Silver badge
Mushroom

Yet Another Needless Distraction

The only successful thing about Tesla's self driving endeavours is that their actions are driving the company towards needless oblivion.

Full Self Drive, Autopilot, the fuss around the OTA updates wearing out the miserly flash storage they'd used, this stupid thing with the batteries, their not-great build quality, their substandard customer service, their immaturity at production design (anyone remember the Musk-driven farce of them trying to automate production of the 3 Series, costing $billions?); all these things are destroying what should be a successful and enduring BEV manufacturer with the best charging network.

Now one of their USPs - OTA updates - has become yet another reason to sue them, not to be thankful towards them. The very fact that it's got to court - repeatedly, in different countries - will surely be a huge red flag to absolutely anyone who hears about it. OTA update screw ups followed by effusive apologies and swift rectification - you could live with that. Having to sue to get a fix - no ****ing way.

Toyota sold their stake in Tesla years ago, apparently because they decided they couldn't work with Musk, the way Musk wanted the company to work. Well, if this is the end result of it being done "The Musk Way", they were right to leave him to it...

Japan's ubiquitous convenience stores now serving up privacy breaches

bazza Silver badge

Re: Something something pun about Horizon

Oh, certainly some American geneticists do know about it, because they were involved in getting the conviction overturned. However, I fear you've made the same mistake as "experts" are often very prone to doing:

"a well known genetic situation that is called chimerism, rare, but well studied"

Unless a comprehensive, statistically sound systematic study quantifying the occurrence rate of this condition can be cited, all that can be said is that it is a condition that is rarely encountered, and be very clear that as to the reason why.

In this particular case, there was no such data available at the time. To the best of my knowledge there still isn't. Even the references cited by the Wikipedia article on the topic admit that tetragametic chimerism is of unknown occurrence, and could be quite high. What's interesting is that the reference in Wikipedia isn't even a published, peer reviewed paper; it's just a short blog. That probably means that science, officially, is mute on the topic. Yet almost everyone (including yourself it seems) would be absolutely certain that it is a rare condition.

Honestly, you'd think with this unquantified uncertainty lurking in the background of genetics, you'd think that courts should be pretty skeptical of genetic differences being presented on behalf of prosecutions (such as child care / custody cases), or at least have a standard for considering the possibility of a chimeric. But I severely doubt it. The view that "DNA matches are generally correct" is so deeply entrenched in the popular psyche, it takes a lot of imagination to to even think to ask the question, "are we really sure?". If I correctly recall the outcome of the case in the US, the perceived "rarity" of the condition was used as a justification to not alter court procedures for similar cases...

Peer Review? Nope

A major problem is that the way such scientific data is handled in the criminal investigation / prosecution system is that it is strictly procedural. There is zero room for the forensic scientist to deviate, inquire, question the standards. If they've been told, "do this and if it's not a match, you say so", that what they have to do; they've been told, "the procedure is safe, follow it". You don't get peer review of evidence, there's no space for academic curiosity and to say, "hang on a mo, I read a paper on this".

Currently the court system relies on there being sufficient numbers of eventual successful appeals. Though as we've seen with cases like those involving Horizon and also Roy Meadows, the damage done can be devastating and fatal. You'd think that the high possibility of such an outcome would focus the minds of the judiciary into getting a better grip on how they run their courts w.r.t. technical / scientific data.

bazza Silver badge

Re: Something something pun about Horizon

WRT the Post Office scandal, whilst Fujitsu's software wasn't the greatest, the largest part of the blame for the wrongful convictions lies with those too lazy to check the software's reporting, and presenting said data as "fact". In my view there were a number of failings. The Post Office didn't verify its evidence. The Courts did not force the Post Office to verify its evidence, repeatedly allowing convictions based on a single unverified source of evidence.

In my opinion, whilst Fujitsu is part of this chain of failure, the Courts' failure to understand or even inquire independently of the quality of the evidence being presented to them is the ultimate real problem. If courts are unable to determine sworn bullshit from sworn fact, you cannot have a fair trial.

The inquiry into this is still going on. However, part of the problem with the inquiry is that it is a former judge running it; one wonders how open he is to examining the role of the judiciary in admitting the evidence in the first place. Historically, when "science" has gone wrong in court cases, they're not exactly keen to examine why. There's repeatedly been miscarriages of justice due to "trusted experts" turning out to be bullshitters - the Post Office scandal, the role of Roy Meadows in the Munchausen-by-proxy baby deaths wrongful convictions. Years ago there was even a rape conviction that hinged solely on DNA evidence; the conviction was overturned, because the convicted man was wealthy enough to commission his own forensic test that showed that, yes, he was a close match but definitely not a perfect match; he won at appeal. That case resulted in a change in the standards required for DNA evidence. The point is, the initial standard that he successfully discredited had been set by "trusted experts", who turned out to have been bullshitting, and had resulted in wrongful convictions.

Chimerics

For DNA evidence, worse still, there's been proven cases of genetic chimerics in the US courts - a child care fraud case was overturned when it turned out a woman's reproductive organs really did have a different genetic make up to the rest of her body.

Science has no idea how common this trait is. There is very little data, so it is considered rare. But again, it's bullshitting; medical science has no evidence for how rare or common it is, and adopts the view "we've not seen it much, so it must be rare". However, you cannot really systematically measure the occurrence of this condition without detailed examination of a large number of corpses, cm cube by cm cube, which is not something that's really possible to do. So far as I know, no one has ever done a systematic study.

So, with every piece of DNA evidence - whether accusatory or exonerationary, there is doubt; we don't really know if there is a reliable read across from the DNA profile derived from, say, a mouth swab to the DNA profile of samples from other parts of the body. It's assumed to be reliable. Yet this doubt is not explained to courts, or investigators, and this too has (in the US) resulted in wrongful convictions that were very difficult to overturn.

In that particular case, it was overturned by means of having a court official witness the birth of the woman's second child, and a DNA analysis of that child and the mother to prove the genetic discrepancy. The Judge in the case ended up saying that he now had no idea whether he could ever trust DNA evidence ever again.

Fed up with Python setup and packaging? Try a shot of Rye

bazza Silver badge

Software Packaging is Hard

Python is in a right mess, which is partly why I don't recommend it for actual software engineering.

Python is not helped by the fact that python gets used in Linux distros / desktops as a system component in a way that exposes that Python environment to users. Of course it's going to get mixed up with their dev python environments. It's amateurish design and it's asking for trouble.

But it's not that great elsewhere. If one looks at anything and everything from autotools to snap, there's some severe issues. Just try running two different versions of gcc on a system and build using the none standard one...

At least with OSes like MacOS, Windows and FreeBSD there's certain guaranteed minima to work to.

In Linux you can see why things like snap and flatpak get invented - about the only way of getting the right environment for software is to bring it with you these days - but feels like that is an insane way to go. Certain projects don't help either (cough GTK cough).

The entire Linux distro world should take a look at Visual Studio. If I install that, I don't end up with a build environment that's entangled with my OS and desktop environment in a tangled knot of conflicting dependencies. I don't end up with compiled code that is platform unique. I can very easily get a packaged installer that'll work on, well, any windows installation. And, if it comes to that, it also does a pretty good job of letting me compile, debug and run C/C++ software for Linux too (though it is then at the mercy of what is inside the Linux distro, but with WSL one can have quite a few different Linuxes at one's beck and call). It does this a lot better than most of the Linux dev tools (which is probably VS Code these days anyway).

With Linux distros as they are today, I really think that Linus and his colleagues in the kernel project are wasting their time. The kernel has done an admirably good job at keeping the kernel system interface consistent - "don't break userland". That's not achieving much if the all the "users" are going to do with software is either build it from source at installation, or run it inside a virtual machine. The kernel is written to support binary compatibility. The rest of the Linux world is so dysfunctional that that is an increasingly ignored and snubbed blessing.

Until Linux distros stop being structured to drive software building in a me, me, me and only me direction, software distribution will remain a messy nightmare. Build / dev environments need to be entirely separate to the OS environment.

US watchdog grounds SpaceX Starship after that explosion

bazza Silver badge

Re: They may call it a success...

>The point here is that hardware rich development is massively cheaper than the alternatives.

It is, provided that one has not made a serious error of judgement. The poor performance of the flight termination system (50 sec between trigger and break-up) alone could write-off the whole concept of a heavy stainless steel built-like-a-tank StarShip.

Superheavy, which doesn't leave the atmosphere, can probably carry linear cutting charges on the outside to ensure instant and good fragmentation without those explosives being exposed to high temperatures that'd cause them to go off unintentionally. Same can't be said for StarShip. It's going to have to re-enter the atmosphere.

If they need to be more sure of the FTS cutting it to pieces when commanded, I'm not sure how they then lose those charges before reentry so that it doesn't get cut to pieces by mistake. It looks like they've tried to get away with two boxes on the outside of the rocket, which I'm sure are intended to be disposed off just before reaching orbit. Easy to drop off a box. Less easy to drop off linear charges attached all around your rocket's body.

Nothing ever launched before has had a need to bring a FTS safely back to ground. The Shuttle managed it by dropping off its FTS in the upper atmosphere before reaching orbit; it was in the external fuel tank and/or SRBs.

bazza Silver badge

Re: They may call it a success...

None of this matters if they can't get a FOD-free launch.

bazza Silver badge

Re: They may call it a success...

Yes, it is a problem. Generally I've seen it most commonly exhibited by what I call the "MatLabists", who think they can model anything.

The hilarious part is that such people often seem to think they can turn their model into a working system, with direct synthesis to an FPGA, or similar. I've never, ever seen that succeed in anything but extremely trivial ways. The worst part of it is that MatLab is a very bad way of implementing an entire system, so the MatLabists don't ever get to explore the entire system, and therefore tend to have a skewed view of how much of the system is composed of their part (generally, not much) and how much of it is other stuff (databases, networks, people, etc). Given that model to implementation synthesis only ever works on a very limited range of hardware, and that there's many, many other factors that go into hardware selection than "does it play nicely with MatLab?", they often totally fail to deliver anything at all useful. And they really, really do not like being told that their part is perhaps only 5% of the entire thing.

I generally budget for starting again from scratch.

Though I will say that I have seen some very good results using kit from Annapolis Microsystems, largely because they build pretty good hardware and their own tooling. They make it easy for their kit to be part of a functioning system.

The problem these days lies in organisations that don't have experienced engineers leading them. Such management gets all sorts of messages, and the Matlabists generally promise generally offer cheap deep insights, certainty, guarantees, where as the more realistic engineers are (in effect) saying "we have to spend some money". If you're not an engineer and know no better, and one "engineer" is saying "you don't need to spend money yet" whilst another is asking for a budget, who are you going to go with?

The best advice I can give to management is to look at track record very, very carefully. If someone has a track record of delivery and can point to successful in-service systems with their name on it, listen to them, give them the cheque book. If someone is putting up a lot of pretty pictures but can't actually show you some physical hardware (or software) that's been in use for a lengthy period of time, ignore them (or fire them).

bazza Silver badge

Re: The fuse wouldn't be that long

I don't know how fast the first stage goes, or whether atmospheric friction heating ever gets high enough for external explosives to be "dodgy". Certainly things like the external fuel tank for the Shuttle got fast and high enough that it would disintegrate on falling back to earth. I don't think the StarShip first stage gets that high or that fast, so maybe it could safely carry external explosives for the whole trip. But, to my knowledge, getting explosives "too hot" is not a good idea, stability wise.

When we look at other programmes, the bit that comes back is generally not the bit that's dangerous at launch. Gemini, Apollo, Soyuz style rockets; it's just the small mostly fuel-less capsule on the top that comes back. The Shuttle had its fuel tank on the outside, and never took it into orbit. All previous manned flight has had the range safety package on a component that did not need to go into space, or did not need to survive re-entry.

It'll be interesting to see if the FAA decides that range safety for StarShip does need to be beefed up. On the face of it, it looks like it is. Solving it could be a tricky problem. When one thinks about the problem of re-usable space in the context of being able to blow it up if necessary, it starts to make the Shuttle's architecture look fairly good.

So Near to Success, So Near to Ruining it All

StarShip feels like it's a good idea, but only if it's become reliable enough that (like a Jumbo Jet or any other airliner) one has high confidence in how well it can be operated. Get it to be as reliable as, say, a 747 and it'd not need a flight termination system.

Safe designs can be dangerously operated. Dangerous designs can be safely operated. All mechanised transport is of the latter. SpaceX have shown with this test that they've got a dangerous design (nothing inherently wrong in that - all things that move fast can be dangerous), but they're not very good at operating it (which is why the FAA has grounded them for now). Fixing that could be a whole lot more painful than any technical design changes.

For example, a lot of commentards (I include myself in that description and set) are saying "flame trench + water deluge" is the way to go. Everyone knows that they'd have a much greater chance of getting cleanly into they sky, with that launch pad set up. So, why not do the thing mostly likely to be successful in 1) being permitted, 2) actually working? Why throw yet another novel, untested, unverifiable idea (the water cooled steel plate) in the pathway to success, proposing to try it out for the very first time underneath the worlds biggest rocket? That feels strongly like trying to persist with a way of operating which the FAA clearly isn't happy with. SpaceX clearly didn't understand their current launch pad's resiliency, what makes them think they'll know any better with a steel plate? Why should the FAA believe them?

They've come this far; they could ruin it all. On the whole, it looks like if they can get it cleanly launched, it would at least reach orbit. If they can reach orbit, they can use it, dispose of it safely, fit it with the mother of all FTS's to make sure that it really does terminate if required. Once it's reliably safe with more relaxed FTS requirements, they can take some time to nail re-usability (remember, re-usability was an add-on to Falcon 9, added once the rocket itself was more or less working).

They don't need to innovate in launch pad design. No one buys launch pads.

Soil Mechanics

When they light up this rocket, they're creating a very intense, very localised earthquake. The way soft sandy waterlogged soil behaves in an earthquake is that it liquefies, flows, etc, starts oozing out of the ground all over the place. So, what they've probably got in the way of soil underneath the launch pad at Boca Chica at launch time is soft jelly moving all over the place. No wonder their concrete failed - it likely had nothing of value underneath it.

So, if they're assuming that their concrete pad, steel plate is going to get any support from underneath, that's likely not the case. I think to do what they're attempting, they'd need a very large stiff plate of something to spread the load out over a large area, and (more importantly) to have some way of isolating the soil underneath from the vibrations. That can be done with, say a thick bed of gravel (as is done with nuclear bunkers). Trouble is, the gravel bed would compact each launch, and the whole thing may be too heavy and sink into the sand anyway

What you likely don't want is deep-sunk stiff foundation piles conducting the vibrations downwards and acting like tuning forks stirring up the soft, sandy soil. The way such piles are sunk in the first place is using shock and/or vibration. That ought to be a clue as to how suited to extremely strong vibration environments such foundations are...

If they're going to persist with Boca Chica and no flame trench, the best thing they can do right now is hire an experienced Japanese construction engineer. They know about structures, earthquakes, and rubbish soil. If one of those folk says, "Can't be done", they'd best give up and go elsewhere where they can have a flame trench and water deluge.

Of course, the beauty of the water deluge is that, not only does it protect the rocket, it protects the structures underneath it. In absorbing shock and vibration, the foundations are protected. Better to hammer away at disposable fluid, than have something that you'd like to remain solid fluidised.

bazza Silver badge

Re: They may call it a success...

The full up, whole problem engineer everything approach is better. It doesn't even have to be slow, if you've got an experienced team. The trouble is that such teams don't exist very often, and get put together only now and then, and you have to keep them busy to keep the team together.

For example, the original Skunk Works - wartime priorities resulted in the best of the best engineers in Lockheed being lumped into a single team that persisted up to the 1980s and built such iconic aircraft as U2, A12/SR71, and the F117. U2 was done fairly quickly, the A12 wasn't too long especially considering how much stuff they had to work out. The F117 - kinda the last hurrah of the original team - took very little time and cost comparatively little money; this was most definitely not a try-it-and-see project.

NASA built a team and got man on the moon inside the decade, by knowing what it'd take to get to a point of launching a Saturn V and have it work first time.

Another - Airbus, created out of the Concorde program between Britain and France. Ok, Concorde itself wasn't a big commercial success, but the "we're working together" aspect was; that lead to the formation of Airbus, putting the best engineers from across all of Europe together. The A300 is a distant memory for a lot of people, but the successors have been wildly successful. Airbus got pretty good at maintaining this team, they (in fairly rapid order) did A320, A330/340, A380 (some development screw ups), and then A350 (perfect development) and now the A320 / 330neos (also have gone well).

SLS has had a difficult, politically influenced birth, but it has to be said that they successfully didn't blow it up several times before finally getting a near-perfect first flight of it. That team, if kept together and left to get on with it, could probably now do anything.

Unthinking iteration is all very well, but if it keeps going wrong people get worried and bored. Right now there's a bunch of SpaceX engineers who must surely know that the program has taken a distinct turn for the worse, and wondering if it's worth hanging around. The will, but it won't take too many failures (especially for "predictable" reasons like too flimsy a pad idea) for people to start looking elsewhere. Engineers are very good at knowing when projects are being managed to the detriment of achieving success..

bazza Silver badge

Re: They may call it a success...

> Agile strikes again

The frustrating thing is that I feel this is giving all engineers a bad name (Musk isn't what I'd call an engineer, not by a long shot).

We're supposed to be people who can design things, get it mostly right, have a reasonably good idea as to whether something will work or not, and have a good handle on the risks being run in a project. Ok, so there's a lot that is "unprecedented" about Starship, but what most definitely is not unprecedented is that flame trenches / water deluge systems work. They've launched this thing, and are now suffering consequences they themselves predicted (Musk's tweet from 3 years back). This is not "smart" in anyway whatsoever.

This is a problem for engineers outside of SpaceX too. Say SpaceX had a really bad accident - e.g. people in Port Isabel got hurt. That would be scandalous, and there'd be a lot of "told you so" going on. That would dampen down any other similar endeavour, as people (quite rightly) would be questioning the abilities of engineers and the government regulator to assure people are not hurt. Arguably, we're lucky that launch didn't seem to hurt anybody, even if it did make a mess, but one feels it could have been very much worse.

bazza Silver badge

Re: You beat me to it, but

The initiation of the abort was visible in the video - Scott Manley highlights it in one of his. So, the time between initiation is very publicly visible - no need to rummage through telemetry. What I don't know is if there is a second abort system on board; SM didn't seem to say so. None the less the idea of one of them having no useful immediate effect destroys the safety case.

It seems clear that there's far too many unexpected outcomes from this flight, if the FAA has called a halt. Having done so, there can only be a full up re-evaluation of the performance of all the safety-related things. For example, having lost engines on the pad, it now must be considered possible for this thing to struggle off the pad, tilt northwards, fly 5 miles and fall to earth; bye bye, Port Isabel.

Another bad thing about the flight; clearly, a lot of damage was caused on the launch pad. That likely invalidates any telemetry they have on things failing. If you're going to smash the underside of a rocket with large lumps of concrete, of course things are going to break. We know they lost engines at start, and soon after, but who can say what damage was inflicted. One could argue that with that much debris flying around and it still getting off the pad is some sort of triumph, but they'd far prefer to know the nature of the failures.

bazza Silver badge

Re: The fuse wouldn't be that long

No need to see the telemetry / command data. Scott Manley has pointed out in one of his shorts on the firing that there was 50 second delay between the termination system firing (evidenced by new leaks opening up in exactly the right places - clearly visible in the videos) and the thing eventually breaking up. That there was a substantial delay between firing and effect is not in question.

If it's going to stay intact for 50 seconds, engines still firing, it can go an awfully long way in that time. Put into the context of if having veered off course having left the pad and heading towards Port Isabel, you could expect it to arrive intact, probably under power, and still full of fuel. It'd be like delivering a small nuclear bomb into the town. Arguably, they've had a lucky escape. Certainly, if I lived in that town, and the FAA said "yeah, 50 seconds is just fine", I'd be telling them it wasn't.

The idea of flight termination is that the vehicle is disintegrated ASAP, so restrict the distance it can travel following termination. Previously, that's not been a problem; rockets are traditionally built from the flimsiest possible aluminium by the cheapest contractor. Punch a hole anywhere, and it'll fall to pieces anyway. But, if you then go and build a rocket out of 4mm thick stainless steel, it evidently does not fall to pieces immediately (it didn't even manage to set the leaking fuel on fire...).

This could be really, really bad news for SpaceX; if they have to replace the point charges they did use for the FTS with linear cutting charges wrapped around it like a fishing net to be certain of cutting it up on demand, this makes reentry very difficult. You'd not want to reenter the atmosphere with explosive cutting charges still on the outside. They'd have to be got rid of, somehow, which sounds messy. If it turns out that an effective FTS is not going to play nicely with a heavy stainless steel rocket doing atmospheric reentry, then that could invalidate the entire design ethos, which could leave them with no program.

bazza Silver badge

Re: They may call it a success...

50 seconds between button press and effect.

I'm expecting the FAA to be quite worried about that. Earlier in flight, that thing can go a long way in a dangerous direction in 50 seconds.

Florida folks dragged out of bed by false emergency texts

bazza Silver badge

Re: Big Brother has another way to cock things up.

My report is that none of my SIMless phones got it.

I'm wondering if thats because of a cell network configs. The protocols support SIMless emergency calls, but the UK configures it's cellular networks to require a SIM for such calls to cut down on hoaxes. Could be the same for the emergency broadcast (though I can't see a reason why).

BTB, Apparently to make up for the gappy emergency call coverage that arises from requiring an active SIM, a phone in the UK can use any network to place such a call.

bazza Silver badge

Re: Fancy that

It's there in case we start running out of tea supplies...

Sick of GNOME, Snap and Flatpak? You might like Linux Lite, but beware rough edges

bazza Silver badge

Oh, and the logs are nuts. It's fine to have timestamped log entries, but it's not fine for the viewing tools to assume that the timestamps are guaranteed correct, and that the as-recorded-in-files order is not.

This is bonkers because 1) how could the file order ever, ever be wrong, and 2) you try understanding SystemD's log files if your system clock ever goes wrong, or isn't there until a network has come up and ntp has done it's job whilst journalctl is sorting entries by invalid and valid timestamps? It's *worse* than useless.

bazza Silver badge

My experience of SystemD and it's view of "when is a network up?" is that it deems the job done if an interface has a link and it's assigned an IPv6 address to it. Which is ****ing bonkers, if there's IPv4 DHCP outstanding, DNS still to come figure, etc. I have to start a bunch of stuff in crontab some time after boot, because depending on SystemD is so massively unreliable. It's not like this is me not understanding what I'm doing whilst setting up stuff of my own, this is out of the box services like Samba packaged with major distros that don't work post boot because SystemD is ridiculous.

And don't get me started on start up circular dependencies. SystemD is perfectly capable of randomly failing to bring up the whole system - again with out of the box major distros stuff - because of such problems.

bazza Silver badge

Likewise, but they always seem to get themselves into a pickle...

Wrong time to weaken encryption, UK IT chartered institute tells government

bazza Silver badge

Re: It's all somebody else's fault

Pretty sure that it's not the harm, abuse and criminal behaviour that happens on the streets that is the problem. The police can in theory see that and do something about it (not as often as we wished perhaps). It's the harm, abuse and criminal behaviour that happens behind closed smartphone apps that is, with the tech firms carefully and mathematically provably looking the other way whilst it happens...

Arm liable for $8.5B SoftBank loan if IPO is a no-show

bazza Silver badge

Re: Got to love capitalism: saddle the acquisition with the debt

Does "normally" mean only the owners can, or can the subsidiary break away from the parent without the parent being able to intervene? Thnx!

The latter sounds thrilling!

Firmware is on shaky ground – let's see what it's made of

bazza Silver badge

I have used a computer that had no firmware at all. Not one byte of it.... That was a long time ago.

Firmware is just software, nothing else. The location it's stored is what prompts the name "firmware".

For a modern compute platform, it's a total nightmare getting the hardware and initial software up. Things like plug and play make it simple for users, but it requires a quite complex set of interactions between hardware and software. This complexity is what's driven the blooming of things like UEFI, and once a sufficient level of complexity was incorporated, adding useless dross like network stacks is inevitable.

It's not going to get better. The eventual architecture for computers will be a CPU with a RAM bus, and an enormous number of Ethernet lanes. PCI will probably eventually die out, because of the cost of developing two separate families of interconnect and associated switches. There's already some systems like this (fairly obscure ones). This means that Ethernet will become the only way of chattering to peripherals. With fairly significant consequences for firmware...

To improve security, consider how the aviation world stopped blaming pilots

bazza Silver badge
Coat

No Blame Culture?

I thought the software industry already had a no-blame culture. I've read some EULAs, there's absolutely no way anyone is going to accept any blame under the terms of any of them...

bazza Silver badge

Heresy today indeed! Perhaps, geopolitical necessity tomorrow. You heard it here first!

The aviation business is a very big part of the world economy, and the western version of it is too big to fail. Merging Airbus and Boeing will at some point look more like common sense than losing out to, say, China. The logical conclusion to the fight between Airbus and Boeing is that one of them will go out of business, which is bad news no matter who you are. Companies failing and merging is what's happpened repeatedly in the industry over the past 7 decades, I don't see why we should expect it to stop. Better that happens in an orderly fashion, with the West still firmly in control, than for one or both Western companies to be mortally wounded in the fight. The democratic world's politicians will have to call off the competition at some point, if the industry doesn't work that out for itself first.

bazza Silver badge

Re: Pilot Error

>Arguably the 2 737 MAX crashes were "pilot error" because they should have correctly applied the runaway trim procedure and landed the aircraft. But they didn't, and unclear instrumentation, <u>bad training</u> and bad design conspired to steer them away from the correct solution and ultimately led to them losing control of the aircraft.

I hope that, by "bad training", you're referring to the initial failure to disclose the existence of MCAS in the first place, and also to the advice given by the FAA / Boeing following the Lion Air crash. You cannot say it's "pilot error" for not knowing how to respond to an on-board system they'd not been told of, or for failing to follow a procedure that in certain circumstances was physically or intellectually impossible (or both) to follow.

As well as the failure to disclose the existence of MCAS to MAX pilots, there was also an issue in that any knowledge of the loads on the manual trim wheels had been lost to time. On the original 737 they were a lot larger and easier to turn. That was when anyone had last looked at what those loads could be. In subsequent generations of 737 the wheels remained, but they'd been reduced in diameter therefore giving pilots less mechanical advantage over the aerodynamic loads. But no one had bothered to revisit what that meant in extreme out of trim situations, because that "never happened". Then with the MAX, Boeing fitted a system that could cause extreme out of trim situations, very quickly, with no useful warning (MCAS).

Worse, they didn't even tell pilots that there was something called MCAS fitted in the first place (this was part of the "no training difference" Boeing had attempted to achieve between NG and MAX). Still no one tried out extreme out-of-trim procedures for real, and the aircraft still got certified. So, the Lion Air pilots were attempting to fix a system that their manuals didn't even mention, and with the fault they had the "book" advice was lethal (because it meant turning MCAS - broken - back on).

The advice given by the FAA / Boeing after the Lion Air crash turned out to be ill advised. The updated advise was based on try-outs in a simulator, not a real aircraft. The problem was that the sim was inaccurate, and didn't recreate the loads on the manual trim wheel. Had they tried it on a real aircraft, they would have realised that a pilot would have to have throttled back to be able to conduct the runaway trim procedure, and given more emphasis to doing that. More likely they'd have realised that, in the circumstances where a pilot was low to the ground, being told by the aircraft that "airspeed is unreliable", and experiencing strong nose-down tendancies in the controls, it would have been asking too much of a reasonable pilot to take an added risk and cut the throttles.

Afterall, low altitude + nose down trim + too little airspeed (what does "unreliable" actually mean?) + cut the throttles guarantees a crash.

It was the poor quality of the Boeing / FAA response to the Lion Air crash, evidenced by the Ethiopean crash, that lead to first the CAAC and then other global regulators grounding the MAX. It was effectively at that point that the rest of the world realised that it could no longer trust the US industrial / regulatory system, and realised they had to act independent of the US. If that isn't indication enough that the MAX crashes were not "pilot error", that there was no "correct solution" for the MAX + MCAS 1.0 failures, then I don't know what is.

bazza Silver badge

Re: Pilot Error

NTSB reports are indeed well thought out, but are in themselves often inadequate. They won't criticise their bosses.

With the MAX crashes in particular, if one asks "why?" enought times about the certification you inevitably end up at floor of both the Senate and House of Representatives, where both parties for decades have been cheerfully trimming the FAA's budget. The current crop of politicians has kinda realised that this is partly their fault (which is why the FAA has been given some teeth again). But we all know that this is, one day, going to happen again when a new batch of politicians ask "Why do we put so much money into this federal aviation agency? Crashes don't happen, cut their budget".

That, coupled with how employment and business incentivisation works in the US these days, is practically guaranteed to recreate the same conditions that lead to the MAX crashes.

I've not seen anything from the NTSB criticising the politicians, the business / political system or the way they choose fund their agencies, or the politicians' failure to ensure a proper business environment exists to support safety. Afterall, the same politicians fund the NTSB. It's quite evident that the role of US politics in the MAX crashes has been carefully not looked into.

Minimum safety standards are only enforced if the funding to do so is not controlled by politics and business, but is controlled solely by engineers who know what they're doing. Politicians hate not being in charge of the bank account, but they've got a bad track record of managing it themselves.

Boeing's Blame Culture

Meanwhile, Boeing as a manufacturer has a habit of blaming pilots. They tried it with the MAX crashes too, briefly, until it became too obvious that it was their screw up that was to blame. They're still trying to wriggle out of liability, trying to not compensate families of the victims. If they cannot corporately accept that they've screwed up, they cannot corporately adjust themselves to not screw up in the future.

The problem with Boeing and the mess they're in is that, if you follow the "why" to its conclusion, the result is that the USA is now a bad business and political environment in which to carry out such endeavours. No Boeing CEO can truly adjust how the organisation works, because the shareholders won't let them.

It's interesting to consider the control a CEO / Chair has on a company. Steve Jobs famously had a vice-like grip on what Apple did, and what it spent its money on. Despite having more money than it knew what to do with, Apple under Job's stewardship didn't really pay dividends. Jobs wanted the money for his own reasons, and had sufficient control of the company and shareholders that what he said went. However, I can't really see that kind of mangement control of a company existing anywhere in the USA these days. If a strong Boeing CEO stood up and said "right, I'm going to sort this mess out and you the shareholders are going to pay for it", they'd be out within the day. Far better for such a person to set up a privately held competitor.

I can understand why some company bosses try and take the business they work for private; better to have private owners who "get it" rather than suffer the vagaries of public ownership. It also explains why some corporate set ups have hardly any voting shares, though that's pretty unhealthy.

bazza Silver badge

Boeing / Airbus Market Share

There's a lot of too and fro in the debate about which company is doing best. However, I think the data in Wikipedia is fairly conclusive. This Table shows the aircraft actually in service across the worlds airlines. It shows that in the 14 years from 2006 to 2020, the in-service share shifted from Boeing:Airbus 2:1 to nearly 1:1. That's a huge swing in market share from Boeing to Airbus, in quite a short time (aircraft last in service a lot longer than 14 years). That's reinforced by the fact that, today, Airbus has thousands more aircraft on backlog than Boeing. Even more tellingly, what with the MAX grounding and COVID, Boeing has taken quite lengthy "delivery holidays", whilst Airbus continued to deliver at quite a high rate even during the COVID pandemic.

One of the reasons why long haul airline tickets are so expensive at the moment is because Boeing has massively under-delivered. Consequently, leased aircraft are at a premium on the rental market as aircraft that have expired their hours are grounded and have not been replaced. You can tell how badly this is affecting the market when airlines are dragging A340s out of storage and putting them back into service. Even the A380 now looks like good sense (Even Qantas have restored their entire fleet to operations).

Continued contraction for Boeing seems guaranteed, especially given that the CEO / board has said they're not really going to do anything about this by investing in new designs. The problem with this is that, with Boeing's performance continuing to be eratic, collapse seems highly likley, and probably sudden.

To Airbus, market share has been their key driver. You can make money if you have market share. You can't make money if you don't have market share. What Boeing has found is that, whilst their inefficiencies could be hidden and ignored when they had high market share, they can no longer be ignored now that Airbus has pinched a big slice of the market. A real indication of this is that Airbus, despite the commercial failure of the A380 program (as big an inefficiency as you can get) none the less managed to survive and thrive. How bad can Boeing be that they couldn't make Airbus really, really hurt with the failure of the A380?

Too Big to Fail? US Gov Military Motivation to Support Boeing?

I think you overestimate the extent to which the US gov is prepared to support Boeing. The US Military have had issues with a lot of Boeing made products of late - Apache, KC46, P8, Airforce One.

Apache - a mature, legacy programme - was inexcusable; the US Army sent a whole batch of brand new ones back because of poor quality manufacturing.

KC46 has had innumerable issues such as poor quality, it not being usable as a tanker at night, and its cargo floor clamps spontaneously letting go of cargo containers. It was and is a nightmare procurement for the USAF. Boeing used every dirty trick in the book to beat up the USAF to win the contract, and then delivered a shite aircraft.

P8 has recently stopped production because of a supplier issue.

Airforce One is very late. And, the cost of saving Boeing to the sake of future AF1's is probably more than the cost of a future bespoke design. For example, Airbus spent about $25billion creating the A380; it's going to take more than that to save Boeing. Paying Lockheed or Northtrop to do a one-off design is probably cheaper.

In short, there's not many reasons at the moment for the US Military to love Boeing.

Meanwhile, Airbus has at least one reason to be loved by the US Military, who clearly want the A330 based MRTT tanker (which is what everyone else in NATO is buying). Airbus, properly teamed up with a US prime like Lockheed or Northrop, could find its successful commercial designs being picked up by a number of US military programs.

Domestic Politics and Geopolitics

An actual Boeing collapse would be a huge issue, because all of a sudden it'll not be legally possible to fly a large fraction of the world's aircraft fleet. Certified flight operations depend on manufacturer-backed "design authority" support, which will have disappeared. That's the part that's "too big to fail".

Plus, if Boeing collapsed with thousands of aircraft still on the order books, it's not like Airbus could fill the gap quickly. That starts getting geopolitical, very quickly. The US Gov and Europe would not want a Boeing-sized hole in the commercial aircraft market filled by a Chinese State backed manufacturer. Some very strange things might happen, e.g. the US Gov asks Airbus to come in and pick up the remains of Boeing, keep plants operating, etc.

The ideal for the democratic West is that Boeing is restored to industrial, engineering and economic health. Aviation is important to the global economy, and no one in the West wants China to gain control of that aspect of it. It's therefore worthwhile pondering, how has Boeing got into this mess in the first place, to know how to fix it? It's related to how US businesses behave and are incentivised, how employment in the US works, and so forth. Boeing has chased profits and cost reduction because that's what shareholder have obliged them to do, and in doing so has accumulated vast debt, lost a ton of market share, has a poor product line up, and huge labour issues (e.g. they've just lost hundred of experienced engineers who've had to retire, due to the contract between the company and the union). You cannot permanently fix this simply by pouring money into the company. It takes wholesale reform of how business operates in the USA. That's a deeply political issue, and one that the US political system is uniquely ill equipped to address.

What's going on round the world is that everyone is looking at the USA / Boeing, to see if the US is actually going to do anything about it. They seem not to be doing anything (apart from a belated attention to certification practises). Some airlines are evidently buying Boeing partly because they're worried if they don't, Boeing CA will collapse and then there won't be any choice.

Airbus too are rumoured to be worried about a Boeing collapse; becoming a global monopoly would attract the most dreadful political heat. It's known that, in launching the A320neo family, Airbus were taking a bet that this would bump Boeing into (yet again) revamping 737. When Boeing responded with the MAX, apparently there was champagne popped open in Toulouse, because Airbus knew they could out-profit another 737 derivative. Then the MAX crashes happened.

I don't know for sure, but I strongly suspect that Airbus seniors are now a little bit worried that they might just have overdone the whole "attack Boeing's market share" thing, sowing the seeds for big problems for Airbus in the future. There is competition, and then there's deadly competition. Airbus now know that if they corner Boeing even more, there's a danger that the consequences can be fatal. It's pretty bad way to do business knowing that if you're too good at doing it, your (incompetent) competitor might end up killing people again trying to keep up. At least the FAA seems to have sharpened its regulatory teeth again, to keep things minimally safe.

One way out of this is to allow Airbus to continue to become truly vast at a high pace, to get to a point where (from everyone else's point of view) Boeing is small enough to fail, ASAP.

Another way out is for the US Gov and European Governments to realise that an alliance on commercial aviation is needed. If a global monopoly is going to be the eventual result, why not arrange that in advance and avoid the chaos? That could involve the US admitting that, "Okay Airbus, you win", but ensuring a smooth transition from Boeing making (defunct) Boeing designs to the same people in the same facilities coming under Airbus-style mangement building Airbus designs, and the whole Airbus vs Boeing thing being buried for good.

There is already precedent for this: this is exactly how Airbus got formed in the first place - an amalgamation of European aircraft manufacturers. A politically backed merger between Airbus and Boeing is no different in concept.

bazza Silver badge

Kodak - the irony being that wet film photography is becoming trendy once more. Like vinyl records. Adapt can mean, "survive", which is what Kodak have done.

Wet film photography at its very best is difficult for digital systems to beat. It remains in use in some quite important niches, as well as becoming more popular in general photography.

SpaceX calendar marked with big red circle for 'first Starship launch' this month

bazza Silver badge

Re: I can't wait.

From an outside viewer's point of view they moved from blowing up a lot of stuff to not lighting so much as a candle pretty much overnight. The context is that, a couple of Autumns ago, Musk called all hands into to office over Thanksgiving to get this engine working, and said that they'd got very narrow financial margins. He suggested the possibility of the company going under, if they didn't get it right. That fits what you've suggested - consolidating what they know into a workable solution, preferably without destructing anything.

The big question is, did they have to blow up so much stuff in the first place? My view is, no, they didn't, and it's not been necessary to do engineering development that way for a very long time. The Victorians and the Wright Brothers moved engineering and aviation from try-it-and-see to design analysis well over a hundred years ago. Learning by failing might be fun, but it's no where near as effective as learning by succeeding and understanding exactly why one did succeed. For example, Skunk Works (as was) was very ambitious, but they didn't need to crash a whole load of aeroplanes to learn how to build a good one out of titanium. They knew that, to succeed with ambition, one had to focus on process, and being good at processes / the paperwork. Skunk Works moved fast, but didn't break things. They moved fast, and made things work first time, and could be trusted to do the paperwork with no oversight.

To succeed long term, SpaceX needs to assemble and mature a team so that they can make a thing work first time, like everyone else (more or less) does. SpaceX's working conditions are said to be very high pressure, and I suspect that they find it hard to recruit / retain the very best engineers who can help them with that. Regardless of ambition, if one relies of getting it wrong a lot, you're going to get out-competed by someone else with the same level of ambition who can get it right first time.

Where Musk might just have got it right is that for something like this there may be only "one time". There's probably not the market to support 2 megaconstellations, and being hoplessly ineffecient with building the first one might not matter, so long as it is the first (and only) one. However, if someone else does build a second one, and is more efficient at doing so, StarLink might survive for only one generation.

Having said that, so much of what SpaceX are doing with StarShip / StarLink / Superheavy feels like a solution looking for a problem, rather than the other way round. StarLink makes only marginal commercial sense (it can, thanks to the weird politics of the USA / lobbying / existing telco monopolies, make money in the USA). Sure, they've got a team who are indeed learning the realities of plugging 33 engines underneath a single booster, and the aero / thermodynmics of a large stainless steel vehicle belly flopping into the atmosphere. They may also learn that commercial realities are an unignorable aspect of engineering solution and design analysis. The wisest and most valuable engineer is the one who asks, "why is this the right thing to build?".

For example, there were engineers in Boeing who were in utter disbelief that Boeing yet again were to revamp the 737 into the 737MAX. Had they been listened to Boeing would have launched a whole new aircraft instead, probably avoided the Lion Air and Ethiopean Air crashs and the vast costs / delays associated with that poor management decision. Musk strikes me as the kind of person who won't have anyone in the company who asks awkward questions about his favourite solutions, and is no different to Boeing's management in that regard.

bazza Silver badge

Re: I can't wait.

>By that, I mean validates a lot of the design & construction ideas.

One of SpaceX's traditional problems is that it doesn't. For a flight test to validate design parameters, you first have to understand what the design parameters are to measure and confirm.

Musk's approach of build and launch on a rapid tempo, who cares if it blows up is an attempt to achieve reliability without all that design analysis, quality control paperwork. It didn't work - Falcon 9 had schoolboy QC errors in its early iterations.

One classic example was the struts holding a He tank in place. They were not QCing these struts, and a tank came loose and the booster was lost. Because they'd done no QC on the struts they'd no idea how strong they were, except that they weren't strong enough. Post mortem QC of struts in sock revealed significant variation, due to poor material quality.

It wasn't until NASA got involved for human rating it and said that the paperwork was compulsory, after which Falcon 9 became reliable. NASA basically said that reliability achieved by random iteration was not good enough for crewed flight, because you've no idea what the safety margins are or when they'll turn out to be too narrow. You have to have a full up analysis of the organisation building it, the design, and measured confirmation of the margins.

Effectively SpaceX learned the stupid way what anyone else already knew, which was that design analysis and QC really, really matters. What matter most to SpaceX now that Falcon9 has settled into a tempo is audit of their QC, to make sure it's still being done right...

The same was happening on Starship / Superheavy, but then somehow Musk got levered aside and they've spent a solid year or so catching up, not launching anything, being far more cautious.

Starlink opens final frontier for radio astronomers

bazza Silver badge

Re: Sorry but no.

The permanent problem all satcomms has had for decades now is that cellular coverage reaches a very high proportion of the human population already, and it continues to improve at pace. The Chinese companies in particular have been laying fibre under oceans and erecting base stations everywhere.

Satcomms is not an answer for the majority, it needs a niche.

Starlink's niche is the US domestic market where, thanks to some very monopolistic practices by the establishment telcos, there is a large market of monied and willing customers looking for an alternative. Starlink is already "essential" to a lot of people in the states. When you do the numbers you can see that SpaceX could make a ton of money from a relatively small portion of the US market. The rest of the world is just a bonus...

DoD taps Apple exec to lead commercial tech adoption unit

bazza Silver badge

History Lesson

It's interesting to consider the extent of adoption of commercial technology that already exists.

Firts and foremost, a lot of today's commercial standards owe their longevity and success to the DoD. Posix was strongly driven by DoD, which helped *nix OSes win over things like VMS. VME is another, still going strong after all these years, and has evolved into OpenVPX. And, let us not forget the role of DARPA in the development of the Internet (DARPAnet).

Secondly, an awful lot of electronics in defense applications is entirely commercial components. It's been a very long time since anyone manufactured components specifically for military environments. So, mil-spec these days is largely about packaging to look after commercial parts.

Thirdly, a good armed services person is always on the lookout for stuff that makes their jobs better, easier, whether it's better boots, drones. Improvisation brings a military advantage, always has done. The most important thing is probably to facilitate that, not manage / direct it.

The thing that is often overlooked when considering commercial tech for military applications is that sometimes it's far more dangerous than it is useful. Eg a drone, bought off the shelf. Great toy, wonderful real time imagery, a useful capability. But, it's phoning home to China, because that's where the app came from, and the position of an entire regiment is compromised.

Half the battle these days is probably stopping the adoption of commercial tech that comes with traits that, commercially, are merely a privacy concern waived through on the back of an EULA, but in a military context could prove to be catastrophic. It's a bad idea to have a mobile phone for example, or an AirTag.

So that's going to be the challenge. The commercial norms of always connected data acquisition that Apple has help foster are the very thing that makes commercial tech dangerous to our war fighters.

Ubuntu 23.04 'Lunar Lobster' beta is here in all its glitchy glory

bazza Silver badge

Re: Wayland?

I've mixed feelings on the topic of X11 forwarding.

On one hand, getting an X11 connection via a pipe, socket, etc is absolutely fantastic, it works very well, suits almost all purposes. And the really good thing is that the quality of the display is "perfect", provided your X server is well set up with the right fonts, etc.

The other approach to remote GUIs - followed by things like Microsoft's RDP - is to forward the whole frame buffer, like a streamed video. I am predisposed against this approach because the quality of the end result is often inferior (compression artefacts, etc). However, the big advantage is (if done properly) that if you've got high frame rate whole frame changes going on a lot, on a slow connection it will (when all the frame changes have stopped) settle down quickly, instead of having to receive absolutely everything and draw it all.

But that's a comparatively rare need these days; high bandwidth connections are commonplace, and any gamer is likely on Windows, X box or PlayStation anyway.

Given that connections these days are generally pretty good, I'd say there was more value than previously in X11 (or an X11 style approach).

High Bandwidth

Looking to the future, one has to ask where we're headed with things like PCIe, Ethernet, etc. Fabrics likes these are now very expensive to develop; loads have dropped out, things like Serial RapidIO cannot compete any longer because the cost to developer the "next chip" is so high. There is a possibility that, one day, the only interconnect we'll have is Ethernet.

Which then begs an interesting question. If the innards of a computer are essentially going to become just a network of components, with IP addresses, etc, that'd mean that down at the electronic level graphics would be client-server, just like X-11 already is.

bazza Silver badge

Re: Wayland?

The problem with Wayland's simplicity is that it pushes the complex problem of things like accessibility out to the app developer...

Italy bans ChatGPT for 'unlawful collection of personal data'

bazza Silver badge
Thumb Up

Re: Err, wot?

Absolutely this.

There's a lot of hand wringing going on along the lines of "think of the lawyers!", calls for new laws, etc. However, mostly, it's already covered. GDPR is just one example, and (so far as I know) there's nothing in GDPR that explicitly restricts it to ordinary IT systems.

My favourite pet hate is the debate about the ethics of self driving cars that find themselves in a kill person A or kill person B situation. The question that gets asked, is, how should a car choose? The actual answer of course is that, if the car had got itself into a situation whereupon a fatality was inevitable, then it had already failed by not having anticipated the potential for such a situation to arise. At least here in the UK, a human involved in such an accident is likely to be found to have been driving inappropriately for the conditions of the road, and guilty of causing death by reckless driving.

We've already seen articles about racist recruitment AIs used by hiring departments. Well, there's laws about racial discrimination in most civilised countries, and a company using a racist AI to hire staff is just as guilty under such laws as if it had been the work of its staff. I think what's interesting is that there is actually a useful role for a racist hiring AI. Instead of using it to make decisions, use it to review decisions. If the decisions of the human hiring staff are found to be matching those of a known-racist AI, then that's a useful warning sign to the company that it's getting things wrong and needs to fix them.

It's going to be the same with things like copyright law. If ChatGPT plagarised someone else's copyright material, then the company running that instance of ChatGPT has broken copyright law in someway or other and should face the consequences. Though this perhaps is an example of where a specific AI regulating law might serve a useful role. Plagarism conducted by humans is a problem, but, generally, one knows who the human is and in principal a court case can be brought and a decision made. The problem with something like ChatGPT is that this could happen on a far larger, switfter, even more opaque scale. So, providing a service like this could be regulated by law and required to always cite its sources, so that it becomes a lot easier for copyright holders to assert breaches of copyright. It would also alert other service users that, if they proceed, they themselves might be unwittingly breaching someone else's copyright. It should not be possible in court in a copyright case to sustain a defence of "ChatGPT told me"...

Gone in 120 seconds: Tesla Model 3 child's play for hackers

bazza Silver badge

Re: $250b? Easy!

Perhaps he's planning on floating Twitter on the Zimbabwe stick market, in Zimbabwe dollars (that started off on a par with the US dollar, in 1980, and by the time it was all over in 2009 it had been rebaselined so that 1 "fourth" dollar was 10^25 of the original). Perhaps Musk has been inspired, and is doing the same with Twitter...

French parliament says oui to AI surveillance for 2024 Paris Olympics

bazza Silver badge

At least they have a way for something to happen, for someone to rule. In the USA they often have a situation where no one can do anything, even if it has become important to do something.

bazza Silver badge

He was probably also counting on the opposition not actually want to win the job either. It's a pretty comfortable thing being an opposition leader, most of the perks, none of the responsibility.

Actually becoming responsible for the running of the country? Who'd want that?

bazza Silver badge

Re: The Olympics have always been a political joke and a waste of time

Wow, that's news to me. I remember that a huge number of people went to Sydney, and they hadn't had much trouble building whatever venues were needed. It was said at the time (probably without being definitive) that it had been profitable. Maybe the cost overrun was balanced by a huge turn out of overseas visitors.

The influence of the IOC is pretty stinky I think. The design of venues gave that away in London. The IOC wants venues to have large amounts of seating so that a large crowd can be got in to make the event appear to be thrilling, boosting the TV audience.

That means that the hosting city's existing swimming pool or whatever doesn't meet the spec so they have to build a new one, which is never going to see a large audience ever again. Waste of money.

What London did was make the seating a temporary addition to a new building, took it down afterwards, leaving the sports facility without all that never to be used again seating. Saved a fair bit of cost, freed up the land for something else.

I wonder what's going on with the Paris Olympics. If they're having to build a new velodrome, that could be tricky. The wood for the track itself comes from only Russia...

I think that eventually, the Olympics will run out of steam. No one will want to host them.

bazza Silver badge

Re: The Olympics have always been a political joke and a waste of time

Quite often its politicians that want it, and the IOC is dead keen on countries spending vast sums in self-engrandisement projects to boost their TV revenue. It's not an ideal venue for "sports" to actually occur. Some events, one wonders if one is simply looking at the results of various government chemistry labs more than anything else.

Very few countries have got the Olympics "right". Sydney, Australia did - made a profit. London 2012 is probably at least cash-neutral, with fairly well controlled costs. Japan 2020 could have been OK, but got ruined by Covid (they built whole new motorways and moved fish markets in Tokyo to cope with the traffic that never came...). Most other places it's been a big waste of public expenditure.

bazza Silver badge

Re: Relax citizen

As ever, it'll all depend on exactly what they do with it. If it's used lazily, as a substitute for actual "thinking", there will definitely be problems. If it's used intelligently, well, maybe there'll be some small benefit (at most).

As always, it's how well do these things get set up. There's a fundamental contradiction in the requirements for things like this. First, it mustn't over react when it shouldn't. Second, it must react well enough when it should. There is no happy middle ground, because no one knows where that is. This sort of contradiction has been the bane of all such systems for a long time (including biometric systems, which are also generally making decisions with fuzzily ambiguous data). It takes human intervention to resolve, and if that's biased (ie. "I believe this snake oil"), then you've got judicial enquiries looming on the horizon...

Apple bags patent for folding phone that closes as it's dropped

bazza Silver badge

Sapphire glass?

Years ago Apple were thinking of cladding their phones in sapphire glass. They didn't, bankrupting the manufacturer (who'd already tooled up to be able to produce), because they realised that indestructible iPhones would not be profitable.

However, I remember a YouTuber got hold of a prototype, and it was remarkably tough, and could be bent unbelievably without breaking.

It was a bit stiff for a flexible display, but that's just a matter of how thin it is. So perhaps ultra thin sapphire is the answer for folding phones. It'd probably only break if it landed awkwardly on a diamond. Pity if that happened, but then you've got yourself a diamond!

Dual Tesla lawsuits pull Elon Musk into right-to-repair war

bazza Silver badge

The Model S got revised recently, didn't it? So that would make it their newest model.

bazza Silver badge

Re: About time

And as Toyotas don't ever break, the spares issue never arises!

The US would sooner see TSMC fabs burn than let China have them

bazza Silver badge

Re: Foresight

Are you seriously suggesting that the US should "force" a company and people from another democratic nation to move to the US and become US citizens?

China debuts bonkers hybrid electric trolley-truck

bazza Silver badge

Funnily enough the city of Nancy in France has just ditched its trolley bus / tram things. Effectively a trolley bus that's guided by a single rail for in town sections of the route. Plus, because the depot is no where near the route it runs they've also got a diesel engine.

Wierd combination, actually serves some needs very well (good on hills, good for accessibility in town because it can get close to a platform, good for emissions). Its uniquenes was its downfall.

And now the Chinese have come up with something not dissimilar. We could see a return to the streets of Nancy yet!

Check out Codon: A Python compiler if you have a need for C/C++ speed

bazza Silver badge

It's nice when your program goes, "Yeah, and? Try harder next time!" :-)

I once revolutionised an entire department (this was back in the early 1990s, when even PCs were still a fairly new concept). A lot of the work relied on a "fast Fourier transform" routine, written in Turbo Pascal (those were the days). My "revolution" was to replace this with C code, but also to actually implement an FFT because the original Pascal in fact implemented a discrete Fourier transform (which is considerably slower!), and no one had realised.