20 karma · joined October 27, 2015
Their business model is to allow free access to a limited version of their product -- which admittedly is good enough for many to use in production.
And if these companies stop getting revenue for the premium product, then I worry it's goodbye to substantial progress on open source version.
Why can't HN be a place were we nerd out over new frameworks but engage in partisan political discussion over the impact of what we build?
This article posted is immensely relevant for the intersection of tech and political discourse, and in such cases, I would personally prefer to see more discussion on HN.
If the article is about new advances in Golang, sure, I'd hate to see talk of politics in threads.
Like fb ranks lower on how much stress it induces since "kids these days" simply don't use it much.
I wouldn’t want, eg my health records stored on a system that isn’t trusted. This is one often cited application of blockchain.
It seems like you have to define a new device on a existing logged in device before using the new device. Is there a way around that? If I want to log into an app for the first time at work and forgot to define a new device name at home where I already can log in, I wouldn't be able to do so from what I understand.
And this idea that engineers are purely scientifically minded totally ignores the endless number of articles suggesting that the best senior engineers have strong product and business sense, and in many places (but not all) having those skills are a defining quality of a senior engineer.
Engineers definitely NEED scientific background to enter the field, but this totally ignores that engineers grow business and product skills throughout their career, and need to do so to be effective
But wonder if GM could pull ahead since it has more of a history of mass producing things, and all the infrastructure around that all built. Time will tell.
That can't be good long term for the tech sector.
I just think that they are opaque to what they really mean by exactly-once and definitely hide the fact that they do not offer exactly-once delivery.
Exactly once seems to refer to exactly once write to kafka and processing in kafka streams that write back to kafka and don't do stuff like make external http requests, in which case you'll need your logic of at most or at least once to delivery results to wherever you're sending the http requests.
Confluence blogs do seem pretty misleading in terms of hiding these issues.