sfvisser

17 ms·

151.
by sfvisser 5y ago
It’s not that weird if you consider that despite the negative externalities all the CO2 producing processes delivered huge upsides to literally everybody. It’s not just Shell to blame, it’s all of us. We did this, we had good reasons to do
152.
by sfvisser 5y ago
Not entirely sure the author understands what problem monads solve and how it relates to his examples. If you just needs a fixed set of inputs without dependencies, conditionals, branching etc you indeed don’t need monads.
153.
by sfvisser 5y ago
Lots of talk why you don’t really need to have compound documents anymore, but no real arguments why compound documents are bad. If your server and client architectures are somewhat sane adding a compound on-load resource is cheap and I don
154.
by sfvisser 6y ago
> I’m starting to think that maybe cryptocurrency is the great filter. It’s actually pretty terrifying. Either cryptocurrency is extremely useful and the energy spent will turn out not to be wasted at all or it is a big useless energy dr
155.
by sfvisser 6y ago
Good luck building anything interactive this way.
156.
by sfvisser 6y ago
Pet peeve of mine: READMEs starting to explain hoe efficient, performant or minimal something is without explaining wat it is and why it should exist in the first place. Or using overly vague terms that only make sense in a very narrow tech
157.
by sfvisser 6y ago
Many single-page-apps, and unfortunately also many regular looking pages, fetch new content using Ajax and splice it in the page dynamically. This has some obvious advantages for some use cases: preserving local state, fast refresh, less du
158.
by sfvisser 6y ago
Oh yes. Charleroi Belgium comes to mind. Once a prosperous industrious town, now the glory is gone. Recently read somewhere there is a bit of revival, culturally at least. Economically I’m not sure. A bit like Detroit maybe.
159.
by sfvisser 6y ago
The problem is not 'someone is not correctly following the serialization rules', the problem is 'the serialization rules are quite terrible'. This is not some interesting trade-off, this problem is fixable on all axes by
160.
by sfvisser 6y ago
Yeah, I think I misinterpreted the intent of your answer, because of a different read of dvt's comment you replied to.
161.
by sfvisser 6y ago
Top comment was clearly complaining about the syntax as an argument against a declarative approach.
162.
by sfvisser 6y ago
All of the above can be done with a super clean declarative interface using functions/methods without JSX. JSX vs normal JS code has nothing to do with imperative vs declarative.
163.
by sfvisser 6y ago
Pretty sure ‘good developer’ wasn’t the discriminating factor.
164.
by sfvisser 6y ago
It was only considered super bad by a subset of people. Usually not the people creating and maintaining web apps.
165.
by sfvisser 6y ago
Ideally, you write a small subset of unsafe primitives and encapsulate those in a safe interface and try to use those to implement your actual kernel logic.
166.
by sfvisser 6y ago
Google Maps is not much better on larger screens unfortunately. It’s almost as if it wants to obscure the map area, no matter what you try. When using it you kind of feel how a once pioneering piece of tech and UX initially built by a sma
167.
by sfvisser 6y ago
> Yes, I can't fathom why the hate is on the law, and not the companies now being exposed by the law.. Because the law obviously didn't help stopping companies from doing shady shit and made the user experience of the web worse
168.
by sfvisser 6y ago
Typescript wasn’t just another language. It was greatly anticipated by many frontend devs that already worked with typed languages in other environments. It filled a very obvious niche.
169.
by sfvisser 6y ago
Definitely respect the author for admitting he was wrong, but it's also scary to see how strongly people can feel about tech they clearly don't understand. Like most of us, I've been there myself in multiple occasions. It&#x2
170.
by sfvisser 6y ago
Yeah, that makes sense.
171.
by sfvisser 6y ago
No clue about this, but I can imagine a highly elliptical orbit in perspective projection makes a seemingly sharp turn at the highest point, right?
172.
by sfvisser 6y ago
I’ve never explicitly used DDD, but I am convinced there is great value in having an obvious abstraction barrier between a domain core and your application and UI layer. It will allow you to pivot the UX quickly without compromising your co
173.
by sfvisser 6y ago
Sure, but that still doesn’t explain the difference in rerendering between writing down the JSX element as a child or passing it in via props.
174.
by sfvisser 6y ago
I must admit I don't fully understand this, probably need to read your linked articles a bit more in-depth first. But if you say react doesn't need to visit the children because the prop didn't change, you have to also answer
175.
by sfvisser 6y ago
I don’t thinks hooks are a great example. Hooks are by definition effectful. Best compared to ‘Applicative’s in Haskell. (Not monadic unfortunately) So a functional component in react using hooks is not pure. You can translate it into FP wi
176.
by sfvisser 6y ago
This would work: <path> <m x=“10” y=“10” /> <h dx=“90” /> <v dy=“90” /> <h dx=“10” /> <l x=“10” y=“10” /> </path> Perfectly s
177.
by sfvisser 6y ago
I really don’t think many programmers nowadays actually think this.
178.
by sfvisser 6y ago
Partially. TypeScript doesn't complain when you pass in a function that ignores some of its arguments. Which is totally fine and safe. If you upgrade your function from no second argument to a numeric second argument TypeScript will no
179.
by sfvisser 6y ago
Because that's no longer a type error. TS is not going to help you calling the right function. :)
180.
by sfvisser 6y ago
> What language with optional function arguments protects you from this sort of behavior? Languages with a sane type system. TypeScript has no issues catching such mistakes. Writing tests to catch simple type errors is such an incredible

More ›