delifue

7 ms·

1.
by delifue 17d ago
It's not like leftpad. It uses segmented array and interally does synchronization, not a simple wrapper to Vec. The append only takes immutable borrow. Its capability cannot be replaced by RefCell because RefCell doesn't allow app
2.
by delifue 1mo ago
The author says it's "100% accurate and free of hallucinations" but I am sceptical. Although I don't know much about chip production, when I ask LLMs about advanced topics like memory order LLMs tend to hallucinate more
3.
by delifue 9mo ago
How does static allocation avoid wasting memory? Static memory allocation requires hardcoding an upper limit of size of everything. For example, if you limit each string to be at most 256 bytes, then a string with only 10 bytes will waste 2
4.
by delifue 9mo ago
Unfortunately web API doesn't yet allow drawing multi-line text in canvas. To draw multi-line text in canvas you need a layouting library
5.
by delifue 9mo ago
Many problems in article are specific to old versions of iOS which is only in old versions of iPhone. Most old iPhone users are not potential paying customers. iOS need to be supported but old versions of iOS don't.
6.
by delifue 9mo ago
I head that Jane Street use OCaml and said similar thing. Although there are few OCaml developers they are overall better so hiring is easier
7.
by delifue 9mo ago
Key sentence Because you weren’t suffering from too much work, you were suffering from too little truly important work.
8.
by delifue 9mo ago
Not being able to store mutable ref in other type reduces expressiveness. The doc already mentions it cannot allow Iterator that doesn't consume container https://github.com/rue-language/rue/blob/trunk&#x
9.
by delifue 9mo ago
Modern large productivity software (including IDE) are often "fragile". Sometimes some configuration is wrong and it behave wrongly but you don't know which configuration. Sometimes it relies on another software installed on
10.
by delifue 9mo ago
There is nuance distinction between "fundamentally work faster" and "being pushed to work faster". The first is what to optimize. The second "being pushed to work faster" often produce bad results. https:&#x2F
11.
by delifue 9mo ago
This reminds of me Makimoto’s Wave: https://semiengineering.com/knowledge_centers/standards-laws... There is a constant cycle between domain-specific hardware-hardcoded-algorithm design, and programmable flexible desig
12.
by delifue 9mo ago
I put some article content to Pangram. Pangram says it's AI https://www.pangram.com/history/282d7e59-ab4b-417c-9862-10d6... The author's writing style is really similar to AI. AI already somehow passed Turing
13.
by delifue 9mo ago
The overuse of emoji make me suspect it's AI. I plugged first paragraph into pangram and result is 100% AI. https://www.pangram.com/history/30310094-f54b-4e74-8d68-e4c9...
14.
by delifue 9mo ago
It's probably KPI-driven. Devs are punished by any visible error. So dev hides errors.
15.
by delifue 9mo ago
It's also possible that OpenAI use many human-generated similar-to-ARC data to train (semi-cheating). OpenAI has enough incentive to fake high score. Without fully disclosing training data you will never be sure whether good performanc
16.
by delifue 9mo ago
Once a metric becomes optimization target, it ceases to become good metric.
17.
by delifue 9mo ago
React server component is frontend's attempt of "eating" backend. On the contrary, HTMX is the attempt of backend "eating" frontend. HTMX preserves the boundary between client and server so it's more safe in ba
18.
by delifue 9mo ago
Any attempt that blurs boundary between client and server is unsafe.
19.
by delifue 9mo ago
Egison is a pattern-matching-oriented language https://www.egison.org/
20.
by delifue 10mo ago
All mistakes can be blamed to "carelessness". This doesn't change the fact that some designs are more error-prone and more unsafe.
21.
by delifue 10mo ago
The biggest value of Rust is to avoid heisenbug https://en.wikipedia.org/wiki/Heisenbug Memory safety and thread safety are causes of heisenbugs. However there are other causes. Rust don't catch all heisenbug. But
22.
by delifue 10mo ago
Maybe the AI feeling is illusion because you already know it's AI-generated, just confirmation bias. Like wine tastes better after knowing it's expensive. In real world AI-generated images have passed Turing test. Only by double b
23.
by delifue 10mo ago
A nitpick about website: the top progress bar is kind of distracting (high-constrast color with animation). It's also unnecessary because there is already scrollbar on the right side.
24.
by delifue 11mo ago
The "diskless" is actually replacing disk with S3
25.
by delifue 11mo ago
Why not just use github pages for static blogs? It's free. No need to worry about extra bandwidth and other costs caused by crawlers.
26.
by delifue 11mo ago
I disagree with this > While UUIDv7 still contains random data, relying on the primary key for security is considered a flawed approach The correct way is 1. generate ID on server side, not client side 2. always validate data access perm
27.
by delifue 11mo ago
With proper data permission check, having predictable ID is totally fine. And UUIDv7's random part is large enough so that it's much harder to predict than auto increment id. If your security relies on attacker don't know you
28.
by delifue 1y ago
When reading I expected it to mention that each thread maintain thread local max and periodically sync to a global atomic can improve performance
29.
by delifue 1y ago
Can you explain what's the same underlying principle between Jevons paradox and Braess paradox?
30.
by delifue 1y ago
I think they Y axis (async/sync) should be auto-scheduling/manual-scheduling.

More ›