The main problem with “fairly unique”, “almost unique” etc. is that there are perfectly good and less mangled alternatives - like RARE, for example.
752 posts • joined 29 Nov 2006
Hipster whines at tech mag for using his pic to imply hipsters look the same, discovers pic was of an entirely different hipster
Three-quarters of crucial border IT systems at risk of failure? Bah, it's not like Brexit is *looks at watch* err... next month
Linus Torvalds pulls pin, tosses in grenade: x86 won, forget about Arm in server CPUs, says Linux kernel supremo
Re: Well currently the problem with ARM is not the CPU
> They [ARM] also give out very little information on the chip's insides
> (if you can work out WTF it actually is), where as both Intel and AMD
> publish schematics
Ha ha ha ha - Intel publishing schematics of the inside of their chips??? What palnet are you on!!!!!!
Re: Well currently the problem with ARM is not the CPU
> every SoC is completely different
This is much less true of the “server” ARM processors than the SoCs that you find on “pi”-type boards. The “server” systems generally are self-describing via PCI descriptors and ACPI, like x86, and come with UEFI, so you should be able to boot then all from the same OS installation media.
Of course there are plenty of rough edges. But if your experience is primarily with “pi”-like boards with chips repurposed from tablets etc., then be aware that the “arm server” space is better organised.
> If you aren't developing the apps on the same kind of
> machine your users are on, test it on the same kind
> before rolling it out.
That’s obvioisly true, but in the context of the article the difference between Windows and Linux is much greater than the difference between Linux/x86 and Linux/ARM64.
Unearthed emails could be smoking gun in epic GDPR battle: Google, adtech giants 'know they break Euro privacy law'
In our family, after my Dad spent a week in the garage trying to remove the cylinder head of a Triumph Dolomite following Haynes’ instructions, the phrase “Removing the studs should present no difficulty” became a euphamism for any seemingly-easy task that would end up taking longer than expected.
First they came for Equifax and we did nothing because America. Now they are coming for back-end systems and we're...
I’d love to see some examples of cases where he says the tool gets the wrong answer.
I had a play with the site a while ago, after one of the stories here, and it basically seemed to do the right thing for “obvious” cases.
I think the “testing” issue is a red herring. I doubt that something as simple as this would not be doing what it was supposed to do. It’s just a website that asks questions and does no more than about 10 lines of logic to work out the answer. It seems more likely to me that this Chris Chaplin has entered details of somewhat borderline cases where he disagrees with HMRC about what the outcome should be, and predictably the tool has told him what HMRC thinks, not what he thinks.
Re: small memory footprint in devices
> the libraries just won't fit on the devices, and the algorithms are likely to run too slowly anyway
These devices do WiFi, and the WiFi link needs something like AES. If the hardware is capable of doing that, plus all the protocol gubbins for DHCP, DNS etc. etc. then also encrypting the payload is a small additional overhead.
Amid polar vortex... Honeywell gets frosty reception after remote smart thermostat tech freezes up for a week
Intel to finally scatter remaining ashes of Itanium to the wind in 2021: Final call for doomed server CPU line
To me, in the 90s, it looked like Intel knew x86 was crap and needed replacing, but they couldn’t bring themselves to replace it with a RISC-ish architecture like everyone else was gravitating to. (That would be admitting defeat.). So they chose this VLIW design, which relied on some extrapolation of where compiler technology might go. But that didn’t happen.
I’m surprised it lasted as far as shipping products, let alone for 20 years of shipping products. There mist have been some very profitable locked-in customers somewhere. I don’t think that would happen today.
> Developers of iOS apps have no way to distribute unvetted apps apart
> from releasing app code as open source so other iOS developers can
> build and install such projects on their own gear
That’s not true; if you’re going to get users to build-and-install it themselves i.e. from XCode over USB, the starting point doesn’t have to be source code; it can be compiled object files in a library.
Forget snowmageddon, it's dropageddon in Azure SQL world: Microsoft accidentally deletes customer DBs
iPhone price cuts are coming, teases Apple CEO. *Bring-bring* Hello, Apple UK? It's El Reg. You free to chat?
> Almost half of it is accounted for by Direct to Home broadcasting.
> Actual space manufacturing brought in £1.9bn
Are you saying that the headline number includes manufacturing satellite TV receiver dishes?
Or that it includes what people pay for their sky subscriptions?
Or just that it includes manufacturing TV broadcast satellites?
Apple: Trust us, we've patented parts of Swift, and thus chunks of other programming languages, for your own good
Re: booby trapped
I think the idea of the Apache license wording is that that is only the case if Apple infringes a patent you hold that is for something in swift, not some arbitrary other subject.
But this is a complex subject, so it may come down to who has the better lawyers.
(Though fundamentally, if Apple sues you or me then they automatically have better lawyers and deeper pockets, so you might as well just roll over straight away.)
As for swift: I’ll be sticking with C++ thanks.
Whats(goes)App must come down... World in shock as Zuck decides to intertwine Facebook, Instagram, WhatsApp
Re: Got the email, fixed it
> Debian stable
Yes, I also run Debian stable and got the email, so upgraded certbot to the version in backports (0.25 to 0.28 I think). But I’m not entirely confident that it has fixed the problem, i.e. that it will now use a different method, because I don’t have any certs that will expire before the Feb cut-off. An earlier email would have helped I guess. Are you confident that simply upgrading certbot to the backports version is sufficient to fix it, without e.g. any config changes?
Interesting story on the BBC anout how quite large numbers of people have been bought these tests as presents because they were interested in their family history, and then discovered their parents weren’t who they thought they were. Cue very elderly parents who thought they’d take their secret to the grave getting a nasty surprise.
Great, you've moved your website or app to HTTPS. How do you test it? Here's a tool to make local TLS certs painless
> AWS has to assume there will be hostile software running on their machines
AWS has an option for “exclusive tenancy”, i.e. you are the only user on that physical multi-core CPU. Of course you have to pay for all the cores, but I don’t think it is otherwise more expensive than “shared tenancy”. If you’re dealing with sensitive information - for some definition of “sensitive” - then this is what you should be using and at least many of these problems go away.
It's beginning to look a lot like multi-threaded CPUs, everywhere you go... Arm teases SMT Cortex-A65AE car brains
I thought the idea of “hyperthreading” was that you could swap from one thread to the other much more quickly once there were two program counters etc. in hardware, rather than having to context switch via the kernel, so you can switch to the other thread when you have a branch misprediction or cache miss.
Now that we care about one thread snooping on another’s branch predictor and cache behaviour for security reasons, things get more complicated. On one hand, a snooping thread that’s hyperthreaded on the same core is in a better position to snoop than one that is more decoupled. On the other hand, having hyperthreading means that you can get away with a worse (and hence more secure) branch predictor, since the core will be kept busy after mispredictions by the other thread - assuming that there is work for another thread to do. I’m curious to know if Arm have any security motivation for announcing this now.
Qualcomm axes staff, winds down data center processor efforts ... while China takes the blueprints and runs
Meanwhile, AWS actually launched their ARM servers and anyone can use them.
I would really love to know what the uptake is like, but since the announcement there has been almost no news anywhere (good or bad). For example, searching the AWS developer forum for “ARM” finds nothing.
Re: Missing item
Yes, I’ve had “support” incidents where they send an email on Friday and if I’ve not replied to it by Monday they just close the case as “resolved”. Bastards.
The other end of the spectrum is a few open source projects where I get Bugzilla emails for things I filed 17 years ago.
I thought it would be cool to have a ‘scope with a network port so that I could print screenshots to a networked printer.
Then I actually tried to do it. It was a nightmare to set up, not least because the thing didn’t have a qwerty keyboard.
So I unplugged the network and took pictures of the screen with my phone.