skysight-inc/HackerNews huggingface dataset:
That 0.4% difference in death rate is measuring survivability as it records the chance of dying from the virus.

That 0.4% difference suggests Finland's health system was better than Sweden's at handling the virus, as your chances of dying were much less.

When it comes to actual deaths Finland was doing over 830% better (i.e. 168 per million compared to 1406 per million) than Sweden.

Edit: Fixed my bad math. My 90% better figure was out by a factor close to 100.
Because they're too restrictive. They're also not something you have too much control over. My site started out with only my resume. I then added photos because why should Facebook benefit? Then came some work stuff I wanted to publish. And then I got into radio control and I posted up builds. In between all of that I play around with some JS ideas/apps/databases.

Maybe Medium and Quora are enough for some, but for some they're just a sandpit when what you really want is a warehouse with a bandsaw, drill press, 3D printer and coffee machine.
I’m a native English speaker here and it’s clear to me. I also think it’s somewhat tricky to express it more succinctly without changing the sentence a fair bit.

Essentially it means “it must have been the case that, at the moment we’re speaking of, someone was watching her.”

Your sentence is slightly different, in that it implies that, in general, someone was watching her during the timeframe we’re talking about, but not necessarily in the exact instant we’re talking about. Also, like the example above, your version could mean she’s someone who in general is watched (like the person who generally lives in Berlin), as opposed to someone being watched right during the instant we’re talking about.

Complicated!
A wobbling muon could unlock mysteries of the universe
I'm using an AMD EPYC Embedded 3201. This is an 8-core (no hyperthreading) Zen 1-based processor with a 1.5GHz base clock and 3.1GHz max boost and 30W TDP. It came on a SuperMicro M11SDV-8CT-LN4F motherboard to which I've added a dual port 10GbE network adapter. Most of the four 1GbE ports on the board are disabled save for the one supporting IPMI.

I'd prefer a newer generation Zen CPU, but AMD doesn't currently have a recent embedded-application CPU with anything approaching that low a TDP.

Something like an Intel Atom C3758 would be the Intel comparison point, but the EPYC Embedded uses a bit less power at idle (the base clocks of the C3758 are higher), and the EPYC Embedded's ability to turbo means it has more headroom when required for only about 5W additional power draw. Moreover, the EPYC Embedded has about 170% more overall CPU performance than the Atom.
I recommend staying, even living, in hostels for a while. Also, stay in a crew house in Fort Lauderdale starting late October. You might find some interesting adventures.
Lately I wrote a small ssh client that allows you to take your configuration files (such as .bashrc, .vimrc) to the remote easily. Got too frustrated copying those manually as I have quite many remotes I work with and also because I like to tune my configs constantly. Also I have some ideas for further development once I have time for that.

https://github.com/drodil/envssh
There actually is an estimate of this floating in the chia Keybase channel. I remember it being very low, but there are many variables. Even at 100x the estimate it came down to less than 10 million USD in CO2 offsets.
Last time I wrote Java was before it had nice things so I may be slightly out of date in my assessment of its verbosity. I really wish it had decorator syntax like Kotlin does:

class Foo(val delegate: Collection) : Collection by delegate
{
override fun length() = delegate.length() + 42
}

val foo = Foo(delegate: LinkedList())
foo.add(1)
foo.add(2)
for e in foo {
print(e)
}
foo.removeAll()
foo.length() // = 42

I think a lot of the verbosity I remember was due to the sheer size of the type of interfaces you'd encounter in practice and an inability to easily compose them without implementing your own set of forwarding decorators (io stream style). That and getters/setters or rather the lack of any language-level support for dynamic properties.
I don't think it's as complicated as you're describing. There are just two systems; the regular case with regular numbers, and irregular cases using hito/futa/etc. One has to learn which counters use which system, but there are just the two of them.

Note also that ~hon changing to ~bon/~ppon is a general feature of Japanese compound words, it's nothing to do with counters specifically.
Make software that can shoot a laser at starlings and/or mosquitos.
I get what you're poking at and I think we're mostly saying the same thing. However I want to point out that at the level of the stack we're discussing, the application of the chosen language is essentially: plumbing. The user-facing "creative" bits I think you're referring to (those in the system at large, which may or may not use Golang middleware) are most likely a react or mobile app. I'm not trying to devalue the self worth of individuals who write Go code by suggesting that the problems their products are solving aren't creative and fun. Not at all. Rather, my point is that the application of their Go code to build yet another solution for processing requests and serving responses ends up as pretty mundane and verbose imperative program logic that requires non-trivial amounts of effort to properly test and verify. Creativity in the "plumbing" slice of the stack to me looks like concise, readable, expressive code that leverages a type system to model a problem domain and then incorporates expressive logic governing how the types interact, the correctness of which is mostly enforced by the compiler itself and where testing is only required to ensure properties the type system can't capture or to make sure traits of a given type are implemented correctly. Go just simply isn't a language that allows for that level of "creativity" in building what would otherwise just be pretty mundane service plumbing.
Nobody called out DreamWeaver !!!!
in system V init scripts on Linux they had standardized dependency declaration comments. when you added services you ran a dependency checker which would translate the dag into a total ordering, laid out using 01 02 03 ... numeric file name (symlink) prefixes.

it was robust, simple and straightforward.

however it was built around bash.
which was large and slow to start up,compared to e.g. dash as scripting shell. and dash was not widely around yet. so each script had the cost of bash startup, the milliseconds of which added up.

and at some point the tipping point was reached.
because he's smart enough with regards to marketing to know that your story itself has to be marketable
> It's an incredibly bold lie

It may be incredibly bold to you because you likely have a reputation to lose. This guy had nothing to lose. If you have muscles you can always get another unskilled job.

In any case, considering how good he is at bullshitting, they should maybe promote him as VP of marketing.
The third reply strips so much away that the tone changes from tentative to apathetic. The third speaker is just doing the bare minimum to keep conversation moving.
>If you’d rather focus on solving problems creatively and expressively, Go is not your tool.

>It’s just my observation

Well, my observation after dealing with js and ruby projects (ruby was my main language a few years ago) - those creating and expressive languages lead to fewer lines, sure, but in the end you are dealing with a pile of crap nobody want's to touch because some of the developers were so creative and wanted to express themselves more than they wanted to solve the problem.

Go is a tool if you actually want to solve the problem and make sure people after can quickly understand how and why you solved it. Rather than stand in awe of your creation.
Going from strength to strength in one ridiculously small package. It is thrilling to watch this runtime evolve.
it could, in theory lead to cancer, but you'd have to be super unlucky. (frameshift -> accidentally leads to some sort of oncogene agonist)
The people down voting this post are the people he talks about hating. There is nothing not to love about killing invasive species. Thank you for proving my point.
> Worst, the way it is written left me a bit confused.

> [ . . . ]

> Quotations mean beliefs of person having such of a approach.

You can learn how not to do something from observing someone doing things wrong.
Or just “il fallait qu’elle soit surveillée.”
if we targeted this, would the coronavirus simply be able to figure out a way to regulate its proteins some other way?
Once, while at a hockey game in Colorado I had this idea that I wish the stadium could be filled with people all thinking about the same problem and trying to solve it. This result is astounding, and shows the power of mobilizing many people to think.
Some previous discussions on HN here:

- https://news.ycombinator.com/item?id=26271117

- https://news.ycombinator.com/item?id=25556286

- https://news.ycombinator.com/item?id=24256883
So this isn't really the stack monoid, this is mutations as a monoid (which is a construction that exists for anything mutable), or the command monoid. The insight is that these mutations have a nice representation as first-class values and you can combine two "stack mutation commands" efficiently.
I built a little browser extension to map your Wikipedia journeys.

