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

Some time ago I also thought that no 3.5mm jack is a deal-breaker, but I bought super cheap jack-usbc adapter that is 5cm long and it works pretty well.


I haven't tried a USB-C to 3.55mm adapter but your experience heartens me.

Headphone jack has been a hard line for me. Having recently moved into the world of wireless charging (I keep a phone 5-7 years and just missed wireless charging being normalized on my last phone purchase back in 2020) I think using the USB port for headphone is finally visible.

I spend a lot of the day with my headphones on and the phone on the wireless charging puck. Not being forced to choose between charging and headphones changes the equation.


Correct me if I'm wrong but those cables must include a DAC to function properly and so usually have a tiny kinda crappy one in them, right?

In this post headphone jack world I use a fiio Bluetooth/USB DAC that's really good quality. But it's about the size of two ipod nanos stacked on top of each other.


> Correct me if I'm wrong but those cables must include a DAC to function properly and so usually have a tiny kinda crappy one in them, right?

Not necessarily. If the device is using audio over alt-mode, it can use its own DAC.


>those cables must include a DAC to function properly and so usually have a tiny kinda crappy one in them, right?

FWIW, audiophiles were very impressed with the measured performance of the €10 Apple USB-C to 3.5mm adapter and its DAC. The Google one is likely good too.


I think there are better ways to spend $200k than fight with deranged patent/trademark system.


I think the commenter meant that once the new syntax is approved and adopted by the community, you have no choice to not use the syntax. You'll eventually change your project and will be forced to deal with reviewing this code.


_You_ might not use it, but somebody's going to send a PR, or some LLM is going to spit it out, or some previous maintainer put it in there, or will be in some tutorial, or it will be in some API documentation.

You are going to have to deal with it as a mess at some point. One of the downfalls of perl was the myriad of ways of doing any particular thing. We would laugh that perl was a write only language - nobody knew all the little syntax tricks.


I came here to post exactly this! Maybe I have very limited imagination, but I cannot fathom how tiny propeller without internal power source could be any use for the search and rescue operations.


Probably you can also add Dragit[1], which is a desktop p2p file sharing tool for local network with automatic host discovery. Currently supporting Linux and Windows. (author & maintainer here) I'm not sure if I should keep on working on the tool, considering the length of the list so far. :D

[1]: https://github.com/sireliah/dragit


There's a cross-platform open-source version of this program: https://github.com/qarmin/czkawka


I don't think czkawa supports deduplication via reflink so it's not exactly the same thing. fclones as linked by another user is more similar: https://news.ycombinator.com/item?id=43173713


That’s not remotely comparable.


This sounds like a labour law horror story. I'm so happy now that I stayed on ordinary 40h/week work contract (no overtime) in the beginning of my career. Otherwise I'd end up with burnout and/or health issues pretty soon.


> If you use ctx.Value in my (non-existent) company, you’re fired

What a nice attitude.


It's one of my major pain points with Go. When can we have proper enum support with compile-time checks whether all the enum values are exhausted?


In about 10 years, maybe :)


Touché!


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: