skysight-inc/HackerNews huggingface dataset:
A agree completely, but we're not really moving to a wireless world yet unless we choose to. The default in-the-box solution is still wired headphones.
Yeah, I mean it's not like they need to allow air to pass to the interior of the phone. All you need is a couple of exposed metal tabs, no different than the USB/lightning port.
Neither google nor microsoft have ARM CPU's yet, so there is as-yet no price competition.
I would definitely understand if we were at a stage where AirPods battery would last half a year but we are not.

Battery-less cable beats wireless 2 hours of talk time quiet easily.

Wireless is the correct path but it was too early to get rid of the working standard without having a better alternative in my opinon.
Join a club for people with common interests. Or find a new interest - I started CrossFit 2 years ago with no prior interest in fitness and to me the social aspect is as important as the fitness aspect, if not moreso.
He did weed out people he considered his enemies, but he did give people free education, a banking system that was more client friendly (in terms of loans etc) and I understand free utilities.

I was of the understanding that the invasion was to increase France's political clout in North Africa, to avoid Ghaddafi's plan of unifying Africa under a gold standard (Gold Dinar) and most importantly to sell oil under the aforementioned currency.
Still he should report
Not sure if available outside the Netherlands, however there's a version on the NPO 3 website with 16:9 aspect ratio:
https://www.npo3.nl/followme/22-11-2018/VPWON_1291086
What you are talking about is called "commit messages". Logging is used by an application that you are building to store information that is useful for helping find out what happened in error conditions.

As for your questions, I tell junior programmers to try to commit their code at least once every 20 minutes. That seems like a very short time! However, when you are first starting out, it is easy to take on pieces that are really large without realising it. This helps you keep the work small. It also helps you understand when you are in trouble. If you find that you can't commit something in 20 minutes or so, it's a good indication that you probably need some help.

When making your commit message, you should have a short message at the top explaining what you did. To understand what is good to write, imagine that you want to know, "How do I do X". Ideally you can search through the commit history for "X" and you will find a commit that does it. That's a good way to learn how to do things in the code. Now that you know what you want to look for, try to write a message that makes it easy for the "future you" to find it.

Finally, underneath the short commit message, try to write a brief description of why you made your change. If you think it is obvious, there is no reason to write anything. But I find that I write something about 2/3 of my commits. If you find that you can't think of something to say, maybe you are having difficulty understanding why you are doing it yourself! It's sometimes a good idea to ask someone "I know I have to do this, but I don't really understand why. Can you explain it to me?" Very soon, you will understand most things in the code.
IoT Devices, Cyber Security and Risks
You could argue he could have done a better job in communicating he and his reputation is no longer what is behind this project. But that it has moved to someone else.
> Maybe calling free software "Open Source" was a mistake.

This conflation is definitely a bad thing. Words with an actual meaning get over-used, simplified, stripped of their original meaning, and then merged. It would be 100% to the detriment of our language if it happens in this case.

Open source does not mean free (as in freedom or beer), free (as in beer) does not mean open source. Free as in freedom almost always means open source.

Side rant: Also, open source doesn't mean "open to contributions". Giving access to the source code does not mean obligation to accept contributions to said source.
Very interesting considering that it enables to make legacy applications work with S3 basically.

The price is quite high for small projects though: $0.30/hour > $216/m > $2592/y
Other disciplines do indeed pay reviewers - a friend's partner told me about being paid in the humanities. So it can work as a model.

Regarding the monopoly comment: firstly, you have (usually) a complete monopoly on the content you provide. The same paper is available from one publisher.

If we talk in more general terms, then we're in the classic situation where the monopolist (or oligopolist, which is often used synonymously nowadays) pretends they don't have a monopoly, because they don't want to be punished or reformed. But, even if we took your viewpoint, that strength of market power - 5 companies controlling 50% of the market - is overwhelming.

