skysight-inc/HackerNews huggingface dataset:
Apple also got a lot of flak for not including a menstrual cycle tracker in their Health app. It was a popular sign of Silicon Valley’s male bias for a while. To wit:

> Perhaps I shouldn’t be surprised. After all, Apple’s first diversity report did show that the company is mostly white and male. So it’s likely that menstrual cycles just aren’t a concern for a majority of the company’s employees. But that shouldn't be an excuse.

https://www.theverge.com/2014/9/25/6844021/apple-promised-an...

> But considering that plenty of other, extremely popular apps for menstrual tracking already exist (Clue and Period Tracker are two stand-outs), all we have to say is, thanks for finally including women in your world, Apple. Welcome to ours.

https://www.health.com/pregnancy/apple-finally-adds-period-t...

> That Apple overlooked period tracking as a key function that roughly half the population would expect to see included in a comprehensive health tracking app is not entirely a surprise.

> Apple today is a company where only 30 percent of its employees are female, and only 20 percent of those in engineering positions are female.

https://techcrunch.com/2015/06/09/apple-stops-ignoring-women...

This last one comes from The Washington Post, perhaps demonstrating that sometimes you’re damned if you do and you’re damned if you don’t:

> Apple notoriously ignored women's health issues as it developed previous versions of Health

https://www.washingtonpost.com/news/the-switch/wp/2015/06/17...
Apparently you don't visit any sites using Angular?
I think the problem is that the market demands growth and while basic search ads did yield insane profits, we are now approaching the end of the Internet growth period where everyone who has expendable capital is also already on these platforms. Tech companies have effectively run out of people to convert into customers and thus they have to do these crazy tracking shenanigans to try to squeeze as much out of every individual as possible.
It's not like you can just fit all of Amazon's load on existing carriers, they would probably need to put more trucks on the road if they absorbed Amazon's load.
How are either of these more private than Slack? Whoever hosts the server can see whatever is on it.
I love how the first-mentioned "hardest thing in computer science," naming things, is one of the shortest sections:

> Did the developer pick good names for everything? A good name is long enough to fully communicate what the item is or does, without being so long that it becomes hard to read.

They mention several times a "Nit:" or other prefix for nonblocking comments. I wonder if that is purposeful and/or reflects the experience of the company.

I also like a lot of the points made in the CL Author's Guide [0]. I've recently finished a similar document at work on how to form good Git commits. I generally like to be able to review a GitHub PR by stepping through a sequence of well-formed commits one by one, each of which sounds like what Google is describing in this document. Regardless of how it's sliced up, by commits or PRs or whatever, in general I just wish I could get more folks on board with this part of writing code.

[0]: https://google.github.io/eng-practices/review/developer/
Setting up a VPN that tracks all of your network activity? That makes me queasy. Why should I trust these people to keep all that valuable network traffic data private for me?

Apple didn't steal this idea. They may have implemented it in a better way given their low-level system access but, in this case, and in my opinion, I'd rather this be something the OS tracks for me for free by a company that doesn't make their money off the sale of my private personal data.
Thirty years of unique data reveal what's killing coral reefs
Technically there's no reason why write can't context switch directly to a process that's blocked on read (or, less commonly, vice versa). That only solves half the problem though; if you want pure pipe-like IO, you'd also need a single system call that combines write with select/poll/equivalent so the caller can immediately become blocked waiting for the return message.
Here's a real-word C compiler where the sizeof() everything is 1; https://github.com/vsedach/Vacietis

For another example, the LLVM webassembly backend doesn't put the call stack in the same address space as the heap at all.
Draw the Rest of the Chart
Interesting, so the acquisition agreement did not have a non-compete clause or golden handcuffs to Slack? If you don't mind me asking, how come you left Slack?
In the EU you can get credit for 1% and less at any German/UK/French/... bank. Do you really want to pay 10-30% instead at Stripe?
Are military vessels exempt?

I vaguely remember reading that US warships in recent accidents had stuff ~like this turned off.
> For sure. For one thing, the car looks flashy and draws a decent amount of attention where I live, so it's fun just driving around town.

It doesn't really look like a flashy car to me unless you've wrapped it..? Where I live (SV) they're about as common as a toyota corolla. Maybe you've done something to it but I don't feel like it's flashy like a Viper ACR is flashy.

> For another, I accelerate pretty fast at lights, so that never really gets old.

I guess but that's, again, not really driving a fast car slow then is it?

> And in stop and go traffic on the freeway, it's fun because I just set autopilot on.

So, you're saying that not driving and watching someone/something else is.
I get that they are different. It was an analogy. Either way, I don't think there's enough momentum to stop it this time either.

