skysight-inc/HackerNews huggingface dataset:
Anglia (which is currently in Germany) wasn't a Danish speaking region until well after the Angles settled in Britain. Which was well after the Roman period. They spoke Old English.
Ross was dumb enough to get fake passports/ids shipped directly to his home address
Not long ago at $JOB I sat through what I call "mandatory psychobabble day". The particular psychobabble being peddled to, or rather, imposed on, us was the DISC system -- a variant of which was recently outed on Hackernews as pernicious hucksterism which somehow held much of Sweden in its sway. It was supposed to make us better collaborators, under the rubric that understanding the traits of both your own star sign under this 20th century horoscope and those of your coworkers will enable you to formulate better communication strategies. Oddly, the most fruitful discussions that day, or at any time at $JOB, were held without reference to DISC at all.

My single moment of satisfaction was in trolling the interlocutor at the end. He still recognizes and smiles to me in the halls, which tells me my trolling was sufficiently subtle.
For more complex state handling in SPAs (subscription, event handling) re-frame is a really great framework based on reagent/cljs.

https://github.com/day8/re-frame
Flavoring: Flexible Nominal Typing for TypeScript
This is a lot more than just Napkin Math. He writes a synthetic benchmark to demonstrate the orders of magnitude difference in performance you can see depending on how you approach a problem.
yeah i used this for a while https://www.npmjs.com/package/tiny-state-manager
I sure hope so, as growth cannot be maintained indefinitely.
In general, Yes this is a big issue when dealing with colors. One example where you run into this; is when you'r reducing color space from say 256 to say 12 color space (most common colors). Using LAB really helps but still not perfect.
That's probably true, but death isn't the only negative outcome. I'm regularly buzzed from behind by bicyclists passing me at high speed on sidewalks. It's quite unnerving, since most of our local cyclists are idiots, generally untrained, unable to quick stop, and often riding without any brakes at all.

I've taken to carrying an umbrella everywhere, swinging it quite dramatically as I walk. This seems to be an effective way to cause cyclists to keep a safe distance.
The irony is compounded by the number of times "Brad Pitt in Fight Club" has been mentioned in this thread. The whole film was a screed against this kind of arms-race thinking of "I need this, this and this, and then finally, I'll have ______".
because it’s a severe illness we are all familiar with.
I am starting to agree with this sentiment, even for today.

I feel like it takes an iphone release and a set of features for Google to even consider some taken path.

I've been a long supporter of Android, by buying pretty much every released OnePlus phone and a few Nexus phones before that... (before the price exploded).

For my next phone I will be going back to the more expensive iPhone.

Everything built into Android feels like a compromise or an afterthought. The only really well built app is Google Maps. All of the other apps, like ones for messaging, calling, even the google assistant, everything feels buggy for some reason. Maybe it's One Plus? (I don't know?)

Permissions seems to have gone through several crazy iterations, but I can't seem to mute my phone, but not my texts, or mute a specific app, but still get slack updates. I know there are some new break the glass features, but it's extremely confusing.

I wish there were just simply profiles that I could just say - hey I want everything muted except slack and text messages. At other times, like the weekend, I want all apps muted except text messages.

But I can't easily do this stuff, it's just really convoluted. I don't know if my mileage will vary on iphone, but I think that's just to get away from general bugginess, voice recognition issues, "map start issue", bad data drops even when my phone has a signal.

Oh, one last thing on Google Maps - if anyone is listening, Can you please stop routing me to staff parking lots BEHIND the store I'm going to? Use some machine learning if you have to and find the best destination point.
* Container images are generally huge. Layer caching helps to the extent that layers are reusable. If you're lucky, you can use something like alpine for smaller huge images. If you write in a language that supports statically linked executables (e.g., Go) then you can get by with a scratch in many cases, but then you could more easily ship a naked executable

