tliltocatl

The major problem with VR is that it simply doesn't have a good use case beyond the initial wow effect. AI certainly does.

Google search became considerably worse around 2019 when they started using LLMs for indexing, which make it ignore keywords it deemed "irrelevant".

People hated that cyanydeez told them the truth.

If you don't want it to be copied, don't show it to anyone never ever.

Scroll hijacking hell.

And still be worth it.

Imagine yourself, not everyone is willing to make the tradeoff. Also, fuck bambu so much.

Really? I was under impression 100µm is state of art.

Encoders are cheap, even interferometric setup is possible to do at perhaps <$300 if you happen to live near the NeHe rust belt. Actuator backlash and stiction will still be a problem. Good actuators are expensive. Solving backlash is what is nice about this setup.

These aren't exactly RepRap-friendly. The piezo buzzers are too soft. For a proper multilayer piezo actuator you have to either go to Thorlabs (a bit expensive) or other manufacturers (either expensive or "don't bother us until you are ready to buy a few thousands"). AFAIR MLCC ceramic capacitors actually can make half-decent actuators, but not sure if these are suitable for precision position. Baking your own would be doable, but who wants to deal with lead? And once you got the chips, there is another problem: how do you couple it to a plastic flexture? "Adult" stuff uses wire-EDM-cut metal flextures. While not completely impossible to DIY, wire-EDM a whole undertaking in itself, and an expensive one.

Piezos are sure the way to go for a fab-in-a-shed youtuber, but not yet for those who want to make it reproducible by others.

Year, we should rather switch to sexagesimal so that children have to memorize a longer multiplication table, and use an hieroglyphic writing system. /s

You can do things with holography that are impossible to do with any other 3D display. I. e. comparing two objects for sub-wavelength differences.

Anything that isn't C.UTF-8 is totally broken anyway.

If I'm reading it correctly, the top comment is arguing that having electronic payments run by for-profit entities adds no value. Not that electronic payments are useless, rather that these should be a state-run service. Which is one way to solve this I guess (not that it will help moral policing stuff much, but at least no more robbing poor Paul to reward rich Peter).

Nobody is claiming payment cards adds no value, that'd be absurd. But their cashback programs and other bullshit (see recent itch.io/Steam moral policing story) certainly adds no value.

Fun fact: being able to run garbage-collected languages (i. e. Lisp) was one of original motivations for adopting demand paging.

Not sure why author does it, but I use C over C++ for one reason: I'd rather not have random hidden malloc() scattered in my code. And no, it's not about latency or performance. Once my code takes an yet unexplored part and runs out of 200kB RAM, the will be no way for me to learn about it - running out of memory will bring down both the logger and the radio link, which is the only way to get the logs from a sensor installed twenty meters above ground in a hazardous environment facility. C may be unsafe, but most errors short of "writing to a random memory area" are either well-contained or at least reproducible. Dynamic memory allocation means that anything may crash everything. Manageable if you have a MMU and can contain crashes within isolated heap, but if not - I'd rather not bother. And yea, you can write zero-allocation C++ code, but why bother if most of STL is now unusable? And you get some new and exciting UB modes (seriously, no union aliasing, what the heck?)

Also, template metaprogramming is way more arcane than C macros. And I need compile-time metaprogramming in leu of dynamic allocation. So C macros it is for now (Zig is promising but still not there yet).

The problem is histological compatibility, i. e. not getting it ruined by the recipient's immune system. The TFA was very lucky having apparently 100% compatibility.

> stability wins

Stability sucks. Instability sucks even more when you are in the middle of it, but it is transient. Stability is forever, until it suddenly isn't.

Comptime here means not "compilation time", but rather ability to run some your code during compilation (i. e. compile-time metaprogramming). Pascal didn't had this.

Abuse reports aren't even done by users. That's a classical externality.

WTF? Government buildings is about the only place these should NOT be banned.

Yes, but enough to run a text editor, or even a mechanical CAD. Not an LLM, but that's the point!

Yea, that's the question. Yield situation can improve. Area overhead would not improve short of a completely new and incompatible tech.

> the module is FCC compliant with its number written on it.

Just like I'm telling in the sibling comment - IANAL but that's probably not enough for EU. RED cares not just about RF PHY, but also for example if you can ran a FOTA update, and if you do, is the key secure enough. So module being compliant simplifies things, but your device might still require a cert as a whole. Again IANAL, this is based on my experience with certifying a full-custom device.

Yuck. Time to build an xSPI/HyperRAM workstation (if only these had multi-bank chips).

> Or do you still need the product as a whole to be compliant?

I'm not 100% sure, but I've been thru a round on RED (on a full-custom device) and much of it involved security and authentication within application software. RED basically boils down to "we are fucking tired of your little plastic shit running botnets, the customer are clueless, so fix it if you want to sell it".

So actual code review and running tests in front of the auditors, basically everything short of a pentest, not just RF PHY stuff. So my gut feeling is that while you can skip the stuff related to RF PHY if you use an off-the-shelf module, the rest will is still be on you.

Based on quick googling the certifiers agree with me (but again, that's not same as as a court saying that's true): https://compliancetesting.com/ce-certification-for-espressif...

How so? FEOL is pretty much the same, BEOL is almost the same save TSVs, the packaging tech is different and more advanced, but not exactly 1:1 comparable. Do TSVs really occupy 3x the area of DDR IO's?

Love the idea, hate the presentation. Also, wasn't able to find the simulator link, is the simulator not publicly accessible?

Also, one friendly tip - if you are EU-based and plan to sell the hardware, drop the ESP32/wireless. Yes, that would mean no wireless pads, but it will make regulatory compliance a lot easier. Maybe replace with a breakout socket (not sure if that is allowed).

I mean, good thing it's patented? To evils cancel each other, I guess.