We used to get these books in the annual international book fair in Delhi back in my childhood days. I still have 2 of them (Mathematics Can Be Fun and How The Steel Was Tempered), but I'm pretty sure we had several more at the time. They were fun reads, and the illustrations used to be great!
IIUC this just pulls in various other crates with some vibe-coding on top. I'm not familiar with the Rust dependency system, but what is the need to have copies of the code? Would it not suffice to just have an "empty" crate that just depends on the original crates?
Very poor. Hardly lasts a week with step tracking and heart rate enabled. Like someone else mentioned, go for a Garmin instinct 2 or 3 solar. My 2 Solar lasts more than 30 days on a full charge.
Not unlikely given the crash in Atlassian's share price over the last year or so. When I was in NetApp a long time back, such rumours would often do the rounds when the share price took a dip, with Oracle and IBM usually touted as the likely buyers. NetApp is still doing strong more than a decade later :-).
I was thinking of using it with Duckdb as well but seems it would be of limited benefit. Parquet objects are in MBs, so they would be streamed directly from S3. With raw parquet objects, it might help with S3 listing if you have a lot of them (shave off a couple of seconds from the query). If you are already on Ducklake, Duckdb will use that for getting the list of relevant objects anyway.
I was thinking the same - if JSONata was a priority for them, why not choose a language with good support, like JS or Java? OTOH if development language was a priority why not choose a format that is well supported in it?
I ran into 5 and 7 in a Flink app recently - was parsing a timestamp as a number first and then falling back to iso8601 string, which is what it was. The flamegraph showed 10% for the exception handling bit.
While fixing that, also found repeated creation of datetimeformatter.
Both were not in loops, but both were being done for every event, for 10s of 1000s of events every second.
> documentation survives when it lives next to the code.
15+ years ago, this was pretty much the standard. Every decision - whether major or just a hack to handle a corner-case - used to be recorded in the code itself. Then tools like Jira and Confluence came in and these things moved to undiscoverable nooks and corners of the organization. AI search tools like Glean and Rovo have improved the discoverability, though I'd still prefer things to remain in the code.
I loved their dry seasoning [1]. Bought some when I visited the bay area several years back and used to use it on everything from toasts to pasta. Sadly, haven't visited US since to be able to pick up some more :-(