sifoobar

21 ms·

151.
Show HN: Snigl – a Forth with a Lisp in C(gitlab.com)
6 points by sifoobar 8y ago|0 comments
152.
by sifoobar 8y ago
I've had plenty of time to watch and listen to these things lately, Germans seem to have a soft spot for complex technological solutions to non-problems. And for hiring the cheapest labor possible, people who just don't give a fly
153.
by sifoobar 8y ago
I fully agree, both regarding programming languages and company culture. A younger and more naive version of me once took one of those savior jobs at a big, established company. I could stand it for 2 months before I freaked out, went to my
154.
Show HN: Snigl – a Forth with a Lisp in C(gitlab.com)
4 points by sifoobar 8y ago|0 comments
155.
by sifoobar 8y ago
Go runs NxM threading behind the scenes, it's far from the same thing. By choice, but it's not what I'm aiming for. And it needs to be built into the core (as opposed to gevent), otherwise it wont run as fast as it could and
156.
by sifoobar 8y ago
Erlang throws plenty of other ideas into the mix though, I prefer my concerns separated. It assumes multiple threads for example, in plenty of applications that's needless complexity. You end up sending messages between processes when
157.
by sifoobar 8y ago
Sorry, you can't sell Lisp. Maybe once upon a time that was possible, but those days are gone. And Lispers generally are a whiny, creaky bunch to deal with; me included. Pleasing that crowd is a serious undertaking. I sometimes try to
158.
by sifoobar 8y ago
Of all the methods for dealing with async calls I've come across, I strongly prefer the Smalltalk process flavor. The general idea is that main runs in a fiber (or process in Smalltalk lingo) out of the box. There's a way of start
159.
Show HN: Snigl – a Forth with a Lisp in C(gitlab.com)
3 points by sifoobar 8y ago|0 comments
160.
by sifoobar 8y ago
True, regardless of language.
161.
by sifoobar 8y ago
It's all black or white, right. Someone says something less than flattering about your latest ideology and the gloves come off. Consider not identifying so hard with your tools, for all our sake. There are very few rules in C; same in
162.
by sifoobar 8y ago
If those two were the only options, definitely. But they're not.
163.
by sifoobar 8y ago
Only as good as Rust allows you to be, which is fine for some until they stagnate or grow out of it; but far from the final answer to anything. I don't get at all how being forced to do anything could ever be a good thing. Smells like
164.
by sifoobar 8y ago
No shit, I recently restarted a project [0] in straight C after giving it a serious try in C++. It's been a while since I dipped my toes, but a couple of weeks of decoding screens upon screens of template instantiations for every singl
165.
by sifoobar 8y ago
From my understanding there are two ways this happens. 1) We mess with plant genetics, which creates weak mono cultures. Bananas being the biggest offender I'm familiar with. And 2) We play God and release our lovely designer creatures
166.
by sifoobar 8y ago
I'm still holding off adding eval() to Snigl [0]. Not because of JIT clashes, since it is a straight interpreter; but because of the can of worms it opens. The thing is that I have to compile code in some kind of context, and depending
167.
by sifoobar 8y ago
None, but that has very little to do with how capable the languages are in the hands of experienced coders. There's a ton of Forth being written in embedded circles, and several well known Lisp projects that are most probably even bigg
168.
by sifoobar 8y ago
How much experience do you have from C, Forth & Lisp? Spend enough time in these languages and you start seeing the world differently. Less syntax (when designed well) doesn't have to be unreadable.
169.
by sifoobar 8y ago
Yet it's not; Forth and C are too primitive for most tasks, and Common Lisp too magical. Snigl aims to find a middle way. Programming languages will always be compromises, you always trade something in to get what you want. Anyone tell
170.
by sifoobar 8y ago
I read that as: less syntax, less leaky abstractions and less macros; and I mostly agree. I would add better integration with the C tool chain, more separation of concerns and less academic ego bullshit. I've been working on something
171.
by sifoobar 8y ago
That's cool, didn't know. We need more of that, some people just don't function very well in office environments and the talent is often somewhere else. Right now though, everything is up in the air when it comes to GitHub. I
172.
by sifoobar 8y ago
I know for sure without looking that there's less C than could have been and no Snigl [0] in there, since I recently packed up my stuff and moved to GitLab. For my needs, the platform is fine; and they embrace remote workers, which I t
173.
by sifoobar 8y ago
Second that, I could recite the Pickaxe book from memory by the time I gave Python a serious try. And I could never really get over loosing my Ruby toys or having to memorize arbitrary quirks like variable scoping, method overriding and mor
174.
by sifoobar 8y ago
Which leads us back to square one, because to do that efficiently they need experience. If they can't tell a dumb feature request from their ass, they're part of the problem.
175.
by sifoobar 8y ago
Learn a different language. I would recommend C, Forth or Lisp for stretching your brain. Solve challenging problems; databases, interpreters, whatever floats your boat. The only way out of the matrix is to keep pushing boundaries, repeatin
176.
by sifoobar 8y ago
I'm pretty sure it was the same old regular buffer overflows as always. Which begs the question, what are you aiming for here?
177.
by sifoobar 8y ago
It's only a hack in C++ these days, from C90 it's standardized. That's like your opinion, plenty of C programmers worth their salt would disagree with you. Look, I'm not saying it's impossible to write code that com
178.
by sifoobar 8y ago
I use C directly when I have to, my preferred setup these days is embedding a more convenient scripting language in C.
179.
by sifoobar 8y ago
I'll repeat this here. Automatic void casts, flexible struct fields and calculating offsets to find the containing struct given a field are three things that I use all the time in C. Last time I checked, C++ wasn't very impressed
180.
by sifoobar 8y ago
Automatic void casts, flexible struct fields and calculating offsets to find the containing struct given a field are three that I use all the time. Last time I checked, C++ wasn't very impressed by either one.

More ›