No doubt it could be, though it would unfortunately make very little use of the facilities of the A77.
11 posts • joined 2 Oct 2013
Removing the rose-tinted spectacles for just a moment, RISC OS is - quite frankly - a complete mess. Still hosted in CVS. Poor documentation. (Currently) closed source development tools (IIRC). Major parts of it still sitting in 32-bit ARM assembly. Scant hardware support. No virtual memory. No multi-core support. No 64-bit support.
Don't get me wrong. I'm every bit as nostalgic as the next Acorn person, believe you me. I'd like to see this spark fresh interest into what was (30 years ago) a really nice bit of kit. But there's a SHED load of work to do on this thing, if it's going to get any traction, and there's no immediate vision of where it's going. And given the state it's in, it's somewhat unattractive to developers who might otherwise find themselves interested in kernel/OS development in this day and age.
I'd be far more interested to see Carmack take the stand. Not only is he the central figure in this, but from what I have seen of him, he is intelligent, lucid and very much able to speak for himself.
Plus of course if it all fails he can presumably whip out a BFG and destroy all the lawyers in the room...
TalkTalk plays 'no legal obligation' card on encryption – fails to think of the children (read: its customers)
Dido Harding goes on record stating two interesting things: firstly, that their security is apparently "head and shoulders" above competitors. Secondly, that TalkTalk will be transparent with customers. It would be useful to understand how she is in a position to articulate the former, and also useful to know how - exactly - TalkTalk will achieve the latter.
Unfortunately, for all her appearances, it is fast becoming more useful to consider the things that Dido Harding ISN'T saying right now, rather than what she IS saying.
Has El Reg nabbed any TalkTalk insiders who are able and willing to give a clearer technical understanding of how this latest one happened?
Updates? If only we could get that far...
A family member's machine updated to Windows 10 last night (the family member in question accepted it like every other update they generally accept that Windows Update throws at them). Their machine is now completely bricked.
Which bit of this strategy from Microsoft - particularly given their track record - was EVER meant to be a good idea?