Wow, they throw some serious spars at these duodecimal people:
> the problem is that Latin uses base ten, so bases larger than ten end up with names that put a bit too much of an emphasis on their relationship with decimal: undecimal, duodecimal, tridecimal, etc. people who like base twelve like to call it "dozenal" instead of "duodecimal" for this exact reason. these names are simply too biased in decimal's favor. ideally, every base should have a unique name that reflects its properties, rather than trivial information about its size.
wait is your email really [email protected]? I registered java.lang.string (at) gmail back when I was learning java 20+ years ago. Haven't really used it in over a decade though.
Can it become a proxy for AI companies to collect patient data and medical history or "train" on the data and sell that as a service to insurance companies.
There's HIPAA but AI firms have ignored copyright laws, so ignoring HIPAA or making consent mandatory is not a big leap from there.
I think this is a case where I simply don't know enough, but couldn't auto-pilot be a lot easier and safer when adding a new axis? A lot fewer things to run into in the air, and if you could just rise or fall a couple dozen feet to avoid an collision seems safer.
The big limitation of autopilots is that they can't handle emergencies. By their nature emergencies are unpredictable so programmers can't reliably code for emergency situation handling in advance. An experienced human pilot at least has a chance to figure out a solution by reasoning from first principles and reacting intuitively to novel situations. These new eVTOL aircraft have a certain amount of redundancy built in but realistically if anything goes seriously wrong they're just going to spin and crash (or maybe pop a recovery parachute if so equipped and within the flight envelope for those to work).
Autopilots also can't handle VHF voice comms (with a very narrow exception for the Garmin Autonomí system in certain situations) or perform "see and avoid" traffic management in VFR.
Not sure about the autopilot part (even planes autopilots follow a flight path). I'm not an expert either, but with roads, there are clear lanes and markings. And ability to generally see around you, and judge distance.
Is what sets the lanes in the air are traffic controllers and flight plans? We're already short on traffic controllers. And there are already lots of near-misses (and not near-misses) even with the heavy regulation and control. Can't imagine having it as mass personal transit driven manually. There'd need to be a mass central system that controls everything, and in that case, might as well just keep it commercial
The energy efficiency isn't great either on personal aircraft
If it's autopilot you could probably also channel the vehicles to specific routes such that they maintain a road like set of channels where they're flying so the rest of us can not worry about random flying cars zooming around our yards and playgrounds.
We already do this with planes which have corridors they fly along.
A small comment for anyone new to xslt. The author references a wildcard rule in the comments [0]. While that is true, they are calling an identity transformation [1]. Identity transformations are very common in xslt.
FWIW, I see your comment. Also late to the thread though. This ruling is being watched at my office. I want to be a bit anonymous, but we've been doing a much more analogue version of some of these things for 75 years. With academics being our primary market. We've only had two legal issues in that time. Both settled out of court. But we walk a fine line.
Understandable. I work in academic publishing, and while the XML is everywhere crowd is graying, retiring, or even dying :( it still remains an excellent option for document markup. Additionally, a lot of government data produced in the US and EU make heavy use of XML technologies. I imagine they could be an interested consumer of Nanonets-OCR. TEI could be a good choice as well tested and developed conversions exist to other popular, less structured, formats.
MyST Markdown (the MD flavour, not the same-named Document Engine) was inspired by ReST. It was created to address the main pain-point of ReST for incoming users (it's not Markdown!).
As a project, the tooling to parse MyST Markdown was built on top of Sphinx, which primarily expects ReST as input. Now, I would not be surprised if most _new_ Sphinx users are using MyST Markdown (but I have no data there!)
Subsequently, the Jupyter Book project that built those tools has pivoted to building a new document engine that's better focused on the use-cases of our audience and leaning into modern tooling.
Yeah this really hurts. If your goal is to precisely mark up a document with some structural elements, XML is strictly superior to Markdown.
The fact that someone would go to all the work to build a model to extract the structure of documents, then choose an output format strictly less expressive than XML, speaks poorly of the state of cross-generational knowledge sharing within the industry.
I think the choice mainly stems from how you want to use the output. If the output is going to get fed to another LLM, then you want to select markup language where 1) the grammer would not cause too many issues with tokenization 2) which LLM has seen a lot in past 3) generates minimal number of tokens. I think markdown fits it much better compared to other markup languages.
If goal is to parse this output programmatically, then I agree a more structured markup language is better choice.
I've casually tried to track down a voice in weather from that time with no luck, but this project scratches the itch somewhat. When I was younger (late 90s-early 00's) I spent a fair amount of my summers fishing with my father and brother on Lake Ontario. We would occasionally turn on the radio and catch a weather report from the coast guard/noaa. There was something about that then out-dated computer generated voice delivering the weather succinctly and to the point.
It was actually a project I used to evaluate coding done by an LLM. It was mediocre and took way too many iterations. But I now have a keyboard shortcut that will fetch KML/XML from noaa, parse out my important details, and read it back to me. The voice isn't quite right. But the morning I spent working on that was a good distraction at the time.
> the problem is that Latin uses base ten, so bases larger than ten end up with names that put a bit too much of an emphasis on their relationship with decimal: undecimal, duodecimal, tridecimal, etc. people who like base twelve like to call it "dozenal" instead of "duodecimal" for this exact reason. these names are simply too biased in decimal's favor. ideally, every base should have a unique name that reflects its properties, rather than trivial information about its size.
reply