Readit NewsAnd this was for the German market only. So I am quite sure that it was more common in the US at an earlier time, as they are usually ahead of us.
I published each version on a separate WordPress blog covering roughly the same topic, chose random pictures, set random publish dates close to each other, and signed them all up for Google News. This non-AI dogshit dominated a small tech niche, making a decent amount of money at the time for a 14-year-old. I am pretty sure I was not the only one coming up with that idea at the time.
Population is aging and paying for the retirement money for all existing retirees is already taking up over 25% of government spending. There’s barely money for anything else so taxes and social security payments are poised to go up while already being close to ~50% for most earners.
There’s a strong and growing far-right movement full of populist and even neo-nazi ideologies.
Infrastructure is still top notch internationally but funding has been cut over the last decades and it’s starting to show.
I could go on but I think you get the picture. Many people in my social circle want to leave the country so I would really think twice about moving here.
To elaborate on that a bit the main things Pulsar gives you are:
1. Still underlying distributed stream based architecture, this is what makes it able to do Kafka like things.
2. Broker side management of subscription state which allow out of order acknowledgement, this means you can use it like a queue. (Subscriptions sort of act like AMQP mailboxes but without the exchange routing semantics). Vs Kafka which can only do cumulative acknowledgement, i.e head of line blocking.
3. Separated "compute" and storage. By storing data in Bookkeeper you can scale your needs to support a lot of consumers separately from how you stash the data those consumers need to read vs Kafka where these 2 are coupled and an imbalance between the two becomes awkward.
4. In built offload with transparent pass-through read. When your data falls off the retention cliff for your standard broker cluster the data can be archived to object storage. The broker can transparently handle read request for these earlier messages though, just with higher startup latency to pull the archived ledgers.
5. Way more plugability than Kafka, in-fact similar plugability as RabbitMQ. You can implement your own authz/authn, a different listener to support a different protocol (there is a Kafka one, MQTT, AMQP etc).
6. Much greater metadata scalability. Before the new KRaft implementation the layout of metadata in ZK meant that you couldn't feasibly have more than about 10k topics. Especially because of how long the downtime would be on controller failover. Pulsar can easily support much larger numbers of topics which prevents needing to use a firehose design when you would prefer individual topics per tenant/customer/whatever.
I primarily got my desk because I was tired of having bad posture and back pain. But since I also started working out heavily at the same time I built the table, I can't attribute the desk only to alleviating any pain I had. It definitely helps though with good posture.
I'm also happy I got a smart version that can remember 4 heights. I had another (much more expensive) table at my previous workplace that didn't have it. And it was a pain switching from a seated to standing position.
If you work a lot in remote dev environments (I use coder a lot at work) that really does the trick.