HNHacker News
TopNewBestAskShowJobs

kruhft

1,034 karma · joined April 7, 2011

Artist, musician, meta-linguist, and Lisp hacker.

Email: kruhft@gmail.com

https://www.github.com/scarlet31.github.io

submissionscomments
kruhft··on Ask HN: Any movies that changed your life?
Fight Club.
kruhft··on John Carmack working on Scheme as a VR scripting language
Finally.
kruhft··on Why you can't dislike something on Facebook
> The truth is that people just don't dislike things online that often

You've got to be kidding me. From what I see, and maybe it's just the places I frequent, that's what the internet is for!

kruhft··on BitMessage - Bitcoin Inspired Peer to Peer Encrypted Messaging
Here's a post with some subscription addresses:

https://bitmessage.org/forum/index.php/topic,1420.0.html

kruhft··on BitMessage - Bitcoin Inspired Peer to Peer Encrypted Messaging
I did a bit of playing with the client. Once you generate an address under the 'Your Identities' tab, right click and select 'Special Address behaviour' and have it 'Behave as a pseudo-mailing-list address'.

Here's a test one if you feel like trying it out: BM-2DCGcvGwvGUr7yYSzWWa6rBrVok8mM7HtK

I don't think the name matters but I called it 'kruhft-list'.

kruhft··on BitMessage - Bitcoin Inspired Peer to Peer Encrypted Messaging
The subscriptions feature looks interesting; I'm assuming that it's a mailing list type feature. Is there a list of subscribable addresses somewhere?
kruhft··on Should String Be An Abstract Class?
Base64 encode a string and it's generically sanitized. They're a bit difficult to read with the naked eye though.
kruhft··on Jaron Lanier: Free information, as great as it sounds, will enslave us all
Looks like I caught it just before the fall :)
kruhft··on Jaron Lanier: Free information, as great as it sounds, will enslave us all
That's the first time I've seen the top comment on a story starting to 'gray out' from downvotes.
kruhft··on In 1949, He Imagined an Age of Robots
He also formalized Brownian motion: http://en.wikipedia.org/wiki/Wiener_process.
kruhft··on Unheralded Mathematician Bridges the Prime Gap
The definition of conjecture says they are basically 'guesswork': http://www.thefreedictionary.com/conjecture. Someone will say 'I think that there are no values of x,y and z can solve x^n+y^n=z^n for n other than 2' but doesn't prove it. This can be due to lack of time, space, or a supreme insight on the part of the conjecturer[1]. The conjecturer has said some important and correct things in the past, so many people will take this experience and look at the conjecture and say 'this is probably right because this guy was right before and we see no errors with this conjecture so we will use it in as a theorem', which is to say they will use it without proof because it makes sense.

Then, sometimes 100's of years later, somebody does prove (or disproves) the theorem and get's some press, and for some very important conjectures, prizes. If the conjecture is disproven, then all the math based on it falls down.

Conjectures interesting because they are puzzles left by people that they can't answer but they want them to be true, so it is up to future generations with their advanced minds, tools and insights to prove them, leading to progress in the field with the advancements of techniques use to prove these conjectures and make them actual theorems.

[1] http://en.wikipedia.org/wiki/Fermat%27s_Last_Theorem

kruhft··on I know who 'Satoshi Nakamoto' is, says Ted Nelson
Funny how after the hype around the ABC proof that now somebody thinks he's Satoshi. I'd be a bit more convinced of this 'unmasking' if Shinichi hadn't been all over the news last week.
kruhft··on Data initialization in C++
After reading up on Lisp macro programming (PG's on OnLisp and others) you will see that it is always advised to use only purely functional code when doing metaprogramming. In Common Lisp and all the others Lisps I've seen, this is not strictly enforced by the language and only advised. The code should be purely functional because you don't know when and how many times it can be called by the compiler leading to some grand mysteries when something does not go as expected during compilation due to unintended state.

The constexpr design is taking this to heart and enforcing that the code to be purely functional. I don't see this as a disadvantage but take it that designers of C++ are forcing best practices for the features they are adding. Best practices are generally not the most convenient, but by doing it this way, they're giving you less 'rope to shoot yourself in the foot'. Lisp was more of a research language woring as a testbed of features that are now moving into mainstream languages now that there is some experience with how to use them in the least damaging way.

Purely functional programming is not as 'easy' to write because almost everyone learns imperative first, which is the most natural way to code (do this, then do this, then do this,...). Using functional code requires you put the control that you would normally put into code into the data. It's a different way of thinking and is not natural in the way that imperative programming is.

And regarding that implementing constexpr wsa a 'nightmare for compiler writers', it should be! Strong abstractions are difficult to design and implement, but once they are complete everyone benefits. Compilers are the one things that should take on the hard features since everyone uses them.

Thanks for your experiences with constexpr and I'll form my own opinions of it after some practial use and maybe i'll find it just as lacking as you do in the end :). I'll stand by my statement that C++11 is heading in the right direction, even though it may have some warts and tradeoffs that it can't be avoided, like anything that matures. It will be interesting to see what C++ goes in the next 10 or more years.

kruhft··on Show HN: HTMLify - Turn code snippets into HTML, for tech bloggers
Export your font-locked (colored) emacs buffer to html:

http://www.emacswiki.org/emacs/Htmlize

or

http://www.emacswiki.org/emacs/HtmlFontify

kruhft··on Source Code Typography
I apologize, the Foreward is the inspirational work I was speaking of:

http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-5.html

Not that the contents of the Preface should be ignored :)

kruhft··on Source Code Typography
> "Source code should be written to be understood by people."

This viewpoint is described well in the Preface to the First Edition of Structure and Interpretation of Computer programs, 2nd paragraph:

http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-7.html

