skysight-inc/HackerNews huggingface dataset:
Point taken, was poorly stated.

Context- I very clearly remember arriving at the benefits of the idea of immutability long before Clojure but I didn't have the word immutability or a hook in the public discourse to connect it to. There were of course related concepts and projects from the late 1990s and early 2000s- idempotent operations in HTTP, log-based file systems, packaging systems like NixOS, some PL papers- but prior to Rich's early popularity I remember difficulties on various projects in explaining this approach to those for whom it was a new idea.

I feel like shortly after Clojure and Rich's talks, the idea- the term "immutability"- achieved R > 1 spread and it quickly became a default design principle.

So the point would be better stated- can you imagine (or remember) when you didn't have the term immutability to refer in shorthand to?
On a second thought, I also don't understand why do npm in two different images, why not just copy the webpack bundles from the builder image into the nginx image ?

For me the cause of the big image size was in

COPY --from=npmpackages /app /app

From your third Dockerfile, it seems replacing the above with the following would have done the trick without adding an extra stage

COPY --from=npmpackages /app/_site/ /usr/share/nginx/html/
> If it's the only software solution it most certainly must be a good one.

We have different interpretations. For me, TPITEOTG means:

Choose one: a solution that works well but is clearly not perfect, or no solution at all.

> Do you think the presentation in a single blog post is enough information about a system to determine its quality and reliability?

Epilogue FTA:

> We created this software on a request from healthcare staffs. It is not a commercial application. Even with this system, we strongly suggest doctors to visit their patients, take real measurements.

> As this software was developed fast due to prevailing pandemic situation, we released it with the most urgent feature monitoring. We tested this for long run, with multiple devices as well. So far it worked out well.

> It does not indicate this is perfect, we are working on improvements and fixing bugs until its very stable.

> Thus we have adviced doctors to use this with CAUTION

Many of the complaints in the OP were specious for the situation in play:

> You're storing patient information in postgres. What certifications do you have to assert that the patient data is stored securely, in line with your government guidelines on patient/medical data? There's a damn good reason this is the "holy grail" of information security certifications.

This is monitoring data from dying patients in a third world country. Do you really think that they should have spent a couple months making sure hackers couldn’t access patients’ vitals before putting into use?

> You've got critical alerting built into the browser window using JavaScript.

Yes, because that is the language of the UI toolkit they are using.

> This "alerting" is the kind of critical thing that sometimes needs immediate" intervention, or someone could die. What happens if your browser experiences a JavaScript error blocking processing? And your alerts don't fire?

The alternative appeared to be that those alerts might not be noticed anyway because they might not have the staff to gown up and go into each room frequently enough.

> What happens if they fire too often and you get "alert fatigue" because they're not tuned correctly or in line with the other alerts available at the bedside/nursing station?

What happens if the device in the room fires too often?

> How much testing have you done to correctly assert that you're interpreting the HL7 or other specs correctly? And aren't misinterpreting data for some conditions or types of individual?

They seemed to find that it was accurate enough for the crisis* at hand.

> The "throw things together quickly" startup mentality might (I stress might!) Be okay where it's the difference between nothing at all and something that can save lives, in a country like Sri Lanka, during a global pandemic, fine.

Whelp, here comes a “not perfect but good enough to use part

> <further hand wringing on future concerns irrelevant to the situation under discussion>
I see people adjusting their masks frequently, which is evidence against your theory.
Until Chrome stops supporting tables..

This site can’t provide a secure connectionpaulgraham.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
I can’t use Spotify(premium!) without having a freaking in-app pop up on iOS too.

I’m actually thinking about going back to pirating music and just building my own player that load things off of S3.
Sounds good, I love state machines and I often write them in C where other people would just go with ad-hoc loops and branches and temporaries. I'll keep an eye out for examples..
you can do this with s3. it’s called presigned urls
As far as I am aware, Apple had been running x86 OSX before even Steve knew about it. So the 5 years double life secret agent was merely a marketing pitch. The whole story was written on cake.co

But what was clear though was Steve wanted a notebook, and Intel Centrino was the perfect fit. And the roadmap from IBM was a dead end. And it was very obvious, ( unless you belong to those group that does not believe in Notebook market) that switching to Intel was the only choice.

But this time there is nothing ARM / Apple CPU can do that Intel cant. The only real advantage Apple get is cost reduction. Intel isn't like IBM where it has no low power roadmap, and Intel's IPC aren't far behind either.
Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.
Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.
Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.
Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.

