jmole

Well it simplifies the logic considerably - if you see an enum value you don’t recognize (mint), you treat it as uninitialized (0).

So any future new flavor will be read back as ‘0’ in older versions.

The example code used added “other” as the last option, which was the source of the problems he described.

This doesn’t happen when you make the first value in the enum unknown/unspecified

it doesn't, it just means that "AI gorilla controversy" was a big deal not too long ago, and they happened to remember it.

How about taillight brightness?

I'm not sure if this has gotten better in recent years, but there are a bunch of high-end vehicles (looking at you AUDI) with extremely bright red LED taillights that are just painful to sit behind at a red light.

None of us has a coherent view of the world, the map is not the territory..

I believe the EU has (or is drafting) laws about LLMs of a certain size which this release would not comply with.

How do you handle client side interactivity? I’m probably an outlier, but all the JS I write is client side, and I sure wish I had a typed language to use in development.

There is a lot more to San Francisco's housing crisis than price controls: lengthy permitting processes, environmental reviews, NIMBY community outreach, etc.

You are missing the point here – garbage collected languages (the "allocate it and forget about it" style, not refcounting like Objective-C) require much more memory to perform at the same level as a language where memory is explicitly allocated and deallocated.

I don't think the Raspberry Pi foundation needs to focus on direct IGBT drive, and there are a lot more tasks in the world than driving BLDC motors.

And yes, there are plenty of highly-specialized microcontrollers that serve a variety of industry niches quite well.

But look at the competitors from ST in RP2354A price bracket of ~$1:

RP2354A, $1 at whatever quantity: Dual 150 MHz CM33, 2MB flash, 520KB SRAM

STM32F103, $0.99 at Qty 1K from LCSC: 72 MHz CM3, 128KB flash, 20KB SRAM.

STM32L431, $0.98 at Qty 1K from LCSC: 80 MHz CM4, 256KB flash, 64KB SRAM.

There are several ST clones from China that are offering a bit more SRAM, a bit higher clock speeds or slightly more flash, like 512KB, but nothing even comes close to the RP2350.

PIO more than makes up for the lack of any digital-specific interface that you think you're missing, not to mention you have an entire extra core just sitting around that you could use to bit-bang whatever crazy interface you decide that you need.

The main area where they are significantly lagging their price-matched competitors is the ADC, and analog in general. I suspect that they are prioritizing limited die area for compute over large analog blocks that are hard to characterize and design on whatever process Sony is giving them.

And if you really need certain specific peripherals (and low-power doesn't matter to you) - capacitive/inductive sensing, DACs, etc., you're almost better off buying a low-spec ultra cheap MCU with the features you need, and then running it as a peripheral to the RP2350. I honestly don't think there's a better price/performance chip out there right now.

This is what happens when your phone and all it's apps are written in a garbage collected language.

The MCU is $0.80 - $1.10.

$1.10 for a dual core Cortex-M33 with 2MB flash and 512KB is a bargain in 2024 compared to other MCUs available at this time, at least in terms of prices that you'll be able to get as a regular consumer in the US. The only other chip that even comes close is the ESP32.

It's incredibly refreshing to see them pricing these at volume costs for non-volume buyers.

The insane component prices that we pay in the US for lower volume electronics manufacturing are killing innovation and driving manufacturing to countries with actual price competition.

Looking on Digikey/Mouser, you'll find that other MCUs with a similar spec are selling for at least $4-5 at qty 3000+.

The RP2350 price is a lot closer to what a large volume buyer would pay for MCUs like this, and still appears to have a healthy margin on top of the cost of dies, packaging, test, etc.

I’ve always kept the dedicated BMC network port locked down out of paranoia, but this seems to be an exploit that a rogue BMC or BIOS could use to access the host networking stack.

it's stopping, like all printers of the era, e.g. https://youtu.be/A_vXA058EDY?&t=41

edit: I see now you were asking about the drum, rather than the paper

NeXT invented Objective-C and encouraged its use, and the object-oriented paradigm was as popular back then as rust is today. It was just trendy to do so.

Memory allocation isn’t that slow (in fact all the ram is SRAM which is typically quite fast), it’s just that you only have 256k-1M RAM in total. This means that any time you’re saving later by trying to fill space now ends up getting wasted when that memory needs to be reclaimed.

Is that via cash holdings or stock holdings? I know Alphabet has had some buyback activity, but I don't really track Apple's moves here.

I am glad to see Alphabet paying dividends now though, it feels like the sign of a company that knows insane stock price growth can't go on forever.

So caveat that I am not a small business in need of any of this stuff, but I'll give you an example of the kinds of things that I have struggled with in the past where I think a solution like this could add a lot of value if extended in the right ways:

- certificate management amongst a plethora of hosts, both SSL/web certificates for external use, and management and installation of self-signed "root" certs for validating internal applications and services - keymastering server: an appliance that acts as a genuine root of trust for an organization, using a Yubico HSM for key storage, but providing middleware & admin controls to manage issuance and distribution of intermediate certificates - AD/LDAP/SSO/etc user management, key issuance, etc.

If you have a small team and you don't need global redundancy for these functions across a large fleet, then it makes a lot of sense IMO to shell out $5-10k for a set it and forget it security appliance that makes certificate/key management simple and easy.

I think the biggest challenge is that it's hard to build trust as a startup without open-sourcing your stack, but that makes it a lot harder to get buy-in for an appliance model unless you have some creative dual-licensing ideas.

But "your keys/certs are stored securely on your hardware in the room next door" is a compelling value proposition & probably a much easier pill to swallow for certain companies than a cloud HSM or other solutions which sorta boil down to "trust me bro".

Think about a company like ADT - they are selling security systems, but the people who really really need security (large clients with large IT budgets) would never buy an ADT system.

So like it or not, you're going to be going door to door and helping smaller clients integrate this into their systems.

I think the right way to approach this would be to better understand the problems your clients would face when trying to integrate this kind of system, and then figure out how to solve them at scale in a way that you make customer acquisition and onboarding easier in the future.

Maybe it's things like creating base docker images for common services or OS pairings that have your stack already integrated. Maybe it's turnkey integrations with existing cloud identity providers or SSO. Maybe it's tailscale integration.

In fact tailscale is probably a good model to look at here - no large organization with an existing VPN solution is moving to tailscale, or at least weren't when they first started. But tailscale made a hard thing easy, and that's exactly what you're doing here.

> There is no strength gain without muscle gain. There is not a single mechanism recorded that would drive this behavior.

This doesn't add up to me, it seems like it doesn't account for the impact of a "trained" nervous system vs. an "untrained" nervous system, skeletal biomechanics, and a whole host of other factors.

Maybe given an ideal muscle in a perfect vacuum, size == strength, but that is not the world we live in.

This video gives some good intuitive examples of Gaussian splatting: https://youtu.be/GInps7ViawA

The information?

But the vibe there is more WSJ and less buzzfeed

The example on their page [0] says: "Baby, Don't Hurt Me" is a song written and recorded by American singer-songwriter and actress Patrice Rushen. I1 was released as the title track from her 1984 album of the same name.

This song was by Haddaway

0 - https://camo.githubusercontent.com/ee418c20b20aab4e9f10bc344...

What attributes would be worth preserving that you wouldn’t otherwise be able to do?

you know what I really want?

A macro for copy and paste, so I can re-map it to whatever key combination I want across all apps in linux.

well, the rubber compounds used are very different too. You would not enjoy riding a bicycle on the hard rubber used for a semi-truck tire.

The 4th-power rule is more applicable when it comes to road damage.

If you want a comparative analysis of tire wear and environmental impact, you have to consider the average mileage before a tire is worn out, the volume/mass of material that's lost, etc.

This article[0] suggests 150,000 miles for steer tires, and 300-500k for drive tires. If a tire starts out at 1/2" (16/32") and is worn down to 3/32", a delta of 13/32" or ~10mm. Radius of a typical 22.5" tire is 500mm and tread width 250mm, so you have (π500^2-π490^2)*250mm = 7.5L of rubber material deposited all over the world for each tire.

Over 1M miles, this is 12 steer tires, and 24 drive tires, so ~200L of tire rubber over a typical semi truck lifetime.

0 - https://www.fleetowner.com/operations/article/21676805/tires...

Honestly, tire companies would love to sell you tires once a year or more, if they were actually safer for the environment, and safe to eat or whatever. I'd happily make that trade-off, if there was legitimate science to back it up.

I think about this every time I drive through the morgan hill / gilroy / watsonville area on the way to a camping trip. You have some of the most expensive crops in the nation (berries, leafy greens, cherries, etc.) growing here in california, and it's surrounded by roads that somehow seem like they are always at capacity, depositing tire dust, particulate matter from diesel engines, and who knows what else all over the soil and the plants themselves.

This stuff should be just as regulated as if we were spraying it on our crops, because we are.

Any article published by the Washington Post is written by agents of their company, and that's why they are the responsible entity. Should you be able to sue every newsstand in your local city if they are selling a newspaper that defames you? After all, those newsstands are profiting from the sale of libelous content...

You could make the same argument about Google search, which is a decidedly more user-driven algorithm determining what you're seeing.

Google can't and shouldn't be responsible for the factual accuracy of sites that it indexes and shows to users.

Consider e.g. what happens when libelous content is indexed.

AI generated content is a different story, and I would not expect a court to lean towards Section 230 protections for such content. But user generated content, or content index, scraped, or otherwise reproduced verbatim from real humans is a different story.

If you want publishers penalized for revenue generation that comes from illegal content, then it seems appropriate to draft a law that requires attribution of said revenue to specific pieces of content, and the ability to use this in discovery.