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

The best is when those “silent updates” restart Teams while you are in the middle of using it.


A million times this. Things seemed more broken than usual in Teams for me today like image attachments not working and such. I just figured it was Teams being Teams until someone informed me there was a service outage degrading things. That’s how low the bar is.


ㅋㅋㅋ is literally “kkk” but it’s shorthand for 크크크 (keukeukeu). There’s also ㅎㅎㅎ (hhh) that shorthand for 하하하 (hahaha). It’s much faster to just mash out those single consonants, sort of like keyboard spam laughing.


ㅎㅎㅎ is definietly not for 하하하. It's more like 흐흐흐 or 히히히, just like hehe in English.


The microchips are basically little RFID widgets that are about the size of a grain of rice. The chip can migrate from between the shoulder blades to anywhere else, and the range is really poor - basically near-contact range.

I once tried a pet feeder that would read a cat’s microchip to determine if it would allow that cat to use it. It worked by having an arch with an RFID sensor that the cat would pass under and it would uncover the food for the matching cat. For one of my cats, it worked great because the chip was still between her shoulder blades in the usual spot. For my other cat it had migrated near her ribs and it didn’t work at all.


As soon as I saw the screenshots of it running in a terminal window, I was in love.


The TUI is built with the awesome Ratatui [0] library (formerly tui-rs [1]). UX is certainly not my area of expertise and I would not have been able to create Trippy without this library.

[0] https://github.com/ratatui-org/ratatui

[1] https://github.com/fdehau/tui-rs


The problem isn’t the lead itself, it’s the phenomenon of tin whiskering that can happen with some Pb-free solder alloys where metallic hair-like structures grow from the solder and cause arcs or short circuits.

This is one such example of a failure in space due to tin whiskers: https://en.wikipedia.org/wiki/Galaxy_IV


It also requires a little bit of specialised knowledge to manufacture things correctly.

(It's much better now - people know more and the solder is better, but 20 years ago this was a huge issue that sent many devices to landfill)


This was a fascinating read, not only for understanding about how Shazam works which is something I’ve long been curious about, but also a great primer on digital signal processing.


Second Reality was truly a technical marvel and arguably represented the pinnacle of the PC demo scene. It’s amazing how much influential it has been and how it continues to endure some 30 years later. Not too shabby for a group of teenagers from Finland.

(And now I feel extra old realizing the original Second Reality was released 30 years ago.)

Aside: I first watched Second Reality on my PC at the time which was a 386/40DX. I must have watched it 100 times at least. When I upgraded to a 486/66DX2 the first thing I did upon booting it up was to watch Second Reality. I was amazed at how much I had been missing before; everything ran smoother and elements that had been truncated before were now visible. Yet even when it was on my old hardware it was still completely presentable. It’s a credit to the Future Crew coders that it could run so well on such disparate hardware.

Another aside: the Second Reality source code was released on GitHub for its 20th anniversary: https://github.com/mtuomi/SecondReality

There was a great 5-part blog series to decipher it: https://fabiensanglard.net/second_reality/


I didn’t notice many things when upgrading from a 486 to a P5-90, but the upgrade an 8-bit Soundblaster clone to a Gravis Ultrasound was incredible.


I would guess that that 486 speeds were the terminal velocity for Second Reality’s performance. That was the high end when it originally came out.

Don’t get me started on the GUS. That was such an incredible sound card for its time.


Every so often I go on a “font bender” and start searching for my “next great coding font”. I’ve been using Hack (https://sourcefoundry.org/hack/) for several years, but after looking at this I might need to give it a try. It looks really nice and the price is right. The font in the OP looks great too, but I can’t bring myself to pay for it. Not when there’s so many great alternatives out there at no cost.


One class of alternatives you could also consider is narrow fonts like PragmataPro[1] (commercial) or Iosevka[2] (gratis, FOSS). Being able to fit more stuff onto the screen side-by-side is what enabled me to get as much into tmux as I have.

[1] https://www.fsd.it/shop/fonts/pragmatapro/

[2] https://typeof.net/Iosevka/


PragmataPro is so close to perfection for me! But it loses to MPlus Code because PragmataPro doesn't support font weights below 400 (yet?)

I still bought it, because it's gorgeous, thank you for sharing it. I've emailed the font creator so hopefully they've got plans for thinner versions.


regular fonts seem wide after several years of me using iosevka


Same. I love experimenting with my coding font and for the past year or so I was using Hack.

I wasn't able to find anything better yet after trying a lot of fonts: Fira, JetBrains Mono, Iosevka, Monaspace, Ubuntu Mono, and others.

Or perhaps I'm too familiar with Hack now and everything else now looks weird..


Hack's Bitstream Vera ancestry brings me back to installing Debian as a thirteen year old, a strong nostalgic pull.


I was the same until I started using Fira Code and don't think I'll ever go back to anything else. the ligatures are worth it

https://github.com/tonsky/FiraCode


Hack is very underrated and awesome. Fira Code is nice, so is Adobe Source Code Pro [0], and Iosevka [1]. Yet, Berkeley is truly at its own level.

[0]: https://github.com/adobe-fonts/source-code-pro

[1]: https://github.com/be5invis/Iosevka


Source Code Pro is damn near perfect for me, I've been using it for some years. Occasionally I get an itch to explore other fonts, but I always come back to this one, all its refined details just feel good to my eyes.


I must say it does look awesome.

Although I'm personally not a fan of ligatures, I feel they may increase mental burden at times;

for example having to look closely if it's = vs == or == vs === among other examples.


+100 I really dislike ligatures. They are one of those things that seem great in theory but I find them to be a real distraction. This is why I never got into the JetBrains fonts — there was no ligature-free option. (Maybe there is now, but I haven’t felt motivated to try it again.)


You don't have to use them, even if they're in the font, just turn them off in your reditor.

Conversely I can turn them on for code I didn't write.

There is no downside to ligatures.


I also dislike ligatures, but I have been using JetBrains Mono for over a year now with ligatures disabled. works great!


> Maybe there is now

You’re right! Check out the NL (no ligature) version: https://github.com/JetBrains/JetBrainsMono/tree/master/fonts...


I have a couple of home automation projects that use Raspberry Pi boards and rely on BLE. One thing I’ve found is the onboard Bluetooth is pretty awful on the Pi 3 and not very good on the Pi 4. Switching to use a Bluetooth dongle made a huge difference with stability and reliability. I no longer had to continually run scripts to try to reset kernel drivers or the entire Bluetooth stack when things got cranky (which seemed to happen many times a day). As a bonus I got a Class 1 adapter that would let me tweak the power output.


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

Search: