sifoo

The Agile movement was all about dropping the process hoop jumping and focusing on solving problems efficiently, that's why it was considered extreme. Too extreme, as the one true implementation to rule them all is worse than what the agile movement was revolting against. This is how the game is played, over and over and over again; any movement that threatens the narrative is embraced, corrupted and ultimately used as a weapon against its core values.

Agreed, that's one of the more important advantages of Common Lisp in my book. But the reason it works so well is that the standardized version was based on plenty of experience and experimentation, and that it's powerful enough to be extended from user code; same goes for C to some extent.

Besides basic semantics, there's not that much stack juggling going on really. Cixl offers four stack operators, drop, dup, swap and clear; the idea is to use more convenient constructs like let bindings, closures and multi methods to keep the stack tidy.

Thank you! PostScript is another example.

Glad to see Forth getting some attention, took me around 25 years of coding to find it.

For those looking for a different take on the same ideas, I'm working on a Lisp-inspired Forth here:

https://github.com/basic-gongfu/cixl

There are several leaner alternatives for application scripting, is it really worth dragging V8 around to get that capability? Lua would be one alternative. The reason I'm asking is that I'm working on a more Forth-inspired alternative[0] for application scripting myself, and I'm curious about the reasons for defaulting to the crappiest language ever invented and an implementation controlled by one of the biggest corporate bullies around.

[0] https://github.com/basic-gongfu/cixl

Lisp trades some of the strictness and static typing of Haskell and Scala, and the convenience of Python I guess; for more raw power. You won't really have a clue what macros are capable of before you see it yourself, I wholeheartedly recommend using Let Over Lambda (https://letoverlambda.com) as a guide. The other side of the coin is that you'll spend the rest of your days waiting for mainstream languages to catch up, but that's true of Haskell as well to some extent.

No, that's my point; there are thousands of very experienced and dedicated coders out there who are not sick of it; because we've been around long enough to not blame our tools, and we have enough experience to appreciate its unique strengths. I'm all for simpler and more intuitive, but Rust is the opposite of that; it's rigid and complex if anything. Why does everything have to be a competition? Why can't several technologies be allowed to coexist? This is not about having your opinions challenged, you need to work on your reading comprehension; this is about not attacking others for expressing different preferences from your own.

Every C compiler and major C library out there to begin with, given that it's the most important and fundamental language in the real world right now. Did you get it this time?

Have you been living under a rock lately, or are you just pulling the oldest trick in the psychopath book; condemning others for reacting to abuse? Sharing and attacking others for not agreeing is not the same thing, I hope we agree so far.

Right, question something and you just don't want others to be happy. Good luck with that. Every C compiler and major C library out there to begin with, given that it's the most important and fundamental language in the real world right now. C++ already pulled this trick, it lead nowhere but in circles.

How is questioning the choice of project to fund feeding trolls? I was under the impression that diversity was mostly considered a good thing, that has to go for perspectives as well. I just don't get why Rust desperately needs a lot more money than any other tool that's equally useful, they were already pretty well funded by other organizations.

I'm not quite as enthusiastic about their choice of funding target. There are plenty of other worthy languages and tools out there that could use that money better in my mind. It's the C++/Java thing all over again, but stepped up several notches; to the point where it's creeping me out since I can't even mention C online without being attacked by the Rust Brigade; and they just don't give up, it's like one of those shitty zombie movies where you have squirting body fluids and jaws chopping at you from every angle. I don't think they need any more money; more like therapy, chill pills and rooms with soft walls/locked doors for a while.

And not everyone who needs/wants that is going to prefer Rust's complexity and rigidness to the simplicity and flexibility of C, or the even more complex yet more flexible C++. It's preferences, priorities; not black or white; no one has any right to force anyone to do anything. As long as humans are in the loop we're going to have bugs, what kinds of bugs will depend on priorities.

Until we have as much code written in Rust as is currently implemented in C, experience hasn't shown anything. The same claims and promises have been made for C++ in relation to vanilla C for ages, and it's just not true. An experienced C coder (which arguably takes longer to achieve) will perform as good as a C++ coder of equal skill level. All they do is trade complexity and convenience for simplicity and flexibility; it's a matter of preference, not life and death.