Rust good, C bad.
You forgot about the third half of the cycle: scientists exceedingly rarely submit a correction note to tone down the hyped up claims made by the PR departments / science press. They are very good at keeping the freak out to themselves. A systemic problem, not sure how to solve for, if even there is a solution.
That's super interesting and I almost want to believe that something like this could be behind the videos, but Fravor described the object as being tictac shaped with a smooth white surface, not a glowing ball of plasma. Also, it doesn't seem like a laser-induced floating ball of plasma would cause the ocean just beneath it to become turbulent and frothy, like the tictac thing did
Each Merlin Engine costs $1M.

A Raptor is expected to cost less than $1M each.

Blue Origins BE-4 is priced at $8M each.

So how did conservative NASA get cheaper RS-25 engines for only $147M each?
I think the mechanistic argument that this paper tries to make about dopamine unfortunately falls into the trap that much of popular science writing dealing with neurotransmitters makes, by using hand-waving, oversimplified explanations of how our brain works to somehow justify its sociological or cultural thesis as being based on "science". I will probably get downvoted for saying this, but Jordan Peterson's writings on serotonin comes to mind here.

This piece can somewhat be forgiven, because it takes the view on dopamine that almost all pop-sci writing takes, which is that it's "the pleasure chemical", i.e "The level of the neuroinhibitor dopamine in the human's brain rises. This induces a subjective experience of self-absorbed well being, while rendering the human quiescent". A more accurate view of dopamine's function is that it controls incentive salience or "wanting", and that wanting vs. liking are distinct attributes of our reward system [1][2]. Dopamine causes the seeking of pleasure. Pleasure itself is caused by something else. This view that the high dopamine state is associated with quiescence and satiety are in direct contradiction with observations. It is well known that amphetamines raise extracellular dopamine in the brain. Folks who take amphetamines become highly motivated, active, aroused, excited, etc. Conversely, there is a class of drugs (dopamine antagonists) which block the action of dopamine. Side effects of these include sedation and lack of sex drive.

I would have to agree with the authors in the conclusion section that "this reinterpretation hangs on the specific assertions as to the function of dopamine..", and unfortunately, these assertions don't seem to be evidence based.

I feel bad for ragging on this paper so harshly, but it struck me that their starting point was that "hackers" in the HN sense, and a select few other small groups of folks on Earth, are special, different, and enlightened, and that the vast majority of other humans are defective and afflicted with a sort of mind-virus. This is such a dark worldview, and it reeks of the kind of silicon valley exceptionalism that is spoken about on this site often.

[1] https://en.wikipedia.org/wiki/Motivational_salience
[2] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5171207/
> Is this really appropriate for a core system component to have this many dependencies?

Absolutely not. The entire OpenBSD base system can be built without an internet connection.
But you can use a custom allocator in Rust: https://doc.rust-lang.org/1.9.0/book/custom-allocators.html

You don’t have that option in Go
Technical foul: How Sudan’s warlords buy their gun trucks
I'm not involved in anything like that but to me that just sounds like a business risk you have to take when making money off of the google store.
Right. And some regulation on email providers to provide fair recourse for banned accounts would go a long way.

But I do also understand the demographics of this site and why some people here would find that unpalatable.
My problem is that there are too many inconclusive trial. Someone makes a small trial without a control group, so the result is promising but difficult to interpret. Someone else makes a small trial without a control group, so the result is promising but difficult to interpret. Another person makes a small test without a control group, so the result is promising but difficult to interpret. ...

So after a few months, we only have promising inconclusive results.

Not that all the trials are different, so it is difficult to compare them. IIRC There was a recent trial with remdesivir without good results, but they only tried the drug in patients with strong symptoms. So people asked what happens if they use the drug in the beginning of the infection.
This is pretty much a judgment of Rust:

Such ecosystems come with incredible costs. For instance,
rust cannot even compile itself on i386 at present time
because it exhausts the address space.

Consider me a skeptic -- I think these compiler ecosystems
face a grim bloaty future.

I would think that OpenBSD developers/users would care about security, since that's pretty much the value-proposition of OpenBSD.
Those jobs exist whether we build the utter waste of the SLS or not, those people will just be actually building something useful.
Besides the many responses about data size, the premise of your question is baffling to me. This is exactly the kind of stuff SQL is for, it's designed specifically for doing this kind of work. Even on a smaller dataset, the "higher level" languages you speak of will certainly be able to produce the same results, but their implementations will almost certainly be more complex, with more points of failure, a great deal less flexible (what if the dataset grows?), and a whole lot more verbose... and all you get for all of those downsides is a more familiar language.
How well can algorithms recognize your masked face?
New approach to room-temperature quantum gates
Why do these people pretend that law enforcement excess, homelessness, government overreach, racism poverty and power abuse is just limited to certain countries ???

I live in America and I have donated to homeless causes here over the years.

So every time someone brings poverty in India as a trope - I ask them to politely look in the mirror.

Poverty is everywhere - just the color of skin is different!
I guess that at the height of Windows market saturation.