In practice, Elsevier and Springer control nearly all Computer Science publishing (for example), so the situation is extremely bad.
Domain Registrar is now CloudFlare for me. Sadly it isn't yet GA, https://www.cloudflare.com/products/registrar/
The Most Useful 50 Web Sites you wish you knew earlier
Interesting - which devices have you found to be good and bad, and how does the difference manifest?

I tend to notice drop offs for sampling bit rate, and can hear the difference with Bluetooth, but I've personally never connected to any device playing decent quality streams/downloads and noticed a difference. Not saying no-one can notice it, just find it interesting I've never done so!

FWIW I listen through some AKG 550s, which I can highly recommend.
I didn't say anything about what the money was spent on (in fact, I specifically said I'm not talking about NASA), I was addressing the fallacy that because the little pieces of paper are still on earth, that means that nothing of value could have been lost.
Apple devices are shipped with headphones, which plug into the device. Does that circumvent the accessibility issue?
That's the answer I was expecting. It seems strange to me to use the end of the High Medieval era and extrapolate that back across the whole.
Pain and Sense of Betrayal as Canada G.M. Factory Closes After a Century
But as far as what APIs you can expose to JS there is a limit. Can you expose WebGL2? Fullscreen? Screen Orientatio API? WebVR? WebAssembly? Input type=Color, OffscreenCanvas? or do you have to wait for Apple to add them to the base iOS WebKit? Can you fix the fact that iOS Safari shows very poor performance animating while streaming assets?
"Step down, join the party. You won't get another offer."
GitHub topics in JSON for programmatic usage
Domains:

* namecheap.com: It's cheap and easy to use. Has a lot of TLDs to choose from.

* freenom.com: Started using free domains, dropped most of them, kept a few as paid domains, which I don't regret.

Hosting:

* server.lu (now part of server.com): Luxembourg is a great location for hosting, especially with a 1Gbit port. I still have my old contract which I don't plan on terminating as long as them don't force me. Getting the full bandwidth throughout Europe. Not the cheapest plan, but one of the best dedicated servers I ever owned.
Will check it, thanks.
The world's first genetically edited babies
Show HN: React component data loading with same code on client and server render
The third member of your team may be any gender.
Biparental Inheritance of Mitochondrial DNA in Humans
> the res, _ := … error handling punt and wanted to confirm that lack of even a warning

Warnings don't exist in go build, because warnings are ignored by people. IIRC there are linters that do highlight those if you care for it and want hints about things to check.

There are legitimate use cases of swallowing error return values†, and if you throw warnings intros cases, then you can't tell the difference between a legit warning and a legit use case that shouldn't warn.

> none of the examples on the golang.org homepage handle error. You appear to have to go into the fourth section of the language tour to find error handling first being discussed 19 pages into the ”Methods and interfaces” section

Skimming over the fact that this is a "Tour of Go", not a full-blown tutorial, there is not a single call that would return an error before the page you mentioned. There are ok return values for map fetches and type assertions before that though, but they're just printed out, and the same pattern continues afterwards. Those are focused code snippets to show features and get the vibe of things. I certainly wouldn't expect from a tour (for any language) to be the equivalent of The Go Programming Language book, nor Effective Go[0].

[0]: https://golang.org/doc/effective_go.html#errors

† It happens that by design you may have the guarantee that e.g ParseInt will work because you're under full control of the input type and/or value.
Arsole

Cummintonite

Rhamnetin

And that's before getting into biological molecules, which sometimes have names like Sonic Hedgehog or Pikachuin.
> Wireless things suck

As a counterpoint, I think wires suck. They get in the way, they get tangled, I have to transport them, they break all too often, I trip over them, they knock things over when I move with them, they blow around in the wind, they present a fire risk and a safety risk, they have some kind of physical connection which keeps changing.

Downsides of wireless: remembering to charge, and configuration (a bit annoying if you have multiple devices).
If we're doing anecdata, my mother (70) got my old iPhone and coped perfectly happily with switching to Bluetooth headphones; indeed, she managed all the pairing, etc., herself.
No I'm writing completely from my own experience running stable releases of Linux distros such as Debian and CentOS.

