gluczywo

It has never been the goal of bitcoin. The original Satoshi paper rather implies the "unbank the banked" objective which is to remove corrupt middleman.

To understand what may happen to the US visitor read this book: https://www.goodreads.com/book/show/30524537-the-russians-ar...

I can confirm it's not fiction as it was written by father of my friend.

TL;DR from goodreads:

During a short business trip to California, Irishman Denis Sugrue was arrested and accused of spying for Russia. But this is no Cold War thriller - this is 2005 in Bush's America.

Facing ten years in federal prison, Sugrue must negotiate the corrupt corridors of American justice and attempt to convince FBI agents that the fact of his innocence outweighs the embarrassment of a failed prosecution.

Web Push API requires centralized service the messages are sent over what has serious privacy implications. Android Chrome makes it even worse because it does not allow changing the Push API provider (Google's proprietary GCM/FCM is used)

For anyone interested in thorough analysis instead of opinions I recommend this really good article from 1994:

https://github.com/papers-we-love/papers-we-love/blob/master...

- Sun's pushing Java and killing everything else

- Stallman's distaste for anything non-GPL

EDIT: wording

For life seen as a part of system/society reproduction is the key motivation (for lack of a better word). Non-reproducing activities are irrelevant temporary aberrations because societies that don't reproduce get extinct and are replaced by societies that focus on reproduction.

This line of thought reaches two decades ago and was expressed in a wonderful essay "Big Ball of Mud" http://www.laputan.org/mud/

EDIT: updated with the quote

BTW Do we really need ~540 bits (~90 chars of base62) to identify permanent link?

This book has been removed as it will shortly be published by APress.

It implies that the system knows plaintext password. Even if the system deletes the password and keeps a hash, it remains the problem of distributing that password to the client in a secure way.

ln -s PROJECT_SOURCE_FOLDER $GOPATH/src/

Global variables (if any) are long explicit phrases while inner loop variables can be a single letter.

Without taking scope into account the naming guidelines become dogmatic and impractical trivia.

EDIT: wording

Language is only a communication protocol most efficient in an interactive context (dialog) that allows two agents with shared but not identical set of experiences achieve understanding in some domain and context with the caveat that understanding is unprovable and not absolute. Understanding that is only empirically tested and behavior probed (e.g. long after successful conversation Agent Alice discovers that Agent Bob "did not get it" as she expected).

By analyzing sole language without experiences, the machine, using something like word2vec, may discover semantic dependencies (e.g. man + cassock = pedophile) but not true semantics that has world consequences.

Even with unlimited language corpora the machine does not have the set of axioms that humans have (experiences and observed stories). These axioms are needed to build further more abstract knowledge.

The article describes server authentication (in the section with misleading title "SSH connections are encrypted") but does not mention the fact that fingerprint should be sent over another secure channel and manually verified.

"Civilization advances by extending the number of important operations which we can perform without thinking about them."

And while it is a powerful line, in case of media and journalists I made a habit of thinking deeply about every message I receive in terms of what is the hidden agenda their mighty landlords try to convey.

You can do concurrency on a single thread. This is the message I find it hard to get across when explaining CSP concurrency libraries.

Some people argue about usefulness of such libraries as being not native and leaky abstraction. I developed Go-style concurrency "port" to Tcl:

https://github.com/securitykiss-com/csp

and it is one of few developed-in-house things that became the productivity booster in my toolbox.

The interesting thing about it is that thanks to the expressive power of Tcl I was able to port not only the semantics but also almost completely mimic Go syntax.

I think that Joe ignores the major rationale for modularization.

Modules provide the way to cut out the fragment of a complex project and apply local reasoning to it.

In other words a module is the way to "divide and conquer" the complexity that crosses the border of the single mind's capacity.

As such a module is not about code compilation, distribution and upgrades. It's about human cognitive abilities.

Having 325 results for UserList.java in Krugle:

http://opensearch.krugle.org/document/search/#query=userlist...

I can't image how to create globally reusable function that has the list of users in the signature.

It does not seem possible in mainstream languages where the OOP dogma tells you to obfuscate your sets, lists and maps and turn them into non-reusable classes.

While in my day to day work I don't feel the need for the compiler (starkits are good enough) it might attract more performance concerned people to this powerful but forgotten language.

For me returning to Tcl is always an immense pleasure. This is what it gives out of the box:

  - convenience of bash
  - power and elegance of Lisp
  - self-containing no-dependency nature of Go
  - clarity of Python
  - probably unique for the entire industry reliable cross-platform GUI toolkit
  - simplicity of Dodecalogue

- good handle on concurrency in bigger projects (with scale, events lead to spaghetti or mega state machines). I tried to address this one myself by developing Golang/CSP style concurrency library https://github.com/securitykiss-com/csp

- large community