When I deal with datascience, I rarely have type problems in my programs that python typecheckers can't catch. I do have type and dirty data problems of the dataframes/csvs/parquet I'm reading.
> I rarely have type problems in my programs that python typecheckers can't catch.
> I do have type and dirty data problems of the dataframes/csvs/parquet I'm reading.
Something about those two statements makes my brain explode. You rarely have type problems, except when dealing with data? Isn't the whole point of a program to deal with data?
Car manufacturers watch the cost of every piece of the bill of materials. Cars compete on price, and the assortment of pieces which add perceived value to consumers. Outside of performance and very highend luxury cars, tires are an afterthought to the average car buyer.
Yes, which is why most optimize tires primarily for price, fuel economy, and NVH, because those are the things which a consumer notices the most when buying a vehicle: "what's the price, what's the EPA estimate, and did I like the test drive?"
Some manufacturers even source tires that have lower tread depths than typical replacement tires, in order to decrease noise and increase MPG at the direct detriment to tread life. Tesla is one of the manufacturers that does this, which is one exacerbating factor for their notoriously poor tire life. They literally come with less tire!
Toyota is infamous for offering special, nerfed versions of well-known tires on their new vehicles. You buy a Tacoma, you don’t get the Wildpeak AT4W, which is a very good all terrain tire. Instead, you get the Wildpeak AT4WA, which is a nerfed version with reduced tread depth that is quieter and more efficient than the real AT4W but less capable and wears out faster.
When buying tires as an average Joe for an average car (like a Corolla or Camry) it seems like being an OEM tire is actually a badge of honor for a tire. The reason is that that's the tire that they report MPG with and that you have on the car when you test drive it, so manufacturers care about ride quality and efficiency in the OEM tire. There's a lot of tires that are cheaper than OEM tires and they perform worse.
I have written a couple of eval harnesses to see how well LLMs drive software I have written. Basically I have data analysis software that I need LLMs to write code for. The code is complex, and I want to shape my APIs such that LLMs do a better job of quickly getting to the right answer. So I test different prompting and api surfaces, it's really easy to make quick gains this way and save your users from bugs. In this paradigm, I'm explicitly not testing different models, and I'm very interested to see how lesser models do with my software. Also for this type of testing, using the open weight models makes it faster, cheaper, and more reliable to test vs frontier models because I can trust that kimi-2.5-a-bunch-of-specs is going to behave more consistently than whatever tweaks Claude is making to Sonnet this week. API and prompting improvements seem to carry across the different models for gross improvements.
I haven't looked that hard, but I can't find articles about this type of eval testing, curious to hear if others have approached writing APIs in this way.
I'm as anti-car and pro-bike as they come. Cars and trucks are a much bigger danger than e-bikes...
But California's clear tiers of ebike regulations are meaningless without enforcement. Over the past half decade blue states have become unwilling to enforce almost any laws. when they do enforce the laws it is sporadically. This matters for ebikes, it matters more for cars. Running a stop sign is absolutely not enforced any more.
Not necessarily? As far as I know they come from the same WebKit source. But the bridge between WebKit and the OS is of course specific to each system. WebRTC is still experimental in webkitgtk while caniuse says Safari supported it back in 2017.
I remember encountering one bug with Final Form that triggered rarely in Safari, 100% in Webkitgtk, and never in Chromium.
Here's the developer of Tauri saying it's hard to recommend webkitgtk / Linux support:
> So if you need good linux support now/soon i can't 100% recommend tauri (for Linux) as of now. (I used to be more "forgiving" but with webkitgtk getting worse/more unstable each release i changed my mind)
Python/Jupyter developer in Boston. I build data tools and I start by talking to the people who'll use them, because code that doesn't get adopted is wasted work. My main thing is Buckaroo (github.com/paddymul/buckaroo, ~680 stars), an open-source data table for Jupyter over Pandas/Polars. I built both the data layer and the React frontend. Looking for a team building data tooling (as a product or in house).
Ted Turner won the America's cup there in 1977. His team named Courageous was legendary. Robbie Doyle was a team member, and got a degree from Harvard in applied physics. In the middle of the trials to see which team would defend the cup for the US, he remade the sails to be more competitive. Doyle went on to found a racing sailmaking company.
I used to live in Newport, RI. I love sailing and introducing people to the world of sailing. When I had guests I asked them to watch this NBC video about Ted's 77 campaign [1]. It really captures the history of Newport, sailing, and Ted
Sounds great. I'll watch it with the kids. We've recently done this podcast about the history of the cup and it was funny and fascinating. https://www.youtube.com/watch?v=hUZmk_G6rFE
Ted Turner won the America's cup there in 1977. His team named Courageous was legendary. Robbie Doyle was a team member, and got a degree from Harvard in applied physics. In the middle of the trials to see which team would defend the cup for the US, he remade the sails to be more competitive. Doyle went on to found a racing sailmaking company.
I used to live in Newport, RI. I love sailing and introducing people to the world of sailing. When I had guests I asked them to watch this NBC video about Ted's 77 campaign [1]. It really captures the history of Newport, sailing, and Ted
I think another factor is that people are rejecting the rounded corners and excessive padding of modern web design, you can't do that in a TUI, so you don't have a designer or standard practice encouraging you to do it. As implemented TUIs have greater information density than GUIs. Make no mistake though, TUIs are a decided step backwards from GUIs. Everything that you can express via text, you can also do in a text area on a GUI app.
reply