344 karma · joined September 14, 2013
You seem to be implying that JITs are somehow more complex and only help with languages having no static typing. Both assumptions aren't quite true. Also, consider the cases where it's much easier for a JIT to produce code, as it has more information than a static compiler.
For e.g. which functions should be inlined? Which mechanism should be used for dynamic dispatch? If you have 10s of types possible at one dispatch but only two seen in practice, the tracing JIT will only compile the fast paths with an exit for the other paths. The AOT compiler will have to produce a vtable or big switch statement to handle all the types as it lacks the runtime information. Which would you consider 'quality code'?
It may be a good toolchain if you're targetting static compilation using the LLVM.
Btw, I would completely disagree that the sysadmin side is or was behind Debian. FreeBSD is way easier to sysadmin than most Linux, even without pkg.
https://www.google.com/search?q=34000+inr+in+usd
=~ $600 US
That's very interesting because LuaJIT has GC as well. Could you please reveal a bit more about the type of application, number of lines, and if the code is public?
def add(sum, num):
return sum + num
Of course you can plug `add` directly in `reduce(add, [1, 2, 3], 0)` which gives `6`.A transducer is an object returned by a call such as `map(lambda x: x + 1)`.
You can now apply the transducer to a reducer and get another reducer.
map_inc = map(lambda x: x + 1)
add_inc = map_inc(add)
Our first reducer simply added, but the next one increments and then adds. We can use it as `reduce(add_inc, [1, 2, 3], 0)` which gives, I'm guessing, `9`.Since the transducer returns a reducer as well, we can compose transducers:
r1 = filter(is_even)(map(increment)(add))
# use r1 in reduce()
It seems in clojure, reduce() isn't the only useful function that works with reducers, there are others which makes this all worthwhile.Is my translation accurate?
IOW, I think storing local time and location as a rule is not a good idea. The rule should be to use UTC and store location if needed. Only if that doesn't work (e.g. '5 minutes after the game is over') come up with some other representation.
I maintain that time and location are orthogonal. If the application needs both, store both - properly in separate fields. That's better than shoving the granular location in the form of a timezone in the time field.
I strongly agree with the principles you chose - specificaly - all time storage and math should be done in UTC (the 'unicode' of time). Timezones only come in when you display or parse times (the 'encodings' of time).
I hope more and more libraries apply this idea. It makes the API a lot simpler and error retardant.
Good job!
I don't see it that way. The you that is follows from the (you, stuff that isn't you) at the previous moment. Your actions and the results are both a consequence of the previous (you, stuff that isn't you).
In other words, I'm having trouble differentiating you from the stuff that isn't you. I just imagine the world is a giant mechanical machine, churning along according to some physical laws, where the you is just a conscious entity that identifies itself with small subset of atoms in the machine and believes it can affect the movement of those atoms.
Yes, but doesn't determinism mean that all of us 'cannot act'?
> From a moral perspective, there is no distinction between the illusion of control and actual control
Are you saying a fully capable driver would be culpable if he was under the illusion of full control while he drove over a pedestrian? Consider a vehicle malfunction, which goes unnoticed by the driver, leading him to believe he didn't brake or steer fast enough. Is the driver still at fault or is it the car? Doesn't actual control matter?
You assume we can choose which direction to go towards. With no free will, we have as much choice in expending our energy as offenders had in committing offenses. It's absurd to state 'we can' or 'we should' while assuming a fully deterministic world.
Choice is most definitely a factor determining moral culpability. Consider a driver who drives into a pedestrian killing him, because at an unfortunate moment, the driver was paralyzed by an unexpected stroke. The driver witnessed the entire event with full understanding of what it means to take a life. Is he morally culpable? I would say no, because he was not in control. You can also imagine similar scenarios involving coercion or accidents.
The key point is whether we are in control of our actions, or merely witnesses with the illusion of control. I don't see how this can be separated from moral culpability.