zzen

There are many of us who don't need public DNS records and rely on local-only DNS records accessible from outside via Tailscale/WireGuard.

Tons of tech companies were firing employees in 2022, so much so Apple was far and wide an exception in just keeping the same numbers. Feels more like an economic cycle / preparing for the worse rather than result of bad decisions on behalf of Pichai. And yes - firing employees to protect the efficiency of the company is (an unpopular) part of a CEOs job.

> “ People who are diagnosed with ADHD at a younger age likely have parents who just don't want / know how to deal with issues.”

I have no idea where you take this opinion from or if you can back it up. From my anecdotal evidence exactly the opposite is true: kids from families who do realize there is such a thing as mental health and who care deeply about their kids - those get diagnosed. Kids from other families just get mostly slapped around and screamed at to get their shit together.

extended?

As somebody who founded and ran R&D-heavy companies in Czech Republic and in Bay Area - this is complete bullshit. Arguably the per-capita amount engineering talent is much higher in Eastern Europe, and it is untapped because the target market is small and there's lack of entrepreneurship tradition.

Sure, if you take 300M market like US and pool all the best talent to west-coast, there is a lot of engineers. But the market is saturated, and it's nigh-impossible to hire a team of the magnitude you can get in Eastern Europe. Canada? Oh please...

7nm has been around for a while. All 2018 iPhones are using A12 which is manufactured using 7nm.

Look, as somebody that's lived many years in Europe and in US, the situation is incomparable. I don't know why - either you have crappy laws, or you have crappy enforcement. If you read the article, it claims both. The FDA has super-low requirements to do anything - and manages to do even less than required to.

The european market is significantly bigger than US one (380m people) but manages to have much better labeling standards.

Because currently the USDA and FDA equivalents in EU actually work, and the laws that require food inspections are stricter. The worry is that TTIP market access policies will force uniform, lowest-common-denominator rules, eliminating european food QA policies.

(disclaimer: I'm the founder of Apiary) First things first - Readme.io is a great product and congratulations to Gregory for following his dream. I did so with my own, similar passion a couple years ago.

That passion was connecting developers - API builders & users. Documentation is just a part of this (interaction, collaboration, prototyping, and testing being others), which is why it’s a bit harder to be completely free-form. That said, we're aware that there's a lot room for improvement and we're working very hard to make Apiary better. Your feedback is really appreciated, I'd like to know more. @dmak, @special and @sidi would love if you could contact to me directly at jakub@apiary.io.  Thanks for speaking out and pushing us to improve.

Couldn't agree more.

Cool article & design approach. I've really enjoyed the Heavybit talk a couple weeks back, wrote about it today at HB blog: http://blog.heavybit.com/blog/apiary-api-design-versioning-t...

I might be missing a point, but how is this different from tried-and-failed GWT?

Apart, obviously, in language of choice.

They have a separate EU hosting region that has separate maintenance (and uptime that's actually significantly better then US region): https://status.heroku.com/uptime?region=EU

So yeah, it was a lame time to schedule maintenance.

Thanks Mahrew! A lot of time went into this, we're all pretty excited at Apiary.

For consumers, "there's an app for that".

For businesses, "there's an API for that".

I think we all know the precedent: http://en.wikipedia.org/wiki/Luddite

And yeah, if it gets really bad, violent protest is just a more extreme continuation of unions.

From my limited familiarity with British politics, this is sadly how most of UK public thinks.

Case in point: some of the most egregious privacy violations were done by GCHQ as opposed to NSA, who contracted out the sensitive spying to UK because of lax legal regulations. But can you see any electoral upheaval in UK that would even hold a candle to things happening in US? No MPs protesting, no public protesting - nothing.

Even my UK friends in IT industry, spending all of their time online - are shrugging shoulders saying "but spies spy, that's what they do, what's the big deal". I feel that Kirsty is just reflecting that cultural background.

Sure, API Blueprint supports JSON Schema. If you're happy to put in the effort, nothing stops you from using JSON Schema in the blueprint and all the tooling built on top of it.

Personally, I believe there is a way to enable new value while fighting back the complexity and corporate engineering culture.

REST needs to mature and get tooling. But we need to avoid the WSDL complexity.

(disclaimer, I'm founder of Apiary, which started apiblueprint.org)

I'm happy that Mulesoft are getting on the "better, human readable API DSL" bandwagon. It's very important.

At Apiary we found that embedding one format (Markdown, for human-readable documentation) into another format (YAML, for structured parseable data) is hard for the consumer, tough for the text editors/IDEs/syntax highlighters and ultimately useless. That's why apiblueprint.org is PURE markdown, that displays well on GitHub, has great syntax-highlighting support in your editor - and is just as parseable (since we ship an MIT-licensed parser with it).

I wish we could've united on a single format, but I guess the stronger will win and a little competition is always good for the end-users.

Not sure how we've ended up in that category. Apiary doesn't generate or manage license keys. And frankly, it doesn't do API management at all. We're helping people design & build APIs.

Thanks for pointing out the typo. Fixed.

Nathan - we have support for private APIs (documentation is available only for authenticated users), so if you don't mind the API specs living on AWS servers, this should work.

Of course the beauty of it is (if you have a Model S) you can help with the mapping by fork/pull-requesting changes on GitHub: https://github.com/timdorr/model-s-api

Agreed. Still - having letting your users send you pull-requests to the documentation is a good idea. My company apiary.io is building API documentation tools that take the open git repo benefits but generate a sensible-looking documentation.

Slap cluster (http://learnboost.github.com/cluster/) in front of your node.js express server and re-run the tests with both cores. I'd guess the performance will close to double.

Hmm. A couple days after the reports of Lockheed Martin becoming the first buyer of a commercial quantum computer:

http://blogs.forbes.com/alexknapp/2011/05/25/d-wave-sells-qu...

Perhaps coincidence. Still, interesting.

Thanks! We split the UI into Usecases tabs, listing tests (each test spans multiple APIs and resources) and Resources tab, which lists your APIs/servers/resources. Each resource page shows what structures/methods this resource accepts, what tests it's featured in and whether it passed/failed.