https://github.com/anirudhvarma12/rabbit-hole-webext/

Unfortunately, I haven't been able to get it to work on Mobile which is where a lot of my own random browsing happens, but I have been told its useful!
The Tide Is Turning, the 2020 Election Will Go Down as the Crime of the Century
Relevant xkcd: https://xkcd.com/1138/
Yes, that is quite slow.

I can regularly do 10000 inserts in about 10-15 seconds, they're done in bulk though, so that might be a part of it.

Also, I don't have 23 indexes, so that's probably a large reason why it's so slow, especially if the table is massive and therefore the index is also quite large.
Good thing tether isn't crypto
Health is extremely important, so if you are gaining weight quickly you should address this issue seriously. Switching from a boring office job to a job where you cook and have access to a lot of food has its risks from the point of view of someone who just read your comment.

From your comment, it seems that you may eat and drink to cope with your problems. If reducing your calories intake on the long term is very difficult, you should consider seeking professional help, notably psychological help. That will improve the quality and duration of your life.
I'm gathering you're not against telemetry, just against over relying on it?

Would the AMEX issue have been found without telemetry drawing attention to it?
> Writing TypeScript is like writing JavaScript but...

...but different.

> Writing C is not like writing assembly...

...it's different.
Then you're lucky. I have, both on the developer side and on the user-getting-a-stacktrace side. It's not pretty from either end.
I come from a small country town and moved in to the city and have disliked living here since the start, multiple cities actually. And yes I know that country people are special when it comes to accepting new people.

It won't be easy but France24 had some good stories about people who had done just that. They worked hard but for the moment they seemed to think that they had made the right decisions. I have enough money to live for more than a year without making a single penny so it's not that as bad as it sound.

Well plan C is going back to industrial work I did during the summers at university. Very dirty, very rough but at the end of the day I felt better than I do now. My boss said that I can come back anytime so that's always a backup.
I moved off Fantastical for this reason - I used to recommend it to my friends and coworkers but I kind of feel affronted that features disappeared behind a paywall that I'd paid a license for previously (several times actually).

I really wish Flexibits had created a different app without the cloud features and let this one languish. Clearly they needed a "teams" version for families/small enterprise that they felt they could monetize. That they bundled it into their main app annoys me.

Same with 1password - but in that case, I felt it was worth my subscription (family for several users, admin capabilities worth it alone).
Yeah, I have mixed feelings about it as well. There are some good things, but there are also ugly warts.

For example if you try to use some numeric types that are not int, int32, float64 (for example float32 or uint16) you'll be in a lot of pain due to constant casting back and forth. Yes generics could solve this one too.

I also couldn't make myself enjoy programming in it. I think it's because it tried to be simple, so anyone can learn it. Because of it is kind of rare to say that you created with a creative way of solving specific problem.

That's very different to for example C, to which Go (at least early on) was compared to.
Yes, Google has to fix this soon. I was bummed when I got know there is no way to restrict my scope to only the folder that I create on behalf of hexopress. There was no other way than to ask for more liberal scope.

Hope Google breaks the drive scopes down to more fine-grained levels.
Are DOF calculators useful? – part 1
It's frictionless in part because it's exclusive and universal. I don't even have to think about what the payment method is, or whether I should trust it, or whether I should choose another one. I'm not necessarily arguing for this, just pointing out that friction can be as much about uniformity as it as about choice.

And let's be clear, this isn't an argument over competing methods of payment, it's an argument about whether Apple should be entitled to a percentage of revenue for iOS app sales, regardless how they are sold, regardless where they are sold.

We should be mindful to keep this question separate from whether there should be more than one place to acquire apps, or whether it matters if the financial transaction occurs prior to downloading or after the app is installed.
Historically it was true in the US too. When I first graduated, some big companies still had pension plans they'd try to entice you with.

