I don't want to be a Coalton shill, but this is almost exactly the reason it was built. It shouldn't be either-or. Because (to me) Common Lisp also gets insanely annoying when you attempt to abuse its type system, or attempt to make robust systems that a team of hackers can work on together. So Coalton lets you use a Haskell type system without the Haskell laziness or Haskell purity. Add a PRINT wherever you'd like.

This was the common convention on the 18-bit DEC PDP-7 computer that Dennis Ritchie originally wrote the B programming language for, and carried over to the PDP-11 C was originally written for. Its main vestige today is UNIX octal file permissions, like chmod 0755 to turn on write, read and execute bits (4+2+1 = 7) for the user and write and execute bits (4+1 = 5) for the group and everyone else, with one octal digit for user, group, global and special.

The legacy 8-bit locales are incredibly complicated, degrade performance even if you don’t use them, confuse programmers, and are completely obsolete because 8-bit fixed-width encodings (other than possibly ASCII) are no longer enough for any real-world program. None of the APIs for them even work with modern programs that support UTF-8, except converting multi-byte strings to wide strings, which are broken on Windows. So you can’t portably do anything whatsoever with locales, because implementations don’t support the small part of the interface that is specified to be useful for modern software.

commenting out a type signature, loading the module, and running :t isXFactorOfY and copy-pasting the signature into the module is a classic thing to do

> you can't really view two mallocs as mergeable even if the addresses it gave you would make this possible. I don't understand why this would be a problem in my case, considering the example I have given above uses only a single, big malloc. Nor am I talking about the use of syscalls like mmap here. > If you now start doing some syscall magic to make your self-allocated array larger, The whole idea is that you don't. You just malloc a large amount(essentially an upper limit) of memory and use it without worrying about reallocation is what I proposed.

I would just pass a function pointer in that gets called whenever a request matches it. If the user thinks what they're doing is heavyweight enough, let them delegate it to a thread pool themselves inside the callback. Another approach is to use something like FastCGI; either make your application a much-simpler FastCGI client and let NGINX handle all the HTTP stuff, or make your HTTP server handle client requests by delegating them to FastCGI clients.

Welcome! C and Haskell is a fun contrast: one makes you think about memory, the other makes you think about structure. Sounds like a good fit here.

Welcome! Rust, C, Linux, and networking sounds like a very solid mix. I’ll be interested in any debugging stories you decide to share.

Welcome! C, Rust, math, and formal methods sounds like a great mix. I’d definitely read posts about reliability and software correctness.

Welcome! Parsers and small tools are always interesting. OCaml is a great language to explore if you like that kind of thing.

I just hate that you still have to use the old boto3 connection style because Glue is still using the old version of some library that can't handle the new connection style.

My guess WOULD be python 3.8 end of support for AWS lambda but that does not quite line up. It was EOS in oct 2024. Likely some other runtime EoL. Same with official 3.8 EoL.

As a language at that time, this C is far closer to basic assembler language than later C versions. Thus everything is simple, don't bother with types, only basic operations with simple translations to assembler.

I've seen this before, and Unix source code from Lyon's book. It is interesting the environments back then versus today. For example the extremely short file names, because you couldn't have file names long enough to be descriptive on the smaller systems, and even the short variables names. Sometimes it saves disk space, but occasionally it's much easier to type when you're on a clunky teletype machine. Also, the primitive early syntax of C is unusual. I didn't see any structs, but you see them in Unix source. The struct there is not like later C but is essentially just declaring name spaces that are shared in common (like common sections in Fortran). Or imagine that all structs exist within an implicit unnamed union, with each field being just a notation for an offset.

If you're not doing anything wrong, what's the big deal? Honest people have nothing to fear from a little investigation.

Every few months it's another one of these. Doesn't matter which admin is in power, just a different flavor of incompetence leading to our data being leaked. When will they actually get serious about this stuff?

Too many.

It's not about *if* you're on camera, it's about the *extent* and *purpose* of the data collection and how easily accessible that information is. Flock cameras feed directly into private databases that police can query. That's a huge difference from a corner store's CCTV.

Seriously. Basic security 101.

It's not a 'mandatory government app for social media access', it's an EU framework for age verification. Big difference. And Cyprus is using it. This is about protecting kids, not spying on you.

Yeah, this feels less about protecting kids and more about control, honestly. Kinda worrying precedent, even if social media can be toxic.

Honestly, this is why I stick to direct search or reputable news sources. AI summaries always felt... off. Like, where's this info *really* coming from, and who else is getting a cut?