BTW, your argument about being able to inspect local code still seems moot in light of the fact that if you interact with the server, you still have to trust it. 90% of the code might be local, but you still have to worry about that 10% that is opaque to you. And there's no practical difference between 10% of code being opaque and 90% being opaque. The "bad stuff" could happen in that 10%.
But the ransomware attackers are already breaking the law with greater proceeds. Why would they stop and decide to play by rules that require them to do more work to make the same pay?
brk() is undefined behavior if mmap is ever called.
That's definitely true, electrolytes make it much easier.
2-3, but I really think the voiceover was worth it!
https://commutestudy.com
It's impossible to tell from TFA or the abstract what precisely is meant by "information gerrymandering". One imagines some sort of graph theory or "six degrees of Bacon" argument. "This node should only influence some number of other nodes, but in fact if you count second- and third-order connections it influences some higher number of other nodes!" Presumably they've picked out some particular criteria for differentiating justifiable influence from unjustifiable influence. The criteria are probably fine; since we don't know them the point is moot.

Even if one accepts all of that, one still can't follow TFA to its conclusion of "...voters really can be manipulated in the digital age. Legislators and regulators must take note." We've been working on this "giant graph of nodes influencing each other" problem for decades now. That's just SEO. That's the basic thing that Google does. Any network has these properties, even the "snail" networks of pamphlets and broadsheets that kept our founding fathers informed.

It was completely appropriate for late-18C pamphleteers to publish and distribute according to the dictates of their own best judgment. It's completely appropriate for today's social network operators to do the same. It's completely appropriate for users to do just exactly as they please, whatever the TOS say. What is not appropriate is for "legislators and regulators" to imagine they have a damned thing to say about this process.

1A is not ambiguous on this question. The government don't get to forbid the public from hearing Trump describing to Billy Bush his techniques of seduction. They don't get to forbid the public from hearing Clinton tell bankers they should be able to regulate themselves. [0] It's a conversation because they don't get to decide everything that gets said. For three years now, a segment of the "intelligentsia" have wallowed in a mode of magical thinking about networks and bots that has left them completely uninterested in real things. If this research can help them break out of this rut, one welcomes it. However, that seems unlikely...

[0] https://www.thedailybeast.com/leaked-podesta-emails-show-ber...
Is there any evidence the insurers are actually driving increased security? Do their policies require certain security standards or backup processes? If they do, it's not a bad start.
You can still capture the malware in honeypots & analyze its behavior – and try all the investigation and enforcement methods currently used.

But, those grayhats seeking to use this safe-harbor would be more open about their identities & methods. They can even deposit their earnings into KYC'd bank accounts!

So imagine some bad-faith actor pretends to be complying, but then turns out not to be & tries to double-dip – taking both the conditional bounty, and more. Such people will now be competing with other hackers who are playing by the rules – leaving the nastier actors fewer open systems. And anyone who seems to obfuscate their identity/methods will stick out as a likely bad-faith actor. Thus I'd expect they'd be a lot easier to catch, and have more to lose, than in the status quo.
I much prefer features built in to my iOS than left as sketchy, personal information stealing, gaping privacy 3rd party apps
Executables should not be part of a data backup and recovery plan.
The credit union I use has pretty standard password rules (that is: decent by bank standards, i.e. pretty abysmal), but what really takes the cake is that the "Forgot Password" mechanism is driven not by a button or link or what have you, but...

...a checkbox.

Worse, this checkbox is exactly where one would normally expect the "Remember me" checkbox, so if you check it out of habit, you'll end up getting shoved into the password reset flow instead.
Nothing embarrassing about it. Until the early 1960s, scientists (and, thus, science fiction) were split about 40/40/20 on whether Venus was mostly ocean, mostly swamp, or mostly desert.
How does this relate to all the work that Christ Lattner et al have been doing at Google with Swift, MLIR, etc.?[a]

Is this... a separate, parallel, more encompassing proposal?

Is there any coordination between these two groups?

--

[a] https://www.youtube.com/watch?v=yCd3CzGSte8
Office 365, Salesforce, Ultimate Software, Adobe Creative Suite, GSuite, ADP, Box, DocuSign, Shopify, HubSpot, Zoom.
Agreed. I find this extra important when working remotely or with other people who work remotely. If you’re not getting any face-time, critique has to be balanced with positivity. In my experience it’s true even with very experienced team members, and even with the very serious & stodgy people who avoid chit-chat and claim to not be bothered by feelings & opinions.
Thanks for sharing this article!
For any large company this effectively means that almost all of your side projects can be construed as falling afoul of this law.
When I actively managed money for mutual funds, we had limits on both total % ownership and how many days of volume we could own. We were small cap growth, so sometimes we could be stopped from owning as much of a company as we wanted because it was too illquid. Passive doesn't care - it buys what it needs to replicate the returns of the underlying.
Also, it's well known that if a hedge fund (or mutual fund) is in trouble, they sell more of what they CAN rather than what they want. That's one reason why we always knew who else owned the stocks we did.
Index funds have no leeway here. They need to sell - whether there is liquidity available or not.
My gut is, there will be much less liquidity available during the next crisis than you'd expect. A lot of "non passive" investment is quant driven, which ends up becoming very homogenous in nature across different firms. Many also have momentum factors in play, where they buy short term positive momentum and sell the reverse. Once again,vthey don't have a lot of leeway for humans to say "this market is different".
Somewhat.

