skysight-inc/HackerNews huggingface dataset:
Nope, you're not entitled to anything. A license is just a license. You're free to use the code. If the releaser gives you no communication about expectations, then it's your choice to use it or not. They're obligated to give you anything, not even the time of day. Enjoy your free code, or don't.
Jesus christ, and where do you think choices come from?
I still use the FM tuner built into Snapdragon phones.

I guess everyone else streams their radio these days.
I'm stuck in the two pair camp as well and I cannot for the life of me understand why Apple makes a 3.5mm to lightning adapter but won't make a lightning to 3.5mm adapter. I have a great pair of headphones that use the lightning cable but I travel a lot and my MacBook along with every airplane uses 3.5mm so I can only use them with my phone. It's maddening.
One of the big reasons given was to make a slimmer phone, but I've got the iPhone SE I use personally here next to the iPhone 7 I use for work, and, if you were to run your hand over them, you wouldn't detect a difference in height off the table.
> BTW, while Gimp is not a photoshop replacement (please fix the window behaviour, guys)

If you mean the multi-window behaviour, as of 2.10 the default is now set to single-window.

If you don't have 2.10 in your distro yet, you can toggle that on in the menubar: Windows -> Single-Window Mode
I don't mean to imply that other products are inferior. A problem can simultaneously exist and have solutions.
Because the JVM takes another tradeoff against Go and Rust: it has a runtime interpreter+JIT, which causes even more performance overhead than Go's GC let alone Rust which - at runtime - is effectively a zero-cost abstraction over C and jemalloc.
> but I don't know why any of the Android manufacturers would follow suit.

The obvious reason is a decrease in BOM which corresponds directly with an increase (however so slightly per unit) in margin. Apple made it "ok" to whack this functionality, so why wouldn't every manufacturer join in?
Android Apps with More Than 2B Total Downloads Are Committing Ad Fraud
I will never understand what motivates some people to downvote rather than reply (unless you tell me...)
Equally annoying is if two people are both previously paired with the car (or speaker!) and it’s connects but not to the one you want.
They could use some of this vaunted machine learning to figure it out.
Apple has had great success in the past by pushing new standards in computer peripherals, deprecating old standards, and generally moving the industry forward by fiat.

I think we've all benefitted somewhat from this attitude, even if it was inconvenient.

The distinction here is that the 3.5mm standard isn't/wasn't a computer peripheral standard. It is/was an audio industry standard. There are many uses for 3.5mm that have nothing to do with phones/tablets/laptops/desktops.

Additionally, the audio industry has a different obsolescence timeline than computer equipment. Audiophile and pro audio headphones (for example) represent a significant investment and are intended to last many years.

In my view, Apple's approach to this was a kind of chauvinistic hubris. No, I don't want to use a $15 adapter of dubious quality on my $1500 custom molded in-ear monitors. No, I can't just get a new pair. No, I can't re-sell them, they only fit my ears. No, they wouldn't sound the same even if a bluetooth version were to become available. No, I doubt the 4 person company that makes them is eager to try to figure out how to make a lightning version, even if they have the in-house expertise.

The decision really shows a lack of understanding of the world outside of computer manufacturing, and it is too bad others followed suit.
I think I can count the number of times that I've managed to get bluetooth to actually work on the fingers of one hand. It's just trash. Give me a wired connection every day of the week, and it better be something universal like USB-A, micro-usb, HDMI or 3.5mm.
I would miss the headphone jack if I ever bother upgrading my iPhone. As it is, I use my Bluetooth headphones a lot at home. Noise canceling and no cord is pretty nice.

But for very good audio I use my normal sennheisers
Just bought an iPhone 6S four days ago because of this and the physical home button. $140 brand new.
How Quincy, Florida Became a Town of Secret Coca-Cola Millionaires
He was recommended to us by an employee. He was capable and looking for a challenge so I delegated some core framework changes to him. Soon he was making changes that he was recommending himself and I began referring to his decisions and simply taking the time to understand his changes so that I could still hold the entire picture in my head.