There's a lot of talk about full stack developers lately, I'm still waiting to find the first full stack manager. Someone who's visionary, yet realistic; confident, yet empathic; powerful, yet humble. I feel like there's some truth to the saying that the best leaders are those who don't consider themselves fit to lead.

It's not magic; it's vast amounts of experience; writing more code than, and twisting brains in ways that, normal people can't even imagine; and sticking with it for decades. I have no idea if I'm 5x or 10x or whatever, what I do know is that it's extremely rare to come across people who are more dedicated to the craft and/or have invested more in their skills.

Traditional Yoga contains a set of exercises for the muscles surrounding the eye. Many problems seem to be caused in part by constantly focusing on the same distance/angle; which leads to lack of muscle tone, which in turn affects eye sight.

Been there, done that :)

https://news.ycombinator.com/item?id=16081592

As far as books go; K&R contains a lot of wisdom despite it's apparent simplicity; and the language hasn't really changed that much since last edition. But to answer some of your questions:

CMake is by far the most convenient build tool I've come across for C so far, the link below will give you an idea of how it looks. I find linters mostly a waste of time , but I run all my tests through valgrind before committing; I don't miss programming in C without valgrind at all; it's also an excellent profiler in combination with KCacheGrind. For testing, simple functions and bit of macro magic on top goes pretty far; C programmers tend to value simplicity, you won't find that many epic unit testing adventure frameworks out there. clang or gcc doesn't really matter, I prefer clang's error messages; and both support GNU extensions, which solve most of the boring problems with coding in C.

https://github.com/basic-gongfu/cixl/blob/master/CMakeLists....

One of my all time C favorites.

Will recommending my own project get me hell-voted? Cixl is a straight forward 3-stage (parse/compile/eval) interpreter that is designed to be as fast as possible without compromising on simplicity, transparency and flexibility. The codebase has no external dependencies and is currently hovering around 7 kloc including tests and standard library. There are some articles explaining design decisions, but I've been mostly busy with code. The code should be perfectly readable though, and contains plenty of good ideas distilled from 32 years of daily practice.

https://github.com/basic-gongfu/cixl

https://github.com/basic-gongfu/cixl/tree/master/devlog

Karma has nothing to do with revenge, karma is just another word for consequences. Every action leads to reactions; if they didn't the universe would have descended into chaos in no time at all. And thats how we learn, by acting and studying reactions until we get it. One of those lessons is recognizing the value of all living beings.

At least they have a chance to fight for their survival, which makes all the difference. If it's horrible when done to humans, it's horrible when done to animals. And as long as we keep doing it to animals, we shouldn't expect to escape the same fate ourselves; Karma 101.

Sounds like a bedtime story in my ears. We're eating more and more meat, and demanding that it gets cheaper and cheaper while the stock market index needs to go higher and higher. It won't stop until the majority is willing to look beyond the bullshit we're being fed and start using their brains.

Have you bothered to look into it? It's not like the information is impossible to find, even if they don't exactly advertise the icky parts of their business. 'Eating Animals' by Jonathan Safran Foer is a good place to start.

What's the difference then? Piling up living beings in awful conditions to kill them in the most cost-effective way is pretty much the definition of a concentration camp. And making them grow faster than they're supposed to at the expense of everything isn't very nice either.

Fish farms are concentration camps for fish, same goes for the rest of the meat industry. The reason they need all the antibiotics is because the animals are so sick they just wouldn't survive without. Many still don't, it's just more effective to let 20% or so die if it allows stuffing more animals in the same space. Did anyone really think we would get away with treating animals like that and not have to face the consequences? Just say no, really. It's a disgusting, harmful habit; much more so than tobacco and alcohol. And down-voting me for telling you what you already knew isn't going to save you.

I thought the fact that he buys and injects blood from teenagers to (possibly) extend his own pathetic life would have proven that much by now. Someone said something about it being easier to pass camels through eyes of needles than for rich men to go to heaven.

Yeah, keep telling yourself that. Do you actually write code to solve problems yourself or are you more into paying others to do the same? I honestly don't know which alternative would be worst here. What I do know is that this attitude isn't serving us. We're in the business of solving really tricky problems, forcing ourselves to do that using dumbed down tools to protect us from our own intelligence and creativity is insane.

It's a work in progress, but this is the longest piece of code so far. It's the start of a simple booking system.

https://github.com/basic-gongfu/cixl/blob/master/examples/bo...