Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
codr7
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
84 ms
·
661.
▲
by
codr7
2y ago
'Just' is overdoing it a tiny bit :) Assuming everyone has a CL installed is going to limit the audience pretty drastically. And what about dependencies? Assume they have quicklisp installed as well? Like I said, I love Common Lis
662.
▲
by
codr7
2y ago
I don't have these issues in C, you're projecting. Not that I write bug free software by any means; no one does, though some like to pretend.
663.
▲
by
codr7
2y ago
Can't remember last time I worked with a dedicated designer, someone who actually knew anything worth knowing about UX. Devops seem to be going down the same path, it's like they expect coders to do it while the code is compiling.
664.
▲
by
codr7
2y ago
In Rust/C++ you can't, it's forced upon you. In C you can ignore whatever you feel like, and that bothers some people so much that they have to stop everyone else from doing it.
665.
▲
by
codr7
2y ago
But you have a choice, you don't have to implement all of C++/Rust. The beauty of C is that it allows you to pick your level of complexity.
666.
▲
by
codr7
2y ago
I would definitely recommend any programmer to learn both Lisp and C at some point.
667.
▲
by
codr7
2y ago
Because Ruby can't handle most of the problems C is used for? Because they're implementing Ruby, for example?
668.
▲
by
codr7
2y ago
Simplify. If you try to write the same complicated mess in C as you would in any other language it's going to hurt. Not having a package manager can be a blessing, depends on your perspective.
669.
▲
by
codr7
2y ago
I think every programmer should at some point write their own language.
670.
▲
by
codr7
2y ago
I love Common Lisp, but I would definitely think twice before implementing anything I want other people to use on their machines in it. A tiny C executable is pretty nimble in comparison to anything you'll get out of Common Lisp.
671.
▲
by
codr7
2y ago
It looks to me like C is still very relevant, and isn't going anywhere anytime soon. I realize a lot of people don't want to use it; and that's fine, don't use it.
672.
▲
by
codr7
2y ago
At least in C it's only plain old function pointers. You don't have to think about exceptions, overloaded operators, copy constructors, move semantics etc.
673.
▲
by
codr7
2y ago
Interesting use of the word 'objectively' there.
674.
▲
by
codr7
2y ago
It does too make the language simpler, and there's no way to rustle your way around that fact.
675.
▲
by
codr7
2y ago
It's not about the algorithms, but about doing this properly, that's the root cause. Sometimes that will manifest as choosing the wrong algorithm, but that's a rare exception from my experience.
676.
▲
by
codr7
2y ago
The stdlib makes choices that might not be optimal for everyone. Plenty of code bases also predate it, when I started coding C++ in 1995 most people were still rolling their own.
677.
▲
by
codr7
2y ago
True, if C wanted to be Rust it would be just as complicated. But who cares? The fact that C chooses not to nail everything down makes it a simpler and more flexible language, which is why it's sometimes preferred.
678.
▲
by
codr7
2y ago
Compared to C I'd say the biggest issue is complexity, of which compile time is a consequence.
679.
▲
by
codr7
2y ago
It's also very mature, not so much of a moving target. Both aspects are something I think many developers grow to appreciate eventually.
680.
▲
by
codr7
2y ago
I haven't designed any CPUs myself, someone with more experience could give you more details. But I don't think this carries much weight anymore, might have been true way back in the days. C gives you more control, which means it&
681.
▲
by
codr7
2y ago
That's very funny, Jesus was pretty much undefined behavior personified from the perspective of the state/church.
682.
▲
by
codr7
2y ago
Not even close to true, may I ask how much experience you have with C (not C++)?
683.
▲
by
codr7
2y ago
I've tried, but never succeeded in doing that; the complexity eventually seeps in through the cracks. C++'s stdlib contains a lot of convenient features, writing them myself and pretending they aren't there is very difficult.
684.
▲
by
codr7
2y ago
Yes, but there are similarities, it has the same hacker mind set imo.
685.
▲
by
codr7
2y ago
Been here since day 1, I was already semi-following PG because of his writing on Lisp.
686.
▲
by
codr7
2y ago
Agreed, I'm talking about most of it, I realize there are obscure corners where it's all about algorithms.
687.
▲
by
codr7
2y ago
I don't agree at all and have pretty extensive experience from writing different kinds of software professionally in different companies to back that up. Most software out there has very little to do with algorithms, and the problems w
688.
▲
by
codr7
2y ago
Nice, there are lots of interesting ideas/possibilities in Lisp that I feel deserve being further explored. I've been working on a custom dialect with a focus on practical use as an embedded scripting language for quite a while no
689.
▲
by
codr7
2y ago
I'd say most skills needed to create quality software have very little to do with algorithms.
690.
▲
by
codr7
2y ago
Most of this world is firmly on the 'short term profits over everything' bandwagon by now.
More ›