The reason he was the best hire is because he is a force multiplier. I felt way more productive once he took on the work that I had not be able to entrust to anyone else.
As I mentioned in another comment, those were computer standards. 3.5mm is an audio standard. It's an important difference.
I just use the adapter and keep a couple in reserve for when I lose one.

Works great.
It's about cashflow. Capex is a major investment, and harder to account for by deducting over time.

Opex is much more reactive, both in accounting and in scaling costs of goods with actual sales.
I miss my ethernet port.
I think the comment still stands though, if you can't master the new tools including for reasons like the company not giving you time to learn them then maybe you (the company) should stick to the old tools.

Doesn't apply if the new tools are forced by management, but often it's the developers driving new tech.
I was responding to this:

> And no human’s life is measurably better since Apple had the “courage” to remove the 3.5 mm jack.
It's no wonder Apple's profits are so high.
That's a marketing problem. :)

"Each one will be a unique and priceless number using the largest of prime numbers. Each number comes with a genuine certificate of authenticity hand signed with the author's private key..."
You don't even need a "buddy". Because, if you know what you're doing, you can be the buddy. Or thousands of them. Whatever it takes.
It usually happens when tests are not fixed.
The adapter works great with the Shure SE846 IEMs. I’d rather use the speakers than die on the no adapter hill.
Very cool tool! A couple of comments/suggestions:

It doesn't handle very large or small floating-point numbers. I'm not sure where the cutoff is, but it's around 1e40 and 1e-46. It would be cool to be able to explore the whole range of 64-bit floats, including subnormals like 5.0e-324.

It would be interesting to leave the input as-is and show two related decimal representations:

1. The precise decimal representation (what is printed now).
2. The shortest decimal representation as determined by algorithms like Grisu [1] and Ryu [2].

It would also be cool to allow jumping to the next/previous representable floating-point number. Showing eps(x) would also be handy—i.e. the difference between the current value and the next closest representable floating-point value.

[1] https://www.cs.tufts.edu/~nr/cs257/archive/florian-loitsch/p...

[2] https://dl.acm.org/citation.cfm?id=3192369
I still miss the ethernet port whenever I'm staying in a hotel with dodgy wifi (many of which have ethernet).

I still miss having a dvd drive every couple of weeks, when I want to watch a video that isn't on a streaming service.

I still miss the serial port when I'm fiddling with bits of hardware (and my old graphing calculator).

Parallel port we're well shot of though.
I assume high pay. Personal financial troubles don't really put you in a negative negotiation position with an abundance of job options.
That sounds like a legitimate reason - they advertise water-resitance and waterproofing for the models lacking a headphone jack.

But.. can't they just make a waterproof headphone jack??
You can use "online" maps and it only downloads the visible region on your screen. It's not a few hundred megs "just to show you where you are" that is utter nonsense.

How about you just actually use the app before you make baseless accusations.
WhatsApp’s chief business officer is leaving
Native speaker of American English here—I've always just called them "strings", but Wikipedia says they're "phloem bundles".

https://en.wikipedia.org/wiki/Phloem
First photo of Mars from NASA's InSight Lander has been revealed
Then how come an offline region of a national park in Google Maps is a larger download than the entire state in OsmAnd?
My understanding is that the headphone jack actually occupies a lot of space. If you have opened up a phone before, it is evident that all internal space is _very_ well accounted for, so removing a headphone jack is actually a very tangible increase in usable internal space. And it's not just the jack, you need to include a DAC in the device, too!

This means being able to include more/new co-processors, different/better microphone technology, etc, not just thinner.

Only what I've heard from other hardware engineers though, I do not work directly in the space. "Sell headphones," could absolutely be a goal.
UNIX `cat`, unchanged from V2 through V6 until it was rewritten in V7, was 44 instructions.
Deutschland 83 is a fantastic show based on these events.
> And no human’s life is measurably better since Apple had the “courage” to remove the 3.5 mm jack. But a lot of our lives are just a little worse.

