niteshade

> Bill caps sound great until you leave one on on a production system and your whole business comes crashing down during a spike in customer traffic.

Hence the "ask on account creation". If I want a dev account, I can choose to cap it. The amount of SMB that would benefit from this is staggering.

> Customer obsession means not shipping bugs? OK, Bob, let's see your code.

A major difference being that my company isn't worth $1T+.

I've used AWS for a long time and spoken at length with many wonderful, intelligent people in the company; and I didn't mean to tread on anyone's toes, I just wanted to express how it feels as a customer who spent >£150k/month for half a decade.

Customer obsession would be things like implementing bill caps on new account creation.

Customer obsession would be NOT shipping buggy, unreliable software like AWS Amplify.

Customer obsession would be CloudFormation-first.

Customer obsession would be not forcing me to upgrade to a paid Support account to report a bug.

The list goes on, unfortunately. I do believe AWS employees mean what they say, but the external reality (IMO) is it takes a lot of time and effort to get AWS to notice their customers unless you're one of the big boys.

16GB/1TB, also two months old:

  SMART/Health Information (NVMe Log 0x02)
  Critical Warning:                   0x00
  Temperature:                        34 Celsius
  Available Spare:                    100%
  Available Spare Threshold:          99%
  Percentage Used:                    2%
  Data Units Read:                    117,513,026 [60.1 TB]
  Data Units Written:                 110,686,292 [56.6 TB]
  Host Read Commands:                 506,322,545
  Host Write Commands:                351,505,939
  Controller Busy Time:               0
  Power Cycles:                       389
  Power On Hours:                     388
  Unsafe Shutdowns:                   40
  Media and Data Integrity Errors:    0
  Error Information Log Entries:      0

Thank you for posting this, very insightful :)

This is amazing! I'd love to see some benchmarks of Artichoke vs Ruby for macOS Homebrew workloads (its mostly the only time the Ruby executable is invoked on my system).

Hi Eskil! Would love to hear your thoughts(rants?) on iOS too :)

While I'm generally in favor of native apps, this article reads like a puff piece from Apple trying to show off how much they value developers, particularly in light of the ongoing skirmishes with Epic, Spotify and the Coalition for App Fairness.

I had the same issue - it eventually started working after restarting the phone.

I've had a brief but successful experience with QAWolf (https://www.qawolf.com/), which is built on Playwright (last I checked)

You can do basic screensharing with Messages on macOS. Open Messages, select a message thread with an existing contact, then from the menu bar, select Buddies > Invite to Share My Screen (or Ask to Share Screen).

Doesn't work for groups (last time I tried at least), and hideously undiscoverable.

AFAIK diffing is the only way, I'd love to hear if anyone has a better technique

Thank you!

It is absolutely daunting if you're first getting into a new project, the only thing that helps is experience, and the only way to get that is to keep trying, unfortunately.

Nowadays, I usually contribute out of a somewhat selfish interest in seeing a feature/bugfix get released so I can use it without having to maintain a fork :)

I do indeed try and reach out to contributors by opening a Github issue with comprehensive detail about the change I'd like to make and more importantly, why. Hopefully (and usually) they're responsive, and I can get their feedback and ask more questions, like any particular parts of the codebase I should look at. I also try to look at open source issue discussions/PRs as a process that can takes weeks (if not months), and so it can often be the case that I maintain a fork in the interim period. However, sometimes I just can't wait and am itching to get stuck in, and the best way to do that (without any prior knowledge of the codebase) is to try and trace the execution flow, which is just fancy-talk for adding `console.log(1), console.log(2)` statements in places that seem relevant.

I've certainly heard people say the best way to get started is on "easy" bugs. That may be true to a degree, but for me it was always because I felt a library/tool that I liked and used could be improved in some way. I found it helped me keep up the motivation to finish what I started, as opposed to fixing a random issue from the tracker that I might not fully understand the context of.

Not a "decision" as such, but getting more involved in open source has given me so much, and helped me build skills in:

- Navigating unfamiliar codebases

- Improving technical writing skills

- Keeping abreast of new tool/tech/methodologies/processes

- Maintaining and managing projects

Threadreader link: https://threadreaderapp.com/thread/1269716700682993666.html?...

Interesting tweets - I could see myself agreeing with a lot of those points a few years ago, before I decided to go into management instead. More recently, I seem to find a "thrill" of sorts in navigating any external bureaucracy and filtering it down to concrete technical requirements for my team.

I'm fairly sure they're based on WebKit, actually. Can't say I've ever seen Chromium inside non-Android mobile/TV browsers, but I could be wrong.

My thoughts exactly, this approach helps with the issue of anonymous purchases (i.e. retailers linking payments with email addresses[0]) although presumably retailers will try and make up for it by shoving analytics on the receipt display page, though that can also be disabled with an adblocker.

[0]: https://www.theguardian.com/travel/shortcuts/2016/oct/16/sho...