There is arguably an objectivly true answer for exactly what payments a given stock will make, and so there is an objectivly true answer for what the present value of the stock is (also dependent on other aspects of the future market). This is somewhat of a philosiphical question, largly boiling down to determinism; and is largly moot because no one claims to be able to predict the future well enough for this to work.

Instead, the working position that most take (at least implicitly) is that there is an objectivly correct probability curve of what the future payouts will be, and therefore an objectivly correct probability curve of present values. How to determine what this curve is is a matter of great debate. Further, there is a sufficient lack of objective methodology, that many of the factors that people use in this calculation would be refered to as "opinion", but there is still an objective reality out there.

However, this only gets us an (unknowable) objective probability curve of present values. In general, there is no objective way to turn this into a price. That is to say it is a matter of opinion how much a 50% chance of making $100 is [0].

In an ideal market, you would be able to sell a stock for its objective value at any time. However, "the market can stay irrational longer then you can stay solvent", so you may pay a premium for stocks that you expect to not be undervalued when want to sell them.

Conversly, you may by a stock not because you think it is worth what you are paying, but instead because you expect to find a greater fool to pay you even more then you paid.

There are also cases where people value stocks not just because of their future payments, but because they actually care about the company (or, in the case of divestment, people dont buy them becausr of personal preferences).

In short, there is some matters of opinion in determining a correct price; but most of the disagreement comes from a factual disagreement about what the future looks like.

[0] this calculus changes when you have many such gambles with varying degrees of corralation (and many a financial problem have stemmed from underestimating this corralation)
Gravito-Electromagnetism
The sender of these notifications doesn't know that the user has closed the app. What this means is that the message send from the sender through the server now has to include whether this is a message or a non-message, which has to be a flag in plaintext.
Window positions? I'd be happy if icons would stay in one place as i plug/unplug displays! To be honest MacOS and linux are the only current consumer OSs that have multi-display handled. And of them, only MacOS properly handles multi-display setups with differing DPIs.
From experience, I would generalise this advice to, "let the callers of the API control side effects".

The justification is largely the same, i.e. that the caller generally has more context and thus better ability to decide when and how side-effects should happen.
Could Apple have slowed down VoIP notifications before, to negatively affect FB messages vs iMessage?
Fanned out, or triggered builds, don' trace well. User api token env variable is wierd and docs are terrible on that point and others. Wanna see a list of projects? Go to "add project". You are required to "follow" projects in some cases. There is no search build feature. There is no real filter builds feature. The paging is terrible. No date search feature. No parameter search feature. If I go to circleci.com even thoigh I am logged in I see a big fat hero advert about how great circleci is and who their clients are. (Hey I'm your client ever thought about that?) Cant name your individual builds. Cant tag your individual builds. Build parameters even when fanned out dont show so 10-20 builds are indiscernible in a monorepo. I could really go on all day, this is not half of it. It just comes across as this big legacy software blob that have too many bad design decisions to revamp and will just go irrelevant through time and they instead of improving their product to gain new customers they just hold on and bleed their existing ones as long as they can. Suppose it makes financial sense though in their defense, their code must be in a total deadlock.
Of course, the hardest problem is not meant to be mitigated by a common and daily behavior like reviewing code.
He is either on a low powered device or overly focused on details. In my experience I have never needed to look at RAM usage on my 2017 16GB MBP, but sometimes I do check CPU usage just to see how hard that intense process is hitting the computer and when it finishes.
Because the larger the group the more expensive it is to run. This is a very early experiment to see if there's anything worth doing a larger study on.
Actually Apple Music in iTunes is just a web view that leaks like crazy, to the point of making iTunes slow to a crawl, if you're quickly navigating through artists and albums.

Not much better than Electron IMO. Apple Music in the browser seems like there isn't much hope of a truly native experience now.
The guiding principle in the Apple world goes something like this: If your entire app is really just a feature that should exist in a 1st party app, Apple will probably implement it eventually.

