Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cdavid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
28 ms
·
271.
▲
by
cdavid
13y ago
Thanks for the correction, my wording was a bad translation from my native language.
272.
▲
by
cdavid
13y ago
I would add compare it with energy-related industries private or public . Each of Shell, Exxon, Sinopec and China national petroleum earn 3 times as much as Apple. 6/10 biggest companies by income are in oil/gas, and privately o
273.
▲
by
cdavid
13y ago
you may want to look at pandasql, where you can do something like from pandasql import sqldf, load_meat, load_births pysqldf = lambda q: sqldf(q, globals()) meat = load_meat() births = load_births() print pysqldf("
274.
▲
by
cdavid
13y ago
What a nonsense. Your facts don't even pass the smell test: around 25 % of people in age of working work as a public servant. As for the working less than possible and the comment regarding Germany: French workers work more than German
275.
▲
by
cdavid
13y ago
I am pretty sure a tweet is more than 1kb: the message itself is 140 characters, not 140 bytes, and you have lots of metadata around a tweet. I would expect easily one order of magnitude more / weet.
276.
▲
by
cdavid
13y ago
blutack, I apologize for the trouble you got with EPD. If you can spare a few minutes to explain me the pb, I will try to understand what went wrong (see my HN page for contact)
277.
▲
by
cdavid
13y ago
I only have around ~1 year of twisted experience, but I felt like the viral aspect of twisted was even worse than that. Not only everything needs to be asynchronous, but using deferred leaks everywhere in your API. Deferred callback firing
278.
▲
by
cdavid
13y ago
I am looking into B+-trees for some sparse array implementations, but little experience with b+-trees (or more advanced features). Do you have recommendation of code and papers to read besides the one already cited ?
279.
▲
by
cdavid
13y ago
Not likely because things like gc makes interoperability with other languages difficult. Pretty much every language can interoperate with C.
280.
▲
by
cdavid
13y ago
The problem is that for arrays, most non-trivial datastructures have a high cost because of indirection. Memory is already the main bottleneck in many numerical operations, and adding pointers is often terrible for memory performance. For a
281.
▲
by
cdavid
13y ago
Actually, I don't think the import * in numpy is anything else than historical artefact. Numpy just happens to be one of the oldest, still widely used python library (considering numpy started as numeric), as you point out. As for impo
282.
▲
by
cdavid
13y ago
numpy allows you to do some pretty low level stuff (like creating buffer from a raw pointer), which GAE wants to avoid for obvious security issues. Same rationale as why ctypes (parts of the stdlib) is not available. I have never used numpy
283.
▲
by
cdavid
13y ago
I was comparing LAPACK to the C library: nobody claims it is weird to use the C library, written > 30 years ago, instead of using something 'more modern'. Everybody uses the C library for system/low level programming, the
284.
▲
by
cdavid
13y ago
scipy.stats distribution objects are a bit particular, that's a bit unfair to pin point them. Generally, numpy and scipy have much better docstrings than python stdlib itself.
285.
▲
by
cdavid
13y ago
many people have been able to use numpy on clouds. You only need gcc and the python-dev package on linux. Frankly, building numpy is not very complicated (scipy is a bit complicated, and only if you are not on linux).
286.
▲
by
cdavid
13y ago
There is room for improvement, and it gets improved all the time (e.g. openblas is a recent contender). LAPACK is essentially an API for linear algebra, which is what allowed people to improve implementations and to benefit from them in old
287.
▲
by
cdavid
13y ago
Numpy does not depend on LINPACK, only scipy does (numpy only uses blas if you have one installed, it is optional). The reason why scipy (and Julia BTW) need blas/lapack is because that's the only way to have decent performance
288.
▲
by
cdavid
13y ago
numpy is quite portable, I am not sure what you mean by not nearly portable enough. The reason why you can't do pip install numpy is pip's fault, there is nothing that numpy can do to make that work. Note that easy_install numpy d
289.
▲
by
cdavid
13y ago
Docstrings are (generally)available at the runtime, comments aren't: they are bypassed early in the parsing. They are completely different beasts (in python like in other languages).
290.
▲
by
cdavid
13y ago
that's a good point, shows my European bias. In France at least, entering in medicine or decent engineer career path requires similar level of grades. Entering into a MBA would be similar to get a very good engineer degree (grade-wise,
291.
▲
by
cdavid
13y ago
Same could be said of doing a MBA or medicine compared to STEM. Yet few people on HN made that choice.
292.
▲
by
cdavid
13y ago
it is surprisingly common in my experience.
293.
▲
by
cdavid
13y ago
Thanks a lot for the detailed explanation.
294.
▲
by
cdavid
13y ago
I don't think the points you highlighted above matter fundamentally: they don't handle memory management for you, and that's the difficulty, especially at the language boundary. What is interesting for me in Lua is the stack-
295.
▲
by
cdavid
13y ago
Removing the GIL is a different problem than designing python without a GIL from the start. Preserving C API semantics (in particular reference counting) without slowing things down is the tricky part. I could be wrong, but I am not aware o
296.
▲
by
cdavid
13y ago
For interfacing with C, I think cython is better than cffi. Well, I don't have much experience with cffi, but I used to use ctypes, and cython is much better. Cffi may be nicer than ctypes, but not enough to make me switch (I may be mi
297.
▲
by
cdavid
13y ago
COW semantics of fork is not that useful with python because of reference counting (at least cpython implementation where the reference count lives inside the object memory representation). It may work much better with pypy (which uses a &#
298.
▲
by
cdavid
13y ago
I would not go as far as saying the GIL speeds things up :) Everything else being equal, I would rather not have a GIL. I don't know any efficient runtime which uses reference counting and has no GIL, and integrating C with garbage col
299.
▲
by
cdavid
13y ago
NumPy developer here. First, I agree that the "the GIL is not an issue" is an annoying meme. It can be an issue, and when it is, it is annoying as it complicates some architectures. I don't think those architectures are as co
300.
▲
by
cdavid
13y ago
If you think twisted is a solution to the problems mentioned in the OP, you haven't understood the problem. Twisted may be a solution to IO bound processes, where you do cooperative parallelism instead of preemptive (aka threads). It
More ›