Very rarely I've had to install Fedora on some intranet to get a specific feature but I can count the times on one hand.
"20-50 of my friends" on every club night?
The Best Documentation Tools for the Digital Age
Elderly? I can guarantee that no human being on earth can confidently setup bluetooth on all devices. And that's the issue, these one-off pairings.

I had a friend sync with my car bluetooth-stereo, it took a while and from the steering wheel I couldn't be of enough help. But it worked in the end, was quite frustrating though.

Then later when I tried to use my phone again it had been lost from the receiver (eventhough it can support two concurrent connections and I've only ever paired with two devices). So now I had to go through the whole dance that it was only paired in one device.

Thing is, anything that literally takes more than 3 seconds is a disaster. After a minute of fiddling with it I remembered I had an AUX cable. And then I could patiently fix it when I had time for it.

Bluetooth is a nightmare for temporary connections. Removing the headphone-jack is akin to removing a fire-alarm system because "it isn't used anyway". Well, the times you need it it is indispensable and it doesn't cost anything.
Huh? I am an iOS developer and I’m certainly not aware of any technical restrictions here.

The YouTube app overlays all kinds of things over full screen video. Link boxes while ads play, for example.

This was more about suitability for the screen format - multiple boxes with small text just didn’t work too well on mobile.
One of the world’s most visited websites that nobody is aware of (2017)
I've experienced a similar problem. I wear my headphones for about 1.5 - 2 hours per day while walking and I've found that I have to purchase a new adapter about every 45 days. I'm surprised that for the approximately $10 they charge for the adapter that they can't come up with a more durable design.
Until we include the cost on the environment within the cost of our goods things will not change. When we do we will encourage a wave of environmentally friendly innovation. It will take a lot of courage for any government to do this.
I agree with you "best books" can be good questions. They could also maybe lead to farming points so you want your book or library to appear at the top of the list you hire the mechanical turk to upvote your project to the top? I can certainly see "best of ABC" turning into a shouting match if people passionately disagree why one sucks and the other doesn't so I can accept the idea that "best books on X" are often more problematic then they seem at first glance. "best stack to clone FB functionality". "best game engine". etc... both seem like they'd turn to crap. In fact you can already see this on stackshare.io where for most products it's basically a popularity contest not a merit contest. "best text editor"
Employee Core Values Rating
Fwiw, some distros have stuck with different init systems: Void uses runit, Devuan (Debian fork) uses sysvinit, Gentoo uses OpenRC[1]. There are probably more that I am not aware of.

Systemd has not given me any trouble, yet, but I run Void in a VM, and it boots extremely fast.

[1] I believe one can also use different init systems on Gentoo, after all it is Gentoo, but I have not touched it in years, so I do not know for sure.
LG is keeping the minijack too for now, unlike Samsung, whose rumours indicate that are dropping it next year.
Drag and Drop ajax file upload using DropzoneJS and PHP
I don’t think it is a moat, just stating the simple case.

I’ve spent a lot of time making cross-compile work for complicated builds. It can be tedious and frustrating fighting compilers and build systems to get it right.

Sometimes it is necessary because the target didn’t have a complete native toolchain, but other times because the target was just so incredibly slow for large builds.

I haven’t built anything with them, but these Arm servers appear to be neither of those two cases.
What I would really love to know is that how they get those results with their newest set of algorithm. They seem to beat every compression algorithm including zstd and lz4 in both compression and speed. And how we can all benefit from those improvements.
How is this news? Most people in China who is a somebody is a party member.
5 Must Have Skills for a Project Manager
Anecdata: I have 19 Bluetooth devices on my iPhone (gamepads, speakers, headphones + dongles, watches, etc.) - of which, I'd say, only one gives me trouble[1] and none really were problematic for pairing.

[1] Cricut Air but then it also has trouble talking Bluetooth reliably to my Windows 10 desktop; I'm not blaming this on iOS just yet.
I use AirPods. I even like them. ... but you do realize that the case isn't a magical source of energy, right? You have to charge that thing... and the airpods themselves last a remarkably long time, but they don't last that long, so I find myself having to do this awkward dance in the middle of meetings where I take one out and charge it while relying on the other one, and then I swap to charge that one... I have lightning earpods, but then I can't charge my phone at the same time, so at some point my phone starts running out of battery and I'd have to switch to the airpods anyway (lol). I have tried buying multiple brands of lightning splitters, and they all suck and often the phone isn't quite able to charge even though it says it is charging.

I honestly don't care if I have a "headphone jack": I totally agree with Apple that it was a shitty jack. It was a fragile hole that made it impossible to waterproof the damned phone. How about they just give me two lightning ports? Or a lightning port and a USB-C port, to make my dreams finally come true of only having to carry around one (USB-C) cable while still getting to be compatible with all of the stuff Apple already sold for these devices?
This was also considered before the bombs were dropped, and has been documented. Wikipedia has some information on it [1], with the short version being that it wasn't possible to stage a credible demonstration without making an actual attack.

[1] - https://en.wikipedia.org/wiki/Atomic_bombings_of_Hiroshima_a...
How many members of the party are there just to boost their careers, and how many for any other reason?
I'd take the term "friends" loosely. A club promotor likely has a ton of people they know and could call on.
> we can consolidate all the important knowledge and pre-packaged work

Noble intent, but time for that is not yet. The state of cloud infrastructure practices today is a primordial soup of ideas, marketing and the myriad of tools trying to survive on the market, like Terraform vs Ansible vs Cloudformation :)

