9
points
em3rgent0rdr
Joined 6,149 karma
- em3rgent0rdr parentWhen C code is run in machines capable of failing with gruesome death, its unsafeness may indeed result in gruesome death.
- I don't think the prevalence of these articles this time of year is because the authors go on holiday, but instead is because the new year is the perfect time to ponder: "Will this be the year of the Linux desktop?"
- Why can't these posts just say "microsecond" instead of the vague and misleading "ultra-low"?
- Very useful. It would be great for the browser become the cross-platform application target. I've been eagerly waiting for Qt WebAssembly to mature.
- Looking at the complexity and area of hardware floating point, I often wonder why we don't see more unified combined integer+floating point units, like done in the R4200 [1], which reused most of the integer datapath while just adding a smaller extra smaller 12-bit datapath for the exponent.
- If you use a tile-based hardware renderer, such as on the original nintendo chip, then pixels are rendered on the fly to the screen by the hardware automatically pulling pixels based on the tile map.
- The '7660 is good for low-power and is my go-to DIP-8 part when I need a half or double voltage supply on a breadboard.
- id Software should have just partnered with a heavy metal band that jointly released an album of Doom music you could put in your stereo while you play the game.
- I'd much rather invest one powerful machine that cand do work and games instead of two that take up extra space and generate more e-waste.
- But how deal with security and DDoS?
- yes, and sometimes Grok.
- To gauge.
- Most look like they were done by a beginner programmer on crack, but every once in a while a correct one appears.
- Both infrastructures are made to last.
- Impressive, but there is a noticeable lag after modifying the terrain or moving the camera. Is there a way to know if the browser is using the GPU or CPU for rendering, and is there are way to see the milliseconds per frame?
- "resistance level trivial"
Could literally replace the control software with a potentiometer (a resistor)! :)
- But you said "phase is 180 degrees" which is 1π, while Barkhausen instead says integer multiple of 2π.
- Sounds like you are stating https://en.wikipedia.org/wiki/Barkhausen_stability_criterion (1921):
"if A is the gain of the amplifying element in the circuit and β(jω) is the transfer function of the feedback path, so βA is the loop gain around the feedback loop of the circuit, the circuit will sustain steady-state oscillations only at frequencies for which:
1: The loop gain is equal to unity in absolute magnitude, that is, |βA|=1, and 2: the phase shift around the loop is zero or an integer multiple of 2π: ∠βA=2πn,n∈{0,1,2,…}"
- This made my day!
- Let's not forget the cost for making and transporting a large thick glass tube and the associated electronics and energy required to heat metal and liberate electrons and guide them using magnetism. I too am much happier with LCDs and OLEDs.
- CRTs are mostly empty vacuum and won't take that much space when crushed.
- Not self-hosting if you actually need email does not address the elephant that self-hosting email doesn't actually do email. I say this as someone who self-hosted for several years but had to give up because important emails were discarded. Until the deliverability issue is actually addressed, self-hosting is not viable for email.
- Congrats on getting something that functions, despite the glitches, which are probably due to crosstalk and other noise over the rat's nest wiring.
- PayPal 20 years ago made it easy to engage in internet commerce across various world currencies. And now users of PayPal have an easy way to commerce with two more world currencies using a familiar trusted interface. Another way PayPal as the middle man helps: "Unclaimed links expire after 10 days", which sounds like it avoids the problem of accidentally sending bitcoin into the void.
- Yes and no. A problem with 8-bit and 16-bit for desktop and servers is the limited memory address space, so the compiler has to insert extra instructions to deal with things like updating the segment registers. And likewise if you need to do higher-bit math then the compiler again has to insert extra instructions. Those extra instructions clog up the pipeline, but aren't needed if your largest program's working memory set and the largest precision math you generally need fits within the ISA's bit size. Unless you are doing scientific computing or other large-memory set tasks like Blender (which dropped 32-bit support), then 32-bit really is good-enough.
I couldn't tell if your comment was a joke, but it is worth mentioning the 8-bit microcontrollers like TinyAVR still fill a niche where every joule and cent counts.
- Not just more power-efficient, but also a little more memory efficient because pointers are only half as big and so don't take up as much space in the cache. Lower-bit chips are also smaller (which could translate into faster clock and/or more functional units per superscaler core and/or more cores per die).
Part of the problem with these discussion is that often when people say "64-bit" vs "32-bit" they are also considering all the new useful instructions that were added to the new instruction set generation. But a true "apples-to-apples" comparison between "32-bit" and "64-bit" should be using almost identical whose only difference is the datapath and pointer size.
I feel that the programs and games I run shouldn't really need more than 4GB memory anyway, and the occasion instance that the extra precision of 64-bit math is useful could be handled by emulating the 64-bit math with the compiler adding a couple extra 32-bit instructions.
- Just reading about this...turns out nommu Linux can use vfork(), which unlike fork() shares the parent's address space. Another drawback is that vfork's parent process gets suspended until the child exits or calls execve().