I'm sure there's a direct link between increasing salaries and the prevalence of job-hopping.
Not sure I follow the 'illegal' part. Code is law here, right?
Yes I do plan on jumping around for a while to see if I find anything else that tickles me.
Actually pg_tgrm, like all things Postgres generally, is superior. It can rank searches by similarity (e.g. proportion of query trigrams present in the matching column's trigrams) and SQLite doesn't, which is a dealbreaker when dealing with anything that potentially includes typos or mutable word order; in many situations you wanna match (or rank high) 'Johnny Doe' when the query is 'Doe, John', also considering that languages with clear markings of grammatical case rely less on word order (like most Slavic ones) pg_tgrm is a godsend for properly hitting rows with such user input queries.
AH! Ok, I think I distilled it down to something simpler: It seems to be similar to the difference between "I would've been spoken to" vs. "I would've been being spoken to". Is that correct?

Ugh, I have to admit it seems technically "correct" after all :-) but with such a painful (and uncommon) sentence structure that it makes you question if it's right...
Which doesn't really address their point about uniqueness/transferability.
You have to love this comment partway through the Linux/BSD deployment instructions, which read slightly more like the Borg manual than compilation docs:

> Please note that your APE binary will assimilate itself as a conventional resident of your platform after the first run...
I think by the most deterministic view of human behavior everything boils down to inequalities of opportunity, but that may be a little reductive.

I was looking at this more in the Rawlsian sense of “everyone should have the same chances, such that if they had the same ability they could achieve the same thing.” I don’t think I (or most “meritocratic” societies) believe that social equalizers should completely eradicate differences in outcome that arise from innate differences in ability—but perhaps those differences should be somewhat reduced.

Concretely: if the same person were born rich or poor, they should be able to achieve mostly the same things. But if the same person were born stupid (or lazy) or smart, it’s probably ok if there is some resultant difference in outcomes, as long as all outcomes support basic dignity and needs, right?
Not that I disagree, although I feel the problem here is that this clause then can apply to all types of softwares. And even hardwares too. Just think if tomorrow Apple says that you cannot talk about degradation in performance in iPhones (because battery capacity reduces over time or something). We both know this, like we know that a user's experience will differ from the other. A company shouldn’t be adding a clause to prevent talking about this, it sounds like a malpractice to me. (I know it’s not that serious but still…)
Yes, of the six letters lost from the English alphabet, thorn and yogh are probably the most consequential for the spelling mess. In this, though, we can safely blame the French. ;)

https://historyofenglishpodcast.com/2016/12/07/episode-87-th...
Some people believe the earth is flat, too.
https://news.ycombinator.com/item?id=27061789
> So what isn't possible is having two threads push/pop to the same conventional stack. So I assume the author is doing something different.

Indeed; what they're doing is building up a command object that represents a sequence of modifications to a stack. And that's something that you can parallelise, map-reduce style: they've come up with a representation for that command that makes it easy to combine two commands into a bigger command, and a technique for doing that combine in-place without needing extra scratch space. This doesn't need any synchronization between parallel threads - of course the final result is only formed when all the threads finish. (To materialize the final value of the stack you'd have to "run" the final command, but it turns out that's trivial for this command representation - just confirm that the number of pops is zero, and then the push sequence is the final value of the stack).
Viral or scalable in business/tech terms, means things that can be sold multiple times. Often times the value is already created and rewarded. In our economy we're not only incentivizing value creation but also building walls around innovations and gatekeeping the fruits of them, so that the innovators, the software developers like you wish, or whoever can earn royalty while no longer innovating.
Not really sure why you're being down voted, you're right.

And yes I eat and drink to cope with my problems, but knowing what the problem is often no enough to fix it.
Long time ago now, but we had disks just unmounting and mounting at free will.

As someone said by-label is not stable and could be changed, causing problems. We still use it though but not in customer facing servers where these problems arise. Maybe related to lvm/snapshot etc.
> No, they mean 192KB. Because that's how they refer to it literally every other time.