Myself and a group of friends have been working on a email receipt parsing framework: https://github.com/openreceipt/source

Ideas, feedback and criticism is always appreciated!

I agree, he seems to have toned it down: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89501#c12

Hey dang, there's some problematic comments[1][2] in here from godelmachine. As far as I'm aware (and at the very least in the UK), calling someone a "paki" is a slur.

[1]: https://news.ycombinator.com/item?id=19254972

[2]: https://news.ycombinator.com/item?id=19255009

Thanks for posting this, I've been looking for an alternative for my grandfathered G-Suite account.

As a UK counterpoint, most of my friends and family (at least 15 people) use iPhones and iMessage/FaceTime is a major reason for sticking to the Apple ecosystem for us.

Hi, thanks for the reply!

> No integration w CF is absolutely true but you're also totally free to do that.

It just seems then that there is no real way for me as a developer to transfer all the accumulated knowledge I already have about AWS to your framework. Looking through Architect's source, it actually seems as if everything is done via the AWS Javascript SDK, which seems a bit ... odd, to say the least. I'd even venture as far as saying it goes against the AWS Well Architected Framework guidelines (1) (which recommends using CloudFormation).

> No auth support is false. We support session out of the box and you're free to impl any auth scheme of your choosing.

Apologies, I couldn't find any mention in the docs. I meant more in terms of using an AWS service such as Cognito Federated Identities, and in terms of protecting API routes with either AWS_IAM, API keys or Cognito Authorizers.

> CORS could be implemented in the file format....

An Architect project deployment is not exactly repeatable if I still have to go to the Web Console to enable CORS now, is it?

> Magic folders!

I personally would prefer either my project's root `node_modules` or a Webpack bundle be deployed, over which I have some measure of control. Node already has a hard enough time with its resolution algorithms, must we add to the madness?

> Serverless framework is an abstraction that is easily as verbose as CF

I can't agree with you on Serverless being as verbose as CloudFormation, and I think you should know better as someone who has dealt with the complexity of setting up API Gateway programatically.

> but I'm not interested in comparing to it because we have different goals.

I think the comparisons are fair - both Architect and Serverless claim to be "Serverless frameworks". I could be in the minority though.

> Serverless is an abstraction between clouds. If mulitcloud is your goal: use Serverless.

I mean... you're not wrong, but that's grossly oversimplifying it. I've personally added support for Serverless AWS projects to allow hooking up Lambdas to Cognito User Pool triggers. That's a pretty solid AWS-only use-case, that likely isn't available on other cloud platforms (or at least, I never implemented it for them).

> SAM is a flavor of CF which is def less verbose but still very vendor specific and …wordy.

Well, isn't Architect vendor-specific as well?

> This isn't a 'pet framework of the month'. I do take mild offense to that.

Apologies for that remark. I'll be honest - I'm not really interested in the story behind the framework, I'm more interested in what it brings to the table. I'm glad your project worked for you and your company, and I wish it the best, but personally I don't see why Architect couldn't have just been a layer of syntax sugar over SAM/Serverless framework. If there was a killer feature that's specific to Architect, I can't see it (unless you count the file format as a feature).

(1) https://d1.awsstatic.com/whitepapers/architecture/AWS_Well-A...

DISCLAIMER: I've contributed a few times to the Serverless framework.

I like some things about Architect, but there are things that just don't make sense:

- Integrations with Slack but no way to define custom CFN resources

- No authentication support

- Custom file format (3)

- Not being able to set CORS in this custom file format (4)

- Magical vendor folders (5)

I am sorry for the negativity, but brianleroux has posted in this thread several times claiming his framework saves 700-line CloudFormation templates. What I don't see is him comparing snippets with say, the Serverless framework(1), or AWS SAM(2). He seems to portray the choices as either his pet-framework-of-the-month or plain old CloudFormation, and that's just not true. That's not to say Serverless or AWS SAM are perfect (they most certainly have their warts), but they are both arguably more mature and have larger communities behind them.

(1) https://serverless.com

(2) https://github.com/awslabs/serverless-application-model

(3) https://arc.codes/quickstart/arc-project-layout

(4) https://arc.codes/guides/cors

(5) https://arc.codes/guides/sharing-common-code

CloudWatch monitors logs for specific keywords, if it finds a certain number of them within a time threshold it creates an "Alarm" which then triggers a Lambda.

You can ask for the status of the parent bug, I've gotten answers before.

For example, I filed a bug report for Continuity not supporting TouchID/FaceID, so that you could unlock macOS from your iDevice. It was closed as a duplicate, and when I asked for the parents' status, I was told it was it was closed as "Not to be Addressed".

Could you go into detail, please? I was close to buying it, would like to know what annoyed you about it

Expected: 50 Actual: 0.4

On El Capitan, I don't even see a padlock on the AppStore prefpane.

Quite literally the first result in Google: http://www.dummies.com/education/math/pre-algebra/the-three-...