bhldr

It's a pretty great format for rapid prototyping, but very complex and wouldn't deploy it as a public API that needs to be supported for a long time.

Robust as the old protocols? The early TCP protocols are very much underspecified. Maybe you have something else in mind.

Yea this is absolutely what I meant. HTML5's complexity is a symptom of this problem.

I'm a bit worried about the authors taking this overboard and trying to redefine the URL standard with similar complexity.

It's easy to be strict if you are both a producer and a consumer.

This is also widely considered a bad idea now. Making liberal consumers allows for sloppy producers. Over time this requires new consumers to conform to these sloppy producers to maintain compatibility.

Just look at the clusterfuck that HTML5 has become. You need to have extremely deep pockets to enter that market.

Say hypothetically if a got my Drupal site for cheap and now I'm hacked. I pay someone another $100 to install the patch and get rid of the malware, I still come out ahead.

What's my incentive to do things differently?

I also think that's a mischaracterisation. It's statistically unlikely for me to transform the world. I just want to carve out a tiny piece of it and make it better.

I don't disagree with you, but this one in particular seems very far from the definition even if you ignore all the hypermedia stuff.

This is a bit far from what most would consider REST. Just call it a HTTP api?

Looks cool though! I would love a product that behaves like a proxy/CDN for images and does some on-demand resizing/filtering.

Thank you, we'll definitely get some legal advice!

Can we get the word 'american' inserted in the title. It's a very local problem.

Most SPA's don't, because most frameworks have some built-in functionality for this.

A quick search in the dictionary reveals 'yes'.

Meatheads will compete over anything

What's the purpose of your cynicism?

Pretty sure that that's non-binding, which means it can change as soon as leadership changes.

The ocean is mostly water, so hypothesizing the size of a whale is not the best idea for long term thinking.

Cleaning up reviews is actually not a Yelp feature. Paid or unpaid.

As an engineer, it's actually a pretty great employer. I enjoy working there and there's lots of folks who've been there for many years.

There's a big difference between the company getting a deal vs. specific people in the company getting a kickback.

Well to each his own right? I personally would hate to work in a place where there's little socializing and quiet all day. I love the open office.

I always get a little annoyed when people make the assumption all programmers want peace and quiet. My day concists of a lot of banter and wouldn't want it any other way. I worked at a major financial services firm for a while too where there there were private offices and lots of silence and I felt isolated and miserable.

How about we all just look for jobs where the work ethic fits our personalities instead of judging if someone else's doesn't fit yours.

Definitely a different thing. This is a HTTP 2 frame, sent by a client

On my phone, so unfortunately no reference, but there is a HTTP 2 spec underway that allows a client to send a cache manifest frame. A server can then push the resources that are newer. Pretty much exactly what's needed.

I think past-apple did do a really decent job and set the stage for many other vendors to follow. Everybody has caught up and surpassed it though.

Looks like blog spam. Third time this user submits the same link and he/she only posts from one domain.

This is not particularly interesting. You can't leave the Mac ecosystem because of vendor lock-in. To me this would make me want to change my tech stack. If you don't care, you are just not the target audience for the article.

You're just as uninsteresting as people not switching to Mac from Windows in 2010 because it doesn't play games.

Enough with the ads here.