lerno

44 ms·

331.
by lerno 7y ago
Funny, I thought I would like the ”try”, but looking at these examples I prefer the Go1 version.
332.
by lerno 7y ago
If we assume average value of GDP at t = g(t) Energy usage per point of GDP = f(t) Then we can obviously construct a hypothetical scenario: lim t->inf g(t) * f(t) = C This is obviously possible if one flips it over, making economic growt
333.
by lerno 8y ago
I’ve read parts of most of those books. Some I’ve read from cover to cover. But none of them are books with info that you couldn’t read in other books. Some definitely better written or more up to date.
334.
by lerno 8y ago
I wonder if it’s not that string theory gets its more reasonable results simply by reducing the singularity of a particle in one dimension. If we look at the idea of a ”point particle”, it’s clearly something that is never observed elsewher
335.
by lerno 8y ago
Yes, and Mainland China has been threatening with military action if they would simply call the country Taiwan. So yes your point was...?
336.
by lerno 8y ago
Wow, people using 512 bit keysizes in 2018?? Back in 2014 I got the recommendation to ditch 2048 in favor of 4096.
337.
by lerno 8y ago
This is why I have little confidence that Tokamaks and similar will have much success. Instead of trying to prevent the non-linear behaviour of plasma it should be utilized. Look at (grossly underfinanced) attempts like focus fusion, where
338.
by lerno 8y ago
Been exactly there with a game. Solution? Take a data centered approach: a command object (just a function really) updates HP, XP, triggers visual effects etc. Monster and Player classes are just thin wrappers around plain data structures.
339.
by lerno 8y ago
The Rust Community has a Huge Crackpot Evangelist Problem and Developers Don’t Know how to Deal with It
340.
by lerno 8y ago
No, some logic simply isn’t cleanly decomposable, plus the main problem here is that objects lets you get away with implicit state (e.g. if (this.x == 0) doA() else doB(); ) for long enough that when you start realizing you need explicit st
341.
by lerno 8y ago
Really? I’d say the accidental distribution of state across objects due to cross cutting concerns is exactly where OO breaks down for me.
342.
by lerno 8y ago
Commando on the C64 didn’t have an ending. It just continued. I know since once you got good enough you could complete the stages effortlessly. My longest play was a couple of hours straight - enough to restart the highscore counter from ze
343.
by lerno 8y ago
Ok, so a ”Maybe” avoided, but instead we added a coupling, plus moved the decision logic to the inside of the Customer object? I would consider this a very bad design. It’s one of those solutions that you think of and tell yourself ”look at
344.
by lerno 8y ago
No no no. That is a one-way trip to hell. There is no ”good for all threading scenarios” thread safe mutable array design. I’ve debugged too much java code where the programmers thought that ”thread-safe” meant ”no need to think about threa
345.
by lerno 8y ago
Interestingly generics seem to drive the addition of type inference in order to avoid having to write too complex types, losing the self documenting nature of the static type, but still not avoiding the problem entirely. Consider the types
346.
by lerno 8y ago
I find myself wondering how many Swift converts actually wrote Objective-C like it was supposed to. I’ve run into a lot of programmers that worked with ObjC as they would Java or C++, that is, using very small and fine grained objects to di
347.
by lerno 9y ago
I can’t believe no-one is mentioning the difference between Elite, WC and X-wing in terms of flight controls. If you know your classic Elite, it’s basically roll and up/down. WC had (as basic controls) left/right up/down. Eas
348.
by lerno 9y ago
Except for the fact that he was talking in context of Europe where this is - unfortunately - verifiably true.
349.
by lerno 9y ago
Let’s assume it is a physical process. We can then recreate it away from a body. We run the experiment. Something is now experienced. Who is it that experiences?
350.
by lerno 11y ago
To have fast compiles be within x2 (or thereabouts) of optimized build is very important for plain productivity reasons. Therefore it's a very valid concern.
351.
by lerno 11y ago
I would say that it is volatile mix of very non-pragmatic constructs and lots of real constraints that creates the problem. If you want to see how to build a pragmatic language - look at JAI.
352.
by lerno 12y ago
Consciousness is typically understood as "the one that experiences". The failure of reductionism to explain it can be demonstrated by an example: You accidentally burn your finger on the stove, this is detected by the nerves that
353.
by lerno 12y ago
If you use the wsdl for discovery, then you are doing something that's rather dangerous as there are no guarantees what that method does or that it is correct -> use documentation instead. If the call is something important (e.g. mo
354.
by lerno 12y ago
The "point" of SOAP is to have an autogenerated API layer + objects on client and server side. The problem is that this does not actually help much in validating data sent or received. In addition, the client side SoapFooData you
355.
by lerno 12y ago
I agree, Chinese simplification was extreme, whereas the Japanese simplification tried to retain the idea of the original character. Possibly, an additional political motivation of the simplification was to make it harder to read old litera
356.
by lerno 12y ago
This is the release that makes you go "people were insane to think that Swift 1.1 was anything near usable".
357.
by lerno 12y ago
I'd have to check in detail, but just looking at the profiler, about half of the time is in the actual setter code and half in bounds checking. One would think that bounds checking is a faster operation than the set if copy-on-write is
358.
by lerno 12y ago
I am not sure of the exact behaviour. I only read something Lattner wrote as a comment on very slow behaviour when passing things back and forth into CoreGraphics that relied on bridging Swift arrays/dictionaries into their CF counterp
359.
by lerno 12y ago
From what we're told, copy-on-write doesn't happen unless it has to (i.e. the compiler discovered that we use it elsewhere). In any case, the issue here with debug builds does not seem to be due to memory access nor copy-on-write,
360.
by lerno 12y ago
The conversion is only supposed to happen once, but there was a bug (don't know if it is fixed yet, it was discovered quite a while ago), which made the Swift <-> ObjC NSDictionary conversion to be performed each time an access w

More ›