arpinum

rust-bucket is 404, did you make it private?

data pipelines and data repair.

I found Quint to be a good pairing with LLM. Easier syntax to learn so you are actually collaborating instead of relying on hope.

It uses http/2, it has streaming.

With ducklake this scales well to multi-terabyte data sets. The big benefit of this server protocol is sharing a high memory server and taking advantage of a shared cache for recent data.

your architecture page is empty. https://getkloak.io/docs/architecture/overview.html

For security products trust is important. writing your website copy by hand will help you build trust. If the design and content does not look human written it will lower adoption.

I said worker/lambda invocation, $0.30/m cloudflare vs $0.20/m for lambda. Total cost depends on async work and memory needs. Cloudflare is $20/m seconds, lambda is $1.66/m seconds, both at 128MB. lambda isn't giving you a full core, if you need CPU it is also $20/m.

I think by operation they mean `git clone` or `git push`, which can read or write hundreds or thousands of objects per operation.

The pricing is disappointing. I'm surprised Cloudflare has not tried to compete on price against AWS lately after a good start with R2. Queues, database storage, database writes, worker invocation all more expensive than the AWS offering.

I read the code. It's a good case study of one-shot output from AI when you ask it to replicate a SaaS product. This is probably better than most because MotherDuck has been open about their techniques to build the product.

Obviously not a production implementation.

Latency, predicate pushdown.

Pre-compaction the recent data can be in small files, and the delete markers will also be in small files. This will bring down fetch times, while ducklake may have many of the larger blocks in memory or disk cache already.

Reading block headers for filtering is lots of small ranges, this could speed it up by 10x.

Yes, I see energy-intensive industry moving away from extreme latitudes in the long run. Most of Europe is at an unfortunate latitude and has surprising levels of cloud cover.

It does not make private energy storage viable on its own. You need to get enough charge/discharge cycles out of it in a certain time period. This means you need almost daily high price fluctuations. We aren't seeing that in Europe. We see high winds push down prices for multiple days and we see multiple weeks with consistent high prices in the winter, with occasional drops on the weekend.

The only interesting part is that renewable production in Europe is so random that there can be far too much for short periods.

The wholesale price system is not a reliable signal or incentive for electricity generation supply and demand in Europe. There are various subsidies, taxes, levies, and fixed costs not shown at the wholesale level that completely change calculations.

These numbers will make customers upset and complain about price gouging if they don't understand the disconnect. Or, it makes customers think that renewables are cheap because they are not seeing the subsidies that on net result in higher payments to renewable providers than carbon-based producers.

I have detailed knowledge of dynamodb. This code does not properly mimic the service exceptions, input validations, eventual consistency, or edge cases. I would not feel comfortable developing against ministack or running tests against it. A lot of these services also have free tiers, so the use cases are quite minimal.

I was also involved in writing a clean-slate port of JSONata after finding issues in the jsonata-go repo and not wanting to run the javascript version in a sandbox. It was relatively easy until we stressed it with 20 layers of nested context and 5000 line expressions and suddenly we had memory explosions not present in the JS version.

JSONata is too tied to the language. Looking back, we should have slightly altered the spec and written some code mods. we didn't have customers bringing their existing JSONata over so they wouldn't notice the differences.

You could hit anything going through the straight with artillery and rockets from the shore. Escort won't do much.

update codex, it's there.

> you're only listing the more trivial things, I wonder why

There is an impression in the comments and the article headline that the test is about vehicle reliability. I'm pointing out a small list of the non-reliability parts of the test.

> the issues that are not directly related to the specific model of the car are roughly evenly distributed among cars

No, because most cars are tested after a yearly servicing which includes a pre-inspection and remediation of issues. Tesla is somewhat unique in not having dealers and a recommended yearly servicing schedule.

Other brands will have dealerships do "pre-inspection" work. The data may be skewed if certain brands are more likely to have pre-inspection done. Some brands even offer it as a free service - maybe they know the public looks at these numbers. Tesla doesn't care, or doesn't have the infrastructure to offer the same service.

The inspection is not strictly about car reliability or build quality, it is about general safety. Article title is misleading

- phone holder in wrong location or not securely fastened

- missing first aid kit

- split in windshield wiper

- low washer fluid

- headlight alignment

- tyre slits from curbing

- tyre wear levels

- surface dirt on brake lines

- rock chip in windshield

- rust on brake disc

- bodywork damage

TUV inspection failures are not a good indication of reliability. The lack of Tesla dealers and no need for yearly servicing means issues get caught at the inspection step for Tesla where for others they are caught at the pre-inspection step.

Also, you need a breakdown of the failures as wear and consumables (washer fluid low, splits in wipers, headlight alignment, mobile phone holder in wrong location) can be a failure but would not be a good indicator for lack of quality.

Would be useful to have SlateDB WAL go to Valkey or somewhere else to reduce s3 put costs and latency.

You would pay less than £9 in the USA for 1 month of sertraline.

Not all data brokers are sketchy, some are very good. Data brokers help assess who is creditworthy and lowers rates for more trustworthy people, and allow the creation of more specialty lending products.

Hard to respect vague laws. Apple can't read the regulators' minds and figure out their interpretations, or instantly pivot when regulators change their minds.

Yes, they were sloppy with GitHub credentials and their response was inadequate. Glad we migrated away from them.

Good introduction, sad that it's needed. I've written hundreds of schemas and massive meta schemas and used most of the 2020-12 spec. I still struggle to navigate and use json-schema.org documentation to look up simple information.

JSON Schema could get more traction if its homepage was oriented more towards users instead of implementors.

The author may be unduly harsh on her father. He got to be publicly married and have a private gay life. He didn't have to live with his wife much. He liked the idea of having a daughter.

Given the hand he was dealt it's a pretty good outcome for himself. Grossly selfish, but not a waste for himself.