rcaught

> Each decision solved the problem in front of it. Nobody was asked to look at the sum of all actions.

This is the perfect description of Telstra as a company.

Aigile

NIH syndrome

While I understand the intent of this exercise, couldn't someone just wasm compile the Servo html5ever Rust codebase?

That's because OP wrote that

> These days a great SDK, not a great API, is a hallmark, and maybe even a necessity, of a world class development experience.

IMO, you can't build a great SDK without a great API. Duct tape only goes so far.

Malicious access to these tokens is malicious access to the service.

Rails 8 will by default use the DB for cache, queues and WebSocket broadcasting - https://fly.io/ruby-dispatch/the-plan-for-rails-8/

Make one program do no one thing well.

hahaha, do you even realize what else this company makes?

It looks like one you shouldn't implement.

Permission boundaries

Savings plans, spot, EDP discounts. Some of these have to be applied, right?

Complexity breeds complexity

> “Apple is not compatible with that. They won’t release something until it’s perfect.”

Apple Maps, Magic Mouse charging from the base, Butterfly keyboard...

Appreciate Kotlin and others pushing it there.

COPY (SELECT * FROM view_name) TO 'output.csv' (HEADER, DELIMITER ',');

This is not showing what you would always do, it's showing something novel that you could do.

In the full context of their statement, many modern databases separate the data storage component. RDS Aurora, etc.

The article shows dynamically fetching a database, with database level views, that dynamically fetch data.

You're just showing a query that dynamically fetches data.

https://duckdb.org/docs/sql/statements/create_view - the View is not physically materialized, but the query is run every time the view is referenced in a query.

I've successfully used it's glob support on S3.

Somewhat related. I've been looking at RPKI lately, and there are two things I'm not overly impressed with:

1. LACNIC and RIPE have 100 year validity on their trust anchors.

2. All RIR trust anchors are valid for all IPs (past their allocations), due to, I assume, inter-RIR transfers.

Keyboard warriors

Also see: https://github.com/simonw/datasette-lite

I'm sure someone will incorrectly consider this a valid reason to create another.