I thought it was rude to pay for an OS and then have to pay separately for software to protect that OS. It seemed off to me that the guy who wrote Melissa got jail time, but nothing happened to those who sold the software needed to run viruses.

I stopped having Windows installed after Slammer hit. After almost two decades away, I got a job at a big American company that issues Windows laptops and lo-and-behold there's some seperately purchsed AV software installed.

It makes the laptop a space heater. If I don't explicitly shut it down, the AV software never drops below 30% CPU and the thing's fans never stop running. They accidentally dropped AV for a couple weeks when they upgraded my machine from Windows 7 to 10 and it shaved five minutes off a ~17 minute Maven build. I'm one employ of tens or hundreds of thousands producing all this extraneous waste heat.

My friends needle me about BitCoin's environmental impact. I ask them what the overhead of AV has been.
- production at scale

- rivalry about countries to acquire it first

- .. followed by unwillingness of low-risk populations to be vaccinated for safety reasons

- backlash after the first side-effects are found
Coronavirus conspiracy theories and Radical Uncertainty
Supply chains don't completely rewrite themselves overnight. Shutting down meat distribution doesn't help people eat. For the time frame of '2020', the meat industry is essential.
I have a learning Trello board with categories "Maybe", "To Do", "In Progress" and "Done". When I come across something new it goes in the maybe category. I also make sure to only work on something if it's "in progress" and keep the in-progress list limited to 2-3 items at any time.
> Developers in particular don't generally care about security,

Bad developers don't, but many developers do. The Rust project itself has hundreds of contributors, to the point that it feels that it has more contributors than LLVM itself (I work on both, and this is an unbacked feeling I get from the velocity of the contributions).

Point being, if developers wouldn't care about Rust, they wouldn't be developing it.
I understand the sentiment and agree to a point. At the same time, I sometimes use docker for seemingly trivial problems because the most important requirement is build consistency. I don't know how to get around using containers when I need that. I can see a static site generator actually needing a reliable build process. What would you suggest though? Just manually/automatically test builds?
40 year old rockets proven to kill 17 people and miss every cost and performance metric when they were operated.
> As a general trend the only things being written in these new languages are new web-facing applications, quite often proprietory or customized to narrow roles. Not Unix parts.

That doesn't imply "real programmers program with real languages". It implies they're not used to enrich the UNIX / open source ecosystem, which might imply there's not a real need for them in the official repositories, since they're not used to build anything else in the repository.

> Additionally, there's the allusions to the fact that the ls/grep-replacements in Haskell aren't POSIX-compliant, which I again read in the tone of "they can't be taken as serious replacement efforts."

There is real value in being "POSIX-compliant". It means programs respect an interface. If I write a script that uses "grep" or "find", I have strict requirements from them. I expect them to take certain arguments and interpret them in a certain way. If I can't simply replace "grep" with "haskell-grep" and get the same results (with stronger safety guarantees or performance), I may not have a use for them in certain scenarios.

The critique that "They are completely different programs that have borrowed the names." doesn't imply "they can't be taken serious", it implies they can't be used to replace the existing ones.
Choosing Clojure: Part 1 – Code Is Data
Yeah. Not sure about BSD, but I was wading into building the GNU coreutils and other GNU packages just yesterday. Fresh hell, they all seem to be build dependencies of each other. ‘sed’ is its own build dependency.

The whole C ecosystem is a joke with respect to builds—all dependencies are implicit; you’re just expected to have the exact dependencies installed on your system at the exact versions and in the exact locations on the filesystem that the build tooling is willing to look. Autotools and CMake are absolutely terrible; they make Python’s build ecosystem look sane and well-designed.

So no, “security” isn’t the most compelling use case (for me, anyway), it’s moving past these dumpster fire build systems as quickly as possible so mere mortals can build their own software. Specifically, hasten the day where my entire application dependency tree doesn’t bottom out in some Autotools, CMake, shell script, project.
Exactly. Actually, it created an incentive to join the insurgent.

Picture that: your skill is to organize soldiers and military operations but the only local and legal employer refuses you and denies you any pension. Did they really think they would go beg in the streets rather than join the militias in dire need or organizational advices?
Yes, public comment like this is an ordinary part of their rulemaking. You can see something similar if you read, e.g. the responses to requests for DMCA exceptions from the Library of Congress. It may seem weird, but plenty of interested parties have lawyers bring up whatever legal points they wish to raise.

But that's also why I don't see them paying attention to the wishes of the general public at all. Most of us aren't lawyers and unless we raise some legal point, nothing we say actually matters to them at all. I think it's pretty clear that they went ahead with plans they had from the start.

So whether or not Russians or other foreigners commented in a web form open to the world or not, I don't see it as having mattered one bit.
Your average high school chemistry teacher has a chemistry degree. They didn’t just take one class in chemistry in high school and become an expert.

