f_devd

Unrelated citation?

Ngl the weird UI bugs made me think it must be made by AI, either that or the developer has very skewed frontend skills where gradients are fancy but sliders & interactions are broken.

Chips?

Only ST, NXP, Nexperia, Osram, and a bunch more obscure ones. It's not a boom, but it's far from a wasteland

Inject some adversarial priming as is in actual usage, and you can probably get that number to >=95%

Because if you go down the callstack eventually you won't get the await keyword anymore; you'll get the actual 'waiters' and 'wakers' which define your scheduling

Except there is little cooling or power in space, depending on your position in orbit you could only have one of those at a time.

I think they mean that a non-observant visitor cannot tell the difference between both situations

Wouldn't be surprised if they have their own internal PBX system with a SIP trunk

That sucks, but also probably the best vindication for their strategy; any other mcu and you just wouldn't know.

Always a bit jarring to see a devboard stacked on an otherwise neat board. Looks promising though.

A UPS-style grid connected inverter (with phase balancing) would be significantly more complicated by also significantly more useful. More in the critical/specialized part category, rather than near-commodity (like MPPT/BMS)

There is no "who", once stabilizing institutions 'fall' the only remaining option is social pressure (which can come in various forms) but that does require a critical mass as it's very much reliant on network effects.

Having worked on compression algos, any NN is just way to slow for (de-)compression. A potential usage of them is for coarse prior estimation in something like rANS, but even then the overhead cost would need to carefully weighted against something like Markov chains since the relative cost is just so large.

Isn't it the employees' responsibility pay for their union membership?

No, contributions are handled by the employer/company

One likely source: https://techcrunch.com/2024/10/17/sam-altmans-worldcoin-beco...

Remind me to never look at twitter replies again, by far most counterproductive threads I've seen

No, it's gc-like. Up to 4x slowdown iirc

Where do you detect malice? The claims are quite accurate.

I have no idea why I should be against using LLM

It highly depends on your own perspective and goals, but one of the arguments I agree with is that habitually using it will effectively prevent you building any skill or insight into the code you've produced. That in turn leads to unintended consequences as implementation details become opaque and layers of abstraction build up. It's like hyper-accelerating tech-debt for an immediate result, if it's a simple project with no security requirements there would be little reason to not use the tool.

I never started for similar reasons

I have the same with journals, but the video archiving has actually come up a few times, still fairly rare though. I think the difference is that you control the journal (and so rarely feel like you need it's content) while the videos you're archiving are by default outside of your control and can be more easily lost.

I would a agree a careful and very small amount of above brainrot in post-training could improve certain metrics, if the main dataset didn't contain any. But given how much data current LLMs consume and how much is being produced and put back into the cycle I doubt it will miss be missed

A more modern approach of doing the same to use polymerized quantum dots (I believe it emits wide spectrum white when a voltage is applied), and passing that through a quantum dot film to get any specific wavelength.

I do not think this is the case, there has been some research into brainrot videos for children[0], and it doesn't seem to trend positively. I would argue anything 'constructed' enough will not classify as far on the brainrot spectrum.

[0] https://www.forbes.com/sites/traversmark/2024/05/17/why-kids...

Hey. That's sounds like an awful experience. Btrfs has some rough edges especially since a lot of maintenance tasks are "manual", and you are right to try and address it. And it's annoying that becomes personal for some people with too much time.

For my perspective, my experience with btrfs has been flawless through 11 machines and at least 3 major releases on each without any maintenance but it could just be I'm not hitting the worst case (only use snapshots on 2 machines, raid on 3). And I've only used btrfs since fairly recently (~4 years now). I've had to recover one drive of a friend using the method I outlined before as he filled the entire drive with media. For me the trade-off of a few rough edges but more functionality & flexibility than other filesystems is worth it.

For your update issue, I think you're mostly correct; the package manager likely assumes the filesystem is not snapshotted (i.e. it will reclaim disk space), while btrfs with snapshots/CoW will use the entire size of written files unless it's in the same snapshot.

Btrfs still can't either give an accurate answer to `df -h`, or repair a damaged volume.

In my personal experience, writing to a full volume corrupts it irretrievably 100% of the time, and then it cannot be repaired.

While I get the frustration, I think you could have probably resolved both of them by reading the manual. Btrfs separates metadata & regular data, meaning if you create a lot of small files your filesystem may be 'full' while still having data available; `btrfs f df -h <path>` would give you the break down. Since everything is journaled & CoW it will disallow most actions to prevent actual damage. If you run into this you can recover by adding an additional disk for metadata (can just be a loopback image), rebalancing, and then taking steps to resolve the root cause, finally removing the additional disk.

May seem daunting but it's actually only about 6 commands.

This is incorrect, quoting Linux 6.7 release (Jan 2024):

"This release introduces the [Btrfs] RAID stripe tree, a new tree for logical file extent mapping where the physical mapping may not match on multiple devices. This is now used in zoned mode to implement RAID0/RAID1* profiles, but can be used in non-zoned mode as well. The support for RAID56 is in development and will eventually fix the problems with the current implementation."

I've not kept with more recent releases but there has been progress on the issue

Depending on what you're trying to teach, I would think something like these would be nicer to read (but with minimal dependencies): https://github.com/jackkolb/TinyRSA or https://github.com/i404788/tiny-rsa

I believe RAID5/6 is still experimental (although I believe the main issues were worked out in early 2024), I've seen reports of large arrays being stable since then. It's still recommended to run metadata in raid1/raid1c3.

RAID0/1/10 has been stable for a while.

FYI XFS is not redundant, also RAID usually refers to software RAID these days.

I like btrfs for this purpose since it's extremely easy to setup over cli, but any of the other options mentioned will work.