{mark}™, revolutionary new data format better than JSON and XML

https://github.com/henry-luo/mark
{mark}™ created by Henry Luo® is a superset of JSON made for the modern web.
{mark}™ runs directly in the browser compared to other data interchange formats like YAML, TOML and HTML.
{mark}™ was invented by Henry Luo® for He was dissatisfied with JSON and created {mark}™ as a superset that fixes absolutely every single flaw of JSON.
{mark}™ is guaranteed to take the world by storm so you should invest in {mark}™coin™ which combines the power of {mark}™ with the power of the blockchain.

Also it's not SEXPRs fuck you Sussman everyone knows you're a jewish scammer faggot.

The advantage of Mark over S-expressions is that it is more modern, and can directly run in browser and node.js environments.

hahaha,

lol

He didn't even bother to get rid of the metadata nonsense. He literally just changed the delimiters.

Why is arbitrary data "running"?

>>2

Being 'more modern' means Mark takes a JS-first or web-first approach in its design. Whether we like it or not, JS has dominated the web. JSON is successful, partly because it takes a JS-first approach. Mark inherits this approach.
Being JS-first, means there'll be least adoption barrier in web.
Being JS-first, of course does not mean JS-only. Mark is designed to be generic and used by other programming languages like JSON.

Also it's not SEXPRs fuck you Sussman

This looks just like S-expressions.
Even the table says so.

>>2

more modern, and can directly run in browser and node.js environments.

Good 1

superset of JSON

It hurts.

Fully-typed

What is this supposed to even mean.

this is what happens when you forget to read SICP

>>8
I wish that reading the whole SICP and doing the exercises was a mandatory part of getting a CS/SE/CE degree.

>>9
Humanity would die out. But we would develop VERY clean fibs programs in the process.

>>8-9
SICP is MIT virtue signaling.

>>10
I accept the trade-offs.

>>11
MIT doesn't even use SICP anymore because it's shit. MIT that is.

>>13
MIT is elite college why would they use a textbook published in 1983?
40 years ago computers were shit, they couldn't even play properly chess, it would be like a mechanics learning about steam engine. Students need to be trained in modern computing and not some old irrelevant shit

>>13
MIT teaches tinkering with Python now. The problem is too many pokers and tinkerers with no good CS education so what do they do? They design a curriculum to make more pokers. They make sure nobody has a good CS education so they won't be able to complain because they don't know any better.

According to Sussman, his students spend most of their time reading manuals for these libraries to figure out how to stitch them together to get a job done. He said that programming today is “More like science. You grab this piece of library and you poke at it. You write programs that poke it and see what it does. And you say, ‘Can I tweak it to do the thing I want?'”. The “analysis-by-synthesis” view of SICP — where you build a larger system out of smaller, simple parts — became irrelevant. Nowadays, we do programming by poking.

>>15
thanks it was very enlightening
I could maybe make a mud from scratch in R5RS but what's the point when I can make a 3d game with poking at engines and libraries?

>>14
They wrote the thing! It's still a valid work of teaching because the fundamentals don't change no matter what is contemporary. There are two reasons why they stopped teaching SICP. The first is that they got tired of teaching it! I wouldn't blame them for wanting to retire from teaching the same material every year for decades on end. The second is that contemporary software engineers don't need to assemble systems from the ground up due to the comprehensive nature of libraries and frameworks.

SICP's principles are completely valid today. You are confused if you thought the purpose of SICP is to teach computer programming.

>>15
The MIT computer science curriculum is still there for people who want it. It's not a bad thing that there are people who want to learn fundamental programming principles to assist their vocation without the need to study the computer science that underpins the programming. It's not a bad thing that there are classes formed to teach these people. That fundamental computer science knowledge isn't going away. These new classes do not replace fundamental computer science knowledge, they complement it.

>>16
Computer science is not a discipline in programming. The theory of computer science is in the study of the nature of computation and language i.e. studying the theory of implementing R5RS from scratch. It's perfectly valid for you to write 3D games while making use of general purpose engines because that isn't related to computer science.

>>17

I wouldn't blame them for wanting to retire from teaching the same material every year for decades on end.

What the fuck kind of reasoning is this?

>>18
Go ask Jerry Sussman and Hal Abelson. They are the ones who wrote SICP, lectured it for many decades, and then decided to retire from lecturing it at MIT.

>>19
You better be ready to prove this because if they seriously changed the curriculum because they didn't want to teach the same material every year they are going senile. This sounds more like you're putting things in their mouths.

put this in your mouth!
*grabs dick*

check this!
*grabs dubs*

>>20
http://www.posteriorscience.net/?p=206

>>23
Shameful.

why's sexpr not standard if it's so great?

But the beast was captured, and with it the false prophet who had performed the signs on its behalf. With these signs he had deluded those who had received the {mark}™ of the beast and worshiped its image. The two of them were thrown alive into the fiery lake of burning sulfur.

>>26
lol'd

>>25
Sadly, it has to do with popularity.

>>25
Can't you read? Because you can't use it in javascript and the web

>>29
SPAWHBTC? It's not used in JS because it's not standard. Despite the name, JSON is not any more native in JS than SEXPCODDE.

>>30
I never said any of those