The iPhone comes with a 1st party email app, but many people prefer 3rd party apps. Same for calculators, weather apps, podcast players, music players, password managers, calendar apps, etc. In another comment in this thread, I linked to several articles that were critical of Apple for not including a menstrual cycle tracker in their Health app. Some 3rd party apps filled the gap for a while, but it seems like it was really a feature that lots of people wanted in the 1st party app. You can call it abusive if you want, but others might say that Apple was answering the needs of its customers. If the 3rd party apps provide better functionality (as they often do... see the examples I listed above), people will continue using them.
https://www.onlinethreatalerts.com/article/2018/4/25/beware-...
I'd add two things, from a decade of experience at Google:

Review code in this order: protocol buffers, unit tests, headers, implementation. It's common for a new employee to be an expert on C++ or Java or whatever languages but it's very uncommon to meet anyone who knows how to define a decent protocol message. The tests should give the reviewer a very clear idea of what's happening in the code (and this should be congruent with the description of the change), if not send back to author at this point. The headers should contain clear interfaces, types, and comments and should not contain anything that's not part of the API (when this is technically possible). Finally look in the CC file; at this point the reviewer should see things they were already expecting and no funny business.

Any claims about speed, efficiency, or performance whether in comments or during the review must have accompanying microbenchmarks or they should be deleted. Wrong ideas about software performance abound, and even correct beliefs become incorrect with time, in which case the microbenchmarks are critical to evaluating the continued value of the code.

When sending a changelist for review, always clear all automated warnings or errors before wasting the reviewers' time. Nobody wants to see code that doesn't build, breaks a bunch of tests, doesn't lint, etc.
I’m surprised. I haven’t heard anything about Ember in years. Not since 2013 or so.
You'd think if they're fine with truncating the password on account creation, they'd also be fine with truncating it on login as well.
That is correct. Similar model for repayment based on % of sales https://squareup.com/us/en/capital
There do seem to be a couple of fixes that would go a long way to satisfy anti-trust concerns:

1) Force internal apps (especially paid ones) to use publicly available APIs.

2) Publicly disclose all App Store metrics that aren't strictly limited to security teams within Apple.

3) Insulate the App Store review team and processes from their other business units and setup a independent watch dog to monitor the process and ensure fair enforcement of the rules.

Fixing these three things would leave us with just the industry wide problem of the power-imbalance in IP disputes between companies of disparate size.
The problem is not only do people “want to believe” but actual journalists who went to journalism school get trapped into the “wanna believe” trap coupled with not wanting to miss out on a scoop results in terrible “reportage” and results in a kind of weird propaganda.
Continuous production of [formic acid] via electrocatalytic CO2 reduction
Many ios features were copied from cydia as well, especially early on.
My body weight puts me barely above underweight when I eat as much as I feel like. I don't think regular week long fasts could be very healthy for me.
When the user is not running the app, what is the use case for the app waking up and processing data that is not an incoming message to be delivered to the user?

Facebook was using the VOIP framework to burn so much power after the user had quit the app that you would see articles pointing out that deleting the Facebook app could double the battery life of the device.

>Deleting This 1 App Can Literally Double Your Phone's Battery Life

https://www.inc.com/john-koetsier/deleting-this-one-app-can-...

If I am not running a messaging app, the only power draw I want to see from that app is decrypting an incoming message intended for delivery.

Anything else can wait until I next open the app.
Google Feedback on TypeScript 3.5
Detects unauthorized source code usage. Free forever
See also Matt Levine's take on ransoms (scroll down):

https://www.bloomberg.com/opinion/articles/2019-08-27/the-li...

And the linked article:

https://www.propublica.org/article/the-extortion-economy-how...

Tl;dr: perverse incentives, paying some ransoms is in the interest of cyber crime insurers, as it expands the cyber crime insurance market. Also there's more ransomware crime now that the word is out that insurers do pay out ransoms.
Google Assistant’s Ambient Mode Turns Android Devices into Smart Displays
Err... Firmware has a history of being closed, buggy and quickly non-supported by the manufacturer. Block level abstraction exposed to the client is as brain-dead as it gets - and it is a good thing. Just imagine that your SSD had an S3-type interface for five years. And you only could use the tools that Amazon released five years ago. No updated versions. No bug fixes. And no "backend changes" to workaround bugs/etc and that was your only copy of the data.
I suppose I'm left wondering if this causation loophole - a properly engineered switch being deemed not to cause anything, despite an obvious cause/effect linkage to an observer - is usable in other, nastier scenarios.

Can I (setting aside the obvious secular punishments for a moment) murder someone with a bomb activated via one of these switches?
The "password must be exactly 8 characters" rule screams AS/400.
Another anecdata, but our kid's babysitter (also 16) doesn't have a Facebook account, and neither does her twin sister. They both have IG and Snap though. She said the same thing: "Facebook is for old people".

Also my 20 year old cousin didn't have a FB account until he went to college and was forced to get one to join some local FB groups. But he only uses it for that. Otherwise he's on IG and Snap.