RSS LispCast
哪吒推荐该订阅
原站:http://www.lispcast.com/drupal
点击立即订阅,“LispCast”的内容有更新,哪吒第一时间提醒您
“LispCast”的内容更新
累计:43 篇(自 2008-11-22 起)
更新:约1篇/月,最后更新1050 天前
LispCast
We have all experienced it: you make an innocent statement about a programming language online, and suddenly you are mired in a flamewar. You are labeled a fanboy and flamebait.Why is choice of programming language such a touchy issue? It's like once you enter into certain areas of the topic of programming languages*, you are instantly transported... (309 天前)
LispCast
Recently, I posted an article about why I didn't like Haskell's type checker (or really, any of the other type checkers I know of) in theory. I sensed that it got a lot of flack. It was an idea I had been pinging around in my head for a while. It was not meant as a criticism against Haskell, but a statement of my preference.Someone suggested to me... (309 天前)
LispCast
The Virtues of Small SoftwareNowadays we have thousands of times the processing power, memory and storage yet, from the user's perspective, software for the desktop, web and mobile seems to run slower than it should, or used to.While it does start a bit backwards-looking*, this article wraps it up with a great positive, futurist spin: mobile devices a... (309 天前)
LispCast
Not Lisp again . . .I'm always searching for a good way to explain what you can do with Lisp that you can't do with most other languages. Joe Marshall has a compelling story, from a skeptic's point of view, for what makes functional programming different. There are multiple parts that trace his way through a course at MIT and toward a love of lisp... (309 天前)
LispCast
Type systems are wrong because the world cannot be put into a tree structure of categories*. Only a small, controlled subset of the universe can be modeled by a given tree structure. Far from making a system extensible and maintainable, type systems often lead to their own inflexibility. Upon adding type after type, a question inevitably emerges: w... (309 天前)
LispCast
Brittle class hierarchies serve a purpose. They let you model your domain. In a sense, you are creating a language about the problem. It is brittle because you want to know when it breaks so you can fix the problem. But sometimes, if you are adding and adding classes, legitimate stuff stops fitting in so neatly. You kind of have to force it, becaus... (309 天前)
LispCast
I have always favored composition over inheritance. It seems like the best way to reuse functionality. I reserve inheritance for truly polymorphic types. Code reuse when inheriting is merely a convenience. Inheritance should never be used just to reuse code.Classes are like the fixed points in your code. They define undeniable assumptions for your ... (309 天前)
订阅者 ( 1 )
u42016712
相关订阅源
RSS CommunityWiki: FrontPage

The multilingual copyleft wiki on communities.

指数 | 1人订阅  

RSS Alex Schroeder: Diary

The Homepage of Alex Schroeder.

指数 | 1人订阅  

RSS chinaSMACK

all chinasmack content.

指数 | 1人订阅  

我要反馈