jeffbarr

There's only one flight deck and it in the right-hand fuselage. I was at a recent friends and family day at Scaled Composites and was able to see and touch this amazing plane.

Back when I was a kid (born in 1960), jeans were called dungarees and you could wear them after school but not at school. This was in the northeastern part of the US, in a middle-class, public school environment. It was definitely not acceptable to wear jeans to a professional job until much later. In fact, I had to wear a tie at some of my first jobs as a developer.

Great question! I checked in with the team and this is what they told me:

"The developer FPGA code is enclaved inside AWS FPGA Shell, to prevent malicious FPGA code from damaging the hardware and to provide the necessary protection for PCI Express and the host machine. The pin assignment of the FPGA is controlled by AWS."

And

"AWS infrastructure monitors the thermals as well and the F1 hardware was designed to sustain high power consumption to enable developers to utilize the maximal available FPGA resources and frequency."

We plan to add additional formats over time. I know that ORC is on the list.

The team saw your complaint and supplied an updated graphic, which is now in the post...

This is not BigQuery.

What's wrong with that graphic?

I'll get on that right away. Great idea!

Currently limited to the part of the US that's east of the Mississippi.

Details on AWS at https://aws.amazon.com/blogs/aws/look-before-you-leap-decemb...

Are you the one who did this in the AWS booth at re:Invent? It was so perfect that my colleagues did not want to disturb it.

Thanks!

I just read it - million to one chance, but I saw your comment! We fixed the link.

(post author here)

You can do all of the design and simulation on any EC2 instance with enough memory and cores. You don't have to run the dev toolchain on the target instance type.

Or eggs and omelettes...

I wrote the post after spending all of about 15 minutes learning about this new feature. We did make things simpler.

> AWS if you read this: Please make your offers and your pricing simpler, NEVER more complicated.

I am reading this. We made them simpler. Decide how quickly you need your data, express your need in the request, and that's that. If you read the post you will see that these options encompass three distinct customer use cases.

Can you share your needs with me so I can pass them along to the S3 team?

Good to know :-)

Sometime around 1979 or 1980 someone gave me a slip of paper with a phone number and said "Dial this with a modem."

I did, it answered "Pentagon TIP," and before too long I was roving around the ARPANET. If memory serves me right the main command was "C" for connect. You simply typed "C" and a small number, and then logged in as "guest"/"guest" (the world was smaller and more innocent back then). I'm fairly certain that I logged in to a system at UC Berkeley.

Which aspect of it do you find the most useful?

* All of the instance types on one page? * All of the per-type facts in one row? * Sorting?

Let me know and I will share it with the team.

Do you have any feedback that I can pass along to the team? Post it here or email it to me (email in profile).

Welcome aboard!

Do you have some specific feedback that I can share with the team? Which aspects of the console and the workflow are not working for you?

We (I am part of the AWS team) pay a lot of attention to that; our "Overview of Security Practices" paper[1] says:

"Each availability zone is designed as an independent failure zone. This means that availability zones are physically separated within a typical metropolitan region and are located in lower risk flood plains (specific flood zone categorization varies by Region). In addition to discrete uninterruptable power supply (UPS) and onsite backup generation facilities, they are each fed via different grids from independent utilities to further reduce single points of failure. Availability zones are all redundantly connected to multiple tier-1 transit providers."

[1] https://d0.awsstatic.com/whitepapers/aws-security-whitepaper...

I started writing the AWS Blog way back in November 2004 and am coming up on 2600 posts!

Good luck recreating the tactile feel of a model 33 Teletype's keys, or the smell of a Linotype's pot of molten lead.

Small correction to my previous answer, Elastic Beanstalk will support ALB in the very near future.

Elastic Beanstalk supports ALB.

That's my post, and my misunderstanding. I'll clean it up now, thanks!

Feel free to get in touch (email is in my HN profile) or to look at the AWS Careers page.