mal10c

I dislike this. But honestly, I dislike assert statements. I mainly write code that cannot fail. And if something does go wrong, I must handle that in an appropriate way. Asserts are never the way because they terminate the program.

In strictly my opinion, I don't have a problem with pre/post condition comments in a header. They clearly describe important details. Introducing yet another way to support asserts seems very unnecessary to me, but I guess I'm not obligated to use it either.

Got this building on FreeBSD for those interested:

1. Install the GTK stack:

  pkg install gtk4 libadwaita webkit2-gtk_60 pkgconf

2. FreeBSD ships WebKitGTK 2.46.6 and the project turns on the v2_50 feature of the webkit6 crate, so switch that to v2_46:

  sed -i '' 's/v2_50/v2_46/' $(git grep -l v2_50 -- '*Cargo.toml')

After that, cargo build completes against 2.46.

The author and I think very much alike. I felt like I was reading a journal from myself. I work for a larger engineering company and often times feel misaligned. This read helped put into words exactly how I approach problems and helps me better articulate that misalignment. Thank you to the author, great read!

I have an almost identical story. I wrote a few games: snake and a choose your own adventure fantasy thing. And likely others that I can't remember, but yeah, I had a teacher tell me basically the same thing. I was pretty sad because those really took a lot of time.

I totally agree with this! I've spent a career learning and making software of all types. I started with DOS 4, worked through VB6, and so on. Now I think more broadly and my mind is always thinking of new ideas, but with a family, it's tough to find time to create some of these. I know what the software needs to do and even what it should look like. I know the acceptance criteria and what will and won't work, so Claude has been great just being an extra set of fingers. I use it to create all sorts of projects that I would never have time to make with my busy schedule, and it's so much fun!

reticulating splines

I agree with your thought process. Factoring in antenna type and reflections also causes difficulties when explaining concepts like super position. The sinusoid is a good illustration of what a given receiver might detect at some location (X,Y,Z). A more accurate way to show that may be a light source fading on and off to match some frequency (below THz). Then factoring in the speed of light, at time zero, the light will be off, at some arbitrary time 1, the light will be illuminated at 0.25 (scale goes up to 1 here). The light energy peak at time 1 is at the light. Then at time 2, the light goes up to 0.5. That means that the 0.25 light is now 1 unit away from the light while the 0.5 is at the light. Step to time 3 and the light goes up to 0.75, meaning 1 unit from the light, the light is at 0.5 and 2 units from the light, the light is dimmer at 0.25. This repeats with the light hitting 1.0 then falling back to 0.75, then 0.5, etc. The movement of light is key and I think that's what is often either misunderstood or just not considered enough.

I really enjoy posts like this one because I always learn something. Sure the whole program can be written using bitwise comparison or modulus, but that's not the point. The thing I learned is how to map that into address space! That's a cool trick!

I don't understand how to use this, but it does touch on an interesting topic. I want to create interactive and animated diagrams. I normally use either Draw.io or plantuml. My goal is to better teach folks about the systems I'm building, through better visualizations. Something like IcePanel (which is way too expensive) sort of shows flows, but I'd like to have full control. Does this tool claim to support something like that? If not, are there options out there that I don't know about?

Honestly, if it ran Affinity photo and SilverFast, I'd be happy to pay that. Same goes for Linux, whatever can run those!

This brought back a lot of memories!

YES! This project, this is what the internet is for!

I agree with the comments, that's a pretty lame excuse. But I've gotta understand where others are coming from here. I just don't see why Apple is in such hot water here - they created a gadget (well multiple) that people like. We're not forced to buy those gadgets and we have alternatives. Sure Apple has made a butt load of money on this, but it's not like other players are prevented from making similar gadgets. I guess if I made a thing, say a new type of keyboard and I also make a motherboard and ultimately some new type of computer - then isn't it my prerogative to decide that I'm only going to support that keyboard with that computer? Or is that thinking too simple: instead is the problem that Apple isn't allowing others to take the device they bought (keyboard in this example) and on their own make it work with their Asus computer? eh, maybe a lame example but happy to hear thoughts and feedback.

This is awesome! About a year ago, I switched to a Moonlander keyboard. At that time, I figured why not try a different layout while I'm at it, how hard could it be? I compared a bunch of layouts and finally went with Colemak-DHm. I'm nowhere even close to my typing speed on a QWERTY layout, but absolutely loving it! This typing game will really help me get more comfortable with that new layout!

For ham operators, there's Winlink, which is an email system that uses ham frequencies to exchange messages. And yep, there are rules where you need to say your call sign periodically, and Winlink does that on your behalf.