ibotty

72 ms·

721.
by ibotty 14y ago
one thing the article does not make clear is that there has been much enforcement by kernel hackers. but only in another jurisdiction (germany) by harald welte. see http://www.gpl-violations.org/ for (sparse) details. the news is, that no
722.
by ibotty 14y ago
the sed one is great!
723.
by ibotty 14y ago
i read the description and it mentions a vim M command. i did not know this one. it is pretty boring. then i figured maybe it's about marks, i.e. the 'm' command. now that is nice. i use firefox though...
724.
by ibotty 14y ago
i guess you make it pretty clear that you only serve people who know their stuff in your cheap offerings. that is a different audience than a "send email cards" audience would be.
725.
by ibotty 14y ago
you are certainly right with your scale, but i guess zobzu's point is, that your non-support costs (say: development) is mostly paid by your 9$ and 29$ customers (in absolute terms). so you cannot just get rid of every customer but your hig
726.
by ibotty 14y ago
incremental compilation is not foolproof either. but the q is, whether compilation speed even matters. your typical c project will spend much time in make (semi-related (to the topic and make): use redo). and if you compile with -O0 your co
727.
by ibotty 14y ago
i think that's not right. see [1] from 2009 for a figure on haskell adoption. (but you are right, in that adoption plays a crucial role in adoption ;).) [1]: https://research.microsoft.com/en-us/um/people/simonpj/paper...
728.
by ibotty 14y ago
is there any good comment in the thread? usually stackoverflow tends to give good answers. but i am as puzzled as before (and stick to my intuition which happens to say singular).
729.
by ibotty 14y ago
something changed, indeed. djb vs. usa: https://en.wikipedia.org/wiki/Bernstein_v._United_States
730.
by ibotty 14y ago
i read a few days ago about a large-scale-y investigation about "obfuscated" and real email-addresses. it seems that it is better to just write me@example.com instead of me(at)example.com as you can find the second pattern through google qu
731.
by ibotty 14y ago
yes. and macros are so easy to use. i usually start a macro before i really know how i am supposed to do it. it's just a "do it for this one occurence" but prepended by qa and ended by q. well i will have to move the cursor to the right spo
732.
by ibotty 14y ago
"except for things like Unicode" cannot be emphasized enough! working unicode handling also for corner cases is extremly important in a unixy text-passing world.
733.
by ibotty 14y ago
now that's nice. i did not notice, as it depends on javascript. but very nice! something to copy i guess ;). (that alone is worth the article. the "real" content is just misunderstanding of unix i'm afraid)
734.
by ibotty 14y ago
nice summary of shortcomings. but for me the biggest one is missing: highly special search queries (yesterday: about erlang, rebar and obscure release building failures) return virtually no usable results. google was way better. somehow rel
735.
by ibotty 14y ago
"- Don't use question marks in a resource URL (.css?v=234)" why? if you get the cache headers right, this is the way to go to let it cache forever. that's a nice thing. (i don't really get why they do not use a caching proxy in front, there
736.
by ibotty 14y ago
already happening. not for a short time.
737.
I've been a terrible person (and so have most of you)(mjg59.dreamwidth.org)
2 points by ibotty 14y ago|0 comments
738.
by ibotty 14y ago
not everyone agrees with linus. ingo molnar supported peter zijlstra. with facts. something linus always wants but usually is too busy delivering (ehem..). "the result of these commits is: 24 files changed, 417 insertions(+), 975 deletions
739.
by ibotty 14y ago
there is progress on this. the bulk of this bug (these bugs) should have been fixed one or three releases ago. there was a lwn article about it.
740.
by ibotty 14y ago
address space randomization (i can dig out a post of (afair) solar designer that goes into more detail, but i think this should be clear as is)
741.
50 Ways to Wreck the Network(lauren.vortex.com)
2 points by ibotty 14y ago|0 comments
742.
by ibotty 14y ago
nice article. but isn't it more work to hide the content from js-disabled-browsers? so why do it?
743.
by ibotty 14y ago
(not very informative, but..) i am not the one who did the blog post. i just found it interesting (reasons stated somewhere else). so i cannot answer any questions about it.
744.
by ibotty 14y ago
breaking news: even an old version of postgres used badly is not that slow.
745.
by ibotty 14y ago
of course that post is not best practice for a sql-database search and not optimized at all. what it shows is that even then, on a single host, a sql database is within limits to nosql databases.
746.
Postgresql vs mongodb(blog.pingoured.fr)
55 points by ibotty 14y ago|50 comments
747.
by ibotty 14y ago
not spectacularly new and exciting but with a few useful links (if your favorite webservice blocks a few disposable email services). thanks for posting.
748.
by ibotty 14y ago
what's the news here? that's only advertisement, isn't it?
749.
by ibotty 14y ago
"Nearly all my 30-plus investors responded immediately with enthusiasm and congratulations, and many of them also offered to help [...]" i certainly did not expect this. i'm always pessimistic about gender issues in the real world. maybe i
750.
by ibotty 14y ago
usually a different websocket port. not what you wanted to hear i guess :|.

More ›