Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mrkeen
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
46 ms
·
871.
▲
by
mrkeen
2y ago
20yos with max 2 weeks of experience in the job - given the inauguration date.
872.
▲
by
mrkeen
2y ago
Democrats don't have a frypan.
873.
▲
by
mrkeen
2y ago
Sources: When Musk does it: https://x.com/elonmusk/status/1858916546338590740 https://x.com/elonmusk/status/1858914228624924963 When others do it: https://www.reddit.com/
874.
▲
by
mrkeen
2y ago
Your politicians are watching from a distance too, and taking note of what works.
875.
▲
by
mrkeen
2y ago
You say "thread safe", I say "dead lock".
876.
▲
by
mrkeen
2y ago
From one point of view, yes. Another point of view is that it's a new kind of de-encapsulation. Apparently this is a 'global' variable: int variable = 0; void foo() { variable++; } void bar() { v
877.
▲
by
mrkeen
2y ago
I put it off as well, I figured precedence and associativity is something I'd learn later after I figured out how to stop my **ing grammars from looping forever. But it was right there in front of me! When I looked at someone else
878.
▲
by
mrkeen
2y ago
> It seems as if you're trying to explicitly instruct a top-down parser. My mistake, that didn't even occur to me! I only ever use parser combinators so I just read grammars as if they were the code, and vice-versa. e.g. you c
879.
▲
by
mrkeen
2y ago
I appreciate the dismissal, but I stand by what I said. I used to think 'precedence was just for removing ambiguity', so I didn't pay attention to it. Then I discovered it was the key to structuring grammars to avoid left rec
880.
▲
by
mrkeen
2y ago
Imo this missed the punchline. I banged my head on the table for days trying to fix a left-recursive grammar, just by moving bits around and hoping. The key is precedence ! Parse loose expressions first (plus, minus, etc), these loose exp
881.
▲
by
mrkeen
2y ago
Rebuttal, how do you implement interfaces in OOP languages in cases where you don't yet expect the object to exist, e.g. an interface with toString and fromString methods.
882.
▲
by
mrkeen
2y ago
Do judges decide speeding tickets and parking fines on a per-defendant basis?
883.
▲
by
mrkeen
2y ago
You're right, it doesn't. It's weird of the government to say "money is not property" in a footnote. But it's just as nonsensical for the plaintiff to argue that he (or his business?) can't be fined becau
884.
▲
by
mrkeen
2y ago
This was a fine . The plaintiff is accusing the government of being unconstitutional after being fined $38,083.20 (of unpaid wages) plus a penalty of $16,000. For: a substantial failure to comply with the recruitment and hiring of U.S
885.
▲
by
mrkeen
2y ago
Oh yeah, i definitely didn't take it seriously. worldgov.org? The title "Crypto is Inevitable" was not supported in the article. I do not believe the statement that "crypto is quietly rebuilding the plumbing of finance
886.
▲
by
mrkeen
2y ago
It's programmable enough to have bugs, and ephemeral enough to roll back state when things don't work out for the majority [1] It's like a credit card that you can't claim chargebacks on when you're defrauded, only
887.
▲
by
mrkeen
2y ago
I used both. I had a terrible time with llama, and did not realise it until I used ollama. I owned an RTX2070, and followed the llama instructions to make sure it was compiling with GPU enabled. I then hand-tweaked settings (numgpulayers)
888.
▲
by
mrkeen
2y ago
I think 70's style ACID-ish transactions are the way to go. Single-threaded reasoning safely transfers across to multi-threaded situations. Parent mentioned them above, argued that that ownership supersedes them, >>> Clojure
889.
▲
by
mrkeen
2y ago
> This has nothing to do with threading Right, but all the promises of the type system have to lead to a first-class multi-threading experience at some point. The safest concurrent program isn't a single-threaded program.
890.
▲
by
mrkeen
2y ago
Right, I was thrown by the real world terms. The ownership system (and syntax) isn't doing anything about a blocked account, it's just preventing a use-after-move, which has nothing to do with this-thread-blocks, that-thread-tran
891.
▲
by
mrkeen
2y ago
Given some Clojure function getFoo() which only calls into the Clojure std lib, and doesn't call any function with 'unsafe' (or similar) in the name, is it always true that: getFoo() = getFoo()
892.
▲
by
mrkeen
2y ago
> Java replaced this implementation in 1997 If that date's correct, they replaced it with another flawed implementation. The 'good' one came much later: https://jcp.org/en/jsr/detail?id=310 >
893.
▲
by
mrkeen
2y ago
Oh right. Enlightening! It's interesting you mention STM. That's one of the reasons I only dabble in Rust instead of switching over to it completely. In do_invalid_stuff(), block(bad_account) transfer(bad_account, good_acc
894.
▲
by
mrkeen
2y ago
> If data is (almost) always immutable, which seems to be a founding principle of Clojure Being immutable isn't some "best-practice" like eating your veggies, where the more you eat, the healthier you are, and occasional s
895.
▲
by
mrkeen
2y ago
Parent's not talking about dynamic scoping in clojure. It's a comparison to designed to elicit a reaction, e.g. "probably doing it very wrong". I.e. if you're not tracking ownership in new-lang, you're probabl
896.
▲
by
mrkeen
2y ago
Irrelevant since it's all closed anyway. Who cares if they claimed they trained it using only a paper cup and two paper-clips. Their model works exactly as well as it works, and you're not reproducing their work either way.
897.
▲
by
mrkeen
2y ago
jdkoeck is right. Storing-events-and-calculating-state is the dual of storing-state-and-calculating-diffs. It's an implementation detail, and if it works well, who cares? I personally use git as an event log. When I commit something,
898.
▲
by
mrkeen
2y ago
> Down that road lies "let's put every event in a fast message bus with higher insert volume and availability than the database, and feed that into the DB asynchronously", hence Kafka and friends. Yes, this is the way. Wh
899.
▲
by
mrkeen
2y ago
Understood, but when we look at all the databases and source-control products, we're standing on the customer side. We get to experience stuff that just works, because the people on the development side opted for write-AHEAD-log and&#
900.
▲
by
mrkeen
2y ago
That figure sounds right - if you're talking about prosecutors being punished. A survey conducted by the Innocence Project, Innocence Project New Orleans, Resurrection After Exoneration and the Veritas Initiative looked at five div
More ›