Good infrastructure is hard, there is global networking with CDNs, DNS, CI/CD, Git integration, HA, monitoring, security, you name it. Thats why you will not find the code on Github, only blog posts on Medium, code brings bread and butter to so many people, including me :), why sharing it ?

And most important. To create really reusable by many infra code is even harder. You need to feel what features should be there for everyone, and what is bloat. It'll take many times the effort of writing non-reusable architecture for one company.

> .. And again they frown

Made me smile :)
> I still want to be able to charge my phone and listen to music using the headphone jack

I guess they want you to buy the wireless charging dock?
"just need", you are right, but then wait for the answer.
It took me five days to receive the link for the download.
WhatsApp's chief business officer Neeraj Arora is leaving the company
Why not scorpions?

https://www.dawn.com/news/1252264
It's the most well known. It's not like the English longbow or archery was a recent innovation by the time of the Hundred Years Wars. by that point there had been centuries of extensive use. The Burhs defending against Viking raids in the time of Alfred needed arrowheads too, as did the Vikings themselves.
If someone's determined, they can always create a legit looking GitHub account, submit a few PRs (they did, in this case), gain trust, and _then_ deliver the malicious code. It just takes time.

But this trust part seems to work pretty well. You need to be trusted to be a Debian package manager, and I volunteer as a Drupal code review admin where we require all contributors to have a real name, and there is a back and forth discussion for a few days until we mark the user as vetted.
What kind of argument is that when machine learning is extensively used to prosecute DMC and copyright violations? Why not detect video similarity as well and determine a cutoff under which a newly uploaded video is "too altered" and cannot be used to replace an existing video?
This problem can be solvable by introducing “Verified Identity” on GitHub. Anyone who wants to be maintainer of popular project can be asked to get Verified Identity. If this person turned out to be malicious, he risks getting tracked down by law enforcement fairly easily. For getting Verified Identity, simplest thing might be validation of phone number. Bit more complex thing might be Verified bank account or credit card. Assuming GitHub has 1M active users and each user verification costs $5, the cost of solving this problem is less than 0.1% of GitHub valuation but can hugely improve trust levels.
I think the problem, in the specific audio area, is the technology itself rather than accessibility.

The Bluetooth standard is trash; no stack/device [combination] just works as it's supposed to do.

