skysight-inc/HackerNews huggingface dataset:
> Ultimately not a good design choice, but the fact that it actually wasn't that limiting and relatively few people care or notice

It was a horrific design choice, and people do notice and do hate it.

Not so much because of how it applies to ints, but because the design choice Java made was to not support any unsigned integer types. So the byte type is signed, conveniently offering you a range of values from -128 to 127. Try comparing a byte to the literal 0xA0. Try initializing a byte to 0xA0!

In contrast, C# more sensibly offers the types int / uint, short / ushort, long / ulong, and byte / sbyte.
I don't think you understand the formal use of the term 'vulture capitalist'
https://prospect.org/economy/vulture-capitalism-killed-sears...
Everyone from original Dart team left, Lars is now one of co-founders of a startup trying to sell a Dart like language for IoT.

Dart and Flutter futures are are now married, and I still don't buy into Flutter.

Languages married with UI frameworks seldom last, specially when the competition outside of the UI framework is so much better in tooling and available set of libraries.

Plus hot reloading were a novelty when Smalltalk, Common Lisp, Oberon System, Eiffel got introduced into the market.

And the competition isn't sleeping either, Flutter touched the Android team nerves hard enough that now we are getting Jetpack Composer, Xamarin already has its prototype available, Qt always kind of had it, so in the next twos (give or take it), all the cross-platform mobile frameworks will have dynamic code reload, with more market relevant languages, couple with 20 - 30 years of libraries.

Until Google releases Fuchsia and makes everyone write Dart code, I will pass. Qt, Xamarin, PWAs do the job just fine, with more mature languages.
I've said it before, the whole speculation-exploit mess seems like chip design's answer to the real-estate-securitisation highjinks which caused the last financial crisis. https://news.ycombinator.com/item?id=16105385 And that's not an analogy which puts all the spotlight on Intel, by any means.

> I'm finding it hard to escape the suspicion that Spectre and (to a lesser extent) Meltdown is another failure of expertise on the same rough scale as the run-up to the financial crisis, the decades of bad or poorly-justified dietary advice, and the statistical problems in experimental psychology. On the face of it, it seems obvious that speculation + cache + protected mode was a combination likely ripe for exploitation, but the response seems to have been "nah, it'll be fine, probably"? And even if it for some reason wasn't obvious, it's now clear that it actually was the case. So the academic and industrial and bad-boy "security community" collectively more or less let the CPU manufacturers take a flyer on this for, what, a decade?
OS/2 was supposed to be a better DOS than DOS but suffered these glitches in the article.

Windows 95 ran WWIV BBS better than OS/2 at the time. You had to write in OS/2 routines to make use of it which is what WWIV did later.

DOSbox is what I use now for DOS programs.
Every commit should combine:

- The code change itself

- Tests that demonstrate that the change works as expected

- Updated documentation relevant to that change (documentation should live in the same repo as the code to support this)

- A link to the ticket/issue that discusses the change

If you use a code review system such as GitHub pull requests or Phabricator you can enforce this kind of commit culturally - in your review point out that the test is missing or the documentation hasn't been updated or there's no link to an issue.

I like building pull requests up from several commits and then using the "Squash and merge" option to merge them into a single commit to master that includes all of the above.

Doing this is great for institutional knowledge, because "git blame" can always lead you to a comprehensive explanation of the change, including a link to the underlying ticket where the change was originally requested and discussed.
And yet if you were to go out today and build the exact same product in the exact same way it wouldn't succeed. Strange.
Can anyone explain to me a rational upside for the Chinese state to over-report detected cases and under-report mortality? Bear in mind, the impact on the domestic economy of failing to reign in an epidemic is as real as the upside of claiming it's fixed to settle export income. Basically it's not in any states interest, one party or otherwise. China's domestic economy depends on people getting better.