* Container images take a long time to build and build caching only works well if your dependency tree is linear (it's not). (Caveat: there are niche alternatives to docker build for which this may not hold, but then you're subject to the other issues with niche tools--support, docs, compat, etc)

* Your deployment target has to have a container runtime compatible with your image format. This is a PITA for end users in many cases.

* Most popular container runtimes make container processes children of the daemon process, not children of the client process. This means killing the parent process will not kill the child process, which means CI environments need to handle all sorts of edge cases. For example, a CI job is waiting on a stuck container to terminate, but eventually times out or the job is killed or similar; each time this happens a container is leaked--this means that CI tools have to support the container runtime explicitly and handle all of these edge cases because it's prohibitively complex for users to manage.

IMO the only advantage (and this is a huge advantage where applicable) for containers is that they can be orchestrated by things like Kubernetes or AWS Fargate.
Well, I'll definitely keep an eye on that piece of hardware. I do intend that the next system I buy can run Linux well. I mean I'm going to stick with it, even if it is bad.

That said.. even though I'm pointing out hardware issues I don't think the free software world should get a pass on these things. I get that a lack of corporate sponsorship can make things hard, BUT, a lot of the issues I'm running into are things that are just about having decent project maintenance.

Like, if my touchpad stops working after I close the screen, clearly they had enough info to actually make a working touchpad driver, but not enough to actually, uh, make it reliable. In most companies you have the concept of "alpha" or "beta" level of software, and I feel like EVERY component in Linux is alpha level. As long as you're 100% on the happy path your experience will be perfectly mediocre, and otherwise it's going bad VERY fast. Like I mean, it's pretty sad that the login screen is broken. I can't be the first person that plugged their laptop into a monitor! And it recognizes the monitor and works fine with it! So it's just an issue of kdm (or whatever the hell it is now) not actually being able to handle a multi monitor setup in... 2020? This shit has been old hat for 15 YEARS.

I don't know what it will take for free software to produce a decent desktop system, but I think blaming it on 3rd party companies is off the table at this point, there's obviously something not quite working with this model when it comes to producing software people can use.
> Bureaucracy always pops up somewhere

Sometimes expressed as the Iron law of oligarchy [0] or the The Iron Law of Bureaucracy [1]

[0] https://en.wikipedia.org/wiki/Iron_law_of_oligarchy

[1] https://www.jerrypournelle.com/reports/jerryp/iron.html
There are plenty of companies that have embraced the opposite of "honesty" (Enron, Arthur Anderson, and Theranos are a few that come to mind).
In TXR Lisp, I doubled down on OOP and extended the object system to support multiple inheritance, just this December.

Real inheritance of code and data allows for mixin programming, which is very useful.

If you don't give OOP programmers the tools for mixing programming, they will find some other way to do it, such as some unattractive design pattern that fills their code with boilerplate, secondary objects, and unnecessary additional run-time switching and whatnot, all of which can be as brittle as any inheritance hierarchy, if not more.
Yeah, this is a nice LaTeX document. The learning curve is pretty steep at first, but Overleaf.com has made that easier, and it's well worth learning if you're a writer of any kind.
From the description:

> NOTE FROM TED: Please do not look to this talk for medical advice. We've flagged this talk, which was filmed at a TEDx event, because it appears to fall outside TEDx's content guidelines. Resonant Frequency Therapy has not been proven effective by scientific research.
It seems like the peer review process is more likely to establish importance than correctness.
It's important to always remember the context that SOLID is a collection of one man's opinions.

When we mix classes to create a new class, the ingredients in the mixture retain their adherence to their respective contracts, and we didn't have to re-implement them.

> I mostly only use inheritance for patching the behaviour of some code.

That's good for you, but you have to realize that classes specifically designed as inheritance bases are also a thing and the experience of using those kinds of classes with inheritance is not the same as deriving from any random class whose behavior we don't like in some aspect.

The conventions by which a class supports inheritance are also a form of contract! The contract says that if you derive from me, you can expect certain behaviors, and also have certain responsibilities regarding what to implement and how, and what not to depend on or not to do and such.

