I think the first (or first couple) AOC relied on JSON input more.
I assumed Eric (the creator) moved away from JSON to have a level playing field and simplify parsing (and potentially build dependencies) across various programming languages.
I'm definitely excited about this, especially after paying $36/month for a NAT that I barely used for a long, long time, and spending too many hours configuring it for my Lambdas.
That said, I don't know how Jeremy Daly got away with making that post, per AWS preview terms. They are pretty explicit about not posting benchmarks on their preview products, and that makes sense as the API is not stable at all.
Still, I'm glad to see the data and hope that the performance has improved. I wasn't accepted into the preview, and I've started work now to move most of our infrastructure to GCP. It notably does not require any fancy footwork to have a Cloud Function talk to a Cloud SQL instance https://cloud.google.com/functions/docs/sql#overview
Wait if I read that doc correctly, does it seem to suggest that connections will be closed when the function goes cold. So the locked up connections where lambda dies without disconnecting isn’t a problem google functions?
Think of a spike in traffic, 100 functions connect one connection per function. Then a break 80 of them go cold. Your max connections is 100, so if 80 didn’t disconnect and are waiting to timeout you are stuck. Any more functions coming online won’t have any connections.
The only work around in AWS was to setup an external connection pool, kind of begins to kill the serverless savings and all.
Jeremy has updated the post in response to the announcement.
- Lots of improvements & better documentation
- Smaller response size, but can be cut down a lot more
- Sub 100ms query performance
> I’m really impressed by the updates that have been made. I do want to reiterate that this isn’t an easy problem to solve, so I think the strides they’ve made are quite good. I’m not sure how connection management works under the hood, so I’ll likely need to experiment with that a bit to measure concurrent connection performance.
The GPL does not require source code to be "publicly available".
IMO the basic premise of the GPL is that users who receive the program/app/whatever may also get the source code, modify it, and further distribute under the same license.
Section 3 of GPL2 states:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
Most do "a" but "b" is acceptable and Section 1 even allows for charging a fee for the source code.
id Software is also the copyright holder of the games and can choose to license the game or parts of the game out however they want and as often as they want.
They did have the occasional issue where they were using comercial libraries and had to take those out of the codebase before they could open source them.
In this case, the theme developers are not copyright holders of the WordPress code and thus are subject to the WordPress.org's license.
I think Segways are great for sightseeing tours, and I've done (and enjoyed) a couple on my travels. Segways basically created a new way to sightsee.
I can't imagine how tours would be able to operate 12-15 mile 2 hour "walking" tours otherwise. You're able to see a significant part of a city from eye level without a huge amount of physical effort.
One trick that seems to have made it easier for me is changing the question from "Do/Should/Can I go to the gym today?" (which is just an opportunity to come up with excuses) to "How do I go to the gym today?".
It seems to tie into the decision fatigue theory. Instead trying to figure out if I can based on meetings/workload/other things in my schedule, I've already made my decision to go on certain days (in my case, every other day) and I just need to make sure my schedule works.
It's independent of LivingSocial but is aggregating deals from other companies (at the bottom of the deal it says with which company, in this case it's LS).
I'm guessing it is going to mix it up by offering deals from other services, whilst it builds up momentum to offer its own.
Judging by the fact that Boise, ID is their only market right now, and the deals on both sites for Boise are different, I'd say it's independent of livingsocial
My guess is that this is just an implementation optimization. Probably analogous to lookupd caching DNS lookups. The developers probably didn't think anything of it.
Even lookupd caches could be represented in similar light: "Your Mac secretly records the websites you visit in a hidden file." It's just that we're all used to (and understand) DNS lookup caches, and locationd and location lookups are relatively young.
I assumed Eric (the creator) moved away from JSON to have a level playing field and simplify parsing (and potentially build dependencies) across various programming languages.