>I pretty like the idea of a superset of JSON that supports (1) comments, (2) trailing commas, (3) unquoted properties, (4) optional {} for the root object, (5) multi-line strings, (6) number separator.
You're 90% way there to YAML.
And YAML 1.2 cleaned up most of the annoying YAML edgecases too
They could if you parsed it into syntax tree wit some methods to access keys instead of parsing into native struct. I think I saw YAML parser doing it...
I think it is purely a technology problem. Discord software is good and for text/voice chat nothing really compares to the ease of use, features and ecosystem around it.
> 90% of everything is crap. In the case of chat, I think that's more like 99.9% of everything is crap.
Right but with 90% of everything crap you moved the 10% of good things into closed (for search results) system.
> If Twitter died tomorrow (not as unlikely as it was 6 months ago) then we'd still have a decent archive of the good tweets. All we'd lose is all the dross. The same is true for other platforms; the good stuff gets cross-posted and preserved.
Tweets are searchable and you can't archive.org discord chat easily. Terrible comparison and it is not same for other platforms.
Eh, that heavily depends on language and dataset you're working with. I've seen "simple" data with some fat thing like RoR on top of it having 10x the latency of the underlying database after all the ORMing.
> Look, most modern software is spending 99.9% of the time waiting for user input, and 0.1% of the time actually calculating something. If you're writing a AAA video game, or high performance calculation software then sure, go crazy, get those improvements.
CPU meter when clicking anything on "modern" webpage proves that's a lie.
Also, sure, even if "clicking on things" is maybe 1-5% vs "looking at things" THAT'S THE CRITICAL PATH.
Once the app rendered a view obviously it is not doing much but user is also not waiting on anyting and is "being productive", parsing whatever is displayed.
The critical path, the wasted time is the time app takes to render stuff and "but 99% of the time is not doing it" is irrelevant.
There is a myth that software developers are good with computers but that's mostly not the case, hence heavy mac/windows usage, harder to break than someone with linux machine and root.
Licenses are PITA to deal with regardless of how much you're being paid.
Especially on servers, and especially if for some stupid reason licensed software need internet access to confirm it is licensed, coz that's extra crap that needs to be added on proxy or firewalls and will inevitably break when they change something.
If it's "hey, pay us X and we trust you don't cheat us" yeah, it's just extra invoice ,whatever.
Counter-point: most of the value is "a repository of images" and that's just hard sell to pay massive extra (over just "a local VM with some code running" or some of the cloud offerings) for a essentially S3-like file storage with slightly different API and some structure.
Yeah tools and common container format is why it got popular but with amount of alternatives that's not monetizable either.
Docker desktop is a smart move honestly, monetize stuff around the containers (managing, making sure its secure) that generally requires a lot of knowledge without it, so the pitch is not just "make the job easier" but "maybe allow company to skip hiring person(s) dedicated to running the whole house of cards"
80x25
> I set all my terminals to 22x23.
You are a very silly man and silliness should not be catered for.
> Will --help run a few quick ioctls to calculate screen size?
Your terminal can wrap text around just fine. If it can't, ask for refund.