skysight-inc/HackerNews huggingface dataset:
Kinda Similar: https://www.youtube.com/watch?v=uNjxe8ShM-8
Kodi. It's amazing how far that project has come since xbmc.
It's a journal site where curators share bite-sized quotes and excerpts from the books they've read on business, philosophy, psychology and everyday life.
Many Americans consider their freedoms to be individual and inalienable - that they exist in spite of government, not thanks to it. Their coercive nature puts governments in opposition to freedom regardless of the intent behind the laws they enforce, or their benefit to society as a whole.

Socialism seems opposed to freedom because it requires a greater scope of government power, and therefore, a greater suppression of individual and collective liberty, than capitalism. Of course, not everyone agrees with even those broad definitions of socialism or capitalism (in the American libertarian sense of capitalism, anyway.)

In other words, in the US the view tends to be that "the government which governs best, governs least."
Most counterarguments related to Hydrogen refer to the poor efficiency of converting (electric) energy to Hydrogen and back.

True, directly using that electric energy from wind or solar is definitely the best option.

However, that is not always possible, since there is no place to consume, transport or store that electric energy.

Furthermore, scrapping all ICE vehicles for BEVs is most likely the end goal. But replacing the worldwide fleet of vehicles will take decades.

HyTech seems to be on to something for these two scenarios.

If for instance you can capture some of the excess solar and wind energy in a metal hydride for some hours, weeks, or even months, you will on a larger scale reduce the load of the electric grid.

And if some of that Hydrogen can be burnt instead of Diesel, the car or truck in your driveway is both cleaner and less dependant on fossil fuels.
Doesn't your narrative just confirm then that "working with computers" has always been related to social norms? Women were placed there and performed as well as any later man(hence many notable women in early computer science).

When ceos started realizing the potential social and economic power of the magic typing box it was no longer socially taboo for men to operate them. Of course, no self respecting business elite man would use one, only dirty hippie social rejects.

That's what makes the whole thing extra sad. For the longest time silicon valley types had to deal with being social outcasts in the business world. Rather than learn from that to be more inclusive they just took up the mantle of the business elite they replaced and perpetuated the same system of prejudice. In fact now that I think about it part of excluding women from the profession might have been an attempt at self preservation. Early tech people knew they were already looked down upon, if they didn't amp up the sexism to make it clear they were real men they would look even weaker to their east coast elite superiors.
https://www.nature.com/news/the-myopia-boom-1.17120

from https://news.ycombinator.com/item?id=9227541
You don't have to buy stuff directly, or even interact with the ad, you just need to see it; be influenced by it. You'll buy stuff later. When you see an ad for a package holiday you don't have to click it for the ad to be effective (although some people do click them), you may just as well decide to visit the operator's website the next day to browse their options. If their ad didn't bother you, chances are it was a good investment (probably).

People who do get bothered by ads and their continuous manipulation use an ad blocker of course.
> It seems insane to me that people would want government to do healthcare

It's not government DOING healthcare, it's still private doctors doing it, just it being free at the point of delivery via a government administered single-payer system.

The reason many government services in the U.S. don't work is because they get defunded to curtail their effectiveness and then scapegoated.

To someone from the EU, it seems barbaric to want to profit off of someone getting sick. You wouldn't want private armies, would you?
here is a fallacy that is frequently made: everything needs to be profitable. no, not everything needs to be profitable. we accept that things that are for use by the general public as essential to their life are not held to the standard of being profitable. this is why we offer food stamps and control the rates for water delivery and electricity delivery very strictly.

healthcare doesn't need to be profitable, it needs to increase people's longevity and their quality of life. full stop. anything else-- anything less-- anything more cruel in the conversation is completely unwelcome and hopelessly off-base.

it's like the people who try to argue that public transit needs to make a profit. no, it's a public utility. it needs to not bleed the public's money dry, sure, but its primary objective is providing a service rather than making money. making money isn't even a tertiary goal. once again, it's a public service.