If BT worked, I think accessibility would pose no problem; ultimately, the intended workflow is: 1. turn on BT on the host device (if required); 2. turn on the client device; 3. listen to music.

As the BT committees and implementers keep pushing features rather than taking care of the stability, for a stable BT to ever happen, it would require all of them to be exiled and replaced by a new generation; I don't think this will ever happen.
I'm talking about the 7th of april to 16th of april, between the moment an attack happened and France/US/UK decided to attack because they had proof Assad was the author of this precise attack. If you could point me to one of these reports, I'd be grateful.
They might, but why should they have to? That tiny ESS DAC in LG phones is measurably better than a lot of external "audiophile-grade" DACs. It doesn't compromise the design or the water resistance of the phone either and probably doesn't add much cost relative to other components.

This is basically an arrogant move that can't really be technically justified.
E.g. By arguing that better external options exist - better external cameras also exist, should we get rid of the camera too?
Then you better stick to that classical sales model that seems to be on the way out. The minute you sell the full package of an unfinished products, people will feel entitled to what they expect it to be (rightfully, imo). So you'd should avoid Pre-Purchase, Season Pass and some degree Early Access. I'm torn about the latter, since it is supposed to be sold "as is" with no expectations, but don't think this is was most actually do.

Also how do you think about post launch updates to fix bugs? Those seem to be generally expected as well, now.
You can cut off the jack and solder a new one. You also don't need specific cord, buy a new cord and add the jack. For non replaceable cords you can open up the headphones unsolder the old cord and solder a new one. Or you can cut the cable somewhere high and patch another cable.

If you can't do these things your self there is probably some cheap electronic repair shop nearby. Most likely cheaper than shipping new brand cable or replacement parts.

On side note plastic in one of my shure 840 joints broke and I managed to fix it by modeling and 3d printing it. They're working fine now. The only official way to fix that was to buy original head assembly and ship it, but that's almost as expensive as getting a new pair.

Repair is possible, just sometimes you need to be a bit creative.
Product configuration can be very efficiently modelled as a CSP. You should use MiniZinc instead
Exactly this.

These are "friends" in the sense that we both mutually want something from eachother, they want free drinks and VIP access, I want them to do free shit for me.

edit: remember this is pre social networking.
The dongle no longer comes with the phone.
>I think we can consolidate all the important knowledge and pre-packaged work, [...]. I think we can make it so nobody ever has to go through the painful process of learning by trial and error ever again.

Just an fyi... that goal is only possible for ideas that have stabilized and broad consensus has converged into widely accepted best practices. Yesterday's "hacks" that are insanely complex get vetted (or modified and replaced) and eventually get folded into the baseline of Normal Things Everybody Knows. But... the world isn't standing still and it evolves in complexity. Therefore, there's always new complexity that requires new hacks that everybody reinvents.

At a high level, the cycle looks like:

chaos --> create order --> new chaos again

We see a chaos of hacks and complexity. We then notice recurring patterns in the disparate hacks and extract some unifying principle that can "simplify" the complexity. If we stop here, it seems we've tamed disorder and everything should be able to be documented and people can stop wasting time repeating everyone else's past mistakes. But all we've really done is raise the baseline of systems sophistication. There's always a new delta of chaos and complexity.

E.g. In the 1980s, sysadmins might implement a rudimentary sync of userids with a shell script and copying "/etc/passwd" files around. But we notice that's chaotic and stupid and doesn't scale. So we rationalize the system with a more unified technology such as a LDAP identity server. But utopia is still not achieved because while LDAP might be ok for employees' sign-on accounts, it's not suitable for millions of customer accounts of a B2C web business. The complexity treadmill is neverending!

>GruntWork, I love what you're doing, but I'm also hoping to make your business obsolete.

If companies like GruntWork and AWS are properly doing their job, they will never be obsolete because the changing world keeps throwing new demands at us and this constant delta of new chaos is always there that needs to be "solved".