Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:Volatility (Score 1) 476

That wouldn't work. People would just swap coins between several accounts in order to reset the expiration date.

That's precisely the point. To give users an idea of how many BTC are actively being hoarded, rather than the permanently inaccessible ghosts of coins that were created when some user overwrote their wallet file.


I mean sure, it gives people a little more information about the market, albeit at the cost of increasing the number of transactions, but what exactly would it change?

Comment Re:Bitcoin is worthless in the long run (Score 1) 476

The ultimate value of Bitcoin does not seem to exist

It allows you to transfer wealth electronically and pseudononymously without the need for a centralised broker.

One might as well claim that the Internet has no ultimate value, as there's nothing apart from being electronic, pseudononymous and decentralised that sets it apart from traditional means of disseminating information.

Comment Re:Volatility (Score 1) 476

Aside from trying to play hot potato with bitcoins, what exactly makes bitcoins valuable? I can't take a bitcoin and turn it into energy, or use it to move things, or settle a tax debt.

No, but bitcoins can transfer wealth electronically and pseudonymously without the need for a centralised broker.

Bitcoins is to currency what the internet is to traditional media. It lowers the amount of initial capital needed to innovate with finances. Quite frankly the appreciation of bitcoins is relatively uninteresting to me; it's the sheer technical potential of a decentralised electronic currency that gets me excited.

Comment Re:The Doctor needs a break too (Score 5, Insightful) 332

The plots, and the Doctor himself, are so incoherent that even I barely know what the hell just happened at the end of an episode, and I'm normally the guy in the room who is explaining the plot twists to others.

I haven't had any problems understanding what happens in each episode. In fact, I find the two new series by Steven Moffat to be considerably better than the old Russel T. Davies series.

Russel T. Davies was infamous for "Doctor Ex Machina" plots, in which the Doctor would pull technobabble solutions out of his ass at the last minute. His villains were either re-introduced monsters from old Doctor Who episodes, or extremely uninteresting evil aliens who were entirely interchangeable.

Steven Moffat actually attempts to write science fiction, in that the Doctor's solutions are based on rules set up earlier in the episode, rather than rectum-derived technobabble. The viewer gets all the information the Doctor gets, so when he reveals the solution there's a genuine feeling of "Oh, now that's quite clever". Moffat's monsters also typically have some kind of interesting gimmick and often have some relation to the real world, giving them a certain scare factor that's not present in Davies' generic aliens.

Comment Re:May not work (Score 1) 858

If a party changes their public key, their coin hashes won't match their coins, and the next transaction will fail.

The user doesn't discard their old key pair, they just generate a new key pair for each transaction. A bitcoin user might own hundreds of different keys, each containing the proceeds from a single transaction. In aggregate, all of these accounts make up the bitcoin user's total wealth.

Comment Re:Not untraceable. (Score 1) 858

An electronic money issuer or a money transmission service.

I'm not sure a client in the Bitcoin network counts as either. The FSA might be interested if someone started a business for exchanging bitcoins for pounds, or vice versa, but I expect it would take a while to work out whether bitcoins were something that it should be regulating.

Comment Re:May not work (Score 1) 858

The soundness of Bitcoin's crypto doesn't seem to have been analyzed by third parties yet. There's nothing in Cryptologia or sci.crypt. Until there's agreement in the crypto community that it's sound, I'd be suspicious.

Bitcoin doesn't really do anything new from a cryptography perspective. It signs transactions with public keys and assumes that there isn't an easy way to find a specific SHA256 hash short of brute force.

Transactions are not very anonymous. If you spend a coin with a server, the server now knows your public key, and can associate it with any other identity information it has for you ( IP address, Facebook login, shipping address, etc.)

A new public key is usually generated for each transaction, so this doesn't actually tell them anything.

Systems like this detect duplicate spending of the same item, but you can't tell if someone has a duplicate but unspent copy of your coins. So you don't know your money been stolen until you try to spend it.

