inferiorhuman

6 เดือนที่ผ่านมาdiscuss

  Of course I wouldn't vibe code in a serious production project, but I'd
  still use an AI agent, except I'd make sure I understand every line it
  puts out.

So you value your ability to churn out insignificant dreck over the ability of others to use the internet? Because that's the choice you're making. All of the sites that churn your browser for a few seconds because they're trying to block AI DDoS bots, that's worth your convenience on meaningless projects? The increased blast radius of Cloudflare outages, that's a cost with foisting on to the rest of the internet for your convenience?

Thanks.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

[flagged]

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

[flagged]

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

[flagged]

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

[flagged]

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

  Rust assumes a runtime, the standard library assumes a stack exists, a heap
  exists, and that main() is called by an OS;

Wrong.

Source: I'm writing Rust without a runtime without a heap and without a main function. You can too.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Sure, some do, but some are coming around and some were never there. Which is why it's important for a company like Adafruit to pick a manufacturer that is towards the open end of the spectrum. Unfortunately NXP isn't that manufacturer even if their silicon is more powerful.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Levis stuff has been made overseas for decades now. It's only with the more recent shift towards using cotton blends in nearly of their jeans that the longevity has suffered.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Nah, it's a spectrum. Companies like NXP and Infineon are at one end. NXP wants a ton of personal information to access even the most basic docs on some of its chips, sometimes even an NDA. Infineon won't even acknowledge you for the most part.

Companies like STM, RP, and TI are at the other end. STM got super popular because they're cheap and the documentation is incredibly easy to get at. I think RP is following suit.

Renesas puts out some documentation, but it's really rough. Anything that has even a whiff of crypto is completely undocumented. They're also squatting on a few Rust crates where Espressif actually hired a Rust developer to work on their Rust HAL. The most comical thing is that while they version their reference manual they don't seem to update it and instead issue a ton of broad errata that apply to multiple manuals.

Before the acquisition Atmel's documentation was well written and organized.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Mostly I'm just leery of software defined peripherals being at the mercy of whatever community springs up around them, nothing specific. In terms of a Metro then yeah, something to slot in where the Due was absolutely with high speed USB, 10/100 ethernet, CAN FD, and all that jazz that wouldn't work on a $10 board. A SAMV70 successor to the Due?

NXP just seems antithetical to an open platform. Then again Arduino went with Renesas, and they're… not great.

Otherwise it's the openness that would pique my interest. SWD headers, yes 100%. But also the documentation. No half-assed SVDs, buggy closed source flash algorithms (Microchip), wholly undocumented peripherals (looking at you Renesas), stuff like that.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Right, but you're not really competing on processor speed. You're competing on maturity of peripherals where the RP doesn't really match up PIO or not.

Edit: I see you're comparing it to the 3.2 but I suspect most folks are going to be comparing your offering to the 4.x.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Which is still a far worse experience than if Cloudflare's services weren't needed.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

  Why do you say it doesn't solve loads of things?

Because I'm sitting here twiddling my thumbs waiting for random pages to go through their anti-LLM bot crap. LLMs create more problems than they solve.

  Um if I ask an LLM about a fake band it literally say I couldn't find any
  songs by the fake band did you type is correctly and it's about a millions
  times more likely to guess correctly

Um if Apple wrote proper error handling in the first place the issue would be solve without LLM baggage. Apple made a conscious decision to handle "unknown" artists this way, LLMs don't change that.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Doubt it. Of all the issues I run into with Siri none could be solved by throwing AI slop at it. Case in point: if I ask Siri to play an album and it can't match the album name it just plays some random shit instead of erroring out.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Someone's in the Embassy matrix channel currently trying to figure out why the SPI driver is preventing the USB peripheral from enumerating on their G0…

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Cortex-A includes a watchdog so yeah.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Considering the USB errata for the F7, I assume they didn't.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

  I've yet to see a MCU vendor ship without bugs. At least with ST,
  the MCU is very cheap.

Moving the goalposts much? You went from "lengthy errata doesn't mean anything" to "at least it's cheap", which was my point entirely. The STM32 lineup is cheap with a bunch of features, has readily available documentation, and that appeals to a lot of people.

  This feels more like an Apple bug to me considering how they work very
  well on Linux, Windows and Android.

Yep, that's the typical STM fanboi response and part of why I'm not so gung ho on STM products. It just feels… cultish and obnoxious.

Meanwhile I've been using Macs on and off since before USB came around and this is the first USB device I've found that glitches out like that. Given that Apple uses off the shelf USB silicon (TI) and the complaints about STM's older USB FS peripherals I came across I'd fully believe it's an STM problem.

What is entirely STM's fault is that they still market the F7 based devices (ST Link, Nucleo, etc) as being Mac compatible. They've also skipped out on putting that fun little wart into the F7 errata.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

Of note neither the debugger nor user USB port on that board work with ARM Macs (guess how I found that out). You can connect it to a hub as a workaround but that may lead to data corruption (per the errata).

Also worth noting that the discrete STLink V3 dongles also use the F7 for USB stuff.

Also also worth noting that not all of the Embassy examples are set up to work with Nucleo boards. It's an odd choice but it is what it is.

inferiorhuman

6 เดือนที่ผ่านมาdiscuss

  Just like security bugs, lengthy errata doesn't mean anything. A popular
  MCU will have bigger errata sheet because it gets more eyes on it.

Yeah, no. From all outward appearances STM stuff is basically rushed to market, fix the bugs later. We're talking basic shit like xyz clock input or watchdog straight up doesn't work. More advanced stuff like one of their USB controllers straight up doesn't enumerate with ARM Macs — still not in the errata or marketing materials BTW although the workaround may end up beating you with some other bugs. Or the one family that they had to completely rework the USB peripheral while subtly changing the part numbers. Or yeah no.

> The spreading out over multiple documents is good organization.

No, it's really not. It's things like reading up on a peripheral in the reference manual and then trying to figure out which pins you can use with it. Some vendors will put that in the section with each peripheral, most will include a table within the RM, and STM splits it up into multiple documents — per variant within a family because the families are often loosely related.

None of this stuff is offered up in printed form, they could at least hyperlink it (whether intra- or inter- document).

It's not that surprising really. You've gotta cut costs somewhere.

comments