Could someone show a legit reason to use 1000-character filenames? Seems to me, when filenames are long like that, they are actually capturing several KEYS that can be easily searched via ls & re's. e.g.
But to me this stuff should be in metadata. It's just that we don't have great tools for grepping the metadata.
Heck, the original Macintosh FS had no subdirectories - they were faked by burying subdirectory names in the (flat filesysytem) filename. The original Macintosh File System (MFS), did not support true hierarchical subdirectories. Instead, the illusion of subdirectories was created by embedding folder-like names into the filenames themselves.
This was done by using colons (:) as separators in filenames. A file named Folder:Subfolder:File would appear to belong to a subfolder within a folder. This was entirely a user interface convention managed by the Finder. Internally, MFS stored all files in a flat namespace, with no actual directory hierarchy in the filesystem structure.
So, there is 'utility' in "overloading the filename space". But...
> Could someone show a legit reason to use 1000-character filenames?
1023 byte names can mean less than 250 characters due to use of unicode and utf-8. Add to it unicode normalization which might "expand" some characters into two or more combining characters, deliberate use of combining characters, emoji, rare characters, and you might end up with many "characters" taking more than 4 bytes. A single "country flag" character will be usually 8 bytes, usually most emoji will be at least 4 bytes, skin tone modifiers will add 4 bytes, etc.
this ' ' takes 27 bytes in my terminal, '' takes 28, another combo I found is 35 bytes.
And that's on top of just getting a long title using let's say one of CJK or other less common scripts - an early manuscript of somewhat successful Japanese novel has a non-normalized filename of 119 byte, and it's nowhere close to actually long titles, something that someone might reasonably have on disk. A random find on the internet easily points to a book title that takes over 300 bytes in non-normalized utf8.
P.S. proper title of "Robinson Crusoe" if used as filename takes at least 395 bytes...
The “CC” in the TI part numbers stands for “ChipCon”, who TI acquired for these wireless products. The CC1100, one of their earliest parts, has a documented but unsupported debug mode which dumps raw quadrature samples out some of the I/O pins. Later parts do not mention such a feature in their documentation, but it’s not proven it was removed.
Author here, it’s totally possible to get IQ samples from the RX chain! Unfortunately, the design of the TX chain is in such a way that it does not work off of IQ DACs, and is more limited in what the silicon can generate.
Which open source stacks work with Infineon CYW43439 (used on Pico w and Pico 2W)? I know about BTstack, but apparently NimBLE is not ported to this chip.
I'm also curious, of all the available BLE chips, which one has the "most sane" development environment? I had the misfortune of using the SiLabs BLE chips, and it seems like the Dev Environment was meant for Web dudes or something -- it seemed very foreign to me, an embedded guy. It was like 5 layers to go from their SDK down to the machine instruction that would set the value of a GPIO pin hi or lo. Confused documentation, spread out over dozens of not-related sections, weird configuration wizards, etc. Now, the Hardware seemed just fine, but gosh, the Dev Environment?
I've heard good things about Nordic's environment, but haven't used it. I also know nothing about TI's or AD's.
The older Nordic SDK wasn't too bad (once you get over the learning curve). Trying to start a project from scratch is challenging though, so much easier to pick the closest example, get that going and modify from there.
However, they've deprecated the old SDK [0] in favour of Zephyr [1] and quite a number of people struggle with it (check the forums and general internet). I have less experience with Zephyr, but both of them use a lot of python support tools which seem to suffer from versioning amd compatibility problems (even trying to keep a stable platform has been difficult here, what works one time doesn't work a few months later). YMMV.
There are good reasons for depreciating the nrf5 sdk. However, I’m not sure how long the Nordic Semi lead is going to last.
Previously if there was a project that came up that didn’t strictly need BLE, I’d recommend the nrf5 sdk because it was reliable and stable. Now with the new sdk they are encouraging people to write firmware that’s much easier to port to other mcus (with zephyr) and the development experience has much higher cognitive load.
There already is underutilized spectrum for V2V, Dedicated Short-Range Communication (DSRC), in the 5.9 GHz band -- the lower 45 MHz(5.850-5.895 GHz) for unlicensed uses, such as Wi-Fi, and the upper 30 MHz (5.895-5.925 GHz) for Intelligent Transportation Systems (ITS) applications, including vehicle-to-vehicle (V2V) communications.
In November 2024, the FCC finalized rules of the 5.850-5.925 GHz band, including for Cellular Vehicle-to-Everything (C-V2X) technology, which is considered a successor to DSRC for V2V and vehicle-to-infrastructure (V2I) communications.
V2V had spectrum allocated to it since 1999. But V2V+V2I got sucked into C-V2X which is astounding to me; on the one hand it make sense (5G is good at this sort of thing), but now you have gatekeepers taking their cut to provide the Service. It it were straight V2V, then it would have been free-to-use. It is astounding to me that in 2024, we still do not have the vehicle in front of you sending to your car's computers data that the driver ahead just hit his/her brakes, and you should be prepared to do the same. AEB is fine, but the current attitude seems to be "Battleship My Car" - meaning, collect all the data, make all the decisions in MY car, other cars be damned...or, ignored.
My guess is V2V just presented too many security holes to win widespread adoption. If you could go around spoofing braking events on the highway, that would be super dangerous. But that's just my guess.
As to talking with cars around you, get a ham radio license, and set your HT to 146.52 MHz -- the national simplex calling frequency. The more people we have monitoring 146.52, the better. That frequency, more than any other ham radio frequency, is the nationwide "SOS!" channel. If you have an emergency out of cellphone range, but you have an HT, often 'somebody' will hear you on 146.52 and can call for help. The other common calling frequency is 446.000 but 2 meters tends to have better range through forest terrain; and probably more people listen to "52" than 446.000 --- but try both in an emergency.
Yes. Beamforming for the receiver, tho, is highly beneficial. MIMO does that for you. The previous poster is correct, the EIRP must not increase when antenna gain does; you have to turn down the wick on the TX.
What percentage of the population is on GLP-1 drugs right now?
Well "According to KFF polling from May 2024, 6% of all adults report that they currently are taking a GLP-1 drug, and 12% report that they've ever taken a GLP-1 drug".
Is 6% enough to affect crop prices? Presumably some ag economist can weigh in. Note it would only be a reduction per person, not a full 6% reduction in consumption.
Must be in the air? Seriously, maybe abundant low-quality sources? AI sez:
The diet in North Korea is characterized by a heavy focus on grains, but has changed over time to include more animal protein:
Grains, Rice, wheat, and maize are the main sources of calories in the North Korean diet. In 1961, over 70% of calories came from grains, and that number dropped to 61% five decades later.
Animal protein
Before 2000, North Korea's diet was mostly vegetarian, with meat eaten only a few times a year. However, since 2005, the availability of animal protein has increased, with an emphasis on poultry, pigs, rabbits, sheep, goats, and cattle.
Other foods
Popular foods in North Korea include kimchi, red pepper paste, soybean paste, soup, and rice dishes. A traditional meal might include side dishes, a main course like noodles, porridge, or grilled meat, and rice dishes.
Regional differences
People in rural areas and mountain valleys eat more vegetables and herbs, while people in coastal areas have access to seafood.
Healthy options
The upper class in North Korea favor healthy, balanced diets, including chicken wraps and tofu rice.
I was instructed as an 11- or 12-year old to read aCfL. I thought it was clever the way the Middle Ages intersected with post nuclear war Earth as the setting. Questions about what is important, venerated, and why. What 'knowing' means.
As to the bleak outlook, I don't remember enough (it was a long time ago), but a few years ago looked it up on Wikipedia https://en.wikipedia.org/wiki/A_Canticle_for_Leibowitz?usesk...https://en.wikipedia.org/wiki/Walter_M._Miller_Jr.?useskin=v... I learned that Arthur Miller Jr suffered from depression and chose to end his life with a firearm in 1996, age 72. I am always somewhat 'on guard' when I read works from people who were suffering with an illness like that, wondering how much of the story is infused with unnecessarily dour material when another, perhaps more upbeat approach, would have served the story as well. I guess I do not want to be dragged into depression by being overly bummed out by Fiction.
2025-Jan-14-1258.93743_Experiment-2345_Gas-Flow-375.3_etc_etc.dat
But to me this stuff should be in metadata. It's just that we don't have great tools for grepping the metadata.
Heck, the original Macintosh FS had no subdirectories - they were faked by burying subdirectory names in the (flat filesysytem) filename. The original Macintosh File System (MFS), did not support true hierarchical subdirectories. Instead, the illusion of subdirectories was created by embedding folder-like names into the filenames themselves.
This was done by using colons (:) as separators in filenames. A file named Folder:Subfolder:File would appear to belong to a subfolder within a folder. This was entirely a user interface convention managed by the Finder. Internally, MFS stored all files in a flat namespace, with no actual directory hierarchy in the filesystem structure.
So, there is 'utility' in "overloading the filename space". But...
reply