HN user

guilt

-19 karma

- Outdated Account -

Posts5
Comments19
View on HN

Are you implying that because you went through a couple of good interviews with them, and because one director who works at Google said that they don't hire this way, it doesn't happen?

That's the worst logic ever.

I'm blaming Google for doing this, and you take it to imply that I said you work at Google? Maybe you didn't accept those offers from Google. It still doesn't mean those things didn't happen at Google - and it is extremely shameful that you resort to defending them.

Congratulations, what you have done is just free PR for Google. I'd rather listen to everyone else than you.

This is not a good thing.

They were finally getting to have a fully built out environment - which could lead to better end user packaging, stripping down a library to its bare essentials.

For instance: what have jpackage achieved for a distribution like RedHat? Does anyone's Java App even pick up these RPM based dependencies for Classpath? Heck no.

Every known large scale Java application pretty much bundles a bunch of JARs. (Probably not logstash - but only one exception)

It is very clear that JDK9 will not be as awesome as it was originally supposed to be. Deeply disappointed.

I think the first thing to dump is the daylight savings time concept.

Then rebase the timezones based on UTC.

It won't help when you have a polar winter or a midnight summer - but at least it will remove unnecessary conversions.

For AEAD, We'd most likely look at ChaCha20(Poly1305(Text)+Text) and I think that's a great idea. :)

We're definitely looking at non-NIST algorithms, we've just had enough of those.

Yes - and I'd say WebSockets have been sucking the juice out of the DataCenter if your clients are mostly idling!

I'm not disagreeing with you here. Our point was that HTTP 2's features start doing amazing things after the first request, now that they have a connection going. Do read that we are excited about what it brings - just not for the very first request itself. And honestly, if they changed that, we'd be a happier lot.

If we don't support TLS, doesn't mean we don't care about E2E Encrypted Data, or E2H Encrypted Data, or Signed Data.

I do understand how the system works - and I've seen ISPs issue fake real certificates (which CA issues Google's certificate?) and I think sometimes, you just have to do it deeper, and yourself, if you have to do it right.

We started building with that approach. We're looking for people to tell us what's cool and what's not!

We at GeoG are building a safe, easy and sustainable platform for IoT. We can totally do everything if we put time and effort into it - which we are ready for! What we want you to do, is start hacking and building things with us. No strings attached!

We recently set up a Community page http://community.geog.co where we want to start listening to you, your needs and suggestions.

Did we mention we have an API? We'd like you to start beaming data and create cool things with us. http://api.geog.co

Also, if you have reasons to hate us, bring it out! We're listening.