I truly don't get the assumption "it's worse than they say" when the most likely outcome (putting Hanlons razor into play), is that mortality stats are nearly accurate and caseload is under reported due to lack of testing and self isolation. Death is hard to hide. I believe mortality stats. Any non reported mortality goes to under reported cases, so it evens out.

I know it's optimistic thinking but I am drawn to a belief the effective cumulative death rate in China only drops, as better figures emerge unless unlike all other virus it becomes more lethal not less under mutation.

A different comorbidity outcome eg opportunitistic pneumonia or delayed onset COPD or something, that's different. That would demand a massive change in view. Change in the long-term disease consequence will be interesting and important.

(For instance the effect some disease has on vaccine immunity across the board comes to mind: if this happens, bad news: but, that is in the future)

Well adapted virus mutate not to kill their hosts. Badly adapted virus self limit.

This is not about liking or disliking the Chinese state, I am asking on what grounds people walk to 'under reports of death, over reports of caseload'

No other claim alters mortality into worse places.

Non Chinese deaths predominantly lie in old, lower immunity, comorbidity sick people. And, saying "it's too soon, wait for the wave" is forward facing speculation. Cumulative infection and death rates are inherently backward looking. Explain to me how these a posterior figures get worse not better.

TL;dr it's not smoke, this article is mis applied stupid maths.

Keeping people on a ship (think norovirus and cruises) or having a religious cult uncover huge transmission outcome.. that's not a true reflection of societal risk under self isolation in the home.

I am told the CDC insisted on a home made test. NIH as in "not invented here" and not national institute of health.. bad move guys. Under testing in a US health system with patient cost recovery. That is a recipe for less successful disease control. The US is going to turn out to be under reported. Death rates will probably be right because dying in America is statistically well understood. People won't front for expensive medical test or treatment. High rates of COPD and diabetes and therefore higher risk of death than many other economies. Also large numbers of underinsured older people.
That may be so. I was responding to the claim that "python's implementation of concurrency and multi threading is fantastic". Under such circumstances I'd expect to be able to do multi-threaded compute.
This is the solution I would recommend to ClearView to stay in business.

Either they don’t have the expertise to distribute enterprise apps or their clients are not capable of maintaining a MDM software and an Apple Enterprise Account.
The latter really bugs me though. It implies that e.g. police officers can install any software on their work devices if they wanted too, which might endanger citizens because of possible data leaks by device loss or hacks.
With a MDM you can wipe sensitive data remotely and separate private data from work relevant data.

We distribute our business apps as unsigned xcarchives and our clients resign them with their Enterprise Certificates and Provisioning Profile and this can distribute them as they like.
There are a number of problems with JSON and these schemas based upon it. And a huge chunk of the problems would be solved with a better, stronger type system. That's why I've spent the past couple of years building a replacement [1], [2], and an RPC layer and service selection mechanism that I haven't spec'd out yet.

We need a binary encoding because they're more efficient in code, time, and power. But we also need a text encoding because we're humans, and eyeballing binary data is terrible. I've made them both [3] [4], and they're 100% type compatible. The idea is that machines communicate using binary, and translate to/from text only when a human needs to inspect it or modify it.

The thing slowing me down atm is the coding side of things ([5] [6] [7] [8]) because it's tricky getting go to play ball with its reflect mechanism. Once I have a functioning gob replacement, I can move up to the next layer.

I'm probably a month away from releasing v1.0 of CBE and CTE, after which it'll be another few months for Streamux, and then the layers on top of that should go pretty quickly because I'm not bit bashing anymore.

[1] https://github.com/kstenerud/concise-encoding#concise-encodi...

[2] https://github.com/kstenerud/streamux/#streamux

[3] https://github.com/kstenerud/concise-encoding/blob/master/ct...

[4] https://github.com/kstenerud/concise-encoding/blob/master/cb...

[5] https://github.com/kstenerud/go-cbe

[6] https://github.com/kstenerud/go-cte

[7] https://github.com/kstenerud/go-compact-time

[8] https://github.com/kstenerud/go-compact-float
I haven't worked on a product that used analytics to drive feature development.