I would suggest reading the whole Preface. It's quite an inspirational work for this field.

kruhft··on At Google Conference, Cameras Even in the Bathroom
Awesome. Thanks for the update.
kruhft··on At Google Conference, Cameras Even in the Bathroom
Seconded, all 3 episodes of Black Mirror are excellent stories about an imminent future that I'm not sure we really want to come about (except for the art project ;-).
kruhft··on Data initialization in C++
This is my first exposure to constexpr and it looks very interesting. According to this article it's a second C++ metaprogramming language: http://cpptruths.blogspot.ca/2011/07/want-speed-use-constexp....

The more I learn about C++11 the more I like it. There's some really amazing new features that I've only seen in Lisps, plus there's full static typing, which is the one thing I miss from Lisps.

kruhft··on Skype with care – Microsoft is reading everything you write
SSH into a secure common server and use talk(3) (http://en.wikipedia.org/wiki/Talk_(software)) ;-)
kruhft··on D-Wave: Truth finally starts to emerge
I like that he addresses that his main fear that, if D-Wave does not succeed after riding the marketing hype-machine, a "QC Winter" would likely happen, not unlike the "AI Winter" (http://en.wikipedia.org/wiki/AI_winter) that occurred in the late 80's. The AI Winter was caused by a huge amount of over hyped claims and promises by the companies taking part which were never (and could never be) met, leading to the eventual collapse of the whole industry which is now only starting to see a practical recovery with the resurgence of Machine Learning.

D-Wave might be the belle of the ball today, but once the crowd turns, it could ruin an entire industry for a very long time. That's why skepticism is important when it comes to their claims.

kruhft··on Extreme syntax
When you have 2 extremes the real solution is almost always somewhere in the middle. I think a good solution to the syntax amount problem is Python, but I still don't like significant whitespace.
kruhft··on Extreme syntax
Common Lisp actually has a suprising amount of syntax, from the obvious ', to all of the standard dispatch reader macros starting with # (#', #., #=, ...), to block comment syntax #| ... |#. Pure lisp has no syntax, but practical lisp has quite a bit. Trying to read arbitrary symbols from external sources can lead to quite a shock without hacking the reader to disable many of it's syntactical features.
kruhft··on Macros in Python
That's known as destructuring-bind: http://www.lispworks.com/documentation/HyperSpec/Body/m_dest...

Is that a macro created by this library or a feature of the library?

Edit: I did some reading and it looks to be a feature macro of the library.

kruhft··on Depression Part Two
Yeah, you're right. The crushing, quasi-suicidal, life long depression that I went through and managed to overcome through non-medial means is nothing compared to the pain and suffering that you and the others in this dicussion are going through.

Clearly, me expressing my experience that with time and overcoming the obstacles of depression is meant to be condacending rather than encouraging people to continue on with life and that things can and will get better with time and effort.

Obviously, nobody else on the planet has experienced the changes that maturity brings, and those that do only talk about them to put down those that are younger than them and not to let people know what they can look forward to as they get older.

In case you didn't notice, this post is filled with sarcasm.

kruhft··on Depression Part Two
How interesting that naming a standard process of mental development through adulthood would garner such a negative response. Growing up is a process, not a state, that one is constantly achieving. That process is generally done through overcoming new obstacles and challenges that one hits during their life and overcoming them. From the definition:

3. To develop and reach maturity. 7. To come to be by a gradual process or by degrees; become

Suicide is not development, or becoming by a degree, it is an escapism and the most concrete and final way of 'giving up'. By perserveering and overcoming your obstacles you learn that nothing is insurmountable given time, although it is usually never easy.

I didn't not mean to be condicending in any way or to insult the decisions of the many great people that have chosen to take their liives. I was just speaking from experience.

kruhft··on Depression Part Two
Answering the headline: no, eventually everything isn't hopeless bullshit. There's still a lot of hopless bullshit, but eventually you'll find something (or if you're lucky, a few things) that makes all the hopeless bullshit worth putting up with.

That's why people find suicide so sad. Almost nothing can't be overcome with time and suicide cuts that time short. You learn this as you overcome things by not giving up.

This process is called 'growing up'.

kruhft··on PayPal exec aims to “obliterate passwords from the face of the planet”
> maybe with one less finger.

Modern fingerprint readers check for temperature and pulse[1]. That doesn't undo the actions of a determined, but ignorant, criminal that saw such a gruesome technique to bypass readers in a movie.

[1] http://www.cbc.ca/news/business/story/2013/02/22/fingerprint...

kruhft··on PayPal exec aims to “obliterate passwords from the face of the planet”
> Anything that requires you to carry an additional device is doomed to failure.

Like our corporate VPN using an RSA dongle?

kruhft··on A Philosophy of Programming Languages
> As we move from the "low" level to the "high", say from the domain of machine code all the way up to, for instance, a rich, expressive Ruby DSL, the question arises, as it does for all language: have we acquired a surplus of content that cannot be simply reduced to core rules?

This was the statement that I started all this with. I am taking "surplus of content" to mean "a bunch of programs" in this context due to the quote speaking of a Ruby DSL. Programs can be reduced to a sequence of logical operations if they are computable, which I would take as 'core rules'.

Therefore, only non-computable programs can not be reduced to a set of core rules by the definition of computability. QED

Maybe you can explain 'it is much more than merely what happens when it runs'? Do you mean that what it took to create the program was greater than the resulting program and it's effects caused by running it? That the meta-logic used to create the program is far greater than the logic in the program itself?

I am 'much more' than the results of actions when I act. I have a past history that has created me, a physical body being used to act with, the world I am acting in, and the resulting effects of my actions, plus everything else I have missed. I that what you mean by 'much more'?

← PreviousPage 14 of 21Next →