Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
whisk3rs
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
whisk3rs
13y ago
Finally, CSS that I can really trust!
32.
▲
by
whisk3rs
13y ago
Agree, the animation is distracting. I'd rather that the bar fade-in (quickly) in place. Otherwise, this is awesome, and I'm going to use it.
33.
▲
by
whisk3rs
13y ago
It is more accurate to say that RabbitMQ supports both fire-and-forget and producer-waits. The exact behavior is specified by a combination of how you configure exchanges and queues, and per-message settings, and how you write your client c
34.
▲
by
whisk3rs
13y ago
> I wouldn't recommend Revel to many (it's Play heritage isn't well suited to Go, IMO) Can you elaborate on the issues you've had? I've used Revel on one project and it was totally adequate. The automatic reloadi
35.
▲
by
whisk3rs
13y ago
Nice. This seems to solve a common problem for developers building rich UIs. On a similar topic, does anybody have any pointers for implementing keystroke-by-keystroke character replacement in an INPUT box that doesn't suck? I'd l
36.
▲
AngularJS: The Bad and the Better
(miceplans.net)
3 points
by
whisk3rs
13y ago
|
0 comments
37.
▲
by
whisk3rs
13y ago
Thanks for the detailed response. I hope to learn from your experiences. AMQP is indeed a complicated protocol so I can appreciate your reluctance to write a client. The failure mode I was referring to with Redis is that you now have additi
38.
▲
by
whisk3rs
13y ago
I'm curious about the justification for Redis in this pipeline. That seems to introduce additional failure modes. Was it the case that a non-durable non-confirming (in-memory only) RabbitMQ wouldn't satisfy the latency requirement
39.
▲
by
whisk3rs
13y ago
No problem. Frustratingly, people rarely seem to talk about how they use RabbitMQ in practice. Also, there are a lot of things that are still a mystery to me (for example, best practices for dealing with things like server shutdowns, or wha
40.
▲
by
whisk3rs
13y ago
Oh, that's great to hear. I'm surprised I didn't find that previously. I vaguely remember trying a php-amqplib and having issues with error messages, but your client promises to be strict-compliant so perhaps I was using an a
41.
▲
by
whisk3rs
13y ago
RabbitMQ queues support two features that can be combined to implement a deferred retry queue, and RabbitMQ will do all the work for you. The first is a "message-ttl". This tells RabbitMQ to discard messages after a specified numb
42.
▲
by
whisk3rs
13y ago
I've built something similar as part of renovations to a large, legacy PHP code base. We're writing our consumers in Go using some impressively well written AMQP libraries ( https://github.com/streadway/amqp )