What you wrote here sounds very naive to me.

I might be completely wrong, but i assume if you have a large enough user base you would use telemetry only in an aggregated way, and then prioritize the majority of the user base. So I might totally be underrepresented but still have the same loss of privacy as everyone else.

I also feel i always have the right to complain about a product, publicly and vocally (it's just a different channel for analytics/telemetry, imo). Much like product owners have the right to just change it remove features that break my workflow.
No, you can still be critical and not have it hurt the company with just a two week absence. Say a product like Uber ceases new development because of a critical developer leaving who knows how to fix the home grown CI. The company isn’t going to go under in two weeks but it doesn’t mean the dev isn’t critical.
Potential for Love-based Currency? Thoughts from extra day (DocAccessPass:g7w1)
"ships from and sold by Amazon.com" is no guarantee of authenticity.
Bare metal just means not a VM. The machine still has an OS.
Notion is wonderful for this. It’s like a wiki with the ease of use of google docs.

My company has basically everything on Notion and any time someone asks a question more than once, it gets added
++ for checking that you were using the correct pronoun for the author!
This is certainly true for the Netherlands (alluded to in the article): the yellow vests (and the supporters of right wing populists in general) are overwhelmingly poor, both in terms of education and in terms of wealth.
How does your offering compare to capnproto?
Having been there, I hope to never touch Cordova or Ionic ever again.

Most of those apps are perfectly doable as PWAs.
This reminds me of when all the planes in the USA (and several other countries) were grounded after 9/11 and there was some evidence that it affected our temperature variation because there weren't any contrails in the sky.

http://www.cnn.com/2002/TECH/science/08/07/contrails.climate...
I've encouraged teams to switch from email to Slack precisely because it takes non-searchable content and makes it searchable. The amount of institutional knowledge that ends up in personal inboxes of a tiny subset of the team (who then eventually leave the company, causing their emails to be lost entirely) has always terrified me.

If you can set up a culture of everyone subscribing to internal mailing lists with searchable archives and wide distribution then I could see it working - but my experience is that the easiest way to get that culture is to switch everyone over to Slack.
Gutenberg https://wordpress.org/gutenberg/
SSL/TLS certificate validity chopped down to one year by Apple’s Safari
And you weren't counting the matury of the eco-system.
There is a pretty strong correlation between wealth and environmental impact. Wealthier countries are in general not great for the environment.
There's now a nursing home in Washington with a staffer, and a resident[1][2] confirmed to have COVID-19, and ~50 people in that nursing home showing symptoms. But, since only those 2 people have been tested, the national stats look amazing! Only 4, no, scratch that, 6 transmissions!

[1] https://nymag.com/intelligencer/amp/2020/02/two-new-us-coron...

[2] Neither of them have been to China.
You can see the same problems even within technology, look how dominant companies like Apple or Google have become whilst the rest of us are gleaning for leftovers.
13m DAUs at $6.67 per month is $86,710,000/month, or $1,040,520,000/year - seems like a pretty big business to me!
Store readme markdown files in the sourcerepo along with the code itself. Make sure during review that changes to code are reflected in the markdown.

Doesn't need to be exhaustive docs - usually just a high- to medium-level explanation of what why and how goes a long way.

Controversial/surprising/confusing choices should be documented in several places - e.g. in the readme, in a bug/ticket, in the check-in comments and also a comment in the code referencing the readme/bug/ticket for more info.

Over-communicating the confusing/surprising stuff helps a lot and helps to prevent the "what the hell is this crap? Let's rewrite it" issues since there is a long paper-trail explaining why things were done that way. Putting code comments referencing bugs/tickets etc (ideally with clickable links direct to Jira or whatever - e.g. "// This does <surprising/confusing thing> - see the discussion in http://bug tracker/12345678" ) means that the trail starts right there in the code, and people have not had to trawl through some nonsense wiki to find the hidden nugget of info (let's face it - we'll read code but hardly ever go out of our way to find and read wikis etc first)
"Lets move on from whether this is fact or not ..."

https://medium.com/@caityjohnstone/confirmed-chemical-weapon...
Update on grade strike
There's someone that commented in this thread about gluten oversaturation that provided some decent links.

Unfortunately, there is no strong consensus that gluten intolerance does or does not exist, and the best most folks without Celiac can do is a nutritional exclusionary screening. The real tell on it is more to do with what grains can or can't be used/tolerated when it comes to wheat sensitivity, gluten intolerance, or fodmap carbs.
It is not proven that Assad did it.

But it is proven that the West used this lie to justify committing yet more atrocities in Syria.
Yes, Flutter is Skia + an UI framework written in Dart.

You can also get Skia + whatever you want and get your own "Flutter".

Currently they still have a better experience to sell regarding code reloading, but competing frameworks are upping their game by adding similar capabilities to their developer toolchains.
I've experienced that as well (both as a junior and as an experienced engineer):

- Follow these steps.

- If anything is unclear or doesn't work, update it.
That’s not because the richer countries are being “clean” as in consuming less resources and polluting less. They are just doing it less in their boarders. They are exporting the dirty manufacturing and in many cases literally trash to poorer countries. If every country became like the US in terms of wealth and consumption tomorrow we are all screwed.
How, exactly, would one own SpaceX stock?
Let me guess, using Xamarin from Mac.
Indeed. School teachers (not particularly well paid or managerial) are definitely part of the clerisy, supporting things like an [edit: added missing word "energy"] transition and, no surprises there, a greater role for education. Managers in companies that operate in the market: not so much.

The term “clerisy” to me rings clearer than “professional middle class” as he latter ignores [edit: removed autocorrect nonsense word] very real distinctions between corporate lawyers and directors of NGOs.
Ok so tell me if I got this right -
say N=100K clients have on average 500K in balances in this financial institution (Q_1: so IG is a broker, presumably..?) and some fixed percentage of clients, call it Np_1 (assume p_1 <= 0.05), participate in this weekend game... like uh so what? Is some of this Np_1 population of IG's clients actually submitting trades in some sort of market simulation, or are they really submitting actual lmt, mkt, sl, etc. orders over the course of the weekend and these guys compose an index that composes friday's closes with the new orders and establishes a rough guide of what would happen if mkts were actually open? I mean, I guess I get it if that's the case, but... I mean that's a super rough estimate. Must be wrong most of the time. Just wondering if that's the idea.

How does it change through the course of the weekend? Is it truly reliant on people submitting orders over the course of the F-M interval? If so, then this assumption clearly has a huge retail bias, (since only retail investors are likely submitting orders over the weekend) and as a result, apparently fails to effectively capture the behavior of larger institutional mkt participants, nor does it factor in the principal investment behavior of larger-scale BB IBs.

Can you help me understand why dark pool behavior would even matter during off-hours here? I seriously doubt anyone working at a MM that offers some kind of dark pool to clients would be submitting manual orders over the course of a weekend... right..?

I feel like I must be missing something. I can't imagine more than 15% of investors, across the retail and (everyone else) investor community are actually submitting orders over the weekend but this is a total guess. And I would guess aggregate notional value for all of those trades would be less than 1%, if I were to guess, of the previous Friday's total gross trading volume
The Shortest Signatures Ever (2016) [pdf]
Extensive discussion two days ago: https://news.ycombinator.com/item?id=22434294
Perhaps Iran received an early transmission chain and is one or two generations ahead of most other places.
Odoo has a full CMS with advanced page builder: https://www.odoo.com/page/website-builder
The Problem with Packages
> you assume you're an authority on what a "good look" is

They don't assume that, they know that. Everybody is the authority of their own moral judgmement.

> But you're doing this while the reader is noting that you failed to express a real argument,

They pointed out that what they're responding to is subverting the desires of people who would like privacy, that's the meat, "that is not a good look" is just a bonus statement, something that would be implied anyway even if left out.
I ended up having to accept that documentation would always end up spread across a dozen different systems: Sphinx/RST + GitHub Markdown + Confluence wiki + Google Docs + Continu + email mailing lists + the customer support website + I found one team using Google Sites + ...

So I built a custom internal search engine that indexed documents from all of those systems and made them searchable in one place. It worked pretty well!
What possible relationships exist between this phenomenon of successful people being middle-aged and not young and the common meme that asserts that life is short?
Understanding the disease quickly and slowing down the spread of the disease is incredibly valuable work. Knowing more about it lets us prepare more effectively. If we can reduce the rate at which it spreads, that gives us more the time to prepare for it by training staff and building up stockpiles. Also even if the number of cases ultimately stays the same, if they are spread out over a longer period that means the number of patients needing care at any one time can be dramatically lower, reducing the strain on the health care system and allowing more resources to be devoted to the care of each patient.

The CDC, or some agency in each country anyway, has four roles in this I think.

The first is as part of international monitoring, research and co-ordination efforts. Pandemics are by definition international phenomena and the countries they are most likely to start in are the ones with weak governments or health care infrastructure. This is the first line of defence.

The second line of defence is advice and information, supporting other government institutions and agencies in co-ordinating their resources. Medical expertise is needed to support border control, diplomatic efforts, internal transit networks, government policy, law enforcement, logistics, the list is endless. These all have a role to play in limiting the transmission of the disease and preparing for the eventuality that is reaches populations. They all need expert advice and that advice needs to be prepared in advance and consistent.

Thirdly if the disease does take a grip, co-ordinating local and regional medical resources and efforts. Collecting data from health care networks to track the disease and direct resources where they are needed most, and ensure those resources are used in the most effective and efficient way possible.

Finally, research. This is a long term commitment to developing new equipment, treatments and techniques. This, and all the previous functions operate at the national or even really international level and can't effectively be progressed by fragmented regional or local health care systems. If it's not the CDC it needs to be somebody.
One might say the whole effect of the domino theory was to justify US military intervention against Russia and every single place they did, it backfired.

Iran, the oil backed coup of the 1950s led to Pahlavi, hatred and fear which in turn led to Kohmeni in Paris. Simply letting the Iranians nationalise the oil industry would probably have been better long-term.

1953 to 2020, US oil interests stuffing up peace...
Surely it would just transition from gold to progressively more expensive elements? I'm not a chemist but presumably we're not going to being synthesizing much Einsteinium for a few years yet
Microsoft is not only using React Native, they are the main contributors to React Native on Windows and macOS.

React Native is also one of the reasons why WinUI core components are all going to be C++, instead of a mix of C# and C++.
>A lot of apps are still developed iOS-first

Why? Last time I checked, Android had 85% of the market share.
This is what I do. And if the Markdown file is not near the code in question, it's a 100% guarantee you've wasted time writing it because nobody is going to read it.

I also write comments first when writing complex code and then fill in the code in between. More than once this helped more than any documentation could, because people do not read documentation if they can avoid it, and avoid it they'll try.
Re: easy search. Slapdash can handle search in all your work wikis/docs at once and is very fast. It can search github/gitlab too. I am part of the team there.
Solo people working on projects aren't too bad so long as they communicate the work they're doing and document it well.

Some people just work better on their own.

IMO, what's worse are "knowledge hoarders". Usually they've been in the company for a long time and they maintain their position by being as stingy as possible with their knowledge. You usually find these people in big orgs, and they can be quite toxic.

They also don't write good documentation.
In Melbourne, the designers got their comeuppance. The barristers ganged up with the judges, and for a while it became a principle of Victorian law that the ergonomics of public transport tickets were irredeemable, and anyone who claimed to have made a reasonable attempt to pay their fare would be let off.

That didn't last long, but the panic it provoked in the bureaucracy was hilarious.