pwm

11 ms·

61.
by pwm 6y ago
> Why is receiving $0.001 a matter of urgency that can't wait until tomorrow? I'm not making a value judgement whether this is utopian or dystopian but imagine streaming money. Instead of paying for the use of something in adva
62.
by pwm 6y ago
> Long term this kind of thing will lead to new jobs and decent wages that force technological innovation because businesses and the politicians they employ can't push costs down by importing cheap labour. It would make me happy to
63.
by pwm 6y ago
Do you think brexit will solve this?
64.
by pwm 6y ago
Single datapoint: The last time I posted a job ad (I was the hiring manager) I got ~40 good applicants within a week. I expected much less and got pretty overwhelmed.
65.
by pwm 6y ago
Just the other day i was doing something with LogicT where QualifiedDo would have been super handy.
66.
by pwm 6y ago
When I travelled to Tanzania circa 2011 I had to have a yellow fever shot. Nothing new here from what I can tell.
67.
by pwm 6y ago
hlint rules are nice for enforcing this, eg. you put sg. like this in your .hlint.yaml: - modules: - { name: [Data.List], as: List } - { name: [Data.Map, Data.Map.Strict], as: Map } and then you get a hlint warning if you
68.
by pwm 6y ago
Depends on the use-case. Bitcoin's current zeitgeist is digital gold/store of value and from that point of view deflation is a strength that complements inflationary currencies.
69.
by pwm 6y ago
The fundamental point of bitcoin is that you don’t need banks. Whether that’s good or bad will be debated for years to come.
70.
by pwm 6y ago
I haven't yet looked much into effect systems so can't really talk about them but I think even with something like MTL you can achieve a decent level composability/modularity where you build up a library of capabilities that
71.
by pwm 6y ago
> However, that doesn’t necessarily imply an all-or-nothing approach where either you’re in a pure function or you can do anything with anything. To elaborate this point I'd say that the most important practical use of all that &quo
72.
by pwm 6y ago
> Forcing someone to write iFoo instead of foo isn’t type safety, but it’s a certain kind of safety The term I'd use (at least from the top of my head) is hygiene. The article uses the word safety in a restrictive sense, ie. prevent
73.
by pwm 6y ago
Interestingly Satoshi wrote about the similarities between bitcoin and gold/precious metals multiple times, eg. [1], [2]. I guess it's not black and white and maybe bitcoin organically transitions from digital cash to digital gold
74.
by pwm 6y ago
My pet theory is that they both require perseverence to get to a fun level and once there doing it provides intrinsic reward.
75.
by pwm 6y ago
I agree. Which language you use defines which editor/ide suits it best.
76.
by pwm 6y ago
> compositional and performance advantages Compositional sure, but performance? Care to elaborate?
77.
by pwm 6y ago
To be fair that is a JSON parse error.
78.
by pwm 6y ago
I’m not convinced either if it can become currency but in my opinion if it will only ever become digital gold, an arguably superior version of physical gold, it’ll already be a great achievement.
79.
by pwm 6y ago
> `fmap _ (Leaf v) = Leaf (f v)` right? (s/v/f v) Compare the Functor instances of the original inductive Tree type with TreeShape a: instance Functor Tree where fmap :: (b -> c) -> Tree b -> Tree c f
80.
by pwm 6y ago
Let's try to make this a tad less abstract with a (hopefully) more practical teaser: 1. Let's define a simple binary tree and a (recursive) function to process it: data Tree a = Leaf a | Node (Tree a) (Tree a)
81.
by pwm 6y ago
> If you build a language that is based around doing everything with stateless data transformations but doesn't address state and branching, it will eventually be a problem I'm assuming you are referring to Haskell? It's a
82.
by pwm 6y ago
Hm, what's the issue with state and branching?
83.
by pwm 6y ago
Anyone curious about the core abstractions and capabilities of build systems should read the amazing Build Systems à la Carte paper: https://www.microsoft.com/en-us/research/uploads/prod/2018/0... H
84.
by pwm 6y ago
My audiophile friends would vehemently agree with this statement :)
85.
by pwm 6y ago
> Rust is a compiled language So is Haskell. What I'm saying is that in 2020 the dev workflow is not: code, compile, run, repeat. Thanks to modern tooling it is now a near-instant feedback loop of: code, red wiggly line(s), fix, rep
86.
by pwm 6y ago
I think we are on the same page. I also write Haskell for food. What I'm saying is that if you write Haskell professionally and types slow you down, ie. you always try to come up with the best possible abstraction for everything, then
87.
by pwm 6y ago
I’m not familiar with Rust’s tooling but i’m wondering whether the dev workflow involves explicit manual recompilation? Eg. in Haskell modern workflows are about conversing with the compiler real-time ie. make a type error and it is immedia
88.
by pwm 6y ago
This is spot on.
89.
by pwm 6y ago
There are expressive type systems around, it’s the industry at large that needs to use them more and educate future generations on why these are useful tools. I 100% agree that spending 2 days on that task is lunacy. But imagine if youcould
90.
by pwm 6y ago
This misses the point of why expressive type systems matter. Beginners and hobbyist (and i’m using these labels in the best possible sense) play with these things, push bounderies, etc... Professionals (in the literate sense, ie. people get

More ›