gilesgate's comments

Yes, that must be it. As I understand it, the deconstruction was included in the working copy of his book before Chapter 1, and then later removed, correct?

Edit: Ah, incorrect. He actually intended it to be a chapter-by-chapter deconstruction but never completed it.

Are you using cwm on OpenBSD or on something else? (Just curious.)

YT link (in case you want to avoid FB): https://www.youtube.com/watch?v=uJ5w11Cm3gM

"On Lisp" is a good book but perhaps too advanced for an introduction, whereas his "ANSI Common Lisp"[0] is better suited to the purpose. Barski's "Land of Lisp" has also received positive feedback.[1]

I'd be interested to see what others consider a suitable general learning path for Lisp.

[0] http://www.paulgraham.com/acl.html

[1] http://shop.oreilly.com/product/9781593272814.do

This might have seemed as a superficial witticism, but it's not meant as one (honestly!).

There's a fundamental difference in approach towards hardware and software that's cultivated slowly, gently, and steadily by Apple. The objective is to shell out money to the company and its ecosystem, and starts with vendor lock-in with proprietary tech and cheap but paid apps in a closed-off app store, to reach to the point of an annual budget for Apple expenditures that follows the latest iterations of their products, which are buffed up with New! Shiny! Features! that aren't much thought out, but are nominally innovative.

Now, if you go the Linux/BSD open source/free software path, you'll be hard pressed to find software to throw money at. Best you could do is donate to support your favourite projects, but that's optional rather than mandatory. After settling down with a nice system configuration, you'll similarly be hard pressed to find reasons to waste money on continued "upgrades", instead opting for something that works, and returning to it. People buying couples (or even stockpiles) of, say, x203's is a good example here. They're not buying the marketed "cutting edge", they're rather opting for something that supports their workflow, at a fraction of a price.

This demonstrates a fundamental difference of attitudes, on the one hand people subscribing to an open-ended channel of (fashionable?) updates in hardware and software, and on the other people maintaining and updating a workflow. Perhaps obviously, I'm viewing this from the slightly biased dev angle (and not necessarily webdev either).

Understandably, video and graphics people may come from different tech cultures and have different expectations, where the Apple way is more or less the only (apparent) way.

TL;DR, I see the Apple mentality as bombastic value inflation with more varnish than wood, while the FOSS camp as gradual value increase albeit with the occasional splinters.

Disclaimer: I do make daily use of my MBA 11" 2013, but I'd be hard-pressed to change it. Yet if I'm forced to, I'd probably not go for lustre, but for something equally functional. (Think of a "My other laptop runs OpenBSD" bumper sticker.) When I need to offload a build cycle that'd take too long on the MBA, I do so on a Fujitsu rather than a Mac Pro.

There you go. Downvote a guy to assure a better explanation.

Haven't tried that, but it really sounds it would be terrible to the wrists after prolonged use (in which case "prolonged" would mean longer than 10-15 minutes).

Might you mean the "nipple"?

Not really surprising. Old MBA 2013 has an awesome keyboard for coding (and is overall a great terminal device), and the Apple Wireless is identical to some MBA/MBP keyboards. The effective distance between the keys and the overall general width of the keyboard are pretty much en par with "proper" desktop keyboards, with excellent responsiveness and key travel. The MBP 2018 is another deal altogether, obviously. Sad, sad story.

The primary difference is whether you think it's alright to spend £35 on a single simple cable or not. Many things that follow simply hinge on that.

Definitely go for it, then, and try to do Common Lisp rather than anything else. You can always expand later to JVM-based Clojure, or indeed contract to Scheme, but it's good to start with the thing itself.

The world always needs more good Lisp programmers.

It would seem as too much of a shot in the dark with questionable ROI for a non-technical (and probably even a technical) manager. From their perspective it would seem as the equivalent of introducing an inexperienced programmer into the team (as your Lisp experience will initially be understandably zero), and there wouldn't be anyone in the immediate vicinity to help with peer review or mentoring. Perhaps it would be more effective to learn Lisp on your own through a few hobby projects, and then gradually (and gently) introduce it as a potential solution for work projects? This does depend on your team's structure, though,

If anyone here has introduced Lisp into their workplace, I too would love to know their approach, be it successful or not. Although I'd be more interested in proper Lisp (OK, and Scheme) than Clojure, the latter wouldn't hurt either.

Somehing missing from he ile?

Previous discussions from last year: https://news.ycombinator.com/item?id=16860646 https://news.ycombinator.com/item?id=16679963

(Common) Lisp usually gets more use than exposure, so it's nice to see large-scale Lisp success stories. Makes me feel warm and fuzzy inside, as it's one of my two favourite languages (the other one being, of course, C).

Edit: APL is a close third, but let's be realistic.

I feel guilty for laughing when he said "to have a friendly chat with HR". It's certainly not a good month for him, as apparently his wife recently left him as well[0]. Bit sad (and perhaps demeaning) to see the video cut mid-way for a message from the sponsor.

But yeah, as jacquesm also said, there's no reason to expect any better from Facebook, is there? It's rather a mark of consistency, being unethical both outwards and inwards.

[0] https://www.youtube.com/watch?v=fssFXlNk6vw

SDF is changing its main PAUX server.

> Broadcast Message from smj@sdf > (/dev/pts/83) at 19:17 UTC... > > > The AMD Opteron 150 known as 'sdf' will now be retired. > A new 'sdf' is standing by to take its place with 8 cores > and 16GB of RAM. > Please stand by for a final shutdown of 'sdf'. > The swap should only take a minute or so > > > > Broadcast Message from smj@sdf > (/dev/console) at 19:21 UTC... > > > Good Night AMD Opteron 150 host known as 'sdf'. > You have served us well for 9 years. > > Final power off in 30 seconds > > Connection to sdf.org closed by remote host. > Connection to sdf.org closed.

Direct SSH to sdf.org doesn't currently work, but you can login by connecting directly to the IP: `ssh [email protected]`.

The new MOTD, welcoming the new hosts:

> Welcome to the new tty.sdf.org! > > Hosts 'sdf', 'miku' and 'faeroes' have upgraded from AMD Opteron 150s w/ 2G > to dual Intel Xeon E5345 8 cores with 16GB of memory. > > Finally, welcome back host 'otaku'!

Similar in Greek academic networks, adapting to local mythology. The amount of routers and mail servers named 'Hermes' was ridiculous.

Different experience in English academia, where I encountered random names (e.g. 'mira' for a shell server and 'laplace' for a Physics Dept server). The acronyms could at times be interesting. Particular favourite was a 'central university network time' server. That was later renamed to ntp.*.ac.uk, after stern recommendations.

> "This robot will never die, it will just keep updating itself and evolving," priest Tensho Goto told Agence France-Presse.

So that's why goto is harmful.

That would be my impression as well.

Linux does have a much wider user base, however, and that enables the community to even stumble across problems more frequently, while a smaller project like OpenBSD might have to orchestrate specifically-themed hackathons and auditing sprints (as they have). But I would take "security by choice" over "security as a byproduct" any day of the week.

Keeping in mind the breadth of resources that aspiring kernel hackers have access to when introduced to Linux, contrasted to OpenBSD's relative scarcity, it makes the latter quite the underdog success story.

(That is not to say that Linux or the larger of the BSDs is the product of monkeys randomly typing on VT100s -- there is considerable and commendable skill in these projects as well.)