dandelion9

6 ms·

1.
by dandelion9 5mo ago
Transducers don't really solve the same problem as async/await.
2.
by dandelion9 1y ago
Your cited examples all make sense in the context of the article. How is a zero-click exfiltration of sensitive data vuln not "real security"? Specialists require nuanced language when building up a body of research, in order to m
3.
by dandelion9 1y ago
Of those, scrypt or argon2id. PBKDF2 is for FIPS compliance.
4.
by dandelion9 1y ago
At a basic level any Lisp-like with an editor integrated REPL lets you put your cursor over the `greet` invocation below and evaluate it, and have the results shown in the manner of your choice (IDE window, inline temporary comment, etc). T
5.
by dandelion9 1y ago
I agree. It's career-driven bullshit bingo. It gives junior's an opportunity to gain an advantage over senior's ("Oh you don't know JavaScript micro-framework 2025 #10?") and everyone involved in billing for ti
6.
by dandelion9 1y ago
WebSockets are often blocked by corporate firewalls/proxies, I don't think it's as simple as saying WebSocket > HTTP
7.
by dandelion9 1y ago
Strong types are not orthogonal to dynamic types, but I'll assume you're referring to static typing instead. My opinion on this is static type systems are great and provide amazing fit when you can model an entire system (e.g. a c
8.
by dandelion9 1y ago
Based on the averages, a DSL is going to suck and be a curse upon your future self/maintainers. You provided a Clojure alternative, but without using the precise feature designed to alleviate this problem: transducers[0]. Transducers a
9.
by dandelion9 1y ago
Structural editing and editor-REPL integration
10.
by dandelion9 1y ago
- Dynamic languages are good, actually. IDE auto-completion and full-project renaming are the features that hit above their weight when using static type systems. IMO the remaining benefits of static types are within the same order of usefu
11.
by dandelion9 1y ago
- 90% of abstraction is dreadful. That means _your_ particular abstraction is almost certainly bad, and we don't want to learn it. - There is a lack of respect for the history of programming. IMO it has caused the industry to be stuck