If a class is not designed for inheritance, then there is no contract, beyond some superficial expectations that come from the OOP system, some of which can fall victim to hostilities in the way the class is implemented, or maintained in the future.
I don't have enough adjectives. This is now SOP, everywhere. Current Affairs had this scathing article about a different waste of money:
https://www.currentaffairs.org/2016/06/the-unendurable-horro...

And this 2003 article from the LA Weekly gives a jarring glimpse into Mouse mentality:
https://www.laweekly.com/keepers-of-the-magic-kingdom/
I feel like this is a lesson everyone in tech gets by their second or third job. If you haven’t gotten this lesson yet, hang tight, it’s coming.
Tool to give to high-performing charities and track your impact
Most programmers want to build new things, not work on maintenance projects, regardless of tech stack.

That said, many people do enjoy that sort of work and finding them is not unusually difficult unless the project is so big that you need dozens of bodies.
> I don’t care about thin or light at all. I’m happy to carry a few extra pounds; these are my tools, and if that’s the price of durable, maintainable and resilient tools means a bit of extra weight in the bag I’ll pay it and smile. I just want to be able to fix it; I want something I can strip all the way down to standard parts with a standard screwdriver and replace piecemeal when it needs piecemeal replacing. Does anyone make anything like this anymore, a tradesman’s machine? The MNTRE people are giving it a shot. Is anyone else, anywhere?

If durable, maintainable, and resilient are your number one priority, maybe you want a desktop. It is trivial to open up the case and replace or upgrade components. Desktops also tend to last longer than laptops. It is harder to transport, but I am sure just like the various mechanics, you can come up with a rolling toolbox for your desktop that you can load into the back of your pickup truck. As a bonus, you can also get higher performance CPU's since you can deal with the heat better in a desktop case. I am sure that such a risk could easily last you 10 years, and it does seem like the perfect choice given your priorities.
Why Astra built a space startup and rocket factory in Silicon Valley
Here's one example showing why people might be reluctant to speak out about wasteful training: (Sorry, this is a bit long!)

