The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
We are being too serious now but genetically the egg is a chicken. The grass is not genetically a cow.
Now that we are in the serious corner: Mushrooms are neither animals nor plants, they are from a different kingdom. They share some genetic traits with life in the animal and plant kingdoms - but more wiht animals than with plants (if what I have been told is correct).
So, do vegetarians, vegans or whatever they call themselves shy away from mushroom because they are genetically closer to animals? Or do they ignore the genetics, saying that "Anything that isn't walking or swimming or flying is OK as food"? How do they then relate to jellyfish, spending part of their life swimming about, and part of their life affixed to the bottom of the sea, growing like a plant? (Consider it a question of principle - I don't think jellyfish are suitable for eating!)
Are you suggesting that vegans are the only ones not eating meat products?
No, but they're the largest segment of the market. Especially the fake meat sort; we carnivores have no need for sad imitations. If I want something that tastes like meat I'll eat the real thing; if I want a vegetable meal I'll go for something that highlights the best a veggies can be (which is not fake meat).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
Me and my colleagues at work have totally had it with SignalR and it's erratic behaviour, everything seems to work fine locally, but as soon as it's tested in a production environment unexplainable problems occur. Also there does not seem to be anything to find about these problems on the internet, like long delays on message delivery
Are we the only ones having these problems ?
We are thinking about switching to ZeroMQ, see: message-queue-servers[^]
They're different technologies.
SignalR is a wrapper around web sockets that can send data back to the browser (which isn't normally possible using HTTP, although SignalR should fallback to long polling if sockets fail or aren't supported).
RabbitMQ (and ZeroMQ and ServiceBus) are queueing technologies, which support sending some data to a queue (or topic) where listener(s) will pick it up and do something with that data.
I can see how queueing can be an alternative to sockets, but sockets are usually not a good (or even possible) alternative to queues.
That looked good to me too, and also NATS (especially with future Docker microservices development in mind), but one of my colleagues already beat me to it with a Proof of Concept using ZeroMQ before I could even start a discussion about it, guess I'm getting too old and slow
And I must say, the more I read about ZeroMQ the more enthousiastic I get, it's even developed by a Dutch guy !
Never heard of NATS (just read your experience on that list).
My biggest objection to ZeroMQ would be the following:
Some guy named Tim wrote:
More complicated scenarios require more setup
ZeroMQ is very fast due to its simplicity, but as a result of this, doing anything harder than passing messages between 2 peers will require a lot more work from the user.
SignalR is (usually) a one-to-many broadcast, with support for channels.
That sounds more like topics than queues, and according to this Tim topics aren't supported in ZeroMQ.
RabbitMQ (and ServiceBus) do support topics out of the box.
Although reading the ZeroMQ website it also seems they support topics as well, so Tim might just be a dirty little liar
ZeroMQ's fine - I've used it in some projects at work. I've always got the feeling that Martin Sustrik (who then went on to start nanomsg - another lightweight messaging system) was the main man in the development, until him and Hintjens had a falling out...
Main difference between ZeroMQ & other messaging systems is the lack of a separate broker server, which is an advantage for some use cases (it was for the one we had), but probably not for others. Being able to support messaging between & within processes (where in-process messaging uses a different, more efficient transport) was also a plus point for us.
We only use the REQ-REP setup, but PUB-SUB (for data distribution) is also on the cards for future developments.
We layered Protocol Buffers on top, to provide message structure. That also worked well.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
I didn't think so, but then I found RabbitMQ Web STOMP Plugin — RabbitMQ[^].