slikts

5 ms·

1.
Deno is probably not worth it(dev.to)
4 points by slikts 6y ago|0 comments
2.
Up-to-date overview of JavaScript and TypeScript tooling(tooling.js.org)
2 points by slikts 7y ago|0 comments
3.
Advanced Memoization and Effects in React(gist.github.com)
2 points by slikts 7y ago|0 comments
4.
React.js: Why using the `children` prop makes `React.memo()` not work(gist.github.com)
2 points by slikts 7y ago|0 comments
5.
by slikts 7y ago
Recursion is a powerful, relatively low-level approach, and the price for expressive power is readability, but it has legit use cases. What you said has a grain of truth in that usually you should prefer combinators like map or filter (if y
6.
by slikts 7y ago
Without modules there can be dependency hell: conflicting subdependency versions, unless all your dependencies update their subdependencies in lockstep.
7.
by slikts 7y ago
You mean statically, not strongly typed. Strong typing roughly means avoiding implicit type coercion.
8.
by slikts 7y ago
This is a common straw man; PHP 5 and 7 made large strides, but that's because there was so much to fix, and there still is and will continue to be, like lack of first class functions, actual modules, etc. PHP is also unsuitable for pe
9.
by slikts 7y ago
Never, since PHP is fundamentally flawed, and trying to redesign it would make the split between Python 2 and 3 pale in comparison. PHP's main selling point is backwards compatibility and the existing ecosystem; a fundamental redesign
10.
A case for using `void` in modern JavaScript(gist.github.com)
3 points by slikts 7y ago|0 comments
11.
by slikts 8y ago
I'll rework that section; thanks for the feedback.
12.
by slikts 8y ago
"Very slightly" means that I shared that I'd submitted it here; realistically a couple of upvotes could have come from that, but I don't know. The talk about botnets and whatnot is just hyperbole. You inferring alternati
13.
by slikts 8y ago
The wording is indeed pretentious, hopefully improved in future iterations.
14.
by slikts 8y ago
It's a major recurring theme; for example, anything that refers to implicit or explicit is part of it. The list you quoted is a placeholder to be elaborated.
15.
by slikts 8y ago
Asynchronicity is just how sequential models are extended to support concurrency. Parallelism and concurrency are orthogonal, so a concurrent model can be executed in parallel.
16.
by slikts 8y ago
That looks nice, but Python is an odd choice for studying synchronization primitives considering it has the GIL.
17.
by slikts 8y ago
You're right, I qualified it with "classic JVM threads", but a less ancient example would be better; it's just not immediately clear which green thread implementations are also relatively heavyweight like JVM green threa
18.
by slikts 8y ago
That's some fevered imagination.
19.
by slikts 8y ago
The trade-offs of locks are accidental locking like deadlocks; message passing removes this trade-off but is less flexible, and dataflow further constrains the use of explicit synchronization. It's part of the larger argument for decla
20.
by slikts 8y ago
Thanks, and yeah, the part about lightweight threads stands to be expanded. Other missing parts are reactive vs interactive, linearizable vs serializable and push vs pull.
21.
by slikts 8y ago
The relations could definitely be made more clear, but if you could point out what specific terms you find unrelated, I could explain how they fit together. The basic organization is working up the ladder of abstraction; for example, schedu
22.
by slikts 8y ago
For what it's worth, the feedback I've had so far elsewhere suggests that there aren't particular inaccuracies. A somewhat contentious part is defining concurrency in terms of order independence, but the main source for that
23.
Concurrency Glossary(slikts.github.io)
197 points by slikts 8y ago|28 comments
24.
by slikts 8y ago
The implicit coercion rules don't matter if you make sure to convert the types explicitly, but then you're just relying on your discipline. You might be able to pull it off individually, but it starts mattering more when working w
25.
by slikts 8y ago
You can't remove JavaScript features without breaking websites. The one exception was when the strict mode pragma was added, but that was a one-off, and there's too much resistance now to add more pragmas (they tried that with &qu
26.
by slikts 8y ago
The issue there is that TS allows dropping out of the type system with `any`, so it might not actually be checking the types you're comparing, so I'd still use ===.
27.
by slikts 8y ago
It's idiomatic to use == to check for both null and undefined at least. A lot of people seem to have a perception of languages as being handed down by some language gods, and apparent problems with the language get explained away by &q
28.
Show HN: A game that pits your sanity against JavaScript's == operator(slikts.github.io)
4 points by slikts 8y ago|2 comments
29.
by slikts 8y ago
Odd to post something you haven't made as "Show HN".
30.
Show HN: Code Minimap for GitHub (Browser Extension)(github.com)
4 points by slikts 8y ago|0 comments

More ›