poofyleek

Very disappointed indeed. Keybase is one of the ones I actually used.

I use gopkg.in. Personally I would like to see the community avoid adding more to the 'go' tool. It is already doing too much. I think the solution provided by gopkg.in is better than other more conventional methods (e.g. npm or maven like). I love Go. But it is ironic that 'go fmt' was designed in from the beginning. And now we are still dealing with semver and package dependencies. I went with gopkg.in because it made the dependencies a non issue from the tooling point of view. It is made possible by having 'import' direct from the repositories, which archive different versions and tags. Perfect for something like gopkg.in. I am probably in the minority.

This is indeed huge. I left Korea right after Park Jung-hee was assassinated by one of his officers. Predictably, this was followed by a military coup and martial law. Park Jung-hee himself seized the reign by means of his own military coup against the previous president. His daughter, Park guen-hye, is now outed by the Supreme court, peacefully. In the old south Korea I remember, the same court had ruled in favor of the military regime to condemn Kim dae-jung to death sentence. Kim dae-jung later was elected president after the democratization of south Korea. I remember the heavily armed soldiers everywhere as I was leaving the country, after the assassination. That is my last memory of Korea. I have not been back since 1979. Perhaps now it is time for me to go back and visit. Congratulations to the Korean people.

It is complex and interesting. I am a novice database user. But I do know many databases use 'gettimeofday' quite a lot. Just strace any SELECT query. Most databases I have used, including Postgresql, also have to implement MVCC which mostly depend on timestamps. Imagine the hypervisor CPU and memory pressure induced time drift, or even drift in distributed cluster of database nodes. It hurts my head to think of the cases that will give me the wrong values or wrong estimate for getting the values. It is an interesting area.

Even without migration, the synchronization can be an issue. In older multi-core machines, tsc synchronization was an issue among cores. Modern systems take care of this. And core CPU clock frequency change is also taken care of, so that constant rate is available via tsc. However, when hypervisors such as VMWare or paravirtualization like Xen come into play, there are further issues, because RDTSC instruction either has to be passed through to physical hardware or emulated via a trap. When emulated a number of considerations come into play. Xen actually has PVRDTSC features that are normally not used but can be effective in paravirtual environments. The gettimeofday() syscalls (and clock_gettime) are liberally used in too many lines of existing software. Their use is very prevalent due to historical reasons as well as many others. One reason is that the calls are deceptively "atomic" or "isolated" or "self-contained" in their appearance and usage. So liberal use is common. A lot of issues come about due to their use, especially in time sensitive applications (e.g. WAN optimization). This is especially true in virtual environments. There are complex issues described elsewhere that are kind of fun to read. https://www.vmware.com/pdf/vmware_timekeeping.pdf and https://xenbits.xen.org/docs/4.3-testing/misc/tscmode.txt. The issue becomes even more complex in distributed systems. Beyond NTP. Some systems like erlang has some provisions, like http://erlang.org/doc/apps/erts/time_correction.html#OS_Syst.... Other systems use virtual vector clocks. And some systems, like google TrueTime as used in Spanner, synchronize using GPS atomic clocks. The satellite GPS pulses are commonly used in trading floors and HFT software. This is a very interesting area of study.

This sounds useful and revived my interest in GAE. The Go example has health check code. It makes sense. Are there equivalent offerings from AWS and Azure? This looks likes a unique GAE feature.

The "structured bindings" feature seems potentially dangerous. I guess it helps unpacking tuples and getting references to tuple members. But it seems to have opened up a whole new set of side effects.

Korean language has built-in social framework for respecting the elders. Different words used when speaking to someone older vs. younger. The language enforces filial piety.

When I learned German, French and Spanish I struggled with gender specific features in them.

When I learned English, I struggled and still struggle with the use of articles, like the "the".

Languages reflect and reinforce culture and mindsets. I am a different person in each language.

Reading translated books is a great mental and cultural exercise.

Elena Ferrante reads better in English than the original Italian.

Jhumpa Lahiri reads better in English than Italian.

This is truly serverless computing at work.

Michelson-Morley experiment failed to substantiate the existence of ether. That was 1887. Much after that, in 1905, Einstein's special theory of relativity stated you don't need ether and any medium for light to travel, as long as one abandons the idea of absolute time.

The comment by Mordehai Milgrom, " the emperor has no clothes, that dark matter is our generation’s ether." rings true to me. So far no dark matter has been found by LHC.

They used to say 95% of the universe was dark matter. Now they say 68% is dark energy and 27% dark matter. Still only 5% normal matter. Could it be that there is 100% normal matter, 95% of which are transient and temporal in vacuum? If we were to follow Milgrom, and not invent substances, it seems plausible that we still have more math work to do.

This is wonderful. The "Mutable" vs. "Immutable" tables are clear. I have been telling myself to think this way -- there are no immutable or mutable versions. Everything changes, over time. The time is the key here. A value of X maybe 1 at t0. At t1, it may be 2. So the source of confusion is due to asking the wrong question. We commonly ask the question of "what is the value of X?". Does that question really make sense? What we mean to ask is, "What is the value of X at a certain time?"

I'm guessing you are right. The usual problems with /mnt/c. I was wondering about rootfs being per user as well. On a server that may be a problem, but perhaps not on a laptop. It sounds like this is not meant to be the basis for production level deployments, but useful for development.

How do they handle various NTFS related issues? https://cygwin.com/cygwin-ug-net/using-specialnames.html

Is there a program that rates other programs in terms of Flesch Kincaid score or the equivalent? Old Man and the Sea F-K score is 4. Code isn't much different than other writings. I prefer to read code written like a Hemingway.

First McAfee http://www.huffingtonpost.com/2012/11/19/john-mcafee-belize_.... Now Le Roux. What is up with the security software guys? Are they destined to be evil geniuses?

I may be naive but why not do away with npm and do what Go does. Import from github or http. Or what common lisp, roswell, ufo does https://github.com/ta2gch/UFO/blob/master/README.markdown

Hahaha. Got down vote for this joke. Irony is thick.

Like

Yahoo Core Business valuation is at this point low enough that any one of the Unicorns, e.g. Uber, Airbnb,... could easily afford it. Tumblr could have raised more money to become a bigger Unicorn and could have acquired Yahoo. Absurdity is reality.

These points are valid but miss the point of Go. To judge Go, as any language or tool, one must program in it for a while -- say a year or two -- and build substantial programs that serve specific needs. The outcome of such experience is clear indication of a tool's usefulness. I started as a very skeptical user of Go. Now I cannot live without it.

Thought nethack went rogue but apparently not.

Worse are Mr. Noodle and his brother.

But who merged pull request to master?

Being liberal in acceptance did not discount the conservatism in output. If diligently only one side of the maxim is followed, there would be less issues. For example, if many implementations were conservative in sending, that alone is sufficient. After that allowing for liberal handling of input is to compensate for those who did not follow the conservatism in output. Postel can't be easily blamed for long term entropic outcomes, accelerated by the abundance of implementations that ignore both sides of the maxim.

:)

like the emacs org-mode pprint support. especially the example output claiming the well deserved rock star status.

The name is unfortunate indeed. There were languages like LOOPS (Lisp Object Oriented Programming System) which evolved into CLOS. Common Lisp loop macro is a kind of special DSL of its own. While the oldest LOOP language may be from 1967 article by Meyer and Ritchie (DMR as in UNIX), a kind of mini language for computation of primitive recursive functions and dealing with computational complexity.