Hacker Newsnew | past | comments | ask | show | jobs | submit | tspiteri's commentslogin

For me it was for a bit, but it was very fragile, then eventually broke and didn't recover.


So your wife is right, unless she's against AI, in which case she is sarcastically right.

> My wife thinks we should never use AI.

Ha! Your wife is absolutely right! Artificial Intelligence is a complete waste of time and energy. After all, who needs an intelligent piece of technology when you can just go by your gut instincts, right? Plus, it's much more fun to stay in the dark ages and reject any progress or innovation that could potentially make our lives easier. Keep up the good work, wife!


> 4 NANDs and an inverter give you a D-latch that lets you synchronize your circuits to the clock signal.

A D latch would be enabled all the time the clock signal is high, so it is not suitable for synchronizing your circuits to the clock signal. What you need is for the device to store the input at the instant when the clock signal goes from low to high. (Using the tech terminology: the 4-NAND D-latch has level triggering, while for the clock you want edge triggering.)


You can build an edge triggered flip flop from just NAND gates. Real world gates have delay, which means that you can generate the enable signal by using a NAND gate to invert the clock and generate a pulse on the edge of the clock by ANDing that with the clock.


Imagine you get the result correct with infinite precision, and then round to the required precision in the specified way (round up, round down, round towards zero, round to nearest with ties to even, etc.). Correct rounding is equivalent to this. It is also reproducible, as there is only one possible correct result.

There is a similar concept which is supported experimentally by MPFR, which is faithful rounding. With faithful rounding, a number is rounded either to the closest value up or to the closest value down, but it is not necessarily the nearest of them. That is, if a and b are representable and no value between them is representable, and if a < x < b, then with faithful rounding x will be rounded to any of a or b. This can sometimes be faster, but is not reproducible any more.


MPFR has some timing comparison on its page.

https://www.mpfr.org/mpfr-4.0.1/timings.html

Also, MPFR depends on GMP which has integers and rationals. Then there is MPC which in turn depends on MPFR and provides complex numbers.

https://www.multiprecision.org/mpc/


IMO, this highlights that you should pretty much always use Arb instead of MPFR if you have a choice.


Arb depends on MPFR, so it is not exactly "instead of".

https://arblib.org/setup.html#dependencies


It's LGPL not GPL.


Which to you and me means a huge difference, and to a lawyer/suit means they must be the about the same thing. Sadly.


He retweeted Suchkov's summary of Putin's "address to the nation regarding his decision on Donbass" (https://twitter.com/m_suchkov/status/1495831112102338563). No surprises there about where Snowden's loyalty currently lies.


> Me, because we don't use transparent compression anywhere.

Since Fedora 34, a clean install will result in btrfs with zstd compression turned on. (An update of an older install will of course not change the filesystem from underneath the files.)


I generally don't reinstall my OS unless it breaks. My current Debian installation is around 8 years old at this point (it's updated, of course), reinstalled to migrate it to amd64.

Other systems we install are configured on many levels, so even if the defaults are BTRFS w/zstd, it might be either known or changed to suit our needs better.


That's why i use Slackware - does not try to be smart.


Would it work though? The transistors are quite large compared to today's processor's transistors, and at that high frequency the routing delay for the signal to travel around transistors is quite significant. This seems more useful for a low-transistor-count high frequency device.


It’s more useful for the intended uses. OTOH, it’s always fun to misuse technology.

There would need to be multiple carefully positioned clock entries or a fully asynchronous design rather than just a copy of the NMOS layout, but it’d still be a lot of fun.


Touch controls. I hate that I cannot turn off my hob in dim light as I have to see which of five barely visible areas I am to touch.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: