skysight-inc/HackerNews huggingface dataset:
No you think it would be in the users' interest but it absolutely isn't. I'm willing to bet money you haven't looked at launchpad's source code at all. Nor have you or anyone else considered operating their own. That is how most of the Ubuntu based distros right now are already getting their software.

If Canonical goes down, a huge part of the usable linux market goes down with it. Possibly Linux Mint too, unless im mistaken.

>vendor lock-in

You are not vendor locked in. You can install flatpak, install via apt, appimages etc... Canonical doesn't ban the removal of snapd from ubuntu distros.

In fact, from a Linux dev I would argue that half the fragmentation for pointless nonsense like packaging and distributions has harmed the community far more. Namely because it's increased the cost of development for these things to a degree that companies won't even bother developing/publishing software on Linux. That has been the primary problem for Linux so far.

Canonical is actually getting first party support from major publishers and people still lampoon them. This includes publishers in the past who never would have considered publishing for Linux before.
That sounds more like what I'd pay for a round-trip economy ticket to Europe and there are probably going to be other costs for lodging etc. associated with the ship. But, fair enough, like (sometimes) long distance train, air isn't necessarily hugely cheaper.

(And, yes, business or first class that you actually pay directly out of pocket for is priced like a luxury good. Of course, you can pay a lot more for the cabin too.)
Is anyone else annoyed that Mozilla chose to spam them with an ad for this new feature via the email address they received when creating the Firefox sync account? Is this really such an important thing that warrants sending an unsolicited message to every Firefox user's inbox?

Yes, the footer says "You're receiving this email because .. is subscribed to Firefox Account Tips." and indeed I can now see that setting in my Firefox account. I'm sure that checkbox popped up sometime after I created the account and was conveniently set to "true" by default.
> If anyone is missing a rib

What do you mean by that?
As a user I don't like neither Snaps (that for sure as this is Cannonical only) nor FlatPaks (as they seem conceptually a "80% solution" which combines the problems of package systems with the problems of self-contianed apps, but don't improve on anything).

For me the only acceptable solution besides proper .debs are AppImages. AppImage doesn't try to "replace" the package management for desktop apps like the former two candidates. It tries to complement package systems for some special cases (like for example commercial software, or for the cases where the user "just wants to try something out" without "polluting" the whole system with a lot of dependencies).

For my desktop needs AppImage is like "Docker, the good parts". A simple self contained format that runs everywhere without any further dependencies. Compared to that Snap and FlatPak are bloated annoyances.
Blindsight: A strange neurological condition that could explain consciousness
I think we need a systems approach in Ag ..in both small or industrial farming..too. So we can achieve systems level results.

Software can be helpful but it’s enhancements contribute very little to the profit margins.

Take for example this cost analysis of orient eggplant for 2005(I picked this eggplant because it’s not a commodity crop grown by industrial Ag and is niche. In other words, it’s not like lettuce or strawberries or corn or soy)

http://sfp.ucdavis.edu/crops/coststudieshtml/BpEggplantOrien...

Check the percent of labour costs and capital/equip costs wrt operating costs. Software will help as part of the bigger systems approach, but at the end of the day, the urgent problem we need to tackle is labour costs and labour availability.
It's an app for personal trainers to help them organize their business. Not a big niche, and there are other apps in that space.[1] That one is from Fitii, which has software for trainers, customers, and gyms, talking to each other. Crunchbase shows Fitii as being from Melbourne, AU, with "1-10 employees". In that situation, VC funding seems unlikely.

[1] https://www.mypthub.net/
I would do what I've been doing on the side for years!
I am freeing people from advertising and M$- Windows!
Preferably DEBIAN ;-)
That's correct. The reason for this is that they foresaw using the CPU for multi-tasking with each application using it's own code, data, stack and zero page (scratch) data. That's also why it has relocatable code. A small multi-tasking OS called OS-9 was written and released for it:

https://en.wikipedia.org/wiki/OS-9
Rust team is going to replace whitelist with allowlist
These phenomena make me twitch.
> Basically, dating in our modern world of few meaningful social connections is a vicious cycle for women. Men rate attractiveness on a normal distribution, women rate attractiveness on a pareto distribution. (ie. 80% of men are "meh" or worse to women.)

Is this based on the OkCupid blog? My speculation is what men on average look for (appearance) is easily communicated via online dating, but this is less so than women. I'd be interested to see what the same chart would look for people known in person, rather than just online.

> I've seen this in action in my personal and professional lives. Smart, attractive women end up implementing (knowinginly or unknowningly) a complex rules engine for screening an endless pool of available men. (Male criteria for engaging a woman online is very low.) When you are a 29 year old female only considering seriously dating attractive jewish/catholic/athiest, asian/black/hispanic/irish/white/etc men 6'1" or taller in professional jobs (generally speaking or a specific gig) who have attribute X, Y, or Z, you're screwed.

There's data showing that women care more about "dating up" in education/social class, which has negatively impacts college educated women and men without a college education. This is due to the widening gap in college degree attainment in the US between men and women[0]. The book "It's Not You, It's Biology" does a good job of going into this.

[0]: https://www.theatlantic.com/business/archive/2017/11/gender-...
The difference is that we can assume that this online-only move, unlike enrolling in an online-only university, is temporary. It does not seem reasonable to kick students out because one semester is online. It's extremely disruptive to be forced to get rid of your housing, figure out what to do about your belongings, and move across the world just to invert the move at the end of the year.
Every now and then I try a Linux distro other than SUSE (currently, openSUSE) and am left disappointed.

Mostly it is the size of the repo. openSUSE has everything. I guess that shouldn't be too surprising, the Build Service also builds packages for distributions not their own: https://build.opensuse.org

And of course there's really nothing as good as YaST for system configuration.

They also provide a full aarch64 OS for the Raspberry Pi, something which is surprisingly still quite rare.
This is to be expected because, due to biological differences, male and female mammals have different mating strategies: https://en.wikipedia.org/wiki/Strategic_pluralism
Can you recommend further reading on said outlawing?
As I kind of alluded to in my comment, I'm not sure many of these things need to be web apps. OS level sandboxing has come a long way in the last ~10 years, and need fewer of the benefits of the web (like publicly addressable resources), and more of the benefits of desktop apps (like filesystem access). Web tech is improving its support for the latter, but I think we could do better if we designed a system today, rather than using one mostly designed between 95-05.
> never really found a good ios app

If anyone is looking, Strongbox and Keepassium are both good.
You're quite right, but domains are fairly unique in that not renewing one lets someone else come along and pick up in the exact same place and "appear" to be the same entity that had the domain before. Phone numbers are another, but they're somewhat difficult to monitor for cancellations and then try to grab (it can be done as I've done it for a past employer, but it's not the same level of ease as a domain).

Even failing to renew a corporate franchise with a state "only" has the consequence of that corporate entity being administratively dissolved. While likely catastrophic for that specific corporation, if "Example Widgets Ltd." fails to be renewed, I can't come along and register "Example Widgets Ltd." on the corporate register and then ring up the bank of the former Example Widgets and say "hi there it's me Example Widgets please hand over checking account."

All of that said, I don't know if there's a better way to handle this. If we assume that domain names must expire--which we currently do, and I can make an argument for and against that assumption--then what's next? It's expired but never usable again?

Good thought experiment for the morning to take my mind off of COVID's impacts on transit funding.
I just switched from MacOS to Mint Xfce on a Razer Blade Stealth 13. Really wonderful OS. Donated $50!
The US immigration problems are just virtue of having huge borders, especially land borders, with developing countries.

Canada, Australia, New Zealand are all quite far away from developing countries and access is much harder and much more expensive. Australia, which is somewhat close to Indonesia has adopted some... unsavory methods to mitigate this: https://en.wikipedia.org/wiki/Australian_immigration_detenti...

So it's not purely the points based immigration system that differentiates between the 2 situations.
I'm taking that as a no. And suggest you get to know some black people.
> Added support for Ubuntu 20.04 LTS on x86_64 platforms.

Huh? I've been using CUDA for a while now on my Ubuntu 20.04 machine
My belief is that this is just false. My basis for that belief is experience with ACM and Usenix program committees, which I've participated in directly, and have talked to peers who have as well; I also chaired one cycle of a Usenix proceeding, and so got to see how a fairly large set of reviewers actually worked. I am not including my experience as a reviewer for non-academic conferences.

To be specific: my experience is that reviewers allocate a very small amount of time to reviewing any particular paper, certainly not enough to reliably spot faked research results. Most of the work of reviewing is simply ranking papers, reducing an intractable set of submissions down to a tractable short list. Submitters are lucky to get any substantive feedback at all (hence the "reviewer #2" phenomenon).

If you have countervailing experience, describe it. Where have you reviewed, where you believe that program committee could withstand "red teaming"?
The GP mentioned that the title originally included a "rib". We took that part out of the title. Some people might read the GP comment and wonder what it was talking about. When we make a change to a title or URL and notice a comment whose meaning is affected by the change, I try to reply with the missing information.
I think that men do in fact filter just as heavily as women.

They just use looks as a massive first filter.

And people from certain backgrounds also use that background as a major filter.