Eh, you could have said the same thing when they removed serial ports, 3.5" floppy drives, CD drives, etc. etc. etc.

Yes, the world is moving forward. Yes, it's a little inconvenient.
> The result was high plasma densities of up to 2 x 1020 particles per cubic meter – values that are sufficient for a future power station. At the same time, the ions and electrons of the hydrogen plasma reached an impressive temperature of 20 million degrees Celsius.

> Since the fusion fire only ignites at temperatures of over 100 million degrees, the fuel [...]

Would it be accurate to say that this gets us 20% of the way there, or is that overly simplistic?
The Bitcoin network at risk
> use one of the nicer frameworks (like Laravel)

Yikes
That's what he meant by "false dichotomy" -- airbuds and bluetooth headphones can still exist even if phones still have audio jacks.
The thing is we shouldn't have to do this. The beauty of the 3.5 was the fact that you could've gone to pretty much any remote corner of the earth and you probably could've access to one if you lost yours.
Hahaha. That reads straight or as sarcasm. Well done! I’m sure there are a million reasons that the 3.5 plug was holding back the iPhone, but I have yet to see even 1/1,000,000th of them in the iPhone.
I think this is great!
Word of the year is 'Misinformation', looks like a swipe at Donald Trump
If it's generating cash-flow of any sort - yes. But I don't do that beforehand. Too many unfinished projects. I have once and I feel like I just wasted money. Won't do it again unless I'll have reasons to believe I might get in legal trouble. For most side-projects that seems pretty unlikely.
Only the best numbers... I hear you, one must back their best issued numbers with actual software to ensure their value ;) BSV has handcash, honestly that seemed like a great wallet until I realized it wasn't supported by any of my held coins!
False. Samsung devices have had good water resistance ratings while still retaining headphone ports. (In fact some of the older models even managed to do so with removable batteries.)
I agree completely. Digital video had advantages. Despite those, analog still makes some sense, if nothing but fewer resources being needed.

Outside some niche uses, digital video really does make general sense. I hear and often agree with analog arguments. I keep analog gear, and in my own hardware projects will stay analog, perhaps also having digital, depending.

But, overall? People largely benefit more from digital video, and with the loss of the CRT, adoption makes sense. Digital only gear makes sense. I have no concerns and can easily use an analog adapter in a pinch.

With audio, it is inverted! A few niche uses benefit, most do not. They are equal or very modest gain at best.

Video gear seems to age out more quickly too. Increases in resolution drive all that, and analog limits do too. Above HDTV 1920x1080, analog has real issues.

Analog audio does not have those dynamics. There is no analog cliff to drive digital gear. Great stuff from the 70's remains entirely relevant. It always will. Ears are just not like eyes.

I will never, ever buy something that only delivers audio digitally.
Doesn't seem to be an issue with Samsung phones.
I would miss a built in ethernet port. (My Thinkpad X230 FTW)

Anyways, your examples are not exactly the same as this situation. In the cases of removing the floppy drive and CD/DVD drives, it was upgrading one technology for another which was able to hold more data, was a more stable medium than the predecessor, and was generally more reliable. The 3.5mm->bluetooth was not an upgrade in stability or reliability, and the ethernet->wifi change was not an upgrade in anything except 'mobility' (but systems with ethernet jacks at that time typically had wifi too, so, again, it was a general downgrade in functionality).
But what about the 
children
 manufacturers!
Samsung does water resistant phone with their flagship S9. And they still have the 3.5.
Of the metrics listed, the only one I will say never to use is lines of code. As a very wise manager told me, "Code is a liability. Functionality and business value are assets." Measuring developer productivity by looking at how many lines of code they've written is like measuring the health of a business by how much money it's spending.

If you can delete code and retain the same level of functionality (for example, because you found a library that will automate much of the task), then that's a huge win. Every piece of code that the team writes is one more thing that has to be unit tested, integration tested, documented, and maintained in the face of future changes. If they can offload that work to a library, or find a way to accomplish the same task by using existing code or by reconfiguring the application, that's almost always preferable to writing new code to accomplish a particular business need.