flagged this article for being too stupid to be on HN; other people in the comments have already pointed out the article's glaring methodological flaws, poor rhetoric, and its malicious moral standpoint.
It doesn't help that "freedom of speech" is broadly taken to mean that the government can't restrict your speech. However, most forums where people congregate to speak are not managed by the government, but by corporations.

And most people seem to find it totally OK for a corporation to silence any speech they want to.
> Are there any good reasons why someone should try to rebase and merge (fast-forward) a pull request to avoid a merge commit?

I've always thought of it as a way to effectively create a branch, do your work, and fast-foward merge it back in to the main branch without having any other work included in it.

To put it another way, let's say you create a fork, do your work, and in the interim, several other contributors do the same thing and merge their work back into the main repo. Now, you could merge the mainline back into your fork and have a merge commit in your private branch that shows the changes that the other contributors made since you created your branch, or you could merge your branch back into the main branch at the end and have it show that it branched off earlier than the current head of the main branch.

In the first case, you now have a commit that shows changes that you didn't actually make. In the second case, it shows that you didn't base your work on the latest version of the main branch.

In contrast, if you rebase and only merge your work into the main branch via a fast-forward merge, your branch will only show commits that you made and it will effectively show that it was based on the latest version of the main branch before it was merged back in.
okay but in J thats:

require 'dates general/misc/format'
4 3$ calendar 2018

4 3$ just re$hapes it from a big as line to a 4x3 calendar. If you wanted to print it to a file you'd want to convert it to a string of course so:

": 4 3$calendar 2018
After watching the video, I feel like this follows intuitively from the fact that sqrt(2) > 1.
Love the tomato analogy - exactly why you need to convert energy, even with the efficiency loss.
That's just a deliberate business model decision though. If all the ridesharing services decided tomorrow to double their prices and downsize in line with reduced ride volume, they could probably turn a profit fairly quickly, albeit on lower revenues and (probably more relevantly) sharply reduced valuations. People will still use them even if they cost as much or more than taxis. They just wouldn't use them as much.
How Software Is Taking on School Shootings (2017)
> I personally prefer merging via squash since it keeps a linear commit history without polluting the history with tons of intermediate work-in-progress commits.

How do you deal with cases where your changes require more than a single commit? Some changes are easier to review when they're separated into several logical commits rather than having one giant diff from a single commit.
1. They developed tools to synthesize side channel exploits based on an architectural model + threat model.

2. They developed distinct variants of Spectre and Meltdown that use remote cache line invalidation (activity on core 1 can cause lines in core 2 to be evicted!) as the side channel.

3. Curent software mitigation of Spectre and Meltdown appear to be effective at mitigating these new variants

4. But future hardware mitigiations risk being too closely directed at changing the observable behavior of the local cache. If they neglect observable behavior of cache in another core, the hardware mitigations will be ineffective.
A new, stronger, EU data protection law (GDPR) is coming into force in May this year.
NixOps supposedly supports several hosting providers, but the DigitalOcean integration is currently broken. AWS works great, but it's annoying to be forced into that choice by the tool.

Haskell and Elm both work great, but I can imagine in future using something like Haste or PureScript Bridge; it'd be nice to work with both the backend and UI as a single project. Not a pain currently, but this is a nice to have.

Biggest pain is documentation. Haskell stuff is documented, but more hand-holdy examples would be ideal. OTOH, some language communities have a culture of writing documentation that is too hand-holdy, flooded with emojis, and is generally frustratingly infantilising. I'd like Haskell to strike a balance between the two. I'm optimistic we'll get there eventually.
Airbnb and the Unintended Consequences of 'Disruption'
Dell officially supports Ubuntu and sells laptops with it on their store.

I've not had any issues with my XPS 13 on it.
Given that jails don't charge the inmates to stay there, your analogy is quite broken.

