Re: Sounds familiar
Yeah, but they didn't have blockchain did they?
Rookie mistake, that.
920 posts • joined 3 Apr 2007
And you'll still find the odd one or two lurking in the darker corners of some recording studios.
If you're really lucky, they might still be in working order, too.
Ah, those were the days - couldn't afford Cubase, and none of the 'usual suspects' were able to get me a cracked copy, so I wrote myself a MIDI sequencer as a way of learning 68000 assembler.
I wish I still had that degree of drive and curiosity - sadly, working as a developer for 20-odd years has pretty much beaten it out of me.
why the UK can't just reuse this code is unclear
As others have pointed out, a bad case of NIH syndrome and Brexit.
After all, as a Proud Independent Seafaring State[tm] whose governing class appear to prefer ideology over reality, we can't go using the same stuff as those filthy forriners, can we? On top of that, it means that we can't give the job to our mates without going through all that tedious competitive tender stuff.
Taking back control, innit?
That is/was closer to the truth than you can possibly imagine ...
Back then, the principal question seemed to be "how can we mitigate quantum effects?" whereas now, as noted upthread, there seems to be a split between "how can we mitigate quantum effects?" and "how can we make quantum effects work in our favour?" - as node sizes shrink, these questions, and their answers, become rather more important.
Of course, we all know that the real answer is "you never know until you look" ;-)
Maybe so, but the laws of physics are a harsh mistress and they don't give a rat's ass how good your competition is or how well they're doing.
It's been a long time since I worked in the semiconductor industry, but even then people were chewing over the practicalities and problems associated with sub-10nm nodes - once you start getting down to atomic scale there are some very real problems to overcome.
Memory is fuzzy, but 'state of the art' back then (early 2000s) was 65nm and the transition to 45nm was starting to gather pace, as was the use of 300mm wafers to increase yield - 10nm was still a way off, but it was still weighing on the minds of people far smarter than me.
Whilst I loathe and detest the fact that Microsoft-era BillG (and his successor, Monkey-boy Ballmer) got insanely rich by pushing sub-standard products, there's no denying that since stepping down from MS, Bill has put a fuck-ton of money into healthcare initiatives and the like, and it's not just Bezos style 'tax dodge disguised as charity work' lip-service, either.
I don't have to like the guy (I don't, see above) but respect is most definitely due for his charitable efforts.
Its British Gas. I never expected less, and am surprised that there is not more.
Oh there is, soooo much more - you have no idea. Their website is a clusterfuck of epic precautions - the login process is painful enough and it just gets worse from there.
The British Gas website pretty much sums up everything that is wrong with modern software 'development', to whit: spaghetti coding: chuck stuff at the wall and keep the stuff that sticks, irrespective of whether it works or not[*].
Is $FRAMEWORK or $METHODOLOGY new and shiny? If so, crowbar it in there and fuck the consequences - form triumphs over function eleven times out of ten.
Why pay for QA/testing when your long-suffering customers will do all of that for free.
[*] - I would say that the Hive website was the Ur-example of this, but it seems to have settled down a bit of late, both in terms of 'style' and stability.
It's all just ones and zeroes. If it isn't a one then it's a zero. How hard can that be?
Getting the ones and zeroes is the easy bit ... it's putting them together in the right order that's the trick.
As the late, great Eric Morecambe once said: I'm playing all the right notes, just not necessarily in the right order ...
Linus' potty mouth notwithstanding, let's not forget that some of this shit is hard - my last tussle with the kernel was way back in the 2.mumble days where I had to write a couple of drivers for some hardware in my lab - my C chops were a lot better back then but even so, hacking on the kernel was not for the faint of heart (one bit of hardware was sorta-kinda supported, which made life a bit easier, but the other wasn't so I had to work from datasheets and whatnot and write everything from scratch) - still gives me nightmares.
You want documentation? Well, there's the code itself ... other than that, good luck!
I probably wouldn't even know where to start now.
There's also the 'some of this stuff is boring' aspect - whilst you'll probably have no shortage of people queuing up to work on the latest shiny shiny or the $ARCHITECTURE_DU_JOUR, there's no escaping the fact that the 'boring' stuff in the kernel will need occasional care and feeding as well, and that's not as sexy by half and people will be less inclined to do anything once the current maintainers have moved on[*]
[*] - I'm one of those developers who actually enjoys working on the 'boring' stuff. It's a dirty job, but someone's gotta do it ...
It's a bit of a running joke round here, but:
- The Audi logo is referred to as "The Olympic Rings Of Twattery",
- Audi itself is an acronym for "A Useless Driver Inside"
- BMW actually stands for "Bloody Minded Wanker" (or, as a German-speaking colleague of mine had it, "Bayerische MistWagen")
(and another wag pointed out that the Porsche Cayenne is proof that Germans do actually have a sense of humour)
White Audi TTs in particular are filed under "things to run away from very fast" since they always seem to be driven by hairdressers with the spatial awareness of a goldfish and the IQ of a can of soup.
BMW and Audi do make some very nice cars, but the image is tainted by some of the idiots who drive them. Much the same could be said about Apple products ...
TBH, I'd rather have the folks working at $WHEREVER slaving[*] away developing code which works rather than sitting in healing circles wringing their hands about whether or not someone, somewhere will be offended by what has been written.
Y'know what? I don't give a flying fuck at a rolling doughnut whether your code uses 'master/slave', 'parent/child' or 'this/that' - as long as it works, I don't care. I really don't. If you must insist on this new-age, touchy-feely, snowflake bullshit then please, keep it to yourselves - or failing that, you can look through some of my code: the terminology used therein would probably make your fragile little heads explode.
[*] - yeah, I used 'slaving'. Downvote away ...
(of course, it should be BEEEEELLLLION dollars, but you get the general idea)
Giving credence to such ideas merely reinforces them, and contributes to an atmosphere where gullible rubes set fire to 4G antennas, because they're too fucking stupid to know the difference.
And therein lies the nub of the problem (emphasis mine) ... these are the same fools who are lauding Spaffer and Hancockup as saviours of the NHS despite plenty of evidence to the contrary.
George Carlin was right ... if my code scaled as well as stupidity appears to then I'd be happy indeed.
I think he really is an Employee of MicroSoft in disguise ... or a total asshat .....
The former would be difficult to prove.
The latter .... not so much.
He's the new millennium's answer to Joerg Schilling (if you don't know who he is then look him up - Poettering clearly took asshattery lessons from him)
And yeah, PulseAudio is an absolute fucking abomination.
Biting the hand that feeds IT © 1998–2020