Of course, one can go too far in the other direction. It's easy to fetishize using external libraries for everything (like we see so often in the JS ecosystem). But that's where I would argue that the analogy of treating code like money shines. Sometimes it is worth spending money to have something custom made for your business, rather than buying an off-the-shelf component. Similarly, sometimes it is worth writing code to do something custom, rather than integrating a third party library, or reconfiguring an existing application. But that choice should be consciously made. Rewarding developers for lines of code written moves that choice out of the realm of conscious decision-making and into the realm of reflex. They get paid for more lines of code, so they're always going to reach for the solution that results in more lines of code, regardless of whether that code is necessary or appropriate.
While “we” are in the 10% I try to think about the changes in the frame of the “90/10 rule” (also how I consider the impact of features in my applications). Anecdotally, dropping the headphone jack (and similarly adding the Touch Bar) has negatively impacted 0% of non-developers I’ve talked to about both.

If I were a company, I doubt I’d change course immediately unless the larger data set said something significantly in the other direction. As developers are still, even with our more frequent “upgrade” cycle, not the largest piece of the pie.
Apple and Google seem to have approached removing the headphone jack, not as a way to reduce costs to the customer by eliminating an obsolete feature they don't use but, instead, as a way to increase the money they can squeeze out of customers by forcing them to replace perfectly good headphones they are currently using with new headphones hopefully made by Apple or Google.

I'm honestly not surprised by this. Headphone technology hasn't really changed for many decades. A good pair of cans made a very long time ago are probably still a good pair of cans. I have some Audio Technica woodies that I absolutely love and are still going strong after more than a decade. To Apple and Google, this is a state of affairs that cannot be allowed to stand! Where's the planned obsolescence and constant product turnover? Apple tried to make their earbuds a disposable commodity that need to be replaced frequently, but people caught onto the fact that it was just due to bad build quality and kept buying stuff from other companies. So, change up the connectors and force wireless standards that are, quite frankly, not that good for audio and ripe for eventual upgrade (i.e. bluetooth) into headphones so people won't be able to use the same pair for decades. Profit!

So what should consumers do if they like their current headphones or just don't want to deal with adapters, charging bluetooth devices, or sorting out multiple incompatible connectors? Buy phones that still have headphone jacks, like the Samsung S9.
You just described a bar.
https://outline.com/ZCPPvZ
I suggest a different narrative. That node.js achieved the decades-old aspiration of fine-grain software reuse... and has some technical debt around building the social and technical infrastructure to support that.

Fine-grain sharing gracefully at scale, is a hard technical and social challenge. A harder challenge than CPAN faced, and addressed so imperfectly. But whereas the Perl community was forced to struggle over years to build it's own infrastructure - purpose-built infrastructure - node.js was able to take a different path. A story goes, that node.js almost didn't get an npm, but for someone's suggestion "don't be python" (which struggled for years). It built a minimum-viable database, and leaned heavily on github. The community didn't develop the same focus on, and control over, its own communal infrastructure tooling. And now faces the completely unsurprising costs of that tradeoff. Arguably behind time, due to community structure and governance challenges.

Let's imagine you were creating a powerful new language. Having paragraph- and line-granularity community sharing could well be a worthwhile goal. Features like multiple dispatch and dependent types and DSLs and collaborative compilation... could permit far finer-grain sharing than even the node.js ecosystem manages. But you would never think npm plus github sufficient infrastructure to support it. Except perhaps in some early community-bootstrap phase.
It's not even remembering whatever non-standard terminology Linus came up with (although when I am feeling particularly curmudgeony I don't even want to know what push is, and why doing a commit isn't enough). It's a) having to deal with it in the first place, because the management decided to cargo-cult it, even though we are not developing anything resembling Linux kernel (there were no issues using TFS before, they just decided that they want to give Microsoft even more money and got a commercial Github account), and b) that I even have to drop to the CLI in the first place for operations that in any other VCS I could do with a couple clicks right in VS GUI. With TFS I had to use command line maybe once a year, and usually for something not strictly necessary. With SVN it was maybe every c9ouple of weeks to fix up the repository it messed up, With Git it is way too often.