Anyway, what happens is that women are invested less in the beginning, but as the relationship progresses it switches. The woman gets more attracted than the man, and starts putting up with more than him to keep her investment.

Baumeister and Tice did some daring studies:

https://www.psychologytoday.com/us/blog/insight-therapy/2013...
I think this overlooks a good many points. For example, the "being the initiator is always better" claim would be more accurately framed "having been the initiator is always better". The data completely ignores the downsides because it only looks at the potential results, not the path to get those results.

Yes, if you're willing to face repeated rejection, if you're willing to bother people who aren't interested in you and ignore the guilt of having done so, then it's better to be the initiator.
That is, as long as the package publisher distributes the source. While it's the case for the some standard repositories, packages in "restricted" (some of "multiverse" too) and third-party apt repository can be published in binary-only mode. You have no ability to at the source in those circumstances, even if you apt-installed them.
The two things (fly-by-wire control system, and linked controls) are not mutually exclusive.
samesame

also;

* rank up the cache settings in mpv to prebuffer the whole vid

* see the ytdl-format setting in mpv.conf to select a codec that your machine can decode in hardware for enhanced power efficiancy (lower fanspeed)
> if this criticism bothers you, then you should never install from any third party apt repositories ever.

This does not follow at all. Third-party apt repositories work just like Ubuntu's apt repositories; you have just as much ability to audit, hold, pin, etc. in both cases.

