Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
timhh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
timhh
1y ago
Explanation of Bradley-Terry here: https://stats.stackexchange.com/a/131270/60526 It's such a great and simple algorithm. I feel like it deserves to be more widely known. I used it at Dyson to evaluate really
62.
▲
by
timhh
1y ago
I mean... you can probably see why they don't spend any effort on that.
63.
▲
by
timhh
1y ago
I have a C library (I've also done a Python one in the past) that you load into the executable you want to debug. It activated based on an environment variable so normally I just permanently link it. When it is loaded it will automatic
64.
▲
by
timhh
1y ago
Yeah I agree - in fact I ran into this very issue only hours ago. The entire error message was literally "operation not supported on this platform". Yeay. https://github.com/rust-lang/rust/issues/141
65.
▲
by
timhh
2y ago
I don't think anyone disagrees with that, but 80 characters is clearly waaay too restrictive. I think 120 is much more reasonable.
66.
▲
by
timhh
2y ago
> We count about 40% of our security vulnerabilities to date to have been the direct result of us using C instead of a memory-safe language alternative. This is however a much lower number than the 60-70% that are commonly repeated, orig
67.
▲
by
timhh
2y ago
It is possible to survive the lunar night. See https://space.stackexchange.com/a/67918/40677
68.
▲
by
timhh
2y ago
No, I mean why can't you select commits in the graph and copy/paste them. I wasn't talking about copy/pasting the lines of text in the `git rebase -i` file.
69.
▲
by
timhh
2y ago
I meant any variation of `git log --graph`.
70.
▲
by
timhh
2y ago
`git log --graph` is just a really really bad GUI. Why not use a good GUI instead? Although in fairness it's quite hard to find a good Git GUI because there are so many bad ones. The only good ones I've found all have some kind of
71.
▲
by
timhh
2y ago
Yeah... how long do you think librewolf is going to survive if Mozilla dies?
72.
▲
by
timhh
2y ago
That's fine until you have to ask a question that isn't answered anywhere on the internet. Then you post a perfectly reasonable question and get it downvoted to hell... https://stackoverflow.com/q/79461875
73.
▲
by
timhh
2y ago
> PR_SET_CHILD_SUBREAPER I wrote a tool that does just this: https://github.com/timmmm/anakin If you run `anakin <some command>` it will kill any orphan processes that <some command> makes. However is st
74.
▲
by
timhh
2y ago
Not e-ink though so the display isn't always-on and you need a power supply. This can hang on the wall and you just have to recharge it every few months.
75.
▲
by
timhh
2y ago
> Give me wifi, e-ink display, and the ability to write a regular program that writes unicode chracters to STDOUT (and have that rendered to the display) and I'll give you my money right now. I bought an Inkplate 10 from eBay for li
76.
▲
by
timhh
2y ago
So you have to already have all the linters installed? Ok I am planning to solve that problem too, but we'll have to see whether it's actually possible to compile e.g. rustfmt to WASI. In my experience so far WASI is pretty alpha
77.
▲
by
timhh
2y ago
I don't really understand. Pkl seems to be a configuration language? How are you going to run clang-format, rustfmt, go fmt, pyright, etc. using Pkl?
78.
▲
by
timhh
2y ago
Yes. Those are both more effort and less reliable than what I am planning (a static binary with WASI plugins).
79.
▲
by
timhh
2y ago
Interesting. I've been working on a pre-commit replacement too, written in Rust but using WASI for all plugins (no exceptions!). I haven't got very far but I think this will have huge advantages over pre-commit, mostly in reliabil
80.
▲
by
timhh
2y ago
Maybe they're not implying this kind of limited dependent type system but surely it is still dependently typed? It's just not the "full fat" dependent typing. Another example of a language with limited dependent typing i
81.
▲
by
timhh
2y ago
Clever. You can see how it works by looking at the shadows of her hand. The "shadow" from the big cylinder is fake; it's actually printed on.
82.
▲
Reasons to Avoid Git Submodules
(blog.timhutt.co.uk)
3 points
by
timhh
2y ago
|
0 comments
83.
▲
by
timhh
2y ago
The people I am referring to are not helping. At this point they are making SO worse. The problems are two-fold: 1. Any community with volunteer moderators attracts the kind of people you don't want to be moderators. They enjoy rigidly
84.
▲
by
timhh
2y ago
I disagree. It was useful because the UI was (and is!) great. Easy to use markdown input, lists of answers sorted by votes, very limited ads, etc. The gamification was also well done. Compared to anything before it (endless phpBB forums, ex
85.
▲
by
timhh
2y ago
Stackoverflow mods and power users being arseholes reduces the use of Stackoverflow. ChatGPT is just the first viable alternative.
86.
▲
by
timhh
2y ago
Maybe you could if you weren't clearly intending this as a way to violate copyright. It still isn't a magic copyright eraser. The law doesn't fall for mathematical "aha but!" tricks like HN commenters assume it does
87.
▲
by
timhh
2y ago
No you can't, any more than you can encode a Disney film as a prime number or in the digits of pi and avoid copyright that way. Read this classic essay: https://ansuz.sooke.bc.ca/entry/23
88.
▲
by
timhh
2y ago
(2022)
89.
▲
by
timhh
2y ago
Difficult to draw conclusions with no code here. An interesting thing they didn't mention is that Matplotlib's point-in-path code is actually already in C. So this isn't really a case of Rust being X times faster than Python,
90.
▲
by
timhh
2y ago
Maybe it's just me but I just use a proper debugger. Debugpy and VSCode work fantastically. In a previous company I set things up so that when there's an uncaught exception it will automatically start a VSCode debug session and co
More ›