This is a ridiculous comparison. There are a lot of things I took a class or two in that I am not qualified to teach.

Most people are not qualified to teach most subjects at s high level.

I’m a professor and there are only certain topics that I am an expert in. I could tech myself high school chemistry again, but it’s been a few decades.
Go’s pathological NIH syndrome does come with downsides. For example, there was an infamous memory corruption bug in the way they called into vDSO.
FWIW, the majority of this 150ms is bootup time and includes initializing the DOM & canvas, JITing the js, downloading & parsing the dataset, and actually running the code, which includes data downsampling & gap detection/clipping.

try to get this perf on the web, and then you can re-asses your statement. if it was easy, then every other js charting lib would not be struggling to do it, right?

for native code (or webgl), obviously this is child's play. but webgl has significant trade-offs. e.g: https://bugs.chromium.org/p/chromium/issues/detail?id=771792

finally, you cannot extrapolate from the 26k/150ms number. uPlot can draw 4.8M points in ~2000ms on an i5 with integrated gpu (after bootup amortization).
> This is pretty much a judgment of Rust:

I guess. It's really a judgment of Rust (specifically the compiler toolchain) for this one use case.

> I would think that OpenBSD developers/users would care about security,

Maybe. Again, I think "cat" and other system tools are really low on the list of priorities for anyone securing a system. Not to say that they don't represent attack surface, by any means, but there are just a lot of things to do before rewriting the utility entirely.
Deezloader is quite a miracle in that regard btw. after so many years there still are the ways to illegally download music from the legal service and that is just... something.
PC gamers. Graphic designers who can't afford a Mac workstation. 3D artists who use 3rd party render software such as Octane. I'm sure there are many other groups that I'm unfamiliar with.
Postfix is actually quite easy to configure. Exim is what you're thinking of.
Exactly. Just wait until a GitHub bug or a PEBKAC causes your private GitHub (cloud based) repo to go public and leak sensitive information (a la AWS’ buckets)
IMHO it happens mostly because of perverse incentives of AD supported media: controversial statements attract more clicks (and more revenue). Point that "masks don't work" (even if it is not stated directly, but assumed) is more controversial than: "we don't know if masks work".

With COVID-19 I see fair amount of articles when a scientist says "We don't have (strong) evidence for X" and an article hints that X is not true (without saying this explicitily).
I don't think you miss anything.

POSIX compliance is a headache which is not only hard to get right but also strongly limits your interfaces and internal tooling.

Many scripts still will run with non full compliance, but that doesn't help if you try to build for OpenBSD.

Also I'm not sure how they ended up with 400 deps for coreutils. I would have expected much less. But yes this means at least until better code signing and so on is the default this isn't at all appropriate for the base of any OS.

I just which the author would have written it a bit less mean in it's wording. (Probably was just annoyed, but sill).
There's no evidence that higher temperatures have an effect on disease transmission.
You are forgetting that the government already has your data.

You already use you most confidential data to pay taxes and divulge all income sources. So you want to give that data to private entities as well?

God.
You're not thinking of the typical consumer, who won't have a clue about why using a proprietary service could be bad until the shit hits the fan.

It's all well and good for you - someone who's aware of the risks and issues - to say "just don't use Google/Facebook", but laws would protect the average person who just wants the quickest/easiest way to get an email account or to sign in to websites.

Also even if consumers were all highly educated in the pitfalls of Google etc., major websites still force you to use Google technologies whether you like it or not. Google Recaptcha is everywhere; eBay forces you to use it to sign in to your account. Are people now supposed "just don't use eBay" now as well?
"For instance, rust cannot even compile itself on i386 at present time because it exhausts the address space."

I don't want to be harsh, but who the hell is compiling anything on i386 now? Real question, is anyone even making fresh i386 hardware that might be used by consumers, or deployed in datacentres?
Maybe I shouldn't have said that, because it's contentious, but I do believe it to be true.

I believe Rust's success has less to do with memory safety, which I think most developers (anyone coming from a GC'd language) consider table stakes, and much more to do with great documentation and incredibly powerful primitives and ecosystem such as the type system, cargo, crates.io, etc.
Which problems does it solve besides memory safety for non-GCed languages?

That’s the only relevant point I ever saw mentioned, others being already addressed by a lot of languages, for example F# and C#.
I like bat more than cat, not because it’s memory safe, but because it’s benefiting from the entire Rust ecosystem and provides features I enjoy that cat does not have.

It’s not always security, but that’s always a plus (though I have no idea if bat is any more secure than cat). I can make the same statement about exa and many of the other tools that are getting better in the Rust suite of CLI tools.
And it took them forever to get anywhere. Compare LLVM with cranelift. Cranelift made so much progress very quickly.