bluepnume

11 ms·

91.
by bluepnume 5y ago
My advice is to get it in front of others as soon as possible. Even if it's just mock flows, it's fantastic getting feedback and even lining up real customers who are ready to onboard when you first launch. We've been doing a
92.
Ask HN: Fundraise for a side-project, or go full-time first?
3 points by bluepnume 5y ago|4 comments
93.
by bluepnume 5y ago
Classes are fine so long as: - They're small and single-purposed - They don't inherit (or at the very least, extremely light inheritance) - There's a very clear relationship between the state and the methods (e.g. a counter c
94.
by bluepnume 5y ago
A malicious PR could also add the character to your eslintrc too though. You'd be forgiven for seeing the line change in the diff and thinking it was just some reformatting.
95.
by bluepnume 5y ago
I was a Flow holdout for the longest time. TypeScript's support for discriminated unions is one of the things which finally won me over. Super glad to see it being improved upon here.
96.
by bluepnume 5y ago
IFrames are both terrible and awesome. I built and maintain zoid, which turns iframes into full-fledged components; it's been an adventure: https://github.com/krakenjs/zoid
97.
by bluepnume 5y ago
Probably pick a different hill to die on. The meaning of "REST" in common parlance is now just HTTP+JSON, nothing more. At best, the url might represent a noun.
98.
The Magic of Serializing Functions(bluepnume.medium.com)
1 points by bluepnume 5y ago|0 comments
99.
by bluepnume 5y ago
I didn't spot any regexes here.
100.
by bluepnume 5y ago
If the objective is to get the maximum 'visual' difference for two hashes, why not re-hash both of them first? That results in any small changes causing a huge difference in the final outputs.
101.
by bluepnume 5y ago
I agree with you, it's definitely a trade-off between developer ease and perf. I get around that in js mostly by avoiding classes and `this` entirely unless I'm sure I'm going to have a large number of instances of something.
102.
by bluepnume 5y ago
I would rather re-implement `filter` in a way that is specific to `Foo`, than to attempt to use an array method on my class.
103.
Functional-Ish JavaScript(bluepnume.medium.com)
1 points by bluepnume 5y ago|0 comments
104.
by bluepnume 5y ago
Right. If NodeList is compatible with Array methods, it honestly feels like it should just inherit those methods. Or implement them separately.
105.
by bluepnume 5y ago
`Array.prototype.slice.call(arguments)` can be replaced with `Array.from(arguments)` (or as you mentioned `[ ...arguments ]`)
106.
by bluepnume 5y ago
My advice is to start of with javascript by forgetting 100% about classes, inheritance, prototypes, and so on. Just use vanilla functions and objects, and when in need of something that looks like a class, reach for the revealing module pat
107.
by bluepnume 5y ago
The fact that NodeList doesn't have a native map feels to me like a wart, and doesn't really justify `Array.prototype.map.call` having to exist as a fallback in the language.
108.
by bluepnume 5y ago
Very interested to learn more about this use case. This is to protect against hostile environments blocking function calls by polluting prototypes? I do a lot of work on SDKs which run in semi-hostile environments, so prototype pollution is
109.
by bluepnume 5y ago
> in x.y.f(), f() operates on x.y Yep, and I think that determining `this` at the call-site is really awful, and has been the cause of many more bugs than is reasonable. OOP you can do in JS with just `class` and `extends`, you no longer
110.
by bluepnume 5y ago
I've worked full-stack in javascript for many years, and I've written plenty of libraries and tooling. I've used call/apply/bind/this extensively and I understand them to a fault. I would still remove them in f
111.
by bluepnume 5y ago
You have my full agreement. You can write great javascript without ever touching prototypes, and probably even avoiding inheritance altogether unless you have a really succinct use-case.
112.
by bluepnume 5y ago
Sorry, yeah, I did allow for closures inside class methods with that statement. That's fine by me.
113.
by bluepnume 5y ago
Show me some code you can only write using either call, apply, or bind.
114.
by bluepnume 5y ago
Call, bind and apply should be discarded and forgotten about, they add too much confusion, there are better ways, and they end up being used as terrible interview questions. Incidentally, we should also discard `this`, unless directly insid
115.
by bluepnume 5y ago
Before you post a comment about Bitcoin fees, please take a little time and try out lightning. It's come an incredibly long way, it's very fast, and very cheap, and very easy using a mobile wallet.
116.
Learning about Bitcoin by building it in JavaScript(bluepnume.medium.com)
6 points by bluepnume 5y ago|0 comments
117.
Fooled by Certainty: A short counter of Taleb's Bitcoin analysis(bluepnume.medium.com)
5 points by bluepnume 5y ago|1 comments
118.
by bluepnume 5y ago
The Waldo example is more an explanation of "what" a ZKP is than "how" a ZKP works. Not a terrible starting point, but yep, definitely doesn't capture the complexity of the real deal.
119.
You don’t need S2F to value Bitcoin(bluepnume.medium.com)
1 points by bluepnume 5y ago|0 comments
120.
Bitcoin: Cutting Through the Bullshit(bluepnume.medium.com)
4 points by bluepnume 5y ago|3 comments

More ›