If there is a difference in reliability (software from third-party repos is more likely to break your system--and, btw, software from Canonical's repos has also broken systems in the past, so "avoid third party repos" is not a guaranteed way to avoid software breaking your system), using snaps to install third-party software instead of third-party repos does not fix that problem: the third-party provider is still just as unreliable as before and their software is just as likely to do something stupid.
I think Google realized they needed a compelling cross-plattform solution because React Native started to gain so much traction.

In terms of migrating away from Android, I think they will use the newer AndroidX packages as the future abstraction layer, which would enable them to replace the underlying runtime with something more native for each platform. It would be a compilation target for Kotlin as well as Dart. All while not deprecating the massive amount of production code out there. But, this is also just a guess.
Microsoft's Project Freta: Free service spots rootkits lurking in cloud VMs
Acc means accumulator and is a standard name when using e.g a fold/reduce functor.
That being said, single letters or non standard abbreviative variable names are a cancer to code clarity as the semantic of what they denote become unaccessible.
I am not so sure. My wife is European and she is very much inline with always going upwards. I on the other hand very much enjoy work life balance as well as making sure I enjoy what I do even if I make less than I could elsewhere.
True but this is a better argument for leaving. They will retain you without ad income largely because that is valuable to them compared to people leaving their platform and what a group of actual non-spectators might entail afa the marketplace.
The n+1 query problem arises from having an API that doesn't let you express the full query that you want so the server can send you back all the data in one go instead of N+1 goes. The n+1 query problem arises naturally from bad API design. That's a spec problem.
Github Link
https://github.com/Microsoft/project-freta
And the chart actually looks very close to linear
The PSU Grievance Studies Affair [1] had the same objective as the 1996 Sokal Affair: to test peer review by submitting obviously bad papers that should be rejected, and seeing how many of them are accepted.

The motivation behind this is entirely reasonable. Bad "true negative" as well as known-good "true positive" articles ought to be regularly submitted to every peer review process as a test of accuracy. A great example of a similar idea was the 2014 NIPS consistency experiment [2].

However, there is a problem with the "dog rape" hoax article [3] as a test of the peer review system. Specifically, the author in that paper claims to have spent over 1000 hours carefully cataloguing the behavior of ten thousand people and dogs over the course of one year. The paper then proceeds to produce silly but surprising statistics: female dogs are 70% more likely to be leashed than male dogs, 100% of dogs with shock collars are male, 847 instances of dogs fighting were observed, and so on.

The problem here is that the data was falsified: the observations and experiments claimed never happened, the numbers were all made up. The article was likely accepted because of its data, but the data was a lie. If this data had been real, it might have been a minor but useful study relevant to economists, sociologists, or urban planners, regardless of how silly or made-up the conclusions at the end were.

Peer review works based on the assumption that the author is telling the truth about what experiments they conducted and what numbers they measured. The grievance studies authors could have submitted fake and silly hoax papers without falsifying data: that's what Sokal did, and that would have been a valid experiment testing the peer review system. But that is not what the authors chose to do.

[1] https://en.wikipedia.org/wiki/Grievance_studies_affair

[2] http://blog.mrtz.org/2014/12/15/the-nips-experiment.html

[3] http://norskk.is/bytta/menn/dog_park.pdf
Agreed, that’s 4 round trips to Google from my main box at home! You can round-trip ping nearly halfway across the U.S. in that kind of time.
I noticed CUDA 11.0 was almost ready for release last week when I went to install CUDA and the default download page linked to the 11.0 Release Candidate. The 10.1 and 10.2 links were buried behind a link off to the side labeled "legacy". The thing is, no library you use is going to be supporting the CUDA 11.0 RC, that's ridiculous. For example, Pytorch stable is on 10.2 and Tensorflow only goes up to 10.1.

This is generally indicative of how poorly organized the CUDA documentation and installation instructions are. The Conda dependency manager has made this a lot easier recently. Especially by, e.g., providing pytorch binaries. Though if you want to use packages like NVIDIA Apex for mixed precision DL[0] you're going to be in for a huge headache trying to compile torch from source while also managing your cuda and nvcc version, which sometimes must be the same but sometimes can not be![1]

[0] Yes, I'm aware that Apex was very recently brought into torch but it seems that the performance issues haven't been ironed out yet.

[1] https://stackoverflow.com/questions/53422407/different-cuda-...
Having recently chosen a Qt stack for cross-platform desktop development over Electron, I'm happy to see that Flutter is now a real contender in this space.

I'm curious about Flutter and Dart bindings and calling interfaces for other languages. If you can integrate a Flutter front end with a back end language of your choice, that would change a lot of things for the better. The only reactive UI offerings for cross-platform desktop development with multiple language bindings are QML, which is great, or Electron with React, which is not so great if you want to use anything but JavaScript for your back end.
You just don't throw everything in a big build method, but make small functions for every logical unit instead. Simple, easy, clean and maintainable.
Seems like the most compelling evidence of racially-disparate treatment is that she got no responses when reaching out via her own email address, but received some responses when reaching out via her husband's (he is an Asian-American man with a recognizably Asian name). Assuming the emails sent were identical, this would be pretty solid evidence of bias.

One potential confounding issue is that her husband is a former Google engineer, and she doesn't mention having any similar experience. It wouldn't be surprising if a VC's vetting process involved checking linkedin to see what experience the person had, and giving points to former FAANG engineers (note: I am not in this category).

Regardless, it's still pretty lousy that VCs that claim to want to help certain types of founders don't even respond to inbound inquiries.
Is it? Is there some kind of comparison with metrics? In my own use I found it to be pretty good, but I have no idea what else is out there.
I agree with the sentiment, but worry that lots of people are doing this and each group is using different names. I wish we would come to a consensus.

For me, I'd prefer stoplight colors. Redlist for stopped, Greenlist for those who can go through, and maybe even Yellow list who can go through but maybe have limited permissions or increased security.
You haven't even explained how it's vendor lock-in. Canonical has no way designed their approach to ban the use of apt, rpm, deb, flatpak or appimages. They are in no way of a position to dominate the market in the way Google does with Android and it's stupid to even think that is their aim.

It should be pretty obvious to you why they aren't exactly going to claim 30% commission on nothing from users who are as cost averse as possible. It should be plainly obvious to you also how they don't have the clout to bully software vendors to publish for them.

They have already plenty of evidence that profitability of distribution of linux software isn't exactly a lucrative market like Google or Apple. The fact that you think that is their aim or that it is feasible in the FOSS Linux community with large scale players like Google/Microsoft/IBM is ludicrous. Canonical tries to attempt to get such vendor lock-in and they would lose so much marketshare apps on their store instantaneously. They aren't even in a position like Apple/Google/Microsoft here who charge money to publish apps.

I have already explained how that argument is complete nonsense.
It seems like people out there are using "this phenomena" to mean "this phenomenon."

I say this not to be rude, but to note that if we needlessly scrutinize each other's grammar, no one will be happy.
Columbus’ poor treatment of the natives is a popular myth. He actually rigorously promoted their well-being (to the disappointment of his men), to the point where his soldiers chained him and sent him back to Spain on a boat to be rid of him.

This author (a practicing anthropologist) has a book going into more detail about his treatment of the natives.
> They want to make it as easy as possible for users to install trusted/safe software from both proprietary/free vendors.

Canonical deciding that Ubuntu won't allow third-party Snap repositories is completely orthogonal to open sourcing their Snap server and/or making it easy for people to develop alternatives. They can perfectly well do both.
One factor that I didn't see addressed in the post which does make a significant impact is that men in general rate women more similarly than women rate men.

See for example:

https://www.marketingcharts.com/demographics-and-audiences/m...

As such, male advantage is probably a lot lower in the real world, if (hyperbolic) every woman has a different man on nr 1 of their preference list, and every man has the same woman as nr 1 of their preference list, all women could theoretically have their best possible partner, while only one man can.