enva2712

brainrot has no meaning

https://en.wikipedia.org/wiki/6-7_(meme)

i’ve run into this issue with pthread_cancel

it makes cleanup logic convoluted when you can’t easily pthread_cleanup_push, forcing you to either block on the join or signal cancellation and detach

rankine cycle lets you cross vapor dome to access latent heat. enables scaleup

i agree with your sentiment, and them botching the license was clearly a problem, but at the same time i think a dev waives their right to be indignant about someone forking and commercializing their code when they provide a perpetual, irrevocable, commercial license to do so. if continue was GPL’d or something i would respect the uproar more

you assume professionalism and technical ability are positively correlated. my anecdotal observations would lean the other way but i have no data to substantiate this on

i do disagree with the methodology of the paper though - adherence to standards is a metric of conformance to a status quo, which as someone else’s comment points out feels like the midwit meme

this is incredibly negative but lacks examples, could you back your statements up with evidence or ease off the hyperbole? the middle ground is the worst

you install the bootloader yourself on arch

this comment is a masterclass in advertising

start relatable: “my experience” add reinforcing detail: works well with fx2 hw add negative experience: bad for analog logic introduce habit trigger: next time use ngscopeclient for analog logic

fixed function compression on-die would be interesting if applied to this

> Don’t say no to leadership when the timeline is not realistic.

This was listed as an action that undermines trust. You agree with the author

(It would look like kind of like a dragonfly eye)

Good point, the sensor count exponentiates and the optics get a lot more complicated if you want a fully integrated system. Nothing on the market I know of but with where we are on the scaling curves now might be the time to try something like it - you could put together a basic proof of concept with a load of commercial sensor elements and wide angle lenses on a sphere. Eventually you can consolidate the central sensors and lenses into concentric hemispheres. You can reduce the data volume by narrowing the camera angles eventually too

Not sure there’s a market but maybe with VR stereo 360 becomes more valuable, who knows. Technologically doable though

Responses so far say to optimize neck latency or use a joystick but why not use a 360 camera and handle it in reprojection. First pass could literally be a gopro or insta360 streaming to the headset and you could eventually integrate cameras and do the stitching yourself. The tech already exists and works, and it removes moving parts and actuators

But are they designed to carry those loads with a drone flock. They’ll also increase the received wind load. Unlikely to cause an issue but you still have to do the math to determine the decrease to the margin of safety

I agree, perfection isn’t a realistic expectation. I also think effort spent building better defenses leads to fewer exploits over time than adding more of the same defenses. The marginal cost of bypassing a given defense is far lower than the initial cost to bypass a new defense

I saw that deno did this but cool to see node picked it up too. I wish there was an option to run turbofan at build to generate the instructions rather than shipping the entire engine, but i guess that would require static deps and no eval, which can’t really be statically checked with certainty

Ahh yes, security through obscurity - if we make it so complex we can’t understand it then no one else can either, right?

The important thing is making walls indestructible, not making more walls. Interfaces decrease performance and increase complexity

Interesting thoughts on using axis lines only when the relative comparison is meaningful, though I don’t think the downsides to superfluously adding them outweigh the other design benefits like providing clear bounds and a visual anchor to attach tick marks to. The article seems a bit objectivist but I think the right tradeoffs depend on the context as well as the data

Thoughts on lattice-based crypto?

The utility of a cryptosystem is the extent it force-multiplies compute in the defensive direction. Crypto that depends on equally computationally leveraged parties is broken crypto

I’d interperet the cease qualifier in goodhart’s law to require the measure to be good in the first place, but I think SLOC is a negative indicator regardless of whether it’s a target

I think there are parallels between Deutsch’s ideas about explanation and the concept of coincident vs inherent complexity

I wonder why they didn’t try a pdms resin as well

here’s the paper: https://www.nature.com/articles/s41586-024-07061-4.pdf

If the drive motor was asynchronous you could use the inductive windings on the rotor to power your rotating electronics, but the phase difference may get pretty extreme

My comment wasn’t about agi, but out of curiosity what definition are you using for it?

To be fair, I don’t see a categorical difference between human intelligence and compression either

> lossy jpeg of web

Knowledge is compression https://en.wikipedia.org/wiki/Hutter_Prize

Offspring

It came fast, I’m barely done celebrating 1696969420

The lens solution is clever and, I’m glad to see lenses catching on outside the haskell ecosystem

I think the primary issue you raise comes down to whether or not the peers can be verified to be updated before applying the migration op. If this is the case, you can go the standard sql route of deploying a diff adding forward compatibility, applying migration op, deploying diff removing backward compatibility. This is the route I’ve gone since in my case the peers are web browsers so I’ve got a pretty reliable deployment system; though the lens solution is much better since it lifts this requirement