Early in my PhD, I was made vice-president (or something like that; I don't actually remember) of the university's Society of Fire Protection Engineers (SFPE). This title was really only a formality as there were no duties aside from some training that the university required. The organization existed mainly to get external speakers every once in a while. The organization was purely professional. Keep this in mind.

The most annoying training could accurately be described as "frat boy training" in the sense that it seemed to be targeted specifically at heavy-drinking fraternity members. The training lasted about 2 hours as I recall and had to be retaken yearly. It involved groups of roughly 100 people watching videos and participating in discussions about (basically) why you should call for medical help if someone passes out after drinking too much. (There were some other lessons, like telling us to call a certain phone number to report on people who seem to be "suspicious" but are not breaking the law.) The entire event seemed to be motivated by lawyers' desire to reduce the university's liability in the event that someone drinks too much and dies.

The first year I was in a leadership position in the local SFPE group I attended the training and thought it was a huge waste of time. None of the training applied to our group. We never had any social events, much less ones with alcohol. Plus, I don't need to be told to call for help if someone is obviously in medical trouble.

Given that, in the the second year of the training I arrived early and politely asked the presenter about why my group was required to attend this training. The presenter responded rudely along the lines of "Of course you have to take the training. Sit down and do it." Not only that, apparently they had a panic button, because soon after that two security folks came in to escort me out of the room for being belligerent. (I don't recall the presenter doing anything that seemed to indicate they were calling for security.) I was really struck by this because I was polite the entire time and was actually going to take the training again.

After being removed from the room, some admin came down to chastise me. I carefully explained to the admin that I don't believe this training is relevant to my group at all, particularly as one of the only graduate students in attendance. The admin continued to chastise me, and told me that I would have to reschedule my training for another time even though I had not missed much as I recall.

Later the same admin contacted me to tell me that yes, in fact, my group was misclassified, and we will never have to take that training again.
Long Term Support means a lot more for a drill where the requirements for drilling don't really change decade to decade.

Supporting computing devices over longer periods than 5-10 years just doesn't really provide much benefit because of the exponential growth in computing power. What we do with that power may appear to be growing more slowly, but software really does do a lot more than it used to.

If you want that level of long term support, you're likely doing it for business, in datacenters, and things like mainframes are an option. For those you can pay a bit extra and get that level of support, like the drill battery adapter.

The comparison being made doesn't seem to hold in such a different market. Your drill doesn't need to go twice as fast to be useful today as it did 2 years ago.
As described in the article, I believe it's more on the advertising side than beating the monopoly for a great cause.
Yeah, I know the history of the terms, I just find them so entirely unhelpful for (harmful to, in fact) understanding Redux, no matter what reason they're there, that providing a translation is pretty much the first thing I do when introducing someone to it. Figuring out what the terms actually meant was the moment I went from "what... what is this thing doing?" to "oh it's a couple very simple things I already understand, no big deal, got it now".

> Finally, you _can_ reference multiple parts of the state tree in your reducer logic, but you have to explicitly set that up yourself [6]. The `combineReducers` utility is meant for the standard use case of defining update logic by domain "slices", and it's up to you to write custom logic if you need more specific behavior than that.

That's cool though.
I know that I regret being talked into doing one of these DNA tests (my concern is privacy-based). I have since requested that my data be deleted and have opted out of everything that I could opt out of, but I'd be a lot more comfortable if I had simply never done it.

When people ask me what I think of these tests, I advise great caution and that they think hard about the cost/benefit tradeoff that they're making.
Did you include section 2.1? How modified is your version?

It's hard to say without the exact contract.

Ask a lawyer
WHO alarm re: new coronavirus cases in France&UK without travel history to China
Okay, and?

By that logic, the government shouldn't ever have to describe its investigative methods and prove they both comport with the law and accepted science because if their investigative methods are known then criminals benefit.
I'm one of those "old dogs" who don't quite get the advantage of using React in the majority of the cases it's used. This article didn't really help...

> What makes these frontends complex?
State management. The frontend “knows” a lot of things, and these things interact with each other in non-trivial ways [...] Example: dark mode support. For example, say your app has a dark mode. All your rendered components must know what theme is on, so they can render the UI in the right color.

Back in my day.... you'd slap a class on the <body> tag, and you'd have all you'd need for your CSS to style the rest of the page accordingly. How is using Redux an improvement here?

None of the examples of "complex" front-ends would be at all difficult in an old-school "just re-render the page" setup using something like pjax or turbolinks. And in my experience (seeing web pages with > 1MB js files) it'd be faster/more responsive for the end-user too.
Digital nomad: this is the reality of living the ‘dream’ Instagram lifestyle
Nobody asked for stupid native-level functionality nonsense in the browser.

It takes too much Javascript, which is not efficient to parse or run, and is usually wasted on "looking/feeling fancy", not actual functionality.
>Its also probably harder to hide deaths than recoveries, so the mortality rate is likely lower.

1) you obviously mean Case Fatality Rate, instead of mortality rate, since the latter is independent of number of recoveries when keeping deaths fixed (unhideable).

2) What would China's motive be to hide recovered infection counts with the result of reporting a higher than truthful case fatality rate? Do you actually believe China wants local panic and fear, or that it actually wants to loose 2% annual productivity per week in quarantine?
> it's not legal to take

How about to copy?

I think that a better comparison would be with an armoured truck having left open its doors and spilling top secret documents all over the road.
You pay for TV and still get ads. I'm more than happy to pay to remove ads but I think it's presumptuous to assume that if you pay any amount of money it's expected that it will be ad free.

