z9e

Yeah. Amazing how people on a forum are offering their opinions on something. Let’s point and laugh at them. /s

I’m more amazed at the toxic (no pun intended) comments in this post. It seems HN isn’t a place to voice health theories.

The highly processed ones that are hydrogenated, such as cottonseed. Trans fat forms from that process.

I think the more worrying thing about vegetable/seed oils is the omega 6. A small amount is not an issue from my understanding. And in fact omega 6 can be healthy for some specific situations. But it’s the fact that these oils are used in just about all processed foods and restaurant cooking to the point where people are consuming more omega 6 than they should be and we’re seeing negative health effects as a result.

So, trans fats which are a known contributor to heart disease are healthy now?

Yeah those sensible gun laws in Chicago - some of the strictest in the country mind you, seem to be working really well. /s

This is hilarious considering progressives in the 1930s praised Hitler as one of their own. Find a new talking point, 2016 was 6 years ago.

There’s also increased cost on businesses to stay open in high crime areas as crime rises, the insurance rates go up and it costs them more and more to recover from property destruction and theft.

In theory yes, you want a 1:1 partition to consumer ratio, that would give you the most optimal throughput, but it’s okay if you have less consumers than partitions, you’ll just have consumers doing more work.

Keep in mind you shouldn’t really go over 20k partitions in a Kafka cluster (recommended by Confluent), as that’s when things will start to get unstable. 10k is a lot of partitions, we have a hundred topics in our main cluster and only are at 15k partitions total. But if your running a high scale low latency environment then that sounds like what you’d need.

My wife is a UX Researcher and what I see going on in the UI/UX industry through her eyes makes this unsurprising to me. Most of the time her research is completely ignored by developers and PMs, her step in their overall process is just a nuisance to them because it delays them shipping features, or it’s insulting to their ego. Now there’s a trend with developers and UI designers calling themselves “UX engineers” to take control of this process and they do a bad job at actually understanding UX Research and mock up horrible designs because they don’t do studies with participants, and simply think it’s a check list of do’s and don’ts.

The whole UI/UX space seems like a mess to me and needs a reboot.

Agreed. I’ve been running Kafka clusters at a few companies now, one that was at a massive Fortune 500 and Zookeeper was the least of my problems.

I’m still glad to see it go away, one less operational dependency the better.

I have never actually seen SUSE used in the wild (running services in a data center or Cloud), it's always been CentOS / RHEL, or Ubuntu.

SUSE is a great distro though and I'm happy to see this. Does anyone have any anecdata where they've seen it most heavily used?

This is happening in all professions I'd imagine. Everyone is so scared that they are violating some social framework - which is constantly shifting in what is acceptable or not acceptable.

To me I think it really slows down progress we could be making in multiple areas. It's kind of like a mental brake being applied to any freedom of thought. Almost like working in an old fashioned company where there's weeks worth of meetings and bureaucracy in order to get a change deployed to production to make sure everyone is okay with it, even those of whom it doesn't even impact.

... Until they hire you back because entropy exists :P

I'm on the DevOps side as well going through the same transition, k8s also allows insane customization, and I have some colleagues that are delaying our rollout unintentionally so they can play around with developing more tooling for deployments which is really frustrating. The k8s scene seems to be filled with constant scope creep and refactoring to get it just perfect before use. Either way, I agree the benefits far outweigh this annoyance that I've experienced. I'm so excited to work on developing tooling instead with my time.

However, I don't think we're free entirely from managing servers the old way with Chef / Puppet / Ansible, unless you're purely hosted there's still the rule of thumb you shouldn't run services that hold state in k8s. But with persistent vol's I do see that changing, though I'm not sure if everyone agree's that's a good idea.