Yarnage

I completely believe him. Even though XML is really verbose I saw quite a few folks adding these types of things in XML comments.

So this wouldn't surprise me one bit. Would be interesting to see some real-world examples though.

That looks pretty neat! I'm always a little wary about the keyboard scratching the screen but overall it's nifty.

I just hope it becomes a real product after the kickstarter stuff is over.

There is a follow-up...

The OP claims it's real. After dealing with some SOAP systems I would entirely believe this is possible.

Interesting. I never thought of that. It seems almost silly that you're bringing insecure content over a secure channel like that but then again it is only images.

They use quite a bit of HTML 5 so they should be able to do this client-side I would imagine. But I dunno.

I'm pretty surprised Google didn't have the client download the images instead. Wouldn't that be a better solution or am I missing something here?

Pretty interesting though and if this becomes a big enough story you can bet Google will be changing something; the last thing they need is someone using Google Docs to DOS websites.

You're cherry picking statements to make this bill sound like something positive. I'd suggest just doing a Google search though; it's been debated to death.

No

When you're able to take Dart and reliably, run it on both the server and the web client then it may be interesting. Right now I don't see a good use case for it right now.

For one, debugging client-side code is going to be annoying especially if you end up running into a bug due to the Dart to JavaScript translation. You're going to have to know Dart and JavaScript well in order to debug effectively.

The other side of the coin, server-side, as far as I can tell isn't really ready for prime time (at least that's what the Dart language website says unless I'm misunderstanding them).

Neat idea but I don't see the practicality yet. In all honestly I don't understand the trend to move away from JavaScript especially when all it does is translate into JavaScript. That seems like an extra layer of abstraction that isn't very useful to me especially in debugging.

Not sure what the point here is; this is all relative.

Sure, .14MB isn't a big deal but if you're uploading 2.14TB of data, I need to know about that .14.

I would have expected that cost to be covered by those seeking to establish a standard rather than the people who want to implement it.

Does that mean submitters and downloaders pay or just downloaders?

I think you mean charge back as the payment has already occurred.

This was a really stupid article.

Basically, by the use of the word "lazy" the author meant "not lazy" in certain areas and by "dumb" the author meant "not an asshole".

That was a 5 minutes of my life I won't ever reclaim...

Title of post: Gmail Down

Opened up the article: :Less than 2% of gmail users can't access gmail.

Hype much? Though email is one of those things that you never want to go down. I couldn't give two shits if any website goes down for a little bit of time on the rare occasion but email? That could make me miss the spam / opportunity of a lifetime.

I've tried it along with virtually all of the other chat apps and none seem to work very well at all with Google Talk. I am constantly disconnected and never get any push notifications which makes it entirely useless.

I wish there was something better out there. I might give some another try soon since it's been a while.

I agree with Crockford.

GMail isn't just a mail client though; it's a web server and a client with push email, calendar syncing, etc; it's basically a simpler version of Exchange.

Are there any good alternatives? Are their any alternatives at all?

Data representation is great in JSON. Actual layout information? Well it's doable but it's not as easy to see. This is why HTML is NOT XML and also why you wouldn't want to convert HTML to JSON.

So I'm not really sure what your point is. Are you trying to say that, because HTML (which is NOT XML) is awkward to represent in JSON, that XML wins?

>For example, there's a problem with coupling between JSON and application data structures in that they must be the same basic shape. So to give your JSON format the ideal shape for consumers, you need to translate into a layer of objects first - and your consumers need to do the same thing to get it into their internal data structures,

Don't you need to do the same-thing with XML? How do you use XML data without conforming it to your internal structures first? You can't just guess...I just don't get the difference here. I'm trying to understand what XML can offer that JSON cannot. Do you have an example?

>Similarly, you aren't free to evolve; instead, you produce another version, and all your clients must upgrade.

Same-thing here; doesn't XML have the same issue? Upgrading formats can make XML useless just as well as JSON. Also, just like JSON, you can upgrade them without issue so I'm not seeing the distinct advantage of XML over JSON. Do you have an example?

I'm not trying to be argumentative; I just haven't seen any examples showing what makes XML better than JSON just lots of "you can't do this in JSON" and I can't find a way to make that true in my head...

What do you mean by "built in"? I don't see how or why an ID couldn't be used in the same manner; the implementation is just a little different because they store data differently.

XML is only a series of nodes and attributes. There isn't really anything else special about it and it's trivial to represent it in JSON so I'm not sure I follow your issue. Could you provide an example?

There are things that seem "natural" when using XML? News to me :)

I don't really understand your point here. Those JSON data dumps don't make any sense...and wouldn't make sense as XML either. Why wouldn't you enforce a schema? I've never worked on a system that didn't do validation and schema enforcement regardless of xsd, json, etc; you need to have well defined ways of laying out your data or it's going to be useless regardless of the format used.

>JSON is great, but it is not nearly as flexible as XML, partly because of attributes.

Attributes can be stored in JSON as well. XML and JSON simply store data in different ways.

>Also, because of it's JS heritage and compatibility, lots of common things are not representable in JSON.

Like what? You can actually put real values in their correct types with JSON. You can't do that with XML, so what types of items are not representable?

>This is mostly because object keys MUST be strings.

The same is true for XML so I'm not sure what your point is. Don't nodes and attribute names need to be strings in XML?

This "article" is odd. I've worked with multiple systems and I don't see a reason why one data model can't be bound to XML and JSON without being awkward. It's so incredibly EASY to output and input with both, why not? Personally I prefer JSON as I haven't found anything that can't be represented within it.

I didn't see any example within the article regarding JSON formats that generate awkard XML ad vice versa. Does anyone have examples of that?

I guess I'm trying to figure out if they're shipping them immediately or not. It almost sounded like they were. I'll skim over the page some more.

EDIT: Nevermind. I figured it out. Reading...

This looks really cool but I'm so very confused about it being a kickstarter. Is this basically operating as a store front or are you still in the fund raising stage?

People. It's missing people.

That is my understanding as well. The person at our local post office recommended putting the township but wasn't aware of exactly why.

My suspicion is that it doesn't matter one bit but I don't know anything about the USPS system.

I'm actually impressed it came back with my correct information. On major websites including Target.com, they do not see my zip code as valid even though it's close to a decade old. Sure, it's knew in the grand scheme of things but that's crazy...

Anyway, I agree with the others that while this is nifty it won't always be accurate for everyone. For instance my township is contained within a very, very large county so typically mail is addressed to the specific township rather than the county. I do not know how or if that could even make a difference but our local post office has suggested it.

Overall pretty interesting idea. I think using this plus a way for users to validate the information found it could be useful. The only thing I would be wary of is the website is technically sending a third party the user's information. Your service could then build up information regarding a website's typical customer. Probably not something to worry about but I know most of the places I've worked at they WOULD NOT allow this; they downloaded their own offline zipcode lookups.

EDIT: Perhaps a way to download and get offline updates would be helpful especially if your website went down.

Manufacturers about 6+ years ago used to allow this. Almost every Windows Mobile phone I had had the ability to do this with a custom application.

I would suspect the manufacturer wouldn't be liable if you put a disclaimer on it but IANAL. It would sure be nice, however...