I mean Red Hat has ads in their RHEL installer.
+1. It's kind of jarring at first--I kept wanting to see some sort of cut or break from the action. Quite an accomplishment, though.

Also, and perhaps inspired by this movie, the pilot for Battlestar Galactica begins with a five- (?) minute-long single shot that introduces most of the lead characters.
Reading what he's posted, it doesn't seem like he's interested in dating, but rather hooking up, and fast. Tinder is still the go-to for that, and it is by design a looks-centric platform.
My suspicion is that the worker-owned cooperative model, especially if it emphasizes the more important worker self-directed part, will tend towards much smaller units of self-organization. I predict we will see confederations and networks of smallish coops, and I suspect this is for the best.
Most insurance policies exclude willful criminal acts perpetrated by the policy owner.
The central premise of the article is that there is no disclosure regarding the vulnerability used, suggesting the existence of some unknown zero-day exploit..

Various well documented analysis have linked this incident to "EgotisticalGiraffe", a well known -- and since fixed vulnerability.

FUD or lazy journalism? I mean, at least read the subjects Wikipedia page before publishing something..
> the first iPhone was really bad

I couldn't disagree more. Sure looking back at what we have today it is easy to laugh at it but it was literally the only product of its kind for perhaps the first 9 months of its life. It delivered on pretty much everything IMHO. It was reliable and it performed well. It really did replace an iPod, phone and PDA with one device.

Honestly the only thing it lacked was copy and paste which I agree was dumb but never did I think it was "really bad" because of this omission.

People can rag on Apple for a lot of stuff but man they really killed it with completely new gen 1 device. Not even the iPod was as good a gen 1 device as it lacked PC compatibility, a physical wheel that could/would break, etc.

It took at minimum a year for any other phone maker to bring something even 50% as good as the iPhone to the market and it took them several years to match (and exceed) it.

I'm not saying the first iPhone was perfect, obviously it was not. There is still not perfect smartphone. However it was a great product and I feel calling it "really bad" is very unjust.
Firefox, Chrome. Are there any others?
Isn't it 5 persons per can?
> […] but that assumes the film covers its costs, which in Hollywood can mean anything.

Not any more. Case law has basically ripped the old “Hollywood accounting” to shreds. I’m not saying profits and losses can’t be manipulated, but you can’t get away with the dirty tricks used 20 years ago, and firms are held to somewhat higher standards.
The same is true about the evolution of language. Parents and their own kids can always communicate just fine, but across 5, 10, 20 generations it can be completely unrecognizable (see: Middle English).
This is why, despite Apple not caring about us anymore, you still see an overwhelming amount of Macs.
> try to do that with a sedan...

Well, it can be done. There's a guy who rebuilt a Tesla Model S from a pair of junked Teslas.

https://www.youtube.com/channel/UCfV0_wbjG8KJADuZT2ct4SA
Yes. My comment triggered most of that discussion.

I have really good solid evidence for another common disease being caused by infection or microbiome dysbiosis. But I am encountering a lot of resistance in the field despite my theory, models and data being much more solid than the status quo to explain said disease and my research coming from a famous lab.

I guess it's really hard for lots of people to accept most of their careers were spent chasing the wrong hypothesis.

I've reached a tipping point where I think I can only push it further and develop a drug in a startup. Alzheimer's and Parkinson's are also something I want to tackle because the mechanism is analogous. If someone wants to help or some VC is interested, just let me know. Contact email is in my profile. These diseases have a big CS / information theory component.
any mildly interesting SPA will need to keep track of state somehow. passing state between react components is more complicated than using redux.
SpaceX’s first astronaut mission could take off in May
... to get the numbers presented at the end for doing napkin math.
Does anyone know if the 'cmdline' hang she mentions ever got fixed? We still see this occasionally.
FYI, AIDS is an acronym (though the periods are dropped) for Auto-Immune Deficiency Syndrome. So all four letters are capitalized.
Facebook Workplace co-founder launches downtime fire alarm Kintaba