I don't think you've quite understood how the system works. The situation you describe can't happen without the entire network being subverted.

There's also the technical problem that "new transactions are broadcast to all nodes". That won't scale.

This isn't quite correct either. There is a simplified payment verification method that doesn't require the full block chain. The Bitcoin network just needs enough full clients to make it infeasible to subvert the network.

Comment Amazon can terminate spam accounts (Score 5, Insightful) 71

Those assurances aren't entirely heartening, though, unless Amazon is way ahead of the curve with content-filtering technology.

Amazon has the spammer's credit card details, knows where each email comes from, and can freeze or terminate accounts at the touch of a button (or via an algorithm). This gives it a considerable advantage over those that have to passively filter spam.

And in any case, spam filters are pretty damn good these days. I've had a public email address for going on 15 years, which used to get hundreds of spam emails every day. Now it's very rare for even one to slip past GMail's filter.

Comment Re:Asynchronous and self modifying code. (Score 2, Insightful) 109

2: functional programming and self modifying code have nothing to do with one another.

This is the equivalent of saying lamda functions have nothing to do with functional programming.

No, it's equivalent to saying that lambda functions have nothing to do with self-modifying code.

I'm not sure where this confusion of yours has arisen. Why would you think an anonymous function is self-modifying code?


Submission + - Programming Clojure by Stuart Halloway ( 2

eldavojohn writes: Programming Clojure by Stuart Halloway was very near to the perfect book for me. It covers many things common to many Lisp languages while highlighting in moderate detail the things that make Clojure unique and worthy of some attention. It spends a large amount of time dealing with the intricacies of interfacing fluidly with Java (down to a package rewrite inside a large project). This fits me as perfectly as a Java programmer and I now feel ready to experiment with peppering functional language capabilities into an object oriented language. The book also strives to show how to simplify multithreading through functional programming which is good because I find multithreading in Java a serious headache that few are good at. It was released in May of 2009, it's currently the only book out there devoted to Clojure and the introduction is written by the languages creator, Rich Hickey, who says, 'What is so thrilling about Stuart's book is the extent to which he "gets" clojure.' The book earns its place on the Pragmatic Bookshelf by guiding the user through rewriting a part of Ant into a new build tool called Lancet--adding to the project what you just learned about Clojure at the end of each chapter.

First, a lot of you are probably wondering what Clojure is and asking me why you should care at all about it. Well, Clojure is a functional programming (FP) language that runs on top of the extremely pervasive Java Virtual Machine and in doing so seems to offer a simpler way of multithreaded programming. It belongs to the family of languages that are Lisps and as a result this book covers a lot of remedial material that is common to other Lisp languages. If you're a serious lisp programmer, you'll be able to skip some of this book (the intro will guide you). Clojure has rarely been mentioned on Slashdot with the resulting comments revealing largely confusion or considering it a buzzword. It's going to be hard to write this review about the book instead of the language being that 99% of what I know about Clojure comes from this book. If you work through this book linearly, you must also use the command line read-eval-print loop (REPL) that, similar to Ruby's IRB, allows you to get hands on with Clojure and Halloway's examples.

Both Hickey and Halloway are very active in Clojure development. In fact, Halloway has a video out on types and protocols, new developments in Clojure 1.2 since the book went to print. Halloway does a good job at providing examples, keeping the book pragmatic and showing you the "wrong" way before incrementally showing you how to correctly accomplish various goals in Clojure. But he loses two points on this review for two reasons. One is that he over evangelizes about Clojure. It would lend a lot more credibility to everything else he says if he would just relent and abstain a bit from painting Clojure as the best language for any task. This ties into my second point which is the fact that books on programming languages are supposed to give the reader two very valuable things: knowledge of when to use the language and knowledge of when not to use the language. Programming Clojure is lacking in the latter--this is not a unique problem as most books about a language really sell their language. All too often in my professional career I see a solution and think, "Wow, that really was not the right tool for the job." (I'm looking at you, Java) Clojure definitely has its strengths and weaknesses despite very little evidence of the latter in this book although I was directed to a QCon presentation where the author speaks more about where Clojure excels in real life.

That said, the book is a great fit for the object oriented Java developer who does not also code a lisp-like language regularly. I say that because Chapter Two deals with reviewing all of the facets of Clojure--most of which are found in other Lisp languages which might be seen as remedial to a proficient Lisp developer. However, before you skip it entirely, there are important notes that Halloway injects into these chapters ranging from how not to do things in Clojure to the minute differences and implications they hold. Chapter Five dives into the fundamentals and features of functional programming in Clojure. This chapter was especially useful to me as I'm not used to languages featuring things like lazy sequences, caching of results or tail-call optimization. Working through the examples in Chapter Five really opened my eyes to some of the more powerful aspects of FP. Like how an infinite sequence can easily be handled by Clojure and its laziness allows you to only pay for what you need from that sequence. While definitions of infinite sequences are also possible in Haskell or Python, Clojure brings this capability to the JVM (not that anything is preventing a more verbose Java library from handling such structures).

Chapter Three focuses a lot on Clojure's interaction with Java and does a great job of showing you how to rewrite part of your Java project into Clojure and run it on the JVM. This includes calling Java from Clojure, creating and compiling Clojure into java classes, handling Java exceptions in Clojure and ends with the beginning work in Lancet (the build tool the book strives to create using what we learn in each chapter). It also contains a bit on optimizing your performance when working with Java in Clojure. This theme continues through the book as Halloway knows that one of Clojure's main selling points is that it can be so much faster than Java if you're willing to put in the extra work and planning to utilize pure functional programming.

In Java, everything is an object. In Scheme, everything is a list. Well in Clojure, the main staple is sequences which brings us to Chapter Four: Unifying Data with Sequences. While this chapter succeeds in teaching how to load data into sequences, how to consume data from sequences and how to force evaluation of lazy sequences, it felt like one of the weakest chapters in the book. This is all necessary in learning Clojure but Halloway skimps on examples and could stand to add some more examples on what is and isn't seq-able, seq-ing on various things and performing functions on various things.

Multicore chips are all the rage these days. And right now it seems that developers are by and large content with coding single threaded applications. But that may change in the future when the user expects more than a few cores in usage. In the introduction, Halloway argues a few reasons why we all should use Clojure and one of those reasons happens to be the somewhat sound logic that we will all have cores coming out of our ears in the near future. That means that as a developer you have the option to spawn more threads which means coordination of threads which means you will be forced to do the dirty dance of concurrency. Chapter Six is entirely devoted to this and, honestly, I reread a lot of this chapter as there are several update mechanisms and models that you can use to manage concurrency in Clojure. Unsurprisingly there is no silver bullet for concurrency even in Clojure. This book has but a handful of figures and their formatting leaves much to be desired but the two in this chapter are necessary references for deciding if you should use refs and software transactional memory, atoms, agents, vars or classic Java locks. This is a potent chapter that ends with a snake game implementation in Clojure demonstrating some basic concurrency. While Clojure protects you from some classically complex issues and may make concurrency vastly more succinct, it still requires a lot of thought and planning. Halloway provides good direction but clearly hands on experience is a necessity in this realm.

Chapter Seven focuses entirely on macros and is somewhat disheartening in that it presents an extremely powerful feature of Clojure that is also very complex. Halloway gives two rules and an exception for Macro Club. The first rule is: "Don't Write Macros." The second rule is: "Write Macros if That Is the Only Way to Encapsulate a Pattern." The exception is you can also write macros if it makes calling your code easier. Halloway does a good job of explaining the basics of macros in Clojure and breaks them down via a taxonomy into categories and examples of macros in Clojure. Macros are a necessity when you're trying to augment Clojure by adding features to it or if you are creating a Domain-Specific Language (DSL). Macros in Clojure do seem easier than macros in most other Lisp langauges. At the end of Chapter Seven, you create a basic DSL for Lancet which was helpful even though I was left feeling helpless in the face of macros. Despite the complexity of macros in Chapter Seven, Eight's multimethods are similar to Java polymorphism and was much easier to wrap my head around than macros. Multimethods are used very infrequently (seven times in the five thousand lines that compose the Clojure core).

Chapter Nine is unfortunately less than twenty pages and deals with "Clojure in the Wild." You would think that a book in the series of Pragmatic Programmer would have more pragmatism than the features of a language with Lancet but let's face it--Clojure is a relatively young language. Nine covers automated tests, data access and web development. The automated testing is a short section on Clojure's test-is packaging. The database stuff appears to be little more than wrappers around the already mature JDBC. The web development consists of an intro to Compojure which is similar to and Sinatra. Compojure shows a lot of promise in reducing the amount of code one needs to write a basic web application. It lacks the feature set and support that Rails has with rapidly building CRUD applications but holds a lot of potential to be flushed out into something similarly powerful. Halloway says his introductions to these projects should "whet your appetite for the exciting world of Clojure development" but I think a more accurate description is that these brief brushes with functional projects leaves the reader ravenously blinded by hunger for more.

Some final thoughts on the book: I caught only two very minor typos in the book. It's all English and code. There were no pictures or illustrations in this book except for one on page 96 in which a tiny drawing appears named Joe who asks a question about vectors. Oddly enough, I didn't find Joe on any of the other three hundred pages. It was very easy to work through this book from cover to cover and the example code was very instrumental in my understanding of Clojure. As a Java monkey, rereading sections seemed a requirement although the book is concise enough for me to enjoy in my free time over one week. Halloway cites mostly websites and utilizes tinyurl to reference blogs like Steve Yegge's blog and frequently he references Wikipedia. Only three of his many citations are other printed books (although one of them is Gödel, Escher, Bach: An Eternal Golden Braid). Halloway's greatest strength is the engaging examples (like the Hofstadter Sequence) that he picks and provides to the user and I hope that future editions of the book build on this as well as expand on the growing base of Clojure projects out there. His github is rife with both instructive and pragmatic examples that could stand to be included in a future book.

Some final thoughts on the language: Clojure holds a lot of potential that is yet to be realized. I cannot say yet whether the succinct syntax offers a good balance between quick coding and readability. To the uninitiated, the code can look like a jumble of symbols. Yes, we escape the verbosity of Java and the kingdom of nouns but is what Clojure offers (a neighboring kingdom of verbs) better? While Clojure is concise, it requires a lot of keywords which required a lot of usage look up when starting. Clojure code is potent and powerful. A mere five thousand lines of Clojure code create your engine--the core of the language. I assume this brevity is due to ingenious reuse that Clojure can offer but I would hate to be the person to maintain that code if I was not the author. What's better is that this code is quickly conjured at the REPL if you wish to read it yourself or augment a feature. A sage coworker who has seen much more than I in this business of software development recommended Clojure to me. He was right that it is a very interesting and innovative language but in my opinion it has a long way to go before it becomes the next Ruby or Java. Clojure needs an equivalent to Ruby on Rails and it's fighting an uphill battle against all the developers like myself that left college with so much object oriented coding and so little functional programming (although Scheme is my alma mater's weed out course). If you find yourself stagnating and are thirsty for some continuing education in the form of a stimulating challenge, I recommend Clojure (and this book on Clojure). Hopefully Clojure's full potential is realized by the community and it finds its deserved place in many developer's tool sets as the right tool for some jobs.

You can find Programming Clojure on O'Reilly, Amazon or in three DRM-free formats and hard copy from the publisher's site. For a sample of the author's writing and to get a feel for how he injects Clojure code into it, check out his blogs on his company's website.

Slashdot Top Deals

When you don't know what to do, walk fast and look worried.