aatd86

9 ms·

151.
by aatd86 11mo ago
Not really, in mathematic or type theory it is a proof. But that's besides the point. If there was nothing, then we wouldn't be able to describe it. We are only describing it because we think it might exist. So in itself it is ill
152.
by aatd86 11mo ago
I thought the smiley would make the 'Nope' less argumentative. Sorry if you felt it was offensive. This was in response to: > Side-note: the deontological argument is an argument for the existence of God, which uses the same pr
153.
by aatd86 11mo ago
Funny thing is to ask: 'Is blue, blue?' Now with existence: 'Does existence, exist?' And then a bit differently: 'Is nothing something?' We see that these are different types of impredicativity. Existence just
154.
by aatd86 11mo ago
As someone who is currently writing their own js framework, llms are able to generate code quite easily. So I am not worried that we will be able to see new frameworks. Now, about the incentives? Probably less inference costs for llms, whic
155.
by aatd86 11mo ago
For release but not for development. Sufficient for the build step to take a long time and you start to notice the friction. The web/browser should not rely on bundlers and compilation steps overall. This should remain optional.
156.
by aatd86 11mo ago
jsx is not really needed. We have templates. Besides it really is a dsl with a weird syntax. I'm doubtful it will ever become an ES standard. And for good reasons. That should be left to the different frameworks to handle.
157.
by aatd86 11mo ago
Nope :) It 's not about that. It's not because I imagine that there is a banana in front of me that there will be. It's not tied to material existence in that way. It's perhaps another notion of existence which should be
158.
by aatd86 11mo ago
Yes but then there is always something that must exist which is the concept of absence of existence. So it doesn't make sense.
159.
by aatd86 11mo ago
You have a material view of existence perhaps. How would the notion of nothingness even exist if there was no existence in the first place? And if we even accepted that nothing was possible, which in itself doesn't make any sense, how
160.
by aatd86 11mo ago
I would not be surprised if the universe was somewhat elastic, expands and then contracts and then expands ad infinitam. After all, existence in itself is irrefutable and cannot not exist by definition. If we subscribe to a theory of the mu
161.
by aatd86 11mo ago
And here I was, wondering if it was about embedding go in a java program... ahah.
162.
by aatd86 11mo ago
Finishing building a framework at the moment. I'd rather say that they are state descriptors... They don't contain all the state. But they are some kind of hashkey that allow to retrieve application state. "Hypertext as the e
163.
by aatd86 11mo ago
> using dependent type system to have "proofs" be equivalent to "types" Do you mean proposition as types? And proof has a program? Or do you see it at somewhat a higher order, since values are proof for a type, and ty
164.
by aatd86 11mo ago
xD you're delivery made me laugh. But I think it is a combination of getting the product out of the gates as fast as possible, test on the main market, and also deal with foreign currencies, legislation and pricing later.
165.
by aatd86 11mo ago
Is your mental imagery 100% under your control or does it seem that your visualization doesn't fully abide by your own will?
166.
by aatd86 1y ago
You must not have heard of Luke Cage. It's very real.
167.
by aatd86 1y ago
Because another mutant might be joining our ranks soon.
168.
by aatd86 1y ago
Hmmh... Warning: Lighthouse issues a warning when the page's <body> element has more than ~800 nodes (elements). Error: Lighthouse reports an error when the <body> element has more than ~1,400 nodes. Other Related Lighthou
169.
by aatd86 1y ago
Displaying so many would require virtualization. No one is going to see a myriad of components all at once anyway. The slowing down part might be eager computations in partially optimized implementations. The same way we use pagination on t
170.
by aatd86 1y ago
Shouldn't a state change should be purely event driven, and not dispatch its own events as side effect? That avoids reetrancy and is an easy rule to adopt...? Or am I misunderstanding the issue?
171.
by aatd86 1y ago
Is their code available somewhere. I need this for UIKit so that I can make my UIs in Go. I have the gist of what it would require but have yet to implement everything. (if swiftUI allowed more control over the UI tree, I would even target
172.
by aatd86 1y ago
a former keiretsu?
173.
by aatd86 1y ago
"empty interface" meaning an interface value that is empty i.e. nil interface... ofc
174.
by aatd86 1y ago
It's a bit difficult statically because it is a flow sensitive analysis. You are not wrong that it is a sharp edge. Completely removing nils from interfaces is not possible because: 1. not backward compatible However I would nuance a l
175.
by aatd86 1y ago
The same thing I don't know... but a long time ago, I remember reading that SSA and CPS were isomorphic. Basically CPS being used for functional languages. edit: actually even discussed on here CPS is formally equivalent to SSA, is it
176.
by aatd86 1y ago
But the LHS can determine how it compares to the RHS when the RHS is determined to be an untyped constant? Or instead of saying RHS (my mistake), let's say the typed side since comparisons are symmetric. A bit like having a special met
177.
by aatd86 1y ago
If it is because of overflow, the idea was that there could be size classes at compile time. A bit like sub/supertyping but for numeric types. A simple type pointer check would be sufficient.
178.
by aatd86 1y ago
Not sure that reflection would be needed. They are exclusively on the RHS. But you're right. They would have a sort of type of their own instead of basically being int under the hood. type conversions do not require reflection. Or mayb
179.
by aatd86 1y ago
But that information disappears when you assign to an interface variable/container that is nillable. It requires an assertion to recover the info about the value inside the interface being not nil. basically `if v.(nil){...} creates tw
180.
by aatd86 1y ago
that's another thing that makes it difficult to fix. Same thing here. 2 is an untyped constant so it should have returned true. (even if int is the default picked on short assignment) any(uint(2)) == int(2) should return false indeed h

More ›