Are you suggesting that you believe that both the number and the unit were a typo?

> Oh, and because it's NOT 196 thousand. 3072*64 = 196608. Which rounds to... 197 thousand.

Truncation is a totally valid way of representing numbers when pinpoint accuracy isn't really necessary. "32K" is a very common way to refer to the number 32768, for example.

> or 192KiB if you prefer that sort of thing

I appreciate the caveat here as I very much do not and believe that the concept of kibibytes being distinct from kilobytes are a scam perpetuated by hard-drive and floppy disk manufacturers as a way to cut costs while still advertising the same storage space. It definitely makes sense to use the same definitions for the SI prefixes, but even two decades after that ISO was published no-one actually says "kibibytes", so clearly it's not much of a standard.

But that's another discussion entirely.
Interesting. Thanks.

Then my explanation of the observed phenomena is likely wrong either partially or fully.
> By default every popular distro before systemd/upstart did

RedHat and friends, Debian all used convoluted init scripts which somewhat validates the need for systemd.
yes, cause that language is a clear priority.
I think what is happening is that people in general, not only software engineers, are getting paid much more and sometimes less because of increasing impact due to tech/globalization scaling and winner takes all network effects.

Look at how much some YouTubers make. Due to the Internet, they can reach far more people than before and make far more money. Also, their popularity begat more popularity without commensurate additional work on their part.

The same is happening to tech companies. You have that same power law with a few at the top making a lot of the money. It applies to YouTubers, tech companies, software engineers at those tech companies, etc... The rise of tech billionaires is another manifestation of this.

Of course this is creating a lot of pushback from other parts of society that are sometimes actually losing influence, money, etc... since there is a negative feedback loop on the other side.
For a custom build it's simply difficult to cram all of that in if you want a very small form factor.

You may want to look at the DEC840 (AMD EPYC Embedded 3101) or DEC850 (AMD EPYC Embedded 3201) that uses Deciso's Netboard A20 and is sold on the OPNSense website's shop. It has two SFP+ transceivers and four 1GbE ports in a 199x186x46mm form factor. It is entirely passively cooled (the enclosure itself is a giant heatsink) and contains zero fans. They don't yet have this available for sale in a 1U rackmount enclosure, but I assume it's in the works.

From what I've heard it tends to use about 15W or so of power at idle and more around 20ish under some real loads. Not bad for something that can supposedly shove 2.3Gbps of IPsec VPN traffic!

It won't cover all of your use cases, as it would require a custom build, but if you're looking for a super beefy router (that you can just connect to an aggregation switch) it's an option. You could probably use it for the next 10-15 years and it'd likely still serve all of your needs.
I have the opposite problem. I started writing content, then started writing custom markup to convert the content to HTML. But I started having so much fun writing marked-up content, it took over. So I have a content surplus.

I know from past experience (personal and that of others) that getting content online is fairly easy. The part I don't get is how to find an audience for content that 'is good' - but doesn't have broad appeal. Publishers know that stuff, who else does?
I find it weird that many English natives try to claim that English grammar is in fact complex (you are by far not the first). I think it might be because in general many don't speak another language and the most common second language is Spanish which has also a very "simple" grammar.

Regarding your example with the gerund, yes it is subtle, but similar subtleties exist in German, e.g. The difference between perfect and simple past (also exist in English), which many native speakers in both English and German get wrong as well.

An interesting anecdote (which might be related) is, that in my experience having gone to high-school in the US for a year and having done language courses with Australian teachers, that there seems to be much less education on the grammar of the language than in Germany. I often knew the "theory" of English grammar much better than the native speakers (doesn't mean I was better at applying it though).

All that said, mastering English is still difficult, just not due to the grammar. Spelling is one thing, but also the vocabulary is huge. Supposedly Shakespeares vocabulary was 60000 words, the equivalent German poet Goethes was less than 40000.