2,885 karma · joined March 14, 2012
Co-founder, Kami - kamiapp.com
It seems to work similarly to this but you run it yourself so it doesn't need to tunnel traffic through cloudflare, and it's open source.
If it's HDMI only, as the sibling pointed out the HDMI port won't work. However, Startech makes a displayport to HDMI adapter which works ( https://www.amazon.com/DisplayPort-HDMI-Adapter-Converter-60... ) (just make sure you get one which supports 4k60hz, most DP -> HDMI adapters don't).
Haven't seen any issues with the latest OSX for the 2015 MBPs though, and unlike with iOS you can easily downgrade to an older OS if you do see issues.
We're still managing our Postgres manually ontop of GCE and I'd rather not have to do that, but I also don't want to give up the replication setup we have and the modules we use.
It's a shame really - IMO it would have made sense to keep developing the inbox concept, it is a quite different way of thinking about email, and if it's a separate app it can move faster than something which has to take into account all the legacy of Gmail. Far from the first time a solid Google product dies just because the dev team moves on to other things and nobody's working on it anymore.
Once they decided to go straight to Starship/BFR with the movable 'wings' and raptor engines on the bottom and cancelled the dragon missions to Mars, there was less reason to go though the huge amount of work to finish developing and qualifying dragon-style propulsive landing. NASA was never super happy with it and Dragon was designed to do water landings with parachutes in case the thrusters failed anyway, so it wouldn't have been too much work to make that the only option.
This has lead to a strange situation where it seems Boeing's Starliner has ended up being more reusable than Dragon as it comes back onto land... But if they get Starship going, all this will be irrelevant.
The closest I've seen are the Dell XPS 13/15 and Thinkpad X1 Carbon/X1 Extreme, but I'm not a fan of the Dell build quality, and the linux support on the Lenovos isn't quite good enough yet (Nvidia Optimus driver issues mostly, and issues with battery life relating to it).
The other potential option is System76, but their laptop hardware just isn't up to par - their POP!_OS seems pretty good though, despite the horrible name, so they are part of the way there.
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, though I will also consider remote candidates :)
More info: https://www.kamihq.com/careers/#frontend , email me your Github and CV at devjobs@kamihq.com. (mention HN)
CS:GO is a classic case of this - the player base is noticeably more mature at certain times of day, and there's a distinct period when all the kids have just got home from school where things are particularly bad. Occasionally you'll get a team where you everyone works together well, but to have that every time you'll need to spend a lot of effort maintaining a huge friends list in order to be able to put a team together at any given time - rather than just pressing the matchmaking button.
(I think you could might get decent results on this by having each player rate the others at the end of the match - but you don't use the ratings to rank the players, instead you'd use them to cluster players based on who they mutually like to play with. You'd then use that as a variable to optimize on when doing matchmaking. Hopefully with enough data you'd be able to predict if players would have a good experience even if they've never played together before.)
Rails/Django etc will correctly sanitize the rendered data for a HTML context, but they don't know that your client-side framework will execute code inside a {{ }} block, so those aren't removed - so if you render something in rails inside a div which is later on part of a Vue or Angular app, you'll have a problem.
There's a few ways around this, e.g. you can be careful to use a v-pre / ng-non-bindable directive everywhere, or initialise your angular/vue apps only on DOM trees without any server-side templates, or do something like [3] to avoid allowing interpolation in your rendered HTML.
1 - https://github.com/dotboris/vuejs-serverside-template-xss 2 - https://github.com/angular/angular.js/issues/5601 3 - https://github.com/dotboris/vuejs-serverside-template-xss/is...
Boom is certainly an extremely risky startup (as was SpaceX)... but isn't that what venture capital is for?
Google could have been a major player in messaging if they had just stuck with GChat/Google talk from the early Gmail days and kept investing in it. It was great on the early versions of Android! The failure here is entirely self imposed and a major indictment of their senior management team.