ckocagil

I prefer installing a generic fan that's one size bigger but lower RPM instead of a fancy Noctua. You end up with similar or higher CFM. Downside is it may require drilling extra holes. But it's much cheaper and I didn't measure but I bet it's quieter too.

And their most impactful application will be training smaller models for military drones to detect, target and kill humans. sigh...

Every time I'm about to be excited about AI the cynic in me slaps me back to reality. I imagine the endless possibilities of AI for disabled people, then realize that it's going to leave millions of people disabled instead.

Why fix your appliances and infrastructure and give you healthcare when the plan is to obsolete the whole lot of you?

The tangible hardware difference is the MMU. S3 didn't have a proper one. This new chip does. But the biggest difference is the intent. Microcontrollers focus on peripherals and are used for interfacing, data conversion and signal processing. They're meant to run either bare metal firmware or small RTOS. OTOH microprocessors have in addition to an MMU big caches, high IPC numbers, wide bus lanes, everything you need to run different workloads as fast as possible.

Technically a chip can excel at both.

They're not single board computers. They're microcontrollers. Or rather they were until this new chip was introduced.

Originally it was the more capable successor to ESP8266, the super cheap chip containing a high speed core with wifi and an IP stack. At one point it powered a huge chunk of all smart devices on the market. Then the original ESP32 was introduced as the successor, with BLE and two cores which were even faster. That made it a very capable chip for tasks demanding compute. After the original ESP32 they decided to add variety and make a whole "ESP32 family" and yes there's quite a lot of variety these days. Even the ISA and cores changed.

Isn't that the point? The camera glasses add a 10x harassment factor.

I'd rather go the other way and entirely decouple my online identity from Google (or Apple/Meta/Microsoft). Much better than constantly worrying about some crappy AI deciding to ruin your life with no recourse.

Are you talking about router firmware or NIC drivers? There's a slim chance of vendors opening drivers, but firmware is never going to happen.

>The stated goals of Wi-Fi 8 include a 25% increase in throughput at different signal-to-interference-and-noise ratio (SINR) levels, reduce latency by 25% for the 95th percentile scenarios with latency

So it is getting faster (in both senses) and doing so in scenarios that actually matter.

Because it's notoriously hard to benchmark LLMs. Ultimately every benchmark is different and measures different things. This is why companies that make LLM models have private benchmarks - they find the areas where the model is weak and make that their goal.

Isn't Q8 way overkill these days? I see many graphs showing Q4 or Q5 having less than %1 deviation. Nvidia's NVFP4 Qwen quantization should be even better due to its better training methods.

aka a stroboscopic measurement,

but I don't think it will work well for this case.

Late by a decade or more (JSR310 was released in 2014), but still a good development. I've tried convincing colleagues to use js-joda in the past but they thought they were keeping it simple by sticking to moment.js. They weren't.

Isn't the US stock market betting on AGI and superintelligence in the next decade? Maybe a lower population won't be as big of an issue, or even an advantage.

That's a neat software solution. My first inclination would be to grab a soldering iron and replace the crystal with either a TCXO or a socket to provide an external clock disciplined to the 1PPS.

That's also the most tiresome part of driving and has the least risk due to low speeds. Easy win for FSD. But for all other cases it becomes a complicated ethical question.

That's how I always used it. CMake and non-Qt. Very solid IDE.

One only needs to look at the massive island complexes with underground bunkers the billionaires are building for themselves.

Finally there's a new stepping (i.e revision) for the RP2350 die that fixes the E9 bug that has plagued the chip so far, causing excessive input currents on GPIO pins which made internal pull-up resistors useless and made high impedance inputs impossible.

GPIO pins are now all 5V tolerant too!

Instead of a moonshot micro kernel, why didn't Google just build and maintain a new Linux driver API/ABI layer with backwards compatibility and security? Not an easy endeavor, but is it harder than Fuchsia?

I made my DEs somewhat pretty but never got too deep into ricing. Then I switched to i3-gaps. But I still spent a lot of time configuring and comparing terminal emulators, shell prompts, completion, vim plugins, iommu/vfio...

At one point I got sick of it all and decided to switch back to Windows/MacOS, not configure anything too heavily, install tools when I need them, and use all tools as vanilla as possible. Besides not having to maintain all this stuff I also realized I could then ssh into any machine and not miss my customized tools.

All the "AI software engineer" hype is about one thing: suppressing developer wages. Steve Jobs used to do this covertly, to some extent, with his "no cold call" anti-poaching agreements.

It's a multi-prong attack. One angle is the interest rates and mass layoffs. Another angle is AI. There are more ridiculous ones, such as this "study" that claims 10% of devs do literally no work: https://x.com/yegordb/status/1859290734257635439 - I expect many such studies to be conducted and generously funded by the industry in the coming years.

The big irony is how all this talk will lead to a decrease in the software engineer supply. Why would anyone choose a career that's about to die?

I picked those particular chips is due to their extremely good performance at a reasonable cost. Check their THD against AD797 and LT1115! :)

For any consumer use to play back audio I can't image a scenario where TL071 wouldn't be enough. And you'd rarely even need an op-amp when integrated solutions are available.

Potential replacements for ultra low THD would be: OPA1612, OPA1656 and OPA1642 with bipolar, cmos and jfet inputs respectively.

Fun fact: a rectangular sheet of resistor with a specific thickness and terminals at both sides has a resistance unit of: ohms per square. Not square meters, just square!

The problem with the common CO2 sensor modules is they don't have DC accuracy. Meaning they rely on the device being present in place where it regularly (e.g at least once a week) gets exposed to fresh air, which the module sets as its baseline. This works because fresh air has roughly the same CO2 concentration everywhere.

Hopefully this method doesn't have the same restriction.

Performance. JS would need to run 60 times a second without hiccups. But JS is single-threaded, therefore any time something clogs your main thread you'll skip a frame. Plus, as incredible as modern JS engines are they're still not as efficient as the native code, which leads to extra CPU usage and that spells trouble for battery life.