oxplot
PoisonTap (2016)
MagSpoof
It would be great if the no fly zones could be uploaded to the drone itself so it would simply refuse to take off in those areas for instance.
Show HN: Modular and affordable split-flap display for everyone
Show HN: Rsv2: Real-Time task scheduler and tracker for time sensitive projects
A Little Something Nothing
WireGuard VPN on Android
Show HN: Jayoh SSH Jump Server
An Incident Post-Mortem
Ask HN: Crowdsource hypothesis verification
Like a lot of folks out there, I often have more ideas, hypothesis and theories about things than I have time to investigate in order to verify or invalidate them. Even for some that I do have time for, it proves to be quite time consuming to make a start, usually because I'm not familiar with terminology and/or concepts to lead me on a path.Do the HNers use any forum, site, service, paid or...
One's taste however can change: food with high sugar leads to heart disease and diabetes, so I better stop eating that favorite dish of mine. You keep doing that for a while and taste of sugar (or salt, or fat) becomes disgusting.
Statements like "Go is crap, it has no generics" originate from one's taste in programming languages so there is no arguing with that. However, talks about what generics (or exceptions etc.) does to the health of the programs you write that span time and other contributors, are no longer subjective matter, but an argument worth having. This is, where I think, Go's strength comes in: its careful development process that puts programs' and programmers' health at the top of the priority list.
Health is not the same as comfort. Taste of a dish you've had for years is comforting. You're not going to feel comfortable when the ingredients you've come to expect are taken away. But if you can get past that, you may end up living longer and healthier. Similarly, your programs may become more maintainable and long lasting.
No one, who is familiar with the philosophy and motivation behind Go, can claim that what I've said above is false. You can say that Go team is slow in progress, but that's what methodical and evidence based approach is like: slow. You need time to experiment, learn and evolve. You other favorite languages act like the general public who at hearing in the news that "coffee is good for you", starts drinking 10 cups a day. Go's approach is more along the scientific way.
Show HN: Svglinkify – add hyperlinks to inkscape PDF exports
Show HN: Pdftilecut – cut PDF pages into tiles
Sounds like your list is a desperate one too.
Good old shortsightedness at play here. No one looks past this year or years to come when faced with changes. Here's what I think, based on history, is happening here:
# Wires are more bad than good for average consumer:
a. Neglected security based on assumption that since it's not wireless, it's immune to eavesdropping (think side-channel attacks). Wireless puts security upfront and center.
b. Cables get lost, break, are not long enough, are not compatible, damage the connectors, bad cables damage the device, cost extra, etc. Wireless doesn't.
c. Cables are cumbersome. They get tangled, you need to remember to carry them, have backups, etc.
d. Cables have short range.
Apple evidently cares quite a bit about user experience. Wires hurt user experience so they want to get rid of them, one by one. You can't push towards superfast, low power and generally more advanced mobile devices and accessories, if the industry has no reason to do so (because everything works and has for the past 50 years).
It's tiring reading every day how someone is upset because their favorite feature is gone because they can't see past their front door.