Earlier quoted context omitted.
I suspect the reasons that XML ultimately lost are: 1. You could represent it as a nested structure of your language's standard lists & maps, which you already know the API of, which you could directly operate on. For dynamic languages, this is much faster to stick a prototype together, even if it bites you in the ass eventually. But by the stage, you've already chosen JSON. 2. It was less characters to manually type…
You forgot my favorite one: 6. Too easy to accidentally reinvent Lisp via xml. I thought it was funny the first time I ran into an instance of it happening, which quickly turned into horror. Not only was the logic split, but it meant mentally parsing this: I mean, it sort of makes sense...?
What the f*** is the edge?
181–188 of 188 posts
Re: What the f*** is the edge?
#182Earlier quoted context omitted.
In case anybody else is confused like I was: there is a plug-in for browsers that turns all mention of “cloud” to “butt”. Parent apparently has this plugin installed, and thus the “to butt” part is “to cloud”. (Users of said plugin will see me just saying butt a lot here :P )
Interestingly enough I didn't even notice it until reading your comment. Looks like I have a "butt" to "cloud" translator in my brain.
Re: What the f*** is the edge?
#183Earlier quoted context omitted.
I still don’t understand what problems people have with xml. The json vs xml debate very much feels like the tab vs white space debate to me.
Basically it's a Markup Language, not a data transfer language, so it was far from ideal to use it as one. See for example the ambiguity between what should go into tag attributes vs. tag content etc. Also the eXtensibility makes things too complicated for many use-cases. You don't have to care about any of this with JSON.
Re: What the f*** is the edge?
#184One time, I got a telemarketing call from someone selling satellite TV or something like that. I kept him on the line some time, asking all sorts of enthusiastic questions about his amazing service. I then proceeded to ask him how high up his satellites were, and if they could be giving God cancer. He (obviously) did not have a good answer. I then disappointedly told him that I was going to have to run his setup by m…
Re: What the f*** is the edge?
#185Earlier quoted context omitted.
Would you mind expanding a little. Google has led me to a brand of window maker, and to of course, black hole event horizons but I am not clear on the specific egress horizon. I can guess what you intended but would be interested in the specifics.
Egress = output; Horizon = the border of control, where packets are "released to the world"
It's a cool phrase though so we should definitely use it
Re: What the f*** is the edge?
#186> real-world transmission times between e.g. London and San Francisco end up at around 150ms. That's [...] a catastrophe for self-driving cars needing to make realtime decisions. Why in the world would/should a car in London be relying on a cloud computer in SF to tell it how to make real-time decisions...?
People should stop coming up with such wrong metaphors. Real-time doesn't mean fast, it just means reliable latency. If you miss a cycle it needs to reboot or stop. But it doesnt mean that they are particularly fast. They are rather slow in fact. A real time controller in car would be perfectly fine with 150ms cycles, it just depends what is controlled. An engine controller is fine with 500Hz, a GPS controller with 1…
This! In other words it is determinism. It should be highly deterministic. Most of the real time controllers even suggest to disable cache to be highly deterministic.
Re: What the f*** is the edge?
#187Earlier quoted context omitted.
Egress = output; Horizon = the border of control, where packets are "released to the world"
I assumed that egress horizon was some new black hole phenomenon with interesting properties about not needing a core/ central point. It's a cool phrase though so we should definitely use it
Re: What the f*** is the edge?
#188Earlier quoted context omitted.
Mobile devices' compute power is there to serve a massive amount of input/output components and sensors. If we start to usurp this computing margin for our applications, the devices will overheat and break, irritating quite some people probably.
You mean glitter and ads? Because sensors and I/O doesn't require much power; nowhere near as much as is available.