|
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.)
|
|
|
|
|
Synchronized wave phases are used in MegaMIMO 2.0 Does it involve a cable?
|
|
|
|
|
Photo-editing and storage app 500px has unveiled a zany new search feature that lets you input a Microsoft Paint-style sketch of what you're looking for, then returns dozens of suggestions for landscapes, animals, portraits, and travel photography. Find me a photo that looks like a stick person
|
|
|
|
|
I tried a smiley face but it didn't give me the Mona Lisa.
Marc
|
|
|
|
|
Android's release schedule has historically been all over the place, but for the last few years we've gotten roughly one major release per year, occasionally punctuated with medium-sized maintenance releases, minor feature updates, and monthly security patches. More updates for people (and carriers) to ignore
|
|
|
|
|
|
If movies about space have taught us anything, it’s that no one can hear you scream. If you get lost in space, nobody’s going to find you. Unless you’re a spacecraft with a direct link to NASA. Then there is hope for you yet. Maybe next time they'll remember where they parked it
Wandering around the parking lot, pressing the fob until they hear the alarm turn off. Embarrassing.
|
|
|
|
|
I saw wrong, I see NSA instead
|
|
|
|
|
November 5, 1999, was Burn All GIFs Day. Had you visited its homepage that Friday, you would have seen the movement's game plan laid out as plainly as its name: "On Burn All GIFs Day, all GIF users will gather at Unisys and burn all their GIF files." This, alongside a selection of pointedly anti-GIF imagery—all proudly PNG files. As long as we don't discuss how to pronounce it
It is, of course, pronounced, "Throatwobbler Mangrove".
Or "it" if you want to play that way.
|
|
|
|
|
Kent Sharkey wrote: Burn All GIFs Day
Isn't there a GIF animation for that?
Marc
|
|
|
|
|
haha
|
|
|
|
|
I think that article had more text in it than the last issue of the magazine I got.
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
|
|
|
|
|
Physicists have proposed a way to braid three beams of light by guiding the beams along swirling, vortex-shaped defects in the optical medium through which the beams travel. Coming soon: physicists make macrame and dream-catchers
|
|
|
|
|
Physicists have proposed a way to braid three beams of light by guiding the beams along swirling, vortex-shaped defects in the optical medium through which the beams travel.
Any blender will do that.
Marc
|
|
|
|
|
When Agile works, it is because Agile’s “principles” are brilliant; and when it doesn’t work, it is because “I only prescribe principles, you are interpreting and implementing them wrongly.” I'll assume there isn't a faulty premise there
(and that it is possible)
It must be possible... right?
|
|
|
|
|
Kent Sharkey wrote: I'll assume there isn't a faulty premise there
Darn right. Geez, when Agile works, it's because the principles are brilliant?
No, when Agile works, it's because the people are brilliant (or at least, competent.)
You could just as easily say, "when the Waterfall methodology with greasy napkin architecture drawings works"...
It's not the process, people, it's the PEOPLE that make the process work!
Marc
|
|
|
|
|
I would even expand that, to say that agile works with Certain people. And with that I mean that they shouldn't just be competent, but also have the right kind of competence that fits the agile process.
There are enough examples of waterfall working perfectly fine as well, as long as there are (differently) competent people working on it.
But I suppose that agile works better in companies that's run by marketing.
|
|
|
|
|
Agile in my vocabulary means "capable of dodging rear bottom-center aimed phallic missiles fired from managers". It usually works.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Ah, so you're saying...
"Individuals and interactions over processes and tools"
(from the Agile Manifesto)
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
The quote was out-of-context. It missed the closing: "Answers like this are dodging responsibility. We need a more constructive response than that."
Ironically, the author then sets out saying exactly what he criticized. And makes several annoying blunders on the way.
For example, "Because Agile facilitates fast feedback, it will expose more issues more quickly..."
No, good testing facilitates fast feedback, not agile. Agile doesn't do sh*t in that regard.
The problem is that the Agile Manifesto describes what many talented, successful senior developers naturally do. Agile as a methodology then tries to force that onto everyone in a top-down way. For completely unorganized projects, Agile does tend to work... until management realizes that it's great for bureaucracies and then it becomes hell for the engineering teams.
|
|
|
|
|
Agile fails because it buys into the conceit that mimicking the successful will make you successful. It's one of the biggest cons out there (this is what rich people do, so if you do them you'll become rich. Just pay me to teach you....)
|
|
|
|
|
At least one hacker says he can clear $250,000 a year by doing something that “comes easily”: hunting down vulnerabilities in computer code and then letting the software’s owner know about it. I see a new career in my future: creating bugs and splitting the profits with a "bounty hunter"
|
|
|
|