https://intellectia.ai/news/stock/ibm-mainframe-business-ach...
60% YoY growth is pretty excellent for an "outdated" technology.
640 karma · joined April 21, 2017
https://intellectia.ai/news/stock/ibm-mainframe-business-ach...
60% YoY growth is pretty excellent for an "outdated" technology.
Just kidding... That sounds like my journey as well. I had friends in the neighborhood who also had the TI-99/4a. We all had Cub Scouts and Boy's Life magazine listings to key in.
Did you have the data cassette recorder? We used to try to "load programs" from Michael Jackson's Thriller album.
I cannot recall the cartoon, but there was a revelation of "why a character was such a bad actor" (a jerk). And the reply was ironically one of care — "I don't want anyone to miss me after I'm gone".
As if to relieve the pain of loss they wanted others to feel relief.
I wish I could recall the cartoon and the author.
It's really not bad, and you can use it for scripting like sed, but it's clunkier.
lol?
But, if you squint, great API design is a bit like embedded domain specific language design as well.
I think there's room for both.
And I think you're downplaying many of the ones I mentioned, but I think this level of "importance" is subjective to the task at hand and one's level of frustrations.
I guess forth as well... hmmm
Extremely clear at the "call site" what's going on.
CLOS seems pretty good, but then again I'm a bit inexperienced. Bring back Dylan!
I don't think move semantics are really that bad personally, and some languages move by default (isn't that Rust's whole thing?).
What I don't like is the implicit ambiguous nature of "What does this line of code mean out of context" in C++. Good luck!
I have hope for C++front/Cpp2. https://github.com/hsutter/cppfront
(oh and I think you can write a whole book on the different ways to initialize variables in C++).
The result is you might be able to use C++ to write something new, and stick to a style that's readable... to you! But it might not make everyone else who "knows C++" instantly able to work on your code.
Ignore the fact that having more keywords in C++ precludes the legality of some C code being C++. (`int class;`)
void * implicit casting in C just works, but in C++ it must be an explicit cast (which is kind of funny considering all the confusing implicit behavior in C++).
C++20 does have C11's designated initialization now, which helps in some cases, but that was a pain for a long time.
enums and conversion between integers is very strict in C++.
`char * message = "Hello"` is valid C but not C++ (since you cannot mutate the pointed to string, it must be `const` in C++)
C99 introduced variadic macros that didn't become standard C++ until 2011.
C doesn't allow for empty structs. You can do it in C++, but sizeof(EmptyStruct) is 1. And if C lets you get away with it in some compilers, I'll bet it's 0.
Anyway, all of these things and likely more can ruin your party if you think you're going to compile C code with a C++ compiler.
Also don't forget if you want code to be C callable in C++ you have to use `extern "C"` wrappers.
It can actually drive emacs itself, creating buffers, being told not to edit the buffers and simply respond in the chat etc.
I actually _like_ working with efrit vs other LLM integrations in editors.
In fact I kind of need to have my anthropic console up to watch my usage... whoops!
Has Ron Minnich's port of "Nix" (not NixOS as you may know it), to 9front.
The entire point of this is to disallow the kernel pre-empting and switching out CPU cores that should be dedicated to an "application". (Application Cores).
One could imagine this arrangement plus io_uring would be awfully nice.
It's not blanket good advice for all things.
In my experience “oversubscribing” threads to cores (more threads than cores) provides a wall-clock time benefit.
I think one thread per core would work better without preemptive scheduling.
But then we aren’t talking about Unix.
It's an interesting idea to think that LLMs could be used to not only explain the code but test the potentially tricky corner cases.
I'm pretty sure LLMs are here to stay, and we're just going to have to learn the best ways to work with them.
I don't think even 386BSD existed when Linus started Linux.