Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
csl
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
csl
1y ago
Yes, I can see how it would make sense to be able to set this in pyproject.toml (typically for private package) uv is still quite new though. Perhaps you can open an issue and ask for that?
2.
▲
by
csl
1y ago
Maybe not exactly what you need (sticky) but you can set UV_NO_BINARY=1 See https://docs.astral.sh/uv/reference/environment/#uv_no_binar...
3.
▲
by
csl
1y ago
An excellent article. Bill Gates himself posted a comment: https://www.pagetable.com/?p=43#comment-1033
4.
▲
by
csl
2y ago
The way I read it, and I may be wrong, is that they will retain the _interpreted_ results, but now the raw and complete data.
5.
▲
by
csl
6y ago
boost.ai | https://www.boost.ai | Stavanger, Norway | Senior software engineer | Onsite | Full-time We are looking for a Senior Software Engineer who will boost our capacity in developing the backend services that power our worl
6.
▲
by
csl
6y ago
I did basically everything you mention, back in the day, although on a C64. In many ways, things were much easier back then: Direct access to most of the hardware, flat memory layout, smaller and vastly simpler ISAs, smaller programs (meani
7.
▲
by
csl
6y ago
Very clever and great article! But it sounds pretty easy to write a cracker for it: Just rewrite the machine code to jump over the check. Or did I miss anything? Edit: Guess it depends on the details and amount of "obfuscation" th
8.
▲
by
csl
7y ago
It appears to me that if one wants to make progress in mathematics one should study the masters and not the pupils. — N.H. Abel (1802–1829)
9.
▲
by
csl
8y ago
https://en.m.wikipedia.org/wiki/Backspace#^H
10.
▲
by
csl
8y ago
The BFR runs on a mix of liquid oxygen and methane, according to Wikipedia. Ignoring obvious scalability problems, wouldn’t it be possible to manufacture that with a pretty decent environmental footprint from various carbon neutral bio sour
11.
▲
Debugging behind the Iron Curtain
(jakepoz.com)
1 points
by
csl
9y ago
|
0 comments
12.
▲
by
csl
9y ago
Truffle + Graal looks awesome. I looked at some old ZipPy slides (JIT compiler for Python) here: http://socalpls.github.io/archive/2013nov/slides/zippy.pdf They have an example where this code is compiled:
13.
▲
by
csl
9y ago
What is your impression of libjit? It looks really nice. I've only tried GNU Lightning, and I made Python bindings for it (although, today I would have used cffi to interface with it instead of my ctypes approach, because of the header
14.
▲
by
csl
9y ago
Indeed I had already linked to your really cool project at the end. Perhaps I should have made it stand out more. The AST approach is more stable, as the Python bytecode can change between any release while the AST changes in a slower, evol
15.
▲
Show HN: Test and improve your typing speed in the terminal
(github.com)
8 points
by
csl
9y ago
|
1 comments
16.
▲
by
csl
9y ago
Anyway, I've made a follow-up post that shows how to JIT compile a subset of Python, directly based on the previous techniques: https://csl.name/post/python-compiler/
17.
▲
by
csl
9y ago
Maybe I need to reread LISP, then. I agree that SICP is laser-focused on Scheme, and thus leaves out general compilation techniques.
18.
▲
by
csl
9y ago
I do see your point, but I tried to make it clear that this is compilation in an extremely restricted sense: It specializes and executes a function at runtime. And I wanted to cover the core technique of doing just that. Perhaps I should
19.
▲
by
csl
9y ago
Is it really that friendly when starting out, though? I found it brilliant, but quite the challenging read. I'd rather just read chapters four and five of SICP [1] and move on to Queinnec as a follow-up on more advanced topics. [1]: Th
20.
▲
by
csl
9y ago
Almost always in evenings, whenever I have time and feel like it. If you're a student, you're probably hosed with deadlines, so pick very small things to try out — things like really simple interpreters. This particular project lu
21.
▲
Writing a basic x86-64 JIT compiler from scratch in stock Python
(csl.name)
325 points
by
csl
9y ago
|
50 comments
22.
▲
by
csl
9y ago
Brainfuck is simple enough that you could just write out the machine code directly in memory. I think that would make a really good exercise. I made one based on GNU Lightning to JIT. Even that can be considered a pretty huge dependency: h
23.
▲
by
csl
9y ago
Depending on how you plan to use it, a bitset may be more efficient (at least memory wise). E.g. https://gist.github.com/cslarsen/1590498
24.
▲
by
csl
9y ago
How can the results be old when the paper is from 2017?
25.
▲
by
csl
9y ago
Thanks, I see now that the whole section is very clumsily written. IIRC, a Busy Beaver may halt or not. You only care about those that _do_ halt, though, and the _champion_ is the one with the most number of 1s on the tape. The whole proble
26.
▲
by
csl
9y ago
If anyone is interested, I attempted to plot the first few Busy Beaver iterations: https://github.com/cslarsen/busy-beaver
27.
▲
by
csl
9y ago
When 23andMe took down their health reports, I reimplemented most of them myself: https://github.com/cslarsen/arv/ (I.e., arv is a newer version of the older dna-traits, which includes the actual health reports:
28.
▲
by
csl
10y ago
Note: The following is complete speculation and probably bullshit . Please correct me! I can't find the actual paper for this one. But reading an older study [0], also about TMEM106B, it seems they had already established an assoc
29.
▲
by
csl
10y ago
There seems to be a preprint on that chapter from here: http://www.hackersdelight.org/divcMore.pdf I recommend the book as well, it's got a lot of really awesome tricks!
30.
▲
by
csl
10y ago
So, a consultancy company then? Which we all know only scales with the number of employees. Most people in Europe use Gmail, right? So they must already have figured out this stuff.
More ›