Re: Quite ironic
AND it doesn't take account of altitude... from a 22nd storey window though, that degree of accuracy rapidly becomes redundant. As, indeed, does a first aid certificate.
9611 publicly visible posts • joined 11 Sep 2009
Not quite sure why the thumbs down. I was responding to the assertion that sealing (a phone/device) makes it harder to repair rather than waterproof, which is marketing hype for why it must be sealed.
It's not purely that it makes it harder to repair - with all other things being equal i.e. it has an equivalent IP rating, by sealing the case rather than compartmentalising the device so it has a removable battery pack (each compartment also having an IP rating), it saves on the thickness of the compartment walls, thereby making the device thinner. Though it's been many years since I was out on boats regularly and going snorkelling (never done SCUBA diving), I am fairly certain that whilst there is a whole host of waterproof devices with interchangeable batteries, the only IP68 device that's going to be just 8mm thick is one of those Pro-slate things that doesn't have batteries!
Not that you'd take an iPhone 14 snorkelling let alone SCUBA diving... just saying. That kind of kit achieves swappability of batteries etc at the expense of being a bit bulkier than your market would stand for. Thinness sold at one point. Still does really, with the roll up phone being apparently an industry goal.
If you gave the job to Derek Meddings, the wings would be at one end of the airfield being refuelled and so on, the engines would be at the side of the airfield being sent out from the service and test hangar, the luggage would be loaded into a module that comes up from an underground railway at the end of the runway and the passengers would board into two bus-like hemi-structures at the side of the airport terminal, which fold together to form the aircraft body. The various components would then be assembled out at the end of the runway where there's plenty of room a few seconds prior to take off!
The only bit of this that I'll agree with is that "Net Zero" and "Carbon Reduction" have become politicised and that it's mankind/society as we know it that's screwed. The planet is indeed likely to 'auto-correct' and it's only microbes, simple plant-like life and cockroaches likely to survive.
Climate Change is the new moniker for Global Warming because a lot of people misunderstood what Global Warming referred to - it was a bit too physics... Warmth having been used as a semantic equivalent to Thermal Energy. Thermal Energy that translates in part to Kinetic Energy within the atmospheric shell, which results in increased atmospheric churn and thus change in the climate. CO2 has been fingered as ONE of the greenhouse gasses responsible for holding that thermal energy caught by the ground, but there are others, such as water vapour and gaseous hydrocarbons.
Let's be fair... if a rise in CO2 in the order of a fraction of a part per million can produce such dramatic effects as have been observed, then it's very worrying indeed! As for the targets being pointless... they do seem rather arbitrary, having been set by what's realistically achievable with effort rather than on the basis of what's realistically going to be effective.
Ah, I wasn't saying not to have the shorter term, just that you have to transition to it in a reasonable way.
The problem as I see it is that the big players have so much weight in the lobbies that they'd kibosh any attempt to introduce a shorter, standard, copyright term. Even if they failed to do that, then they'd still find a way around it somehow.
And you also have to find a way to grandfather the rights existing code enjoys which is reasonable and fair - you can't just curtail existing rights. If you tried to do that then the short period would only be applicable to everything in 90 years or whenever - far too late to help today. And then you get into the issue of what exactly *IS* code / software... you can't apply this to other creative outputs, for example art, music, literature... you still need to have the existing protections for those.
You have to look at the rationale for having copyright protection in the first place. To my mind that seems to be protecting the monetisation and use/abuse of the results of intellectual activity.
I think the simple answer really is that it should receive the default protection for only 20 years UNLESS it is registered on a some public register rather like the patents office.
If you're bothered by the copyright expiring then register to extend the protection for another 20 years; if you aren't bothered then fine, it's an orphan / abandon-ware.
Of course there would have to be some transitional arrangement... and protection against abuse by copyright-trolls... maybe a right to re-assert held by the originator or the originator's estate which expires after a certain period to match the existing law, until it passes beyond the date where a work could have been protected under the old rules, and no extension beyond the existing legislation.
The same could actually apply for EVERYTHING copyright, actually. There's lots of stuff around which is effectively abandonware because no-one enforces it. This gives a bit more of a legal status to such things.
of this being a far cheaper and higher resolution eye-tracking system for research... until I read on. Unless the app can get the full flow of data from the eye sensors when it's running "full screen" mode, as it were, then it's going to be useless for that.
Does it also have a camera built in, so it can correlate gaze with stuff you're looking at IRL? That would be useful for all kinds of things - for example the fooking stupid new displays they've put in railway stations that put the two most useful pieces of information, when the next train departs and what time it is now, about 60 feet away from each other so you have to play hunt the data when you're potentially in a rush.
I can see a lot of labs would buy this just to see if it can do that job. Even if their subjects would then look like some kind of reboot real life film version of Bender.
because the mains in our building is exceptionally dirty. The laboratory device worked fine when used with a laptop, but not with a micro PC from Dell. The engineer couldn't figure it, so left the laptop used to set it up just to keep us going - job done for him. But then the laptop needed to be plugged in to charge. The machine didn't work. USB was loading and dropping device drivers like crazy. So I had a brainwave and dragged a spare UPS in from another room. The micro PC worked fine when on the UPS battery. The more expensive hubs and cables have through grounding, which created a ground loop. The cheap and nasty one didn't - route the USB through that and it was all good, and I could return the UPS to the job it was intended for.
iMessage is great. Like many Apple applications it integrates different accounts from many different service providers and several different technologies into a single portal relevant to the function. For example if calls come in via the voice network, or FaceTime or Teams or Zoom, then they appear in the calls list in the one application. If you get a message by SMS, it appears in the Messages app in Green, same as if it pops up in blue it's sorted out automatically that the sender has an iOS device and shifted the conversation from SMS to Internet with all the associated extensions to the capabilities. What's App requires that both ends have the same application and uses proprietary standards. I end up using a combination of Messages and What's App for some people, Messages and Telegram for others, Messages and Signal, We Chat, KiK etc... it's a nightmare remembering who uses what, BUT it means that FaceBook ISN'T dominating the instant messaging market.
Basically there's two ways to look at this... every machine is going to need some kind of period of time for recovery (excepting maybe a Commodore 64, which you can measure in microseconds), and the question is WHEN do you put in the time... do you have an overly elaborate shut down procedure which puts everything into the right state and the right position ready for powering on, OR do you have an overly elaborate start up procedure?
I needed to power off our S3 storage due to extended electrical works which were going to take out both of the supplies (there's ALWAYS a single point of failure, somewhere).
I looked through the manual and there was a section for starting the system, which was about 8 pages long, but nothing about powering it off again.
I put in a support call to the vendor and they went "um... ah... hang on... we'll write a procedure for you." They came back with a 14 step process that covered 4 sides of A4. "And the restart procedure?" I asked... "Is that the same as the one in the manual?"
"No! You just push the power buttons in the sequence you generated in step 3 of the shutdown procedure, leaving 5 minutes between each node. See? It's that one line there, right at the end of the page 4."
I went for a walk round the local park with a colleague a few years ago. He flatly refused to go into the bit of the park that was hedged and fenced off, as the sign on the gate clearly said "nature area", and that he might see something that would conflict with his religious obligations around modesty.
He stayed out of THAT field.