Re: Larry Complains to mummy
Google dropped out due to ethical concern, lol oh and they didn't have the relevant DoD certification.
MS are still interested in bidding.
126 posts • joined 15 Aug 2013
As has already been mentioned, you don't have to login into a remote system to the data. You can get the same information in the car if you don't want the convenience of having the information remotely. As you seem to have a problem of having the extra convenience the car will work just fine if you switch the option off.
And why is it odd to upload the data to a central location for the app to access it ? How else do you propose the app can read the data from the car ?
This has very little to do with Linux. IBM has realised there is enough of a market for on-prem and hybrid cloud and their current range just doesn't cut it. MS have delayed (again) with on prem azure and OpenShift is the most mature product out there and they have windows in a container support coming soon.
Of course the real question is how badly with they f**k it up or if they will leave Redhat to continue developing their products instead of trying to do some half arsed integration.
Plus of course getting rid of dinosaur IT and injecting fresh blood who don't have huge pension commitments will help.
1. Suppliers aren't typically responsible unless there is a manufacturing defect. Parts will have been to VM specs and design certified by VM.
2. While there is some drive from consumers for all these gadgets however the bigger driver is the 'me too' factor. Nobody wants to be one not offering big touch screen controls.
4. Most manufactures are expected BEV to be niche for time yet. Tesla will be around for a few years to come.
5. Connected car is already a given thanks to the EU insisting that you car can call emergency services in the event of accident. Don't forget that insurance companies have been collecting data for years already even if they can't access car controls yet.
I guess they didn't want to join,
All trying to gather and monetise your data but all on different platforms. So if I was a parking company for example I now need to speak to 30 different suppliers instead of single one for the automotive industry.
Doesn't bode well for v2v communications.
If it wants to sit on the edge, if it can't be run on a arm CPU then the footprint is too big.
Biggest IoT issue I have today is having 10 different vendors coming to me with 10 different solutions for the same use case. And its not even 10, its 30 or 40 or more and the solutions are too specific to the use case. Need something more generic.
As a comparison there are very few situations where you need video feed and even if you do then the chances are you will try and process it at the edge. The vast majority of IoT devices are going to be low data rates.
As for factories, not cheap in the slightest to get infrastructure in there. From personal experience support industrial environment. > $10k for an access point is pretty common once you consider tapping into a 3 phase power supply, running fiber and never mind trying to do all this during maintenance windows. Same with hospitals, you generally don't want AP where there is infrastructure already. That verses putting in a couple of $200 battery power AP.
Will add that WiFi is generally very difficult to do in a factory, lots of electric interference and metal getting in the way. Forget trying to get even a 3G signal in there. While is LaRaWAN is designed for longer range, there are plenty of use cases for it complementing WiFi.
Did you read the article ? Its not designed for high data throughput, never claims to be. Its designed for low data volume sensors like temperature, water flow, light, distance, vibration that are sending a reading back once a minute. If you want to be sending high res video stream then these devices are not for you. However if you can process your video or images at the edge and send back the results of what you are looking for then there is potentially a use case for you.
Its interesting you mentioned hospitals and factories. Both of which are terrible for WiFi signal and hard to cable for power and network. To put a traditional AP on a plant floor could easily cost > $10k. Compare that to a device that costs < $200, has a 10-year battery, can be set in resin to be completely environment proof, has a magnet on the back for rapid deployment. You could flood an entire plant floor with zero maintenance mesh network for less than the cost of a single AP.
Going back to sensors, we are looking at a still image use case. There isn't enough bandwidth to send back the whole image but actually we can process the image at the sensor and send back a yes / no for what we are looking for. Problem we were hitting was the power used to do image processing was dropping battery life from 10 years to a few months. Solution was a rechargeable battery charging using a PV panel that worked from a nearby florescent light. Also as the solution is two way we can update the image processing code and send firmware updates though these can take days to get there.
The issue over standards is still a pain but hopefully that should work itself out in the next couple of years.
They are making a big push on prices, especially on contract with handset.
Regarding service. Recently moved from VM to Vodafone. Got the PAC code from VM no problem. Entered it on a Vodafone website and got a text back saying it will be done by 5pm the following day. 5pm came and went and of course it didn't happen.
Called them up and said there was a problem with the transfer request via Website but its manually entered and it will be done by 5pm the following day. That didn't happen. Called them against on Friday evening, got told that PAC team don't do weekends and nothing could be done untill Monday. Called Monday and told it would be done by Midnight. That didn't happened, called again on Tuesday and was told 5pm again. This time they managed to do something, outbound calls were back to my old number but inbound calls didn't work to either old or temporary number, just went to voice message. More calls, and finally at lunchtime Wednesday inbound calls started working on my old number.
So a week to do a number transfer but the real annoying thing, every single time I called they sent a text survey. Not just a single text but a couple texts each time.
For some use cases yes. But SSD greatly drops latancy, higher IOPS,higher density, lower power usage and better reliability. In addition potentially allows dedup, compression and encryption in situations where spinning disk doesn't.
So cost per GB can be very misleading and not always the same as VFM.
Also need to think about IOPS which is a much bigger factor than bandwidth and of course density with 15TB 2.5" drives already available and 30TB drives have been announced . Added on that flash memory allows re-dup, compression and potentially encryption in situations where spinning simply can't there are plenty of use cases for flash storage. Not saying its the right solution for every situation but there is plenty of situations where it now is the right solution.
Re: what about Apple?
Apple allows you to use any search engine you want. In addition you can use Opera, Firefox etc as there are apps for them. Google allows very little freedom for the consumer. Ffs Apple even allows removal of the bloatware so they are not breaking the law in this case.
The issue isn't that consumer doesn't have browser choice or maps choice or choice for any of the google offering. The issue is that Google if forcing its apps to be pre-installed and not removable and no rival can be pre-installed so Google apps becomes the default choice.
I'm guessing the vast majority of users can't be bother to download alternative to Google apps.
It will have the same footprint as Windows, so now we will have your app running on windows on a container platform which itself will be running on a hypervisor. Really makes sense ?
There is zero chance that the app will take advantage of vertical or horizontal scale, will probably use local storage, be connected to by some SMB or other non-scaleable protocol, etc
The only reason you would want to do this is so that you can ticket the box to say your application is running in a container.
Yes and no, having seen what happens in large cooperates you have a pool of talent that thinks a certain way and can no longer innovate. In that instance your best bet maybe to layoff the dinosaurs and start again, preferable by moving location and keeping them at arms length and staff them with new employees who don't get encumbered with existing culture. Best thing would be to not even brand it as HPE.
The problem with most company purchases that are made for innovation reasons is that the bigger organisation tries to impose their outdated policies instead of leaving the smaller more nimble company as they are.
Unless you are using it for data centre levels of writes then a non-issue these days. Techreport tested a Samsung 250GB 840 TLC drive and managed it managed 900 TB of writes before dying. In case you are wondering that would be almost 10 years of writing at 250GB per day.
Of course the drive could die on the first day so I am sure you are keeping backups right ?
"You wouldn't blame Ford or BMW if a mechanic did a piss poor job of replacing your breaks would you?"
Actually is a good analogy because BMW is exactly who would be blaming if the dealership contracted by BMW did the work. BMW trained the mechanic to their spec and certified them to work on their behalf.
I would say the VM should pass on the fine to the contractors but they most likely can't because VM's own inspectors probably signed off the work. So the blame here is fair and square with VM.
Tesla, entering a market that others are struggling or exiting,
There is some question over long term demand especially with US government dropping subsidies for EV and power companies wanting to charge a higher rate for EV charging.
Biting the hand that feeds IT © 1998–2019