hoodunit

7 ms·

1.
by hoodunit 8y ago
TS/Flow don't quite lose types "whenever" partial application or currying is involved, it's a bit more subtle than that and in many cases it works fine. But especially when using generics with currying you often hav
2.
by hoodunit 8y ago
No, that is exactly correct. The brunt of the argument applies to most popular languages- Java, Python, Ruby, and what have you- although the specifics vary.
3.
by hoodunit 9y ago
You can get exhaustiveness checking in some cases in TS by adding a default statement to a switch and assigning the value to type 'never'. This is a bit cumbersome, of course, and the fact that it's opt in partly defeats the
4.
by hoodunit 9y ago
Naming closures or functions absolutely is a good substitute for a large class of comments. When you write a comment as a function name, that comment gets maintained when the code changes. It also encourages modularizing your code- often wh
5.
by hoodunit 9y ago
Yes, it's fun. I wrote a wrapper for playing Screeps with PureScript and a blog post about it here: http://blog.ndk.io/purescript-ffi.html .
6.
Refactoring 30000 lines of JavaScript with types(reaktor.com)
2 points by hoodunit 10y ago|0 comments
7.
by hoodunit 10y ago
Are you referring to the Data Retention Directive [1], which was invalidated in 2014? Or are there still other EU-wide laws on data retention? [1]: https://en.wikipedia.org/wiki/Data_Retention_Directive
8.
by hoodunit 10y ago
Part of the issue is that legally in the U.S. a) privacy violations are usually punishable by law only if a specific non-privacy harm comes of it and b) privacy is treated as an individual right and not a societal good. If a company gets ha
9.
by hoodunit 10y ago
Which specific ones, for example? "Every one" could cover a lot of ground and doesn't have much information content. It's doubtful you have experience in every one, and it would be useful to know which specific ones have
10.
by hoodunit 10y ago
This is what makes me wonder, is there actually a steep age bias and drop-off of older developers or are we just living a demographics change? I'm guessing there are far more developers today than ten or twenty years ago. When those de
11.
by hoodunit 10y ago
PureScript compile times have been quite good for me in the last two versions or so, so there has been some improvement there.
12.
by hoodunit 10y ago
One area in which Flow may be "technically" sound but it feels illogical is how in how it infers certain types. TypeScript requires that a variable has one type that doesn't change, but Flow will infer multiple types for a va
13.
by hoodunit 10y ago
I actually found the opposite was true in our project - TypeScript was easier to add into the code than Flow. The biggest reason for this was that Flow demands null/undefined checking and null was used extensively throughout this code
14.
by hoodunit 11y ago
I admit the claim is overly grandiose, especially in this particular case where there's still a decent gap between core.async and CSPM. If one generated Haskell code directly from CSPM it might be a stronger claim for that, but I haven
15.
by hoodunit 11y ago
The go blocks in here are really ugly, but to be honest I just found it difficult to refactor in this particular case. The issues were a) I wanted all the events in a single event loop to make timing issues clear and to fit the model semant
16.
by hoodunit 11y ago
To clarify my statement: the idea of lean Clojure for making Clojure viable for Android development basically works. More static compilation of vars dramatically reduced startup times; I think further "lean Clojure" changes like d