Whatever technical advantages of Git are (and technically it is good), I think it fails as a tool to let me do my job easier.
I think you are onto something here. DRM is probably a driver here. if you have an analog signal, you can "pirate"...
AirPods require neither of these things. The case is always charging them. You want to use your beyerdynamics? Fine. Your phone came with an adapter for them.
Well in any case iPhones got bigger and thicker in the last cycle so they must have neededa lot of extra room.
Go back and read code you wrote 1, 2, even 5 years ago. If it's still clear and logical, and you don't think "who's the clown that wrote this?" then you're good. If you can hand it to someone else and they don't think "who's the clown that wrote this?" then you're very good.
Large CI, but a convincingly high odds-ratio that 'high deadspace' syringes increase transmission:
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2654245/

Lab testing shows less transmission with less deadspace (up to a point: thick gauge needles were all detectable):
https://www.liebertpub.com/doi/abs/10.1089/aid.2016.0023

This sounds quite substantial (33% vs. 1.4%), but there's room for confounders:
http://www.injectingadvice.com/v4/index.php/articles/equipme...

Overall it seems quite effective.
EC2 Instances Powered by Arm-Based AWS Graviton Processors
I've been in startups since the late 90's. Not once have I seen a startup fail due to technical issues. Several of these made it to the double digit million raised, 100's of employee phase.
Failure was always related to the wrong product being built or a bad business model (poor product/market fit, pricing is screwed up, some sales, but not enough to cover cost, no plan for marketing, etc.)

Poor code quality is rarely perceivable by customers, except in the most extreme cases.
Dominic is a prolific contributor and compassionate leader in the JS and P2P communities - and it was a disheartening thread to read. The suggestions that he (working for free!) should have done more seemed unfair.

We should look to fix these:

- If we're going to rely on hundreds of packages per project, we need fine grained security like Android or iOS. deno seems to be doing node right - https://github.com/denoland/deno/issues/171

- Lock down versions for now. Use 1.2.1 instead of ~1.2.1 or ^1.2.1.

- If npm must remain at the center of node's module system, they might have to add auditing and approval tools. 'npm install' can warn about unaudited modules. The problem with that is that it will make npm (a business) even more central to the node ecosystem - which may not be a good thing.
And make sure you are present when everything is sent to the copier. If the boss tells you that he/she needs you to sign two copies, don't do it. The copy you receive could be a totally different document than what you signed for the company. If the boss insists on making a copy at home, don't sign anything either. Offer to meet at a Kinkos or something to copy stuff. You want to make sure you're getting the same document out that you signed.

Or just go work for a more established company where you don't have to deal with this stuff. Because, frankly, you're not ready for a startup if you don't have the mental intuition to ask for everything in writing.
Are you sure you do not have disability insurance with your current job?
#2 is more likely than #3 because a reasonable person gives access to another contributor or someone they spent a few minutes vetting, not a total stranger with no GitHub history.
Similar to "Steal this Book" and its advice on marijuana:

> There are two other ways that we know work to increase the potency of grass
you grow or buy. One consists of digging a hole and burying a stash of grass
wrapped in a plastic bag. A few months in the ground will produce a mouldy
grass that is far fuckin' out. A quick method is to get a hunk of dry ice, put it in a
metal container or box with a tight lid (taping the lid airtight helps), and sprinkling
the grass on top. Allow it to sit tightly covered for about three days until all the dry
ice evaporates.
Biophysics and biochemistry would both fit the bill.

I would not take the site you linked seriously - it's the ramblings of a crackpot. If you happen to have a biology background and would like to debate this, I'd be happy to elaborate.
I still don’t get it. What is a “project” and how does it differ from a “repo”? If they are the same thing, isn’t every project/repo going to cost at least a $1?