|
All I am saying is a warp bubble is much safer!
Speed is "null" and space is moving safely around ya!
|
|
|
|
|
I though it has shield to contain the spaceship
|
|
|
|
|
It would be great if we achieve this relatively soon. I remember reading about possible planets in the habitable zone within 10-20 light years. Would be cool if we could have data from out neighbour solar systems within a few generations.
We will need a quantum entanglement communication device so that we don't have to wait 100years for a probe to make a one way trip and then another 100years for it to return.
|
|
|
|
|
Quantum entanglement does not and cannot transmit information. So yes, you're stuck waiting.
|
|
|
|
|
It will be powered with dilithium crystals I suppose. Or magic. Perhaps unicorn vomit.
|
|
|
|
|
If you are into creating sweet UI, then you’re definitely going to want to dig into the new Visual Layer with Windows.UI.Composition. I definitely need to add Gaussian blurs to my next database edit screen.
|
|
|
|
|
Kent Sharkey wrote: add Gaussian blurs to my next database edit screen
That is simply not enough! Minimum requirement is that they are animated. 
|
|
|
|
|
Kent Sharkey wrote: I definitely need to add Gaussian blurs to my next database edit screen.
I'm pretty sure these are intended for Win10 consumer apps not LoB ones because we know those computers won't be upgraded from 7 for a few more years. Oh wait, you're not doing W10 exclusive consumer apps either... 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
"Look at all these things this can do."
"How about a functional interface?"
Silence.
"Look at all these things this can do."
|
|
|
|
|
ScaleArc has released the findings of a recent survey that the company says shows that consumer software is seen as more reliable than enterprise software. Even worse news: they considered Skype as reliable
|
|
|
|
|
Yeah. I also think of "entreprise software" as synonym for crapware.
I think there is a very good reason for that.
End user software come in multiple version. v1, v2, v3... each version getting better.
Enterprise software often come in one single version, kind of rushed, with changing requirement during development phase which screw up initial design and cost cutting exercise....
|
|
|
|
|
According to three scientists, Mark Ziemann, Yotam Eren, and Assam El-Osta, Microsoft Excel has trouble converting gene names. Excel has a function for that? They thought of everything!
|
|
|
|
|
Misspell dictionary is not science volume dictionary. We all know the MS office dictionary have limitation 
|
|
|
|
|
|
Google is ready to take virtual reality past Cardboard. "The nature of reality is pure subjective fantasy"
|
|
|
|
|
Google's gRPC aims to oust JSON for exchanging data between HTTP-connected services { "save": { "us", "from": [{"the", "horrors"}, {"of", "JSON"}], "formatting"}
|
|
|
|
|
And XML makes you warm inside. Admit it!
... such stuff as dreams are made on
|
|
|
|
|
So they're replacing a declarative syntax with something that:
1) I couldn't find an example of what it looks like after perusing docs and examples
2) It appears that you need the protocol buffer compiler to generate the code that sends/receives the data?
Erm. Doesn't that seem a tad overcomplex?[^]
Marc
|
|
|
|
|
Protocol buffers are a binary serializer. If they're aiming at the web market now though, I think they need to update their web page[^] to say "why not just xmljson". I looked at them a few years back to replace the .net binary serializer with something less version brittle; but it got pushed to a next major version that never happened. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
There's always BSON - Binary JSON[^]
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Infoworld: The one drawback to HTTP/2 and gRPC/protocol buffers, according to Philips, is that since they're both binary, compressed formats, they aren't directly human-readable. For people who are used to JSON as a standard data interchange format for microservices
Not sure what is new here. MongoDB and many other NoSQL DBs and technologies already use BSON(Binary JSON) message format.
Wonde Tadesse
|
|
|
|
|
It's got the magical "Parfum de Google ". 
TTFN - Kent
|
|
|
|
|
Polishing what has been done. Good job google. 
Wonde Tadesse
|
|
|
|
|
The one drawback to HTTP/2 and gRPC/protocol buffers, according to Philips, is that since they're both binary, compressed formats, they aren't directly human-readable.
Yeah, and that's the major reason why all of these human-readable syntaxes are sooooo sllllooooowwwww and cumbersome to parse and send.
What is wrong with a simple translation tool. I.e. open the binary data and parse it to some JSON-like syntax only when (and IF) some human actually wants to read/edit it. The way HTML/XML/JSON/et al works now is that it's kept in human readable form, for in case some human in the 0.000001% chance actually wants to read the "raw" data themselves. But for all the rest the computer needs to constantly convert the syntax back-and-forth between text and binary.
Exactly why stuff such as BSON was even invented. By all means if your target audience is some human having to read/edit the raw data, go and use such inefficient formats as JSON (or worse XML). But if you actually intend communications between binary machines, then what's the point in doing this double conversion at each end?
The argument to "keep it human readable" simply falls completely flat in most cases. Since the very first thing you need to do is to write a serializer/deserializer to convert actual binary data to text and back. Keep it binary in the first place and use that translator you've built to convert it ONLY when you (NOT the computer) actually want to read/edit the RAW data instead of through a program. See it similar to reading Hex code instead of binary digits, would you keep a compiled program in text based Hex / UUCode / Mime / etc. just for the off-chance that some guy wants to view the internals - i.e. every time the program starts it first has to be converted back into binary? Or would you rather just have an editor/viewer which displays the binary in whatever format only when actually needed.
|
|
|
|
|
The article is poorly written and misses the point; what this mainly solves is taking care of both the message and transport layers in a multi-platform way. The following gives a much better overview: [^]
(One error is that JSON is roughly equivalent to Protocol Buffers, not gRPC.)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
