It's pretty generous actually, Apple and Samsung rarely backport marquee features. I figure Google is trying to build up loyalty amongst Pixel and Pixel 2 owners so that they stay with the brand.
2,885 karma · joined March 14, 2012
Co-founder, Kami - kamiapp.com
It's pretty generous actually, Apple and Samsung rarely backport marquee features. I figure Google is trying to build up loyalty amongst Pixel and Pixel 2 owners so that they stay with the brand.
We also had a case not long ago where a chrome update introduced a bunch of bugs with stylus input on Chromebooks (a mission critical use case for us)- there we just had to tell people to downgrade to 66 or wait for the 68 update, there was no viable workaround.
I see your point though, there are plenty of untrustworthy third-party repairers.
Absent that, the only way to provide a reliable service is to make it very process-based - Run this procedure to find which of these 5-6 components in the device is most likely faulty, replace it with a new one by following this standard procedure, then run this automated QA test and if it doesn't pass, replace the next most likely component until it passes.
It probably costs Apple a lot less to do their warranty/applecare repairs in this way, replacing whole boards at a time, than to try and hire enough people who could do board-level repairs.
It does suck for people who are out-of-warranty and have a minor fault like in this case though - and Apple should have a better solution for them. Arguably if it's a minor fault, they should charge a minor fee to fix it even if their solution is replacing a whole component.
Apple also seems to be trying to restrict third party repairers (and not just for security-critical components), which is indefensible IMO.
The theory behind it is that the public shaming (particularly for public figures) from being named would be a punishment, and you shouldn't be punished for a crime without having been found guilty. There's been quite a few high profile abuse cases with this recently where rumours spread around around which 'high profile sportsman' it is.
These days with blogs and social media it usually just turns into a rumor mill, and someone outside NZ jurisdiction can name the person legally. It's also a pretty clear violation of free speech, and judges seem to be very willing to give name suppression, and sometimes maintain it in place even if there is a plea deal and the person is convicted - There's a solid argument that it results in abusers being back out in the public, without people even being warned. So it's not exactly my favourite bit of NZ law :)
Having a separate app that takes a different approach which heavy users of email might like makes sense - the UI you need when you are getting 100+ emails a day is very different from when you are getting 5.
We’re helping over a million teachers and students eliminate printing and scanning and the associated costs and effort - so our teachers can spend more of their time on achieving better learning outcomes for the next generation.
At Kami, we don’t believe in keeping our engineers locked in the backroom implementing specs sheets - you’ll be talking to the teachers who already love our product, and figuring out how to make Kami work even better in their classrooms. This position will suit an Engineer with a good product sense and is comfortable working relatively autonomously.
We're constantly pushing the boundaries of what you can do in the browser - I just spent the past week tracking down Chrome bugs on the new stylus-enabled Chromebooks! Our frontend is a SPA built in angular, and we have a Rails API/Postgres/GKE/JRuby backend that it talks to.
Most of our users are based in the US, and there may be occasional travel to attend conferences and visit schools using our software, which is a lot of fun! ( See the wrapup from our last conference in Chicago, IL: https://blog.kamihq.com/iste-2018-wrap-up/ )
Our office is in Central Auckland, New Zealand (with great public transport connections), and this position is local.
More info: https://www.kamihq.com/careers/#frontend , email me your Github and CV at devjobs@kamihq.com. (mention HN)
It's highly debatable if there is a higher risk to human life as well - unlike with rockets where you fuel up before the astronauts board, you don't have people approaching a fueled up rocket which could explode with no possibility of escape. Instead if there is a issue while fueling up, the astronauts are in a capsule with a escape system which should pull them safely away from the rocket if there is a problem.
Arguably it'd be riskier to use non densified propellants for these missions as then they'd be using different procedures than the cargo missions they launch regularly and will have less experience with it and opportunities to find and fix any issues on a cargo mission before it affects a manned one.
I'm a big SpaceX fan and they've got a big lead in terms of actual launches and recovery experience, but don't count Blue Origin out.
And the ship has taken far bigger poundings in the past, one of them blew a huge hole in the deck.