djanowski

8 ms·

31.
by djanowski 11y ago
Thank you!
32.
by djanowski 11y ago
\o/ Thank you!
33.
by djanowski 11y ago
Yes, you're right that most frontend developers already rely on Node for various tasks. This would be most helpful for those who still haven't introduced Node as a dependency and trying hard to get away without it :) In any case,
34.
by djanowski 11y ago
Most importantly: it's very easy to end up with a huge CSS file that can't be compressed, and it makes everything more complicated. Representing hierarchy in the class name makes the output shorter, in most cases, and makes the HT
35.
by djanowski 11y ago
That's awesome. Let's keep in touch :)
36.
by djanowski 11y ago
Both Less and Sass implement features that I consider anti-patterns: nesting, @extend, etc. Sure, you can ignore them, but there's a lot of code in the tool to support that. The code needs maintenance and puts the barrier of entry high
37.
by djanowski 11y ago
I don't think you read the top section of the README. It clearly says that I was first looking to write a simpler CSS preprocessor, and then came across M4. I'm not saying the tool I wrote will replace all preprocessors. My po
38.
by djanowski 11y ago
Thank you!
39.
by djanowski 11y ago
It's true. sassc(1) is a great step forward in terms of speed. That said, Sass encourages practices that I consider bad. Nesting, @extend, etc. Sass's design also makes it difficult to implement a basic feature like grouping all m
40.
by djanowski 11y ago
That's... a really good question. I added instructions in the README: https://github.com/djanowski/hasp#installation Thank you!
41.
by djanowski 11y ago
> Cool hack! Thanks! > Why did this horrible language become so popular? Why has it not been replaced? I don't know. Maybe just like other tools in POSIX systems -- it works :)
42.
by djanowski 11y ago
You're right. I didn't mean to say sourcemaps are useless. For now, they were a trade-off. It'd be interesting to see if they can be added using M4.
43.
Show HN: Hasp – A minimal CSS preprocessor using the M4 macro language(github.com)
72 points by djanowski 11y ago|42 comments
44.
by djanowski 11y ago
By the way, antirez is already working on a lazy deletion of large objects: http://twitter.com/antirez/status/626406286083670016
45.
Thanks Pivotal, Hello Redis Labs(antirez.com)
347 points by djanowski 11y ago|36 comments
46.
by djanowski 11y ago
Already using Quip for Mac, loving it. Great job.
47.
Show HN: Twisque, a tweet-later experiment using Disque on Heroku(twisque.herokuapp.com)
10 points by djanowski 11y ago|0 comments
48.
by djanowski 11y ago
I would say that Disque follows the minimalistic philosophy of Redis. However, Disque is a specialization of one of the most common use cases of Redis: queues. So I wouldn't expect so many primitives--Disque knows about jobs and queues
49.
by djanowski 11y ago
And there's a Ruby client for it already: https://rubygems.org/gems/disque
50.
by djanowski 11y ago
And there's a Ruby client to start playing with it: https://rubygems.org/gems/disque
51.
by djanowski 11y ago
There's some extra background here: http://antirez.com/news/88
52.
Redis author just released Disque, a distributed message queue(github.com)
77 points by djanowski 11y ago|2 comments
53.
by djanowski 11y ago
Looks good. Add yourself to http://redis.io/clients .
54.
On software popularity(soveran.com)
140 points by djanowski 12y ago|71 comments
55.
by djanowski 17y ago
Cool, I'll try to make it. Also – there's an Open House at Cowork Central this Wednesday, so feel free to join us: http://eventioz.com/events/open-house-jelly
56.
by djanowski 17y ago
:-) Fortunately they changed their minds and gems are auto-approved now, so the barrier is still there, just a little bit easier to lift ;-) Again, GitHub rocks. We tried to create a simple script to make it easier for us to also deploy to
57.
by djanowski 17y ago
Exactly! We've been doing the same thing – releasing only to GitHub because it's so easy and fun (and easier now that they e-mail you when the gem fails to build...) The idea behind Joe is that if you're already releasing to GitHub, it's re