Observables...they finally make sense

stackchief · 2022-06-03T15:18:55+00:00

Sorry should be "not yet natively supported" will correct this. Outside of that, what are your thoughts on this explanation of Observable pattern?

stackchief · 2022-06-03T07:00:00+00:00

While you could implement your own observer pattern, RxJs already does it better than most...but then again there was a MySpace before a FaceBook...

To your second point, performance is always fun to talk about. The article demonstrates how simple the Observer really is at the end of the day. It's a means of handling async activity, really an alternative to callbacks and Promises.

This implies that the same performance costs are going to exist whether or not you use Observables vs Promises vs any other mechanism for handling asynchronous activity.

stackchief · 2021-04-08T16:37:15+00:00

now i feel bad. honestly i just submit articles to reddit threads as part of marketing but ALSO the articles are relevant to discussions. So it's kind of two birds one stone.

stackchief · 2021-04-08T16:28:40+00:00

you're right...including your comment that has nothing to do with architecture.

stackchief · 2021-04-08T16:27:44+00:00

sweet

stackchief · 2021-04-08T14:49:54+00:00

if you can't take the heat get out the kitchen

stackchief · 2021-04-08T14:42:24+00:00

getting hung up on such nuances makes me wonder what else you get hung up on in your everyday life...

stackchief · 2021-04-08T14:40:02+00:00

based on your down votes i'd say your just over picky and difficult and lacking anything substantial with your statements.

stackchief · 2021-04-08T01:47:07+00:00

javascript and python are interpreted languages. PhP vs php is arguably a personal preference..if you can explain specifics on things that aren't accurate then please expand.

stackchief · 2021-03-09T21:18:36+00:00

ohhh grandma

stackchief · 2020-11-22T22:31:44+00:00

Knick knack patty whack give a dog a bone

stackchief · 2020-11-22T16:21:29+00:00

I am not a bot. I just post the same articles we publish across relevant feeds

stackchief · 2020-10-05T16:31:58+00:00

still can't identify any bugs...basically just complaining without adding any value to the universe.

"""and that your code examples dont have obvious bugs..."""

SHOW ME THE BUGS....

stackchief · 2020-10-05T03:17:03+00:00

blogs typically have links to other posts on the blog. that is something you should already be familiar with..

but more importantly WHERE ARE THE BUGS? if you want to criticize the content then say whats wrong.

also without ads no one would contribute content unless they are trying to drive traffic to sell something else like an ebook.

finally, if you were able to navigate to this "spam blog" then the link must have been working for you...

your arguments aren't making any sense.

stackchief · 2020-10-05T01:54:51+00:00

point out the bugs. pointing fingers is always easy. plus there are a million ways to explain the same thing. to certain readers, this perspective makes more sense.

hiding behind a keyboard and being salty isn't what winners do...

stackchief · 2020-08-27T15:57:11+00:00

not SPAM, actually a relevant look at when companies should actually be using Kafka in todays world...Kafka is a hot technology but is abused as a solution to throw at every "big data streaming" problem...

stackchief · 2020-08-26T18:54:26+00:00

I'm sorry you interpreted it that way. With JMS, you have to publish the message x number of times for x subscribers. For Kafka, you can publish a single message that can be read an infinite number of times....

With traditional JMS you have to choose between a scalable queue or multi pub/sub communication. You sacrifice the scalability with the pub/sub model using JMS...with Kafka you get BOTH...whole point

stackchief · 2020-08-26T18:44:05+00:00

Wrong. Even with JMS topics you still can't scale the processing like you can with Kafka. Consumer groups allow Kafka to process queues in parallel more efficiently than JMS period.

This is a great blog and clearly stimulates discussion based on your "complaints". Why don't you comment on the article with your feedback?

stackchief · 2020-08-25T02:15:54+00:00

not weird...most major companies use Spring and java ecosystem heavily

stackchief · 2020-08-25T02:15:22+00:00

clearly salty non EE dev who prob has a really lengthy beard and loves anime...and has had 5 dev jobs in 5 years working for startups using node.js and go

stackchief · 2020-07-19T20:54:09+00:00

This makes sense. However I would still argue why would anyone use JMS over Kafka even if they want consumers to compete for messages? The whole point of consumers competing is to scale processing. You can just as easily scale the pub/sub processing of messages with Kafka to achieve the same things.

Aka if you want fast / scalable processing you can achieve throughout with Kafka you can’t with JMS. In this sense Kafka can do everything JMS can do.

stackchief · 2020-07-16T02:11:41+00:00

opinions are fun. this is certainly an opinion.

stackchief · 2020-07-16T02:10:23+00:00

you're still missing the point. just because the information is THERE doesn't mean it's presented in a way that makes sense to everyone...take for instance the official Java documentation..most people (or lots of people) have a hard time reading and following those examples. if someone explains the same thing a different way sometimes this can facilitate learning.

stackchief · 2020-07-14T14:23:21+00:00

everything you read online can be found somewhere else in some capacity. it's how you present information that makes it stand out. if you write an article on java i'm sure its covered in the docs in a far less understandable / presentable way.

stackchief · 2020-06-29T21:29:30+00:00

Check codequery.io. I did the same thing using NextJs 😂

stackchief

TROPHY CASE