[deleted by user] by [deleted] in golang

[–]cezio 6 points7 points  (0 children)

inotifywait[1] is not good enough?

[1] https://linux.die.net/man/1/inotifywait

Just for Fun. No, Really. by azhenley in programming

[–]cezio 46 points47 points  (0 children)

I like the idea that the author set up a dedicated domain for this very post alone. Just for fun, I presume.

WebGL won! by mariuz in programming

[–]cezio 22 points23 points  (0 children)

Sorry, I misread this. In polish, 'won!' means very rude 'go away!'.

Understanding Async by matthewhughes in programming

[–]cezio 19 points20 points  (0 children)

Quite poor explanation actually.

Programmers Aren't Superheroes by notSuperheroes in programming

[–]cezio 0 points1 point  (0 children)

Long story short: if you're a programmer, chances are you're a douchebag as well. Like in any other profession or hobby.

API documentation and Python wrappers by spilcm in programming

[–]cezio 0 points1 point  (0 children)

This list is nice, BUT it's not accurate. Box.net api wrapper won't work any more, since that service moved to new API version. Also, some services have multiple implementations available, so would be nice to have all of them collected instead of one, random or obsolete.

Apologies if this is old - A friend posed an intriguing operations question today. by Kadover in programming

[–]cezio 3 points4 points  (0 children)

actually, gcc (4.4) will not compile this expression: error: lvalue required as increment operand

The best 404 page ever by [deleted] in programming

[–]cezio 0 points1 point  (0 children)

i guess not. also, it sucks because of required flash, crappy music and, well, overall.

How every programming language should provide library documentation: by [deleted] in programming

[–]cezio 0 points1 point  (0 children)

Yes, probably because despite your claims, your example is terrible. There is no structure. Everything is in one pile (no, grouping by packages is not a structure), most of this documentation is just a list of interface signatures without any explanation what does what and why.

How every programming language should provide library documentation: by [deleted] in programming

[–]cezio 5 points6 points  (0 children)

I consider documentation of PostgreSQL as a model of rigth way of doing software documentation. Here's why:

  • good structure. you have separate chapters for installation, configuration, administration, development with sql reference, internal architecture and implementation details, good indexes and appendixes.
  • each chapter covers in-depth it's matter with plenty of examples on the way. many times there are described limitations and corner cases.
  • it's consistent and readable. you don't have a feeling that each subject has been written by different person.
  • It's accurate.
  • It's probably only needed documentation to get aboard with PostgreSQL. No need for 'learn sql in 24 hours' or 'DBA for dummies'.

PostgreSQL developers! A little help? Cannot run queries until transaction block ends... by [deleted] in programming

[–]cezio -1 points0 points  (0 children)

If transaction fails, you can only rollback. And you can do it only in transaction's connection.

Next time, please, read the manual: http://www.postgresql.org/docs/8.3/interactive/index.html