Perhaps this term is specific to americans, however to an Australian a 'work truck/ute' would be used for labour purposes and not for the family, for example hauling materials, transporting tools or as part of the business itself ?
Yes, American. There's other better descriptions here, but generally speaking most contractors I know have a truck, which they use for work. That's really all that I mean. I mean we just call them trucks. Nobody would say "Hey, nice work truck!"
People buy vehicles based on their needs. The F150 is sort of a hybrid between a work truck and a prestige family SUV like a Ford Explorer. If people are doing serious towing regularly, they will probably upgrade to a 250/350 class (3/4 ton or 1 ton). Plenty of people buy smaller trucks like the Ranger, which is basically like driving a crossover mini-SUV with a bed. People who are doing really serious transport may have a flatbed on an even bigger truck, but nobody uses those as family vehicles. I know people who have those little RHD mini trucks, which seems super useful to me.
I don't know Utes, which by googling, basically looks like a midsize (Ford Ranger, Toyota Tacoma) with a flatbed. We don't really use those.
Actually, it's kind of a market problem. Tons of people I know have expressed desire for a smaller truck like that little barebones Toyota Truck, but they don't make them here and we aren't allowed to import them.
Or maybe it wasn't a reason that makes you look superior, and it's just that a couple people thought the joke was annoying.
You also can't evaluate "HN" based on a couple downvotes on a comment in a buried thread. (I can't see what the score was but it's currently positive so I'm guessing a couple.)
I didn't know about the statem limitation, I have howerver worked around it with gen server like wrapper, that way all state transitions were handled with gleams type system.
I have been meaning to ask about that on the discord but its one of the ten thousand things on my backlog.
Maybe i could write a gen_event equivalent.. I have some code which does very similar things.
Tbh, i loved my minidisc player, robust and shock resistant (I guess it buffered ?) rewritable media. Compared to even CD players it was ahead of the game.
Mine was great too, but it just never took off quite the same, maybe because of price. 'originals' were expensive, and so were recordable discs.
There was also (IIRC) built-in DRM, so you could record digitally from a CD or read-only minidisc to a writeable minidisc, but not then from writeable minidisc->minidisc. Even recording from analogue to minidisc resulted in something that would be restricted.
But this is all just rehashing things that have been talked about many times over the intervening years. They were great, but they never quite made it and then mp3 ate its lunch.
CentOS Stream employs a rolling-release model, which is much less stable than RHEL.
The previous main selling point of CentOS was bug-for-bug compatibility with RHEL. Red Hat is just killing the distro by moving their focus to a non-existent market. Enthusiasts will choose RHEL, while enterprises would choose the more stable RHEL, which Red Hat could earn money from, or alternatives like Alma or Rocky.
CentOS Stream has major versions and EOL dates, and thus is not a rolling release. It functions as the RHEL major version branch and follows the RHEL compatibility rules, so it's the same major version stability as RHEL.
While you may have considered bug-for-bug compatibility the main feature, it was a major point of frustration for many users and the maintainers. That model means you can't fix any bugs or accept contributions from the community. CentOS finally fixed both problems by moving to the Stream model.
reply