The complaint that it looks old-fashioned is addressed partly by using ttk (themed tk) but also just about every aspect of the widgets can be styled using a simple xresources-style config.
It's fast and lightweight, free forever, stable as hell, and there's lots of resources online.
I really liked Redis for a long time. Simple, fast data-structures in-memory. That's it. Along the way there have been some nice enhancements like Lua, which solves a lot of the atomicity issues. But somewhere after 4.0 I feel they have lost their way. First they saw all the attention Kafka/event-stuff was receiving, so they baked-in this monstrous, complicated, stateful streams feature. Now we have SSL (do people really expose Redis on the internet??), ACLs, cluster stuff, and most relevant to me a new wire protocol.
To my thinking, Redis fit very well in the "lightweight linux thing" category. It seems they aspire to be enterprise software, and this may be a good move for Redis-the-Business, but it's not good for users like me who just want simple in-memory data-structures and as little state as possible. Forcing a new protocol that adds very little value (in my opinion) also seems like a great way to alienate your users.
The shortcomings of snap are well documented. I assumed anyone reading the comments would have been aware of them. But apparently some people will jump on any chance to virtue-signal.
As always I'm happy to see one of my projects getting repped. Huey was something I started out of frustration with celery. It's more of a celery replacement than an rq replacement, though it covers both. If you haven't heard of it -- it does tasks, cron (periodic tasks), delayed tasks, result-storage, etc., and supports multiple worker models (process/thread/greenlet).
* how did you settle on 10 seconds? Keeping two databases in sync is a complex process. I'd suggest that the difference between running 1x/min or 6x/min is negligible -- and if it's not then probably you need something more sophisticated than a simple cronjob.
* I am providing free software. You are not contracting with me to provide developer support, so in my book I'm under no obligation to be courteous and polite all the time. I try to be most of the time, but nobody is perfect. Luckily the source is available if you don't want to talk to me. That was my point and I'm surprised that is so triggering to some people.
I don't understand why anyone would want type hints. It makes the code so ugly and complex. Pythons appeal for me was always that it is "runnable pseudocode" with a strong object system and great libraries.
To me it feels like python is running as far away from simplicity as fast as possible.
Internet culture is always changing. A devoted core of people is doing something cool, new people come in who are just there for the scene, finally (in the cases discussed in the article) business interests co-opt it and it becomes sterile. This is described in the article geeks, mops, and sociopaths, if you're interested.
I liken fb to reality TV. Everyone can be a star. Like Warhol said.
Twitter is pushing some weird buttons. I think it attracts narcissists, and gets people hooked-up on their own chemistry. I've always had a really low opinion of twitter users.
Missing old shit is death. Just start making the things you care about or are interested in.
The complaint that it looks old-fashioned is addressed partly by using ttk (themed tk) but also just about every aspect of the widgets can be styled using a simple xresources-style config.
It's fast and lightweight, free forever, stable as hell, and there's lots of resources online.