141 karma · joined August 23, 2011
Just as unfortunate as how Python turned its back to Mercurial
During the next few years, other sellers joined the trend pushing it even more.
This year, in order to stay competitive, Amazon Spain has been "forced" to follow the trend and have a Black Friday WEEK.
I had similar motivations in 2006 to write a tool to copy files "point to point". So here's my shameless plug:
https://bitbucket.org/etanol/canute
In my case, cryptography was not a requirement, though.
https://github.com/kennethreitz/maya/blob/d57a78c6bc6b5295f7...
And i18n support in humanize is a bit lacking, as it only translates to French, Korean and Russian. Given that most of the translations needed to render human dates can be found in the CLDR database, maintaining their own looks like a bit of a wasted effort.
Reference:
* Audio: speaker controls tone, speed and emphasis
* Video: body language
* Feedback: listener can acknowledge reception or ask for repetition
Written language has more time to be composed and it usually has the possibility of being ammended before submission.
Therefore, I always considered natural the difference between spoken and written language styles.
On a less picky opinion: agreed, complex ideas should not be written in complex language.
https://github.com/replit/empythoned
It's a pity it didn't get more traction. The effort invested seems a bit more worthwhile.
I bet not many people have the guts to call themselves mechanical engineers just because they know how to fix the break pump of a car, for example.
I want to believe that the blame is on the image thumbnails on the Desktop or some folder that is difficult to circumvent. But still, such privacy violation and lack of professionalism from the technicians is not ever mentioned again in the OP.
I prefer Mercurial because is much easier to use but this file rename issue always make me feel uncomfortable when reorganizing code.
These days I'm giving Fossil a try, which still is easier to use than Git and the repository size sits between Git and Mercurial.
SQLAlchemy's issue repository will remain hosted on Trac;
while a Git repository can be mirrored in any number of
places, an issue repository cannot (for now! Can someone
please create a distributed issue tracker? Should be
pretty doable, though getting Github/Bitbucket to use it,
not so much...), so SQLAlchemy's long history of issue
discussion remains maintained directly by the project.
http://fossil-scm.org !!!http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...
http://en.wikipedia.org/wiki/Girls_Just_Want_to_Have_Sums
Hence my whining. I hope I'm very wrong.
It's kind of embarrassing.
http://www.bourkedesign.com/wp-content/uploads/2010/10/ie-po...
«An asynchronous, event-driven architecture based on
highly optimized coroutine code scales across multiple
cores and processors, network cards, and storage systems.»
It may be a dumb question, but isn't this statement a bit contradictory? As far as I understand, event-driven design and coroutines (i.e. cooperative multitasking, lighweight threads, etc.) are the techniques usually chosen to AVOID concurrency.How does such a design imply multicore scalability? Obviously, coroutines and event loops don't prevent you from running in multiple cores. I just fail to see the correlation.
Now seems that software is taken for granted, e.g., you download TCP/IP Arduino implementations to connect your circuits to a LAN.
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stabl...
You can try it if you want, save this into an executable file (test.awk):
#!/usr/bin/env awk -f
{ print $2 }
Then run: echo "Hello world again" | ./test.awk
I get the following: /usr/bin/env: awk -f: No such file or directoryAnd, by the way, I think the comment at the bottom of page 27 is not correct:
The qualifier const can be added to the left of a variable or parameter type to declare that the code using the variable will not change the variable. As a practical matter, use of const is very sporadic in the C programming community. It does have one very handy use, which is to clarify the role of a parameter in a function prototype...
Actually, the use of const is encouraged as it helps the compiler to catch more errors as well as to enable some optimizations.