Taxpayers foot the bill either way.
And the competitor will be able to operate in the USA, whereas FB won't be operating in EU, giving the compeditor an advantage.
I think the real means real numbers
The idea behind XML schema, DTD, etc. is to pick a simple language to express schemas in, so that implementations in different languages have a decent chance of being compatible with each other.

Python isn’t a good choice there, as it is too flexible. For example, that code could have gotten the list of allowed country names from a file, database, or URL.

⇒ If I have to send such json to you, I almost would have to write my program in python, and even then, it could be hard for me to replicate your setup.
Performance debugging: from 1.3X slower to 48X faster than Apache Kafka
Well, that assumes that solving whatever problem can be handled by a remote driver with no situational awareness of what's going on can plug in 5 minutes later and deal with things.

That's not necessarily unreasonable for handling rare and non-urgent events but it's a lot different from having an alert backup driver. (Of course, if you need an alert backup driver, there's no benefit to autonomous systems once you get past the testing stage.)
Besides's this projects cli, jp (https://github.com/jmespath/jp), I see jl (https://github.com/chrisdone/jl) and jq (https://github.com/stedolan/jq/) in the comments. I wonder if anyone has had experience with all three (or even just one) and can comment on their experiences?
> By that method of thinking only the rich are free.

"Money is coined freedom" -- Fyodor Dostoyevsky

> Eu has more "freedom" in that everyone has access to these things.

Agreed. Which is why I think that Europeans area also "richer" (the above works both ways, IMHO).

The "freedom" in the US is very much a freedom of the rich and powerful to do whatever they want unhindered. Which looks a lot like tyranny to everyone affected. Certainly employees are much more free in Europe, because they can't be fired on a whim. For example, had James Damore been a Google Employee in Munich, he'd almost certainly still have his job, or a very fat compensation payment.
It's the "yet" that'll kill them. With the focus on growth, a VC backed company will not be able to ignore the massive EU market forever. Can it pivot, quickly, to be respecting of privacy? If you've build your whole business on collecting and using personal data, how can you change?
The article is a summary of a a study that reviews over 500 other papers dealing with how preventative care may or may not save money.

It concludes that only childhood immunizations and one other thing save money. And that fifteen additional interventions are extremely low cost.

This is an unintuitive result, but backed by a careful review of quite a bit of evidence.

What evidence shows preventative care does save money?
I used a few in my past life as a bad sysadmin. Mostly Ubuntu Server's. Some Fedora's, some CentOS's, some Arch Linux. I never did try Gentoo in production servers though.

And through the years I learned to dislike their hive-mind approach to problems with half-baked crippled solutions that get approved and merged to production because some untouchable dev/guru/mastermind decided that he alone was a significant sample of all linux users:

- Forget about extending and improving ifconfig. Lets change everything and create a new command, afterall ifconfig is not that important,.

- Forget about your system dir layout. Lets change it and mix everything up into /

- Oops that kernel update completly screwed iptables...

- Oops that kernel update somehow introduced packet loops in the network

- Today I learned that I/O DoS is.

- wtf systemd ? Now i have to read up on this new sh*t that they are pushing down my throat. Oh wait there is no documentation.

- Don't get me started on filesystems...

Anyhow, I find Unix systems very hard to manage and maintain, i mean we do have all these devops tools to automatically manage configs and programatically setup machines in a coherent way. Linux just likes to show more than others that it exists, and does it in very inappropriate ways.
> It does however preserve full history.

Frequently, I see a commit history like:

Implemented feature

Forgot semi-colon

Fixed syntax error

Addressing review comments

Removed unnecessary method

History like that, other than the initial commit, is not very useful. It makes more sense to rebase to clean up the commit history such that it becomes a logical series of commits, which can then be viewed via git log or git blame.
There's no official release of MySQL 8.0 yet, correct? Or... something that isn't an RC?

I was confused by the numbering, but perhaps never paid attention to major point releases before. I saw 8.0.0, 8.0.1, etc through 8.0.6, but looking closer, they're all dev or RC releases, but nothing has been declared 'production ready' yet, officially (or so it seems). Will that be reserved for the 8.1 label? Or will we just see something like 8.0.11 as the first "production release"?

EDIT: thanks for the replies - GA is the term I need to be looking for.

EDIT 2: Also: https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html is a decent overview both of new features and removed/deprecated stuff.
I read a bunch of webcomics, and some of them I discovered through the ads they bought on the sites of other webcomics. Then I ended up contributing to Kickstarters and Patreons, which hopefully offset the cost of the ad.

However, creators buying ads on each other's websites to attract visitors who will then spend more time seeing ads ... seems kind of circular. It might be that part of the ad ecosystem in that space is fueled by hopeful artists who make a loss trying to promote their work.

As far as physical goods are concerned, I don't really buy anything except to replace something else, and then I just go to whichever place is most convenient and buy what they have, so there isn't much room for ads to influence me.
You missed this part, though:

Of all the interventions they looked at, only two were truly cost-saving: childhood immunizations (a no-brainer) and the counseling of adults on the use of low-dose aspirin. An additional 15 preventive services were cost-effective, meaning that they cost less than $50,000 to $100,000 per quality adjusted life-year gained.

They’re not against paying for things, just not paying uncapped amounts.

It does sound barbaric, but just take it to the extreme. Is, say, $4M of federal taxpayer money for one quality-adjusted year of life gained a good trade off? Someone has to make that call.
You can rebase locally into commits that make sense and then merge normally on GitHub.
I remember when xml started down this road too. "We aren't going to be sgml, but just a lightweight markup. Xpath, xslt, etc. And now we have xml today, the modern day sgml.

But this time it's different?
Show HN: Free sms with python via way2sms
I'm still looking for an "open" alternative that is strong on free speech without being home turf for white identitarians (gab.ai).

Looking an Mastadon's policies makes me give up hope:
https://mastodon.social/about/more
Facebook Notification Spam Has Crossed the Line
I wonder which races sweat the most.

I'm basically Irish, and boy do I sweat. Even when I was young and fit, I would be drenched when my co-workers/friends looked dry.

My brother once asked the family doctor about his sweating. The doc just said everyone is different.
How many countries are in one but not the other? Switzerland, Liechtenstein and ? Or is there another reason for remembering the distinction?
That is surely what it will come to at some point.
An even less accurate representation now than it was back then.
Fun fact: AARP is the biggest lobbying entity in the USA. And it’ll only get bigger with baby boomers joining the club.

Edit: GenX, not baby boomers.
Neat, as a VIC-20 owner back in the day I wasn't really aware of this.

I remember my parents getting me into a week long computer camp when I was 8 or 9 (below the minimum age and required a special interview) and all the computers they had in the lab were PETs -- and how excited I was to be able to record the BASIC programs I worked on and bring them home to run on my brand new VIC-20.

That said, Commodore was not nearly as good at Apple and Atari at keeping backward compatibility on their 65xx 8-bits, and they did something weird with the Plus/4 type machines, which bizarrely had almost no compatibility at all. You could easily run software from the late 70s on a mid/late 80s Apple IIgs, or on an Atari XE.
I use dryer balls to prevent stiff clothes and static: eg https://www.amazon.com/Dryer-Balls-Count-Assorted-Colors/dp/...
Calling the commodore's firmware a kernel is a bit of a stretch in my opinion because it did not schedule anything. The 6502 had no MMU and therefore no virtual memory or running of more than one app.

One clever idea I learned when I was a kid tinkering with C64 was how the ROM resided at the same memory address as RAM. By toggling a bit, you can switch between the two. Applications back in the day would toggle this bit really fast to give the capability of having an assembly language program running in the background while your basic program interacted with it.

I learned this and it stuck with me over the years. C-Net BBS by a company called Perspective Software, if I recall correctly, did just this.

Cool article!
The author seems to go through great lengths to call a phenomenon where people bought something to sell it for a higher price followed by a sudden collapse in said price, something other than a bubble.
I have never created an apps or worked with React Native before. But, I would share the experience from my colleague who develops Android apps in our startup.

We are a startup that helps people in the middle-low income using technology. The people who use our technology usually have Android mobile phone with minimum specifications (Jelly Beans, low memory and spaces). At first launch, we used Android Native to build our application. The application meets our costumer needs since we consider to build an apps that consumes low memory and spaces. Then our costumer are growing and the features are complex, we use React Native to existing native app. Our application now consumes memory and spaces two times than Native one. Beside that, sometimes when you use a library, Native is more stable than React Native.
I really don't understand why the debate on H2 is so focused on electrolysis. Even today, 95% of all hydrogen is produced not by electrolysis, but from natural gas through steam methane reforming (SMR).

SMRs can be easily scaled up to meet all H2 demand, and they are easily fitted with carbon capture technology (since it's a single large emission point). Then you have zero-emission H2 in quantities as large as oil and gas today.

I'm entirely convinced it will be the future, and that we'll never be able to scale pure BEVs beyond 10-15% of all cars in any large country, simply due to electricity production and distribution constraints.
So filing a QEMU bug on FreeBSD's tracker is supposed to help how?
My comment is slightly rhetorical. "Bad management" and/or "misplaced company values" are the answers, and they're exactly my point. Apple has lost touch with the perfectionism that made it so wonderful.

I think perhaps Tim Cook doesn't realize that Apple didn't create all this emotional loyalty from artists just by having pretty boxes and wallpaper, but by cultivating a kindred spirit with them. And to do that, you have to actually care about the quality of your work on a fundamental level.
https://news.ycombinator.com/item?id=16394828
The squash is only performed when merging the pull request (via GitHub’s merge button on the pull request). The actual work is done and reviewed as individual commits.

The nice part of this workflow is that the changes are all squashed into a single commit in the trunk, but there’s always a link to the pull request where you can see the individual commits pre-squash.
It's hard to recommend Brailsford enough, especially when talking about computing history.

EDIT: For more von Neumann history, check out http://www.siam.org/news/news.php?id=38
I thought JavaScript was the xslt of json.
> Dell officially supports Ubuntu...

Meh. I'm writing this from an Asus EeePC which was once officially supported by Ubuntu, but now with broken graphics and wifi.

The non-free graphics driver is not included in Ubuntu anymore and the wifi works only with non-free binary blob.

Also, I recently found that wifi doesn't support channel 13 and 14 (found it accidentally when my laptop wasn't seeing the nearby hotspot) with the non-free blob. Now I run Debian testing.

Don't trust in those "Officially supported" things, unless it's Debian GNU/Linux. Otherwise, it's eventually going to be broken.
> US does a lot self censoring

And corporations do a lot of censoring of their employees. Most of what passed as "corporate policy" at my last US-based employer here in Berlin was so blatantly illegal in Germany it was laughable.
I'm pretty sure eyesight, if already bad, degrades the quickest in your younger years and flattens when you get older. That's how it happened when I was growing up, and the doctors assured me that I wasn't going to go blind as my experience was "normal."

I haven't had a significant change in eyesight for a while now. What's fascinating is how each doctor has a different interpretation of what a proper prescription is. Some like to give too strong, some too weak.

I switched doctors a while ago, due to a move. The new doctor told me my prescription and I was a little surprised by the difference. I asked her why such a change and she showed me what the world would look like if I was using the prior prescription and it was like seeing a massive blur.

She said she had no idea how I was able to see at all. I was using that prescription for one year, and I didn't have any problems seeing anything before.

(I wear contacts and I sort of need to know my prescription so I know what box goes to what eye as my left and right are different. When I wore glasses, I had no clue what it was)
After using FreeBSD for many years and having to move to linux for various reasons, I still miss kqueue and FreeBSD's superior networking stack.