skysight-inc/HackerNews huggingface dataset:
If you have 20 parameters, you should probably compare the effect sizes first. If there are no outliers, p=0.05 or p=0.001 can't make the result important.

https://www.tandfonline.com/doi/full/10.1080/00031305.2019.1...

> no p-value can reveal the plausibility, presence, truth, or importance of an association or effect. Therefore, a label of statistical significance does not mean or imply that an association or effect is highly probable, real, true, or important. Nor does a label of statistical nonsignificance lead to the association or effect being improbable, absent, false, or unimportant. Yet the dichotomization into “significant” and “not significant” is taken as an imprimatur of authority on these characteristics. In a world without bright lines, on the other hand, it becomes untenable to assert dramatic differences in interpretation from inconsequential differences in estimates. As Gelman and Stern (2006 Gelman, A., and Stern, H. (2006), “The Difference Between ‘Significant’ and ‘Not Significant’ Is Not Itself Statistically Significant,” The American Statistician, 60, 328–331. DOI: 10.1198/000313006X152649. ) famously observed, the difference between “significant” and “not significant” is not itself statistically significant.
Decision Support Systems #4: How to Implement an IA Solution
Only if loan companies can freely deny loans to folks who cannot prove their credit worthiness (spoiler alert: that's a lot of lower class/immigrants/disadvantage populations). Credit is a complex problem that simple "common sense" solutions will never adequately address.
The real problem to be seen with the Versa lies in the source of its software being a better example of how to build their product.

I had a Pebble since their first kickstarter and the work Pebble did to make exactly what you are talking about blew Fitbit's current product out of the water (Even though Fitbit bought them and used their tech to make the Ionic and Versa). The Pebbles were faster, lighter, smaller, with better battery life (2+ weeks!) and a fantastic UX (By the same people who worked at Palm on WebOS). Sure they didn't have a touch screen, but they also intentionally had enough buttons to not need one. (Meaning they worked better with gloves)

Then you talk software quality, after using the Versa for a little while, the biggest problem is that its UI is such a mess to use. If you don't want to configure a watch face on the Watch, the Apple watch has that feature too and it is instant and easy to use, just like the Pebble was. Once you use everything else it's really clear that the smart features on the Versa are an afterthought that Fitbit tasked some scrum team to get done and shoved in the app in a week, marked the task as done, and moved on, forgetting that for the casual user, that is the only other thing you want to do with the app.

The other entire problem is that the Apple Watch is complex...but only as complex as you want it to be. If you never click the home button it can do everything you do with your watch with a nicer (bigger) screen, an easier, and a faster UI, and plus it has Siri and much better notification access. Fitbit is stuck between Apple and Garmin and they justy can't pick one. I imagine the Google sale would fix that pretty fast.
Thermal noise is a very high source of true randomness. Thermal heat, at absurd amplification levels, fundamentally is asking the question: "How fast are the molecules moving at this location at point in time?"

Which will affect the voltage and current on the line, which will affect the timing of the circuits, which will be amplified into uniform noise through some mechanism, generating true randomness. After all, we can't predict the location and velocity of molecules! Heisenberg uncertainty principle!
Would you expect free upgrades as new OS versions are released? What about ongoing access to support?
Try that again, but try the suggestion of not using latin characters any longer in favour of, say, the highly logical Korean Hangul writing system.

Still as keen on the idea?
Makes sense if the company could have done without the employee they would have fired them earlier.
The slant of that website is, uhhhhh, impressive, but let's set that aside and go to the primary source[1]. First, it's a self-reported survey, not a study. Tellingly, it doesn't list any absolute numbers, just "yes/no" reporting. For example, 77% of businesses reduced hours hours per-employee, but it doesn't say by how much. That doesn't seem at odds with the study being discussed in this thread. That is, hours may be reduced, but overall wages and employment remain up relative to other industries. Actually that's another interesting thing about the survey you link. It cites a 6% to 1% drop in growth rate, but doesn't compare that to other industries, as the study in this thread does. The survey also says that food costs went up (an expected result from the wage increase), but they didn't ask what the impact on revenue was.

The survey you cite seems low quality anecdata compared to actual industry numbers shown in the study being discussed.

As to your first point, no, "the minimum wage hike" did not occur in late 2018. The final increase ($13.50 to $15.00) did indeed take place near the end of this study period, but the overall increase from 2013 to 2018 (from $7.25 in 2013 to $13.50 by late 2018 to $15.00 by end of 2018) reflects a more than doubling of the minimum wage over the study period, so I think it is still a valid reflection of the impact of such a dramatic increase.

[1] https://thenycalliance.org/assets/documents/informationitems...
Mostly agreed about C, but buffer overflows aren’t an excusable failing justified by design constraints.
Why wouldn't they? As technology improves, it's a relatively small area of silicon in the chipsets.
AirPods Pro Launching on October 30
Chipotle Debuts Debt-Free Degrees for All Employees
WireGuard is a Linux module, so it makes sense for it to rely directly on HW instead of a userspace PRNG .

https://wireguard.com
Probably not possible. See: https://en.wikipedia.org/wiki/Embodied_cognition
>There are some jobs that don't create $15/hour in value. Why is that hard to imagine?

Because those jobs don't disappear when that minimum wage is raised. This has been tested by comparing the job differences across state borders where the minimum wage has been raised on one side but not the other (Dube/Lester/Reich and Card/Krueger).

>Minimum wage dictates that those jobs and the products they provide will not exist

The reality is that that it tends to dictate whether cashflow is funneled into profit margins or wages.
This isn't a technology problem, it is a geometry problem. Car pooling/sharing cannot work very well because eventually the car needs to go down some "dead end" that you didn't want to go down to pick up/drop off somebody, and that time is wasted. If you are the last one on and first one off it is great, for everybody else it is wasted time where they are not making any progress getting to their destination. Everybody would be better off (less congestion - less expensive roads need to be built) if everybody carpools, but you are always personally better off to be the one person who doesn't.

It may seem like you can solve this by just picking up in the neighborhood. However there are not enough people in any given neighborhood to make that work. This morning exactly one person (car) passed me on my way to the bus stop - I don't know if this person would go the same direction as me or not: there isn't much opportunity for ride sharing within one neighborhood.

Transit has the same problems. It solves them by forcing people to walk to the stop/station. At least everybody feels like they are making progress. They also come on a schedule which means you can't leave when you want to.
Where does this misconception come from where people think Linux users don't pay for things? If you provide a decent tool that kills pain and doesn't cost an arm an a leg, we will pay the money. Especially if there's no good alternative out there. I've yet to come across a good mail/calendar/combo that works well. Gnome calendar/contacts/Geary is getting there but it's still far off. Same with office suite. If Microsoft released Office for Linux without charging me over a million pound per second of usage, I'll gladly shell out the extra money to have decent office suite.
> Document how to build and run it.

This, especially in non-web repos (C/C++) is common mistake of READMEs and docs.

Let's take an example of XFCE-WM project [0]. The main README does not include any information how to compile it, nor provides any link to the documentation how to build this very specific code. If you will google it you might find following wiki page [1], which is general for all repositories. In the COMPOSITOR [2] file you might notice some information about flags that you can provide during building, and that's great such doc has been created, but except that document I couldn't find any information how "fresh contributor" would like to debug and test some change in code that he made in the cloned repository. Download and install some linux distro on virtual machine and then invest (1h+) to configure it accordingly to run it there? Use Xephyr (I guess "fresh contributor" has never heard about this tool)?

In my honest experience, the "how to build" step is probably included in many of repositories, but the "how-to-run" is usually lacking in READMEs and it is what I really would like to see in complex projects (e.g. desktop environment).

> Document your availability. If you have to step away from the project, put this at the top of the README, even if it's temporary. Don't drip-feed interaction - be either on or off.

One more thing related to docs and "how-to-build-&-run" thing. Let's say the project owner have some critical accident that made him unavailable to push progress of development forward for few months or longer. If there isn't any knowledge shared (docs, other contributors) then I guess the project will be stalled and possibly forgotten if there is no clear incentive to use alternative methods of repo maintenance (e.g. fork).

[0]: https://github.com/xfce-mirror/xfwm4

[1]: https://docs.xfce.org/xfce/building

[2]: https://github.com/xfce-mirror/xfwm4/blob/master/COMPOSITOR

[3]: https://en.wikipedia.org/wiki/Xephyr
> This is especially critical for cryptographically-secure PRNGs - those are things you really do not want to be maintaining yourself

My conclusion would be exactly the opposite: If your RNG is so important that it has to be cryptographically secure, you owe it to your users to put in the time and effort of maintaining a proper implementation yourself, or at the very least use an open source library that provides this functionality in software. Otherwise you're always going to be at the mercy of a potentially misbehaving environment.

In terms of entropy, you don't really need to "maintain a pool" for CSPRNGs. You either have enough entropy to feed it with, or you don't. Once it is properly seeded, you can squeeze as many random bits out of it as you want (or at least, as many as anyone would ever reasonably need). It's really no different from a stream cipher, the key is the seed, and you're just encrypting zeroes. You don't need to suddenly get another randomly generated key after encrypting 100 MiB to encrypt the next 100 MiB securely.

Another great thing about entropy is that you can't reduce it. Which is why you really don't have to spend any time thinking about whether a particular entropy source is well behaved or uniformly distributed or anything like that at all. You just have to be certain that you have overall enough entropy that nobody can guess the entire seed. So anything the OS can give you? Dump it in there. Any kind of user interaction? Dump it in there. The time? CPU jitter? Network jitter? Just put it all in there. 100 MiBs of 0s? You know what why not, just put it on top because you literally can't make it worse, only better.
Computers are made from transistors... so there's a good chance that its probably shot-noise instead.

https://en.wikipedia.org/wiki/Shot_noise

Johnson Nyquist noise is measured from resistors, and is therefore present in every circuit. Shot noise however, is more evident in transistors.

------------

I don't know if the AMD circuit is Shot-noise or Johnson Nyquist noise. But its important to remember that there are many sources of noise / randomness in normal circuits.

The funny thing about true-random number generators: noise sources are all over the place! A beginner who plays with transistors will almost immediately "discover" a form of noise, and be forced to minimize it.

With regard to "true random" circuits (of which there are many, many different kinds), they all isolate a particular noise, and then amplify it. You have to isolate a particular form of noise if you want to get a good entropy estimation.

EDIT: It seems both shot noise and Johnson-Nyquist noise are white-noise, so maybe it doesn't matter. White noise + white noise should result in white noise, but its been a long time since I've taken this circuit class...
It only took one hour
AMD no longer has a fab so can’t compete with Intel on process (though they can in theory choose someone else’s process other than Global Foundry).

Clearly this restriction isn’t hurting AMD right now! But process is the topic under discussion.
Looks like an aluminum welder on a robotic arm.

Not discounting it, because I think the simplicity of doing it that way is brilliant for plenty of parts. Plus, I bet there was plenty of trial and error to get the timing and gas settings right for something like this. Got to give them credit there. Aluminum welding is a bitch (I suck at it). So, I'm not trying to rain on their parade... but a quick google search is showing they're not alone. To be fair, I think they might be doing it better though... especially when it comes to scale. A few minutes in, I don't see anything near to their scale, which is cool.
I don't know about per-mile, but there are more crashes in the city per hour.

(that's data from the highest crash rate country where you were able see so many crashes that you develop a feel)
You can learn about a maintainer's experience with closed issues that keep being bumped here: https://www.henryzoo.com/an-issue-with-issues/

Even though I'm maintaining Lock Threads [1], I sometimes shake my head when I come across a closed issue that was locked by it, but I also have to admit that all I want is to ask a question quickly and get the information I need, without considering how my shortcuts affect maintainers.

There may be times when there's a legitimate reason for commenting on a long-resolved issue, but unfortunately most of the comments on closed issues are low effort support requests. Locking them as resolved is the best solution we have so far to avoid spending our time retriaging closed issues.

[1] https://probot.github.io/apps/lock/
Hungarian is really foreign to EVERYONE :)
Me switching to english is in the context of work, not chatting with peers in my free time. At work in tech everyone* (few exceptions) communicates in english (emails, bug reports etc) also between Swedish colleagues, so it's very natural.
I wouldn't send a text message to my wife in English if I happened to struggle with the diacritics on the device I'm on.
Pretty sure it's satirical.
> Alphabet reported that its revenue rose 20 percent to $40.5 billion for the third quarter, but that profit dropped to $7.07 billion. Profit ... was hurt by rising costs for research and development and marketing, the company said.

> Google is spending heavily to hire employees, invest in data centers and pay for marketing of new products like its Pixel smartphones.

> Alphabet said it added about 6,500 employees in the quarter, for a total work force of about 114,000 people.

> The company also said its tax rate doubled to 18 percent from 9 percent a year ago.
How's your battery life at this stage? Have you replaced the battery yet?
I'm surprised to see no mention of Tup [1] in the discussion. Verifying the dependency graph for maximizing parallelism is its major feature.

[1]: http://gittup.org/tup/examples.html
> but we've reached a point where the lies on one side (and it is one side, the Republican side) have diverged so far from reality than the base of that side can no longer engage in any meaningful debate on any issue

As someone who has no love for the Republican party, I have to say that your statement shows a sort of tunnel vision. Just take the latest Ukraine scandal: it's true that Trump pressured the Ukrainian government to investigate his political rival, but at the same time, it's obvious that Hunter Biden only had his job because he was the US Vice President's son. That's corruption by any reasonable definition. Yet plenty of Democrats are insisting that there was nothing improper with Hunter Biden taking the job, and that this is all fake news. But if it were Trump's son on the board of a Ukrainian gas company, guess how Democrats would react (and rightly so)?

> To be frank I think the benefits of "Free Speech" are vastly overvalued. You shouldn't have the right to say whatever you want, at least not in the context of politics.

I prefer the First Amendment to the truth police. Of course, if I get to pick the truth police and they always agree with me, that's great for me. But it's not so great for anyone who disagrees with me, and it ultimately means the end of democracy.
A day in the life of a quality engineering sysadmin
I'd just like to point out that I find the reflex of "I don't like the comments here, so I lock the bug report down" rather misfortunate.

On the same note, I like to see how the discussions here look like a good distributed brainstorming session instead (ignoring a couple of naysayers).
Yes: those netblocks belong to them and you can't take their stuff just because you like the look of it.

There aren't enough addresses in v4. Reclaiming one or two /8s here or there won't fix that. Before IANA runout in 2011, we were going through over one /8 per month, and demand has only gone up since then. Those class Bs you're so worried about would last the internet maybe 2 hours each.

You can push as many allocations around as you like, but there just plain and simply isn't enough v4.
It doesn't force anyone to do anything.
Implemented through https://www.guildeducation.com/why-guild/how-it-works/
A few quick ways to reduce your attack surface on Linux
You can absolutely bike in the cold, and in the rain, and even in light snow. Also, public transit & busses can get you further without even the dreaded prospect of burning a calorie.

Removing free rental of public space to park your private vehicle is something I _do_ endorse though!
Google web search' aim is to give most relevant results to the Uncle Joe who is obviously bad in choosing keywords.
cheapest office is like 5€ per month for whole office package? How can that be too expensive?
Pro (noun.), abbreviation of Professional: born 1798, died 2019, aged 221
>I have no doubt he was saying this in reaction to planned economies of the time.

True, Nazi Germany was a planned economy and that's certainly not socialist in the sense of workers having control of the means of production. It can also be argued that New Deal or war economy WWII USA was a planned economy too.

They both used the state to control the economy and to use public resources to contract out to private enterprises.

The West still has relics of economic planning after Keynesianism through monetarism and central banking control.
You first submit an issue where you ask if the maintainer(s) would be open for a PR. That way you wont waste any time building something that might be ignored.
Just wait until they start working. Screentime on macOS is showing me I'm looking at screens over 80% of my waking hours.
It's a matter of defining "full self-driving."

If you're accustomed to horses and see someone selling cars, it'd be reasonable to say, "Those are ridiculous. There are numerous places only my horses can reach. There will virtually never be a time cars fully replace horses." And you'd be right. It's still true--there are places horses can reach that cars cannot. But because of the value of cars, society has reoriented itself such that reaching those places doesn't matter to the vest majority of us.

I think self-driving cars will be the same. We don't need them to operate in every single road / circumstance ever. There may always be roads that self-driving cars can't drive on. But it'll become irrelevant because the vast majority of places people want to go will become navigable by self-driving cars, whether through the cars getting better or the roads becoming more easily navigable.
You could construct things that wouldn't fit inside the nosecone of a launch rocket if you assemble them in orbit.

You could also repair/refit things without them having to go through re-entry and then be launched a second time E.g. replace damaged/worn out rocket cones or solar panels etc if you can build them in-situ. Imagine Earth-Mars shuttles that just go back and forth that would need maintenance
I always have an AltGr key, because I tend to program on Finnish keyboards. (Identical layout as Swedish, but because nobody came up with a term to group those 2 together, there seem to be always 2 options to chose that make no difference...) What I really hate about AltGr / this layout is the curly braces and square brackets. It makes programming so much harder to need to use AltGr for each of them.

That said in Linux/X11 you could configure everthing to your likings. I must admit I prefer complaining...
Not exactly https://en.wikipedia.org/wiki/Geology_of_the_Moon. I think the problem with moon resources is the moon's gravity while forming was strong enough to pull metals like iron and nickel down into the centre where we can't get at them (they're on the surface a bit too, but not conveniently concentrated). Asteroids, on the other hand, can contain lots of accessible nickel, iron, cobalt, etc.

I'm no expert though!
There sort of is although I don't know why anyone would want it.

https://github.com/renatolond/mastodon-twitter-poster
> Perhaps you have misunderstood the purpose and implementation of federating sites like these?

No, I absolutely understand how federating sites work, and don't need the condescension.

It's common, in many types of federated reimplementations of non-federated sites, to create special-case bridges that allow treating a large non-federated site as if it were following the federation protocol, precisely to help people migrate and to continue interoperating with users who are on the non-federated site.

In the specific case of ActivityPub, there are multiple bridges that allow following Twitter users as if they were part of the fediverse. Multiple Mastodon users I know have mentioned them. People just don't talk about them very clearly, or document them in migration guides. Hence my comment suggesting that.

If specific portions of the fediverse want to avoid ever interacting with Twitter bridges, they can absolutely do that, just as they can avoid interacting with other portions of the fediverse. But it would be helpful if potential new users had some information they could use to migrate more smoothly.
His point is that none of those things actually tell you about the class, it’s just theater. If you want to know what it really does, you need to look at the source code, that’s where the truth lies.
For most apps the looks don't really matter to me, so I wouldn't pay just for that. I would only pay for an app if it:

- does the job

- has no free equivalent that works

- saves me a lot more time/money than the cost of the product, or doesn't cost over 20€ (this is my personal threshold, for personal work. I would be fine paying more for something that I would use in professionnal work)

- has useful and innovating features (especially if something that has already been made hundreds of times like a music player)

- has a good UX

- has good documentation/support

- has a trial version
Studies post-ban haven’t shown that. https://www.cdc.gov/pcd/issues/2013/12_0327.htm