News for hackers. Stuff that matters.
Re:Structure and Interpretation of Computer Programs – JavaS... by slimed on Wednesday December 18, 2019 @08:45AM (#21824691)
There is a simple explanation of course. You are not the intended audience. Ditto for the blockbusters you mentioned.
Re:Structure and Interpretation of Computer Programs – JavaS... by caiocaiocaio on Wednesday December 18, 2019 @09:40AM (#21825257)
The target audience are people who don't want to learn Lisp but want to write a bunch of Lisp interpreters and compilers. Obviously.
Re:Structure and Interpretation of Computer Programs – JavaS... by ng12 on Wednesday December 18, 2019 @11:11AM (#21826282)
There's a reason SICP isn't called Structure and Interpretation of Lisp Programs. Lisp is incidental.
Re:Structure and Interpretation of Computer Programs – JavaS... by edflsafoiewq on Wednesday December 18, 2019 @02:08PM (#21828136)
There is a reason SICP uses Lisp.
Re:Structure and Interpretation of Computer Programs – JavaS... by ng12 on Wednesday December 18, 2019 @02:36PM (#21828446)
There is. Scheme is a great pedagogical language. The book isn't _about_ Lisp though.
Re:Structure and Interpretation of Computer Programs – JavaS... by caiocaiocaio on Wednesday December 18, 2019 @02:08PM (#21828135)
Imagine a book where you wrote a bunch of Javascript implementations without learning Javascript.
Re:Structure and Interpretation of Computer Programs – JavaS... by slimed on Wednesday December 18, 2019 @09:57AM (#21825433)
That's a pretty narrow view of the teachings to be gained from SICP.
Re:Structure and Interpretation of Computer Programs – JavaS... by vanderZwan on Wednesday December 18, 2019 @10:02AM (#21825501)
I'm with you. As much as I find most remakes terrible, to say others should not enjoy them is a form of gatekeeping.

If people who would otherwise not enjoy any of the insights to be gained from SICP do get into it through this version, great.

Re:Structure and Interpretation of Computer Programs – JavaS... by b0rsuk on Wednesday December 18, 2019 @11:21AM (#21826392)
I think the target audience is people who don't like to learn, and I find that worrying in the context of programming.

It's not like code examples in a book are intentionally obfuscated. They are also not some atrocious pile of spaghetti code you may have to put up with at work. I think any foreign PL programming book is a joy to read next to working as a software maintainer. And while the original book aspires to be a general programming book (the title!), I think we should allow Scheme programmers to have their poster child book/success story.

I also have a modest, optimistic interest in Rust, and tinker with it from time to time, but I don't think everything should be converted to Rust. The language team is open about sacrificing readability for other values, like execution speed, memory safety, concurrency, correctness. But with Rust at least the occasional rewriting hype can be justified as "testing the limits of the new language" and "optimizing" - because the language is pretty damn efficient. With Javascript it's... what? Some kind of idealism about running all programs in a browser sandbox? And isn't it a bit ironic that an idealistic book about software architecture is rewritten in an ad-hoc language, with a minefield of bad features you're not supposed to use but you will encounter at work?

Re:Structure and Interpretation of Computer Programs – JavaS... by slimed on Wednesday December 18, 2019 @11:37AM (#21826578)
> I think the target audience is people who don't like to learn, and I find that worrying in the context of programming.

A strange comment to make about someone trying to tackle a text like this

> I also have a modest, optimistic interest in Rust, and tinker with it from time to time, but I don't think everything should be converted to Rust.

This is a great example of how your perspective differs from that of the intended audience. They don't want the book in JS because it's a language they're already picking up and want to tinker with. It's likely one of the only languages they are confident with. Maybe they just finished their CS degree or (gasp) a coding bootcamp and would like to understand more of the fundamentals before learning their second language. Especially one like LISP that represents an entirely separate branch of programming language design from JavaScript.

As someone who writes Clojure professionally, I certainly share your hope they would choose to pick up lisp eventually. Let's not hamper their development in the meantime by steering them away from resources like this that might assist their journey.