Comment Re:What changes does the Professor suggest? (Score 4, Insightful) 6
Comment Re:so (Score 1) 6
Comment Re:The answer is another question (Score 1) 153
Comment Re:Sure! (Score 1) 192
The Four Programmers Sketch (Four old programmers sit reminiscing about the "good old days" of coding.)
Programmer 1: Aye, kids these days have it easy. Writing in Python, JavaScript—high-level languages that do everything for ‘em. Back in my day, we had to write in C!
Programmer 2: C? You were lucky! We had to code in assembly—punching in opcodes by hand!
Programmer 3: Assembly? Luxury! We only had ones and zeroes, flipping switches on the front panel to program each instruction!
Programmer 4: Ones and zeroes? Pfft. We only had zeroes! And we were grateful for ‘em!
You programmed with a keyboard, luxury! We manipulated the bits on a breadboard.
Comment Re:The stock market (Score 1) 57
Comment Re:AI is made of people (Score 1) 168
Comment Re:Syntax (Score 1) 3
The syntax of some of these examples seems more verbose and harder to follow than just writing the XML or JSON itself, especially the anchor examples. Aside from that, XML to JSON conversion exists, though with limitations, seemingly the same ones, such as no comments in JSON so instead you're adding an additional key. Might as well just write one or the other and convert, especially because libxmq is nearly JSON anyway.
This seems to be an effort in part at minification which in JSON can be achieved by other efforts such as shortening the keys and having an agreed map on both sides. If they're going for readability, I'm not sure if this is more readable than JSON. It might appear more readable than XML. I look forward to this standard becoming the 15th universal standard.
The discussion forum on GitHub is inactive at the moment with 1 discussion about windows. As for adding in comments to JSON that's probably not required if both parties understand the payload being exchanged and as you mentioned can easily be worked around by adding in a "_comments" key/value pair.
As I read it with the style chosen, it seems to be more like JavaScript or Java (given the Authors background). This seems reads like someone who wants the features of XML added into JSON, but didn't want to call it JSONX. Having just googled this, the name is already taken by IBM for JSON as XML.
Comment Re:Godfellas (Score 1) 134
Pree was a good example of anticipating ineptitude.
Comment Re:Small government crowd (Score 1) 119
Comment Re:MAID in Canada now accounts for 4.1% of all dea (Score 1) 127
Submission + - AWS will pay devs to verify Rust standard library because of 7,500 unsafe functi (devclass.com)
"The issue AWS highlights is that even if developers use only safe code, most applications still depend on the Rust standard library. AWS states that there are approximately 7.5K unsafe functions in the Rust Standard Library and notes that 57 âoesoundness issuesâ and 20 CVEs (Common Vulnerabilities and Exposures) have been reported in the last three years. The cloud giant also claimed that âoethe rate of change of the standard libraries is faster and more unsound.â "
"The Rust Foundation says that there is a financial reward tied to each challenge, and that the âoechallenge rewards committee is responsible for reviewing activity and dispensing rewards.â How much will be paid though is not stated."