4 ms·
TL;DR: Those who program in Lisp know what they're doing; those who program in C don't. Spare me your smug condescension. Your position is founded on a flawe
by AnimalMuppet 7y ago
TL;DR: Those who program in Lisp know what they're doing; those who program in C don't.
Spare me your smug condescension. Your position is founded on a flawed premise.
You're in the minority for a reason, and it's not because you're smarter (or because you "get it" or "understand what matters" or whatever). Lisp is not the one right way; it's the right way for some problems and some circumstances. And the same is true of C. Pick the right tool for the job, not because of a worship of one tool. C is more often closer to the right tool than Lisp. That's the reality that you're trying to ignore with your "C users don't understand" rationalization.
Now, if you wanted to argue that C is overused, that in some circumstances where C is chosen Lisp would be a better choice, that would be a reasonable argument. But "C users just don't understand what matters"? BS. You need to get over your blindness.
- hhas01 7y agoCongrats on illustrating that you don’t know what you don’t know. Life must be so simple and safe living in that Plato’s cave of yours. I don’t use Lisp; I’m not a fan of Lisp itself. I am a fan of what Lisp lets you do which C does not: take an existing language and make it into a better one; one that serves your needs, not the assumptions of its creators. Whereas I have and do use C. And I constantly lament the utter uselessness of C’s macro system, which makes it impossible to reshape or improve C as a language in any way that counts. You see, I don’t actually have a problem with C’s minimal interest in safety or high-level expressibility. It was after all built to do a very constrained, low-level, one-time job: implement a kernel, where safe program execution may reasonably be considered the expert implementor’s responsibility. I do have a problem with not being able to extend C into a safe high-level one; not that that’s stopped millions of know-it-all C weenies such as [presumably] yourself taking it and mashing it into domains it is ill suited for (high-level applications programming). .. You’re all so proud of the monster you’ve built; so when your C program eats your users’ data because a buffer blew or a pointer dangled, well that’s their tough luck, isn’t it. Not your problem for using an inherently, unfixably, unsafe tool in the first place. And definitely not C’s for not being capable of raising itself up, only dragging everyone else down. ’Cos let’s not pretend these dumbshit foot guns of yours don’t have a very valid use: keeping the dumb outsider riff-raff like me out of your private personal playground. Alas, I’m an exceptionally persistent SOB: I may despise writing code, and loathe the lousy languages you lot provide to do it, but I absolutely love the solutions I provide despite all those barriers you put in my way, and my users love them too—and that is the only judgement that counts. That I happen to evolve new languages and develop deeper insights into a culture and philosophy of language design that is both utterly alien and utterly above and beyond you, well, yes, you got me there: I am feeling a tad smug about that right now. But only cos you’re being a reactionary dick. I went down that route not to be clever or superior, but because it was the only way I could hope to solve the problems I’ve got using the very limited wetware tools I have. And it worked. So maybe try humility sometime, and realize that all your C languages, for all their popularity and influence, are but one tiny, samey, undistinguished facet in a whole vast rich infinitely colored world of computational thinking of which I know just a little and you know nothing at all. And then get back to me; who knows, we might even have something positive to talk about.
- SaxonRobber 7y agoWhere did the C touch you?
- hhas01 7y agoOn my 0x00000000. Repeatedly.
- hhas01 7y ago(@Mr Robber: I don’t know who flagged you, but I LOLed. It was cheeky but fair comment: if only I had a language to express myself with less than a thousand words.:)
- SaxonRobber 7y agoIt’s all good, life is too short to care
- hhas01 7y agoSrsly, I hate the complacent acceptance—even proud embrace—of unsafe unreliable irresponsible tools in this profession. It’s like a badge of pride, and very unhealthy. Because while you may get away with it when your programs are small and simple and manually verifiable, it is an approach to software construction does not—can not—scale. Worse, it breeds a culture of casual contempt and responsibility shirking that permeates everything we make and do. It’s not just developers—I’ve got plenty choice words for modern management too—but ultimately it’s the developers who are meant to be the domain experts in converting users’ problems into solutions. Too often they convert them into more problems. As a user who got so hacked off at programmers’ failures to deliver the solutions I need that I eventually taught myself how to do the damn job myself, I’m well aware of all the pitfalls and mistakes on both sides—and have made most of them myself. But at least I learn by it and do my damndest to improve. .. Now some of my bad attitude may be jealousy, as I really envy your big powerful capable Mk10 programmer brains while I’m struggling to emulate Programmer 1.0 on the wetware equivalent of a Timex 1000 with the wobbly rampack. But mostly it’s furious disbelief with a huge side of frustration as I see all you smart people squander your smarts lazily brute-forcing bloated ugly crappy not-quite solutions, instead of using your smarts to figure out much better ways of doing it and then doing that. K&R worked under massive, crushing limitations (obsolescent 60s hardware) and turned those limitation to their advantage. Those limitations forced them to work small, smart, and fast; and that paid in spades. Delivered UNIX in record time, which had its flaws, but by golly unlike the “superior” MULTICS it shipped. Creating their own dedicated kernel-implementing language just to do that job, instead of bodging it in some unsatisfactory off-the-shelf language? Yeah, the follow through is not so great (Unix’s faults are well railed on elsewhere), but that original process of creation? Brilliant. #GreatArtists
- hhas01 7y agoBTW, I think you’ve misinterpreted “don’t know what they’re doing”†. I’m not talking about code, I’m talking about the business domain. (I thought it obvious from context, but clearly not.) And yes, a depressingly large number of working programmers today have zero interest in learning anything except how to write more code. But how can you write code that solves a user’s problem if you refuse to learn what that problem is and how it was arrived at? And then you blame the users for “not speccing the job right” when they discover your “solution” not only fails to make their lives any better but often makes it even worse. I’ve worked a decade professionally as a user-turned-developer, so please don’t say this attitude isn’t cultural right down to the bone. I’ve seen it, I’ve dealt with it, I’ve walked out because of it. And looking around me that seems pretty much par for the course. This is why I like a philosophy of reshaping your stock language into something that much better expresses the business concepts and processes you’re dealing with, then writing your solution in that. It forces you to learn the user’s job before you get underway, because you can’t fake understanding: your new “business language” either does the job or it sucks. Building up that vocabulary is the first test of whether or not you understand what you’re doing; and until it proves you do you’ve no business proceeding or you’re just wasting everyone’s time (including your own), and giving this industry an even worse reputation for shafting the customer by giving them shit than it already possesses. -- † Ironically for exactly the reasons I’m talking about: you’re unable to see anything that isn’t about coding. But the code is the least significant part of the overall puzzle; and until you understand the puzzle in its entirety you’re not fit to solve any of it. TL;DR: I may be nuts, but I ain’t what’s broken.
- AnimalMuppet 7y agoNo, I got that you were talking (at least in part) about the business domain. I have had the privilege of mostly working on smaller projects (two to 20 programmers), where the connection to what the business is trying to do was pretty clear. Maybe I've also had the privilege of mostly working with grownups. Or, possibly, maybe you're too cynical. (Your experience has driven you to that cynicism; mine hasn't. I have no data on which of our experiences best reflects the wider world of programming.) But I agree that, if you don't know what the user needs, you probably can't code it. But I think you're overselling Lisp in this context. The kind of programmer you're talking about, given Lisp, won't develop a "business language" that matches the user needs. They will at best just develop a language that matches the product manager's feature request description, and at worst they'll just start hacking away in Lisp without developing any vocabulary at all. And I think you're misreading where I'm coming from. I can see a lot more than just the code. I totally get that delivering what the user needs is what counts. Just one example: In a hallway conversation, I said we should do X instead of Y because it would be better for the users. The better part of a decade later, I got reminded of that hallway conversation, because it turned out that a litigation-happy competitor had patented Y, and in a court case wanted to apply that patent against us, but couldn't because we didn't actually do Y. I said that the attorneys should say that, if our competitor had patented delivering a worse user experience, they were welcome to the patent on it.