skysight-inc/HackerNews huggingface dataset:
I used to be a pretty hardcore libertarian. The standard libertarian arguments only really work when you have a mostly libertarian system already however. They tend to have problems when you have some form of a welfare state such that individuals who for whatever reasons are unable to support themselves end up being supported by the state. That in itself is a classic libertarian argument - the logic of welfare inevitably leads to government overreach in all areas of life because the state has established a financial interest in preventing people from engaging in "harmful" behaviors.
As someone who drunkenly bought 10 keys and unboxed gloves I can confirm. I'm now competing at a much higher level.

Seriously though I think the loot box model is ethically wrong. However, I don't believe it's wrong to offer skins for sale - this is no different than people wearing different brands of clothing when they compete in sports
The IETF's standardisation process almost can't help but improve whatever it is you're trying to standardize. Not only are you being shepherded by peers with expertise in whatever corner of networking you're excited about (the Area Directors for whichever Area your Working Group was assigned to) but you're obliged to put up with anyone who cares to offer an opinion mailing it in. Looking for consensus isn't a good way to run a restaurant kitchen, but it may be the best possible way to agree network standards. Even when contributors say something you believe to be completely stupid figuring out how to put into words exactly why they're wrong is likely to be instructive, and as often as not they're not /quite/ as wrong as you first thought.

For example the TLS Working Group is polishing up a document telling people to cut it out with the TLS 1.0 after all these years and get to something at least vaguely modern like ten year old TLS 1.2 instead, (once upon a time named the diediedie draft, these days it has a more respectable name). Martin Rex offered the opinion that TLS 1.2 is _worse_ than TLS 1.0 and 1.1 because it doesn't smash SHA1 and MD5 together to produce a single hash. He reasons that if, somehow, SHA1 is broken enough to allow a preimage attack, TLS 1.0 is fine, whereas TLS 1.2 with SHA1 is now broken.

Of course people said Martin is barking up the wrong tree. But much more importantly they took another look at their document, it didn't actually _say_ you should implement SHA-256 when you upgrade to TLS 1.2, but they all agreed you should do that, so probably the document wants to spell that out...
You see the problem though, I need to try it and practice it to see how simple and clear it is. I can write code that I can easily understand. I can write terse, clever code that I can easily understand. But I want to write code so that the next person can also easily understand it. More importantly, code that's easier to understand has less chance of getting buggy when it inevitably gets rfactored or extended.

>and it's dramatically more compact

Why do I want that?
“I Tested into Stanford Through My Own Hard Work.” JK, Her Parents Paid $6.5M
Sorry, but these examples aren't properly analogous.

A driving equivalent would something like automatic breaking technology. If it was proven that people driving with this were 50% less likely to cause accidents and the technology was available in all cars, then it would make sense to fine people that opted to manually turn it off.

Abortion isn't the same situation at all. That is a loaded topic involving religion, body autonomy, the concept of a "soul", person-hood, and science. It is not a binary issue.

Vaccines are black and white. There is sound science proving they don't cause autism and by not getting them the rest of the population is in danger. I would think heavy fines would be appropriate throughout society for these type of circumstances (or some other types of behavioral push).
By useless I meant that the use of HTTP doesn't contribute anything essential. Though maybe I could be wrong? But that's what I understood by "is not core to its operation". I understand it to just wrap the JSON in HTTP for the benefits that come from its ubiquity in use and not so much because of merits of the mechanisms described in the HTTP spec.
> The fact that the general fuel is going to be sold and re-burned means this is at best carbon neutral, so from a cynical environmentalist point of view, what's the point?

It's meant to replace a carbon-emitting process (burning gasoline made from fossil fuels) with a carbon-neutral process. The replacement process is not carbon-neutral.
It sort of seems like a shame to throw out the entire approach and move to something vm-based when it was already working so well, but I guess if it improves both performance and compatibility it makes sense?
A new approach to targeting tumors and tracking their spread
AMD | multiple Linux developers | Toronto, Canada | REMOTE | Full Time | https://jobs.amd.com/job/Markham-Linux-Developer-Open-Source...

(Remote possible for senior candidates at certain countries.)

The successful candidate will be responsible for:

* Open source graphics driver feature development based on Engineering and Marketing requirements

* Contributes to software projects of significant technical importance

* Solves complex non-recurring problems that leads to development and implementation

* Driver bring-up and qualification on new hardware platforms

* Debug, analyze and resolve quality and certification issues as reported by Customers and QA

* Improve driver performance

* Write detailed design notes for new features

* Coordinate closely with peers and colleagues to ensure timely and effective communication of all assigned work activities

* Coordinate with developers in the open source graphics development community

* Coordinate with Linux distributions

Requirements:

* Proficient in C and C++ programming

* Excellent debugging and trouble-shooting skills

* Broad technical knowledge of Linux operating systems

* PC architecture knowledge

* Strong oral and written communication skills

* Experience dealing with customers or Linux community

Nice to have:

* Experience with 3D graphics APIs such as OpenGL and Vulkan

* Contributions to Mesa, LLVM (amdgpu backend), Xorg, or kernel GPU drivers highly valued

* Experience with Linux graphics driver programming a plus

* Experience with open source Radeon graphics driver programming is a strong plus

* Experience with Linux build and packaging tools (make, rpm, dpkg)

* Strong shell scripting and Linux systems administration skills
Well, so my thinking is along these lines. What we now call "full-time" - 40 hours a week - is not a law of nature. It's a social construct. In the beginning of the industrial revolution everybody worked 12 hours a day without the weekend. Labor movement (or was it Henry Ford? I don't know) pushed for shorter working week. It didn't seem to destroy the economy. So I don't see why we can't make it even shorter. And HN crowd, as indeed relatively well off, can lead the way. As more and more people work "part" time it might change the popular perception and eventually the rest of the society and regulation might follow.
If only they could just add a very easy way to invoke functions (at least those with simple interfaces, i.e. taking just simple value types as inputs and returning a simple value type) from other languages (incl. Java and Python) this would already be a huge value boost even if performance would be not perfect.
I don't know if I want to find out what the J stands for...
$2000 would go a long way toward building your own robomower.

Find a broken lawnmower in the trash for "bulk pickup" - free (getting it fixed might cost a bit of money, but in most cases, mowers get thrown away because the carb gets gunked up due to not being stored properly, or the air filter needs cleaning; ie cheap fixes).

Get the base or motors/wheels from an electric wheelchair (this might cost a bit of money, but should be doable for under $200 if you look carefully).

Various bits of steel, castors, bolts, etc - under $100.00 if you scrounge.

RasPi Zero W, GPS/IMU, sensors, etc (ie, electronics, sans motor controller) - $100.00, maybe a bit more.

Motor Controller - spend money on a good one, or money on the parts to build a good one. Probably looking at $200-500 dollars for a dual-motor controller. If you are really cheap, though, you can build a decent dual motor controller for the price of four 40 amp BOSCH relays, some wire, and one or two 40 amp DC SSRs; that'll get you a controller for well under $100.00, just don't expect great things from it.

The rest is up to you. Granted, that's the hard part, which may be worth the $2k depending on your skills, time, patience, etc.
> gas in CA is almost $4/gallon in the Bay Area

And the national average (today) is $2.95, you might as well compare Hawaii and Alaska which are also economic islands.

>it doesn't take much time for normal rates to hit $6/gallon in the next 10 years or so.

The national average 10 years ago was $2.45, which is $2.90 accounting for inflation. The only way gas hits $6 is if we have a second Great Inflation or massive political changes in the United States and abroad.
You haven't even mentioned the runtimes, and the target platforms, and the whatever elses.
I think it's wrong/confusing to say that they're "launching" React Native for Windows. React Native for Windows is out already, and it works fine. They're just announcing the kickoff of a C++ rewrite.

https://github.com/Microsoft/react-native-windows/blob/maste...

> In this sub-folder, we are working on a vnext rewrite of React Native for Windows10 built in C++ that reuses the C++ core bridge implementation from Facebook’s React Native. This will allow React Native for Windows10 to innovate and provide features by sharing the same core as Facebook’s React Native.

Cool, but this is basically just an implementation detail.

(I do wish it supported Windows 7 and 8.)
App-based drivers in New York City are already legally entitled to a minimum wage of about $17 an hour after expenses. The Taxi Workers Alliance says its demands include greater job security. A Lyft spokeswoman said Lyft drivers' hourly earnings have increased over the last two years.

I am confused by this article. Drivers already have a (relatively high) minimum wage. Now they want job security according to the article? What would that look like given that drivers can work anytime they want?

Also, why did Lyft comment on the wage if that is not what drivers are demanding?
1. Everyone does that, why should I do different thing?

2. I've heard about corporate firewalls which close everything and nobody has power to overcome that, so I'll tunnel everything via HTTP(S) and forget about those horrors.

3. HTTPS provide absolutely hassle-free encryption with reverse-proxies. I don't even need to think about it. Using TLS library sounds too complex and I must make some real effort to implement it. Rolling out my own encryption? Everyone will scream!

4. HTTP/1.1 protocol is really simple. There are some hidden gotchas in the corners, but basically it's headers, empty line and then either bytes or stream of chunks, that's all about it. So I can pass routing information (URL path), I can pass some metadata in headers and I can pass either a singular message or a streamed content. And with HTTP libraries in every language you'll get that functionality almost for free, both for server and client.

5. Theoretically you can leverage HTTP caching on various levels. Might be tricky, but certainly easier rather than implementing it from the scratch. And with things like Cloudflare you can't really build anything similar.

6. Browsers can only talk HTTP. So even if I don't need it know, if I would ever need to build web application, I'll have to provide HTTP bridge. And web applications are really common nowadays. You can't really make IMAP client in JavaScript running in browser. But you probably can do it with JMAP.
What's your favorite Windows laptop these days?
No, it's just the most widely supported protocol of that kind, so why not use it? Is there anything specific against it/how do you answer for another protocol the question of "why not HTTP, which is similar and has better support?"?
(Caveat: I think you'd ideally want http/2, which isn't as widely supported)

EDIT: actually, one point: you can talk JMAP over HTTP(S) directly from a browser without a translating server.
Ah, that certainly explains it. I'm still highly skeptical of how widespread this will ever be, since electric cars will become even more compelling as electricity costs decrease, but you've convinced me to not dismiss this completely as impractical. Thanks for the context.
http://gs.statcounter.com/os-market-share/desktop/united-sta...

Seems to suggest that ~70% of the US still uses Windows as their primary desktop environment, so you might have a very particular selection bias.
Getting the same amount of protein is difficult? I've never seen someone try to argue going vegan is cheaper then eating meat. Maybe cheaper than eating steaks, but chicken breast/thighs and ground beef? Eggs are also an excellent source of protein, it comes out to about a $1 for 80g of protein.
If we replace fossil gasoline with renewable gasoline, that reduces CO2 emissions. Our gasoline will be zero carbon, and may actually be certified as slightly negative, as we will not be emitting CO2 from drilling and refining as fossil fuels do. If we replace all liquid fuels now made from oil with fuels made from air mining of CO2, it could reduce emissions by approx. 10 gigatons per year. That is huge.

The membrane will definitely replace distillation in a number of industries, but the most exiting thing to do with it is to replace fossil transportation fuel with renewable fuel.
I work as a data scientist but want to learn more about data engineering and software engineering as I prefer those aspects of the work.

Hadoop seems outdated now though as we have moved to the Cloud whereas we used to have Hadoop on-site and it seems most of my friends companies have done the same.
Support for retweeting with a photo, GIF or video lands on Twitter, mobile only
This binary view is completely unhelpful towards a solution. We've taken important steps towards protecting the environment before (Montreal protocol, clean air act, etc) and have mobilized tens of millions of people to work on crucial problems, as in WWII.

Many small and incremental improvements can have important and large scale effects over time, and humans are occasionally capable of rising to the occasion if it becomes severe enough.
You are the exception. Normal people freak out and become helpless (often showing as anger) if some systems they assume to work suddenly stop. Everything from plumbing to supermarkets to taxis. And in my experience, there isn't enough space for nuance in the public consciousness for most people to not blame the actual service workers.
The Dropbox technical blog is always a very interesting read, I love that they provide so much detail into the technical background of their solution. Still was left with quite some questions when trying to understand this article though:

- Dropbox did not want to be running a single version of the software / a single region, because they consider the risk of a single software bug / human error resulting in data loss too high. However, the alternative they choose introduces a completely new code base which will have to be battle tested. This increases the risk of a data loss bug, which would affect a smaller fraction of the data, but any significant data loss issue would be game-over for a company like Dropbox. Did they consider partitioning the system into smaller subsets (some single region, other multi-region), using staged roll-outs of new software versions? Or is there really some fundamental incompatibility between Magic Pocket and multi-region?

- The "New Replication Model" story sounds a bit too simplified. It seems to re-introduce some issues that the single region Magic Pocket solution had already solved: the size of the IO operations becomes quite small again (fractions of the 4M block size), placement of data on the disks becomes less predictable, which could cause increasing rebuilt times when a disk fails. Also, the number of IOs to read or write an object increases significantly (2-3x in the example), which means that the observed advantages in latency go hand in hand with a 2-3x lower maximum supported load than in the Magic Pocket case, before the latency explodes due to running out of IOPS on the HDD's. The whole design seems to ask for far more IOPS than the Magic Pocket solution, which sounds like an odd match to SMR HDD's.

These issues are maybe alleviated by the fact that moving data to the cold tier happens asynchronously, and the cold data is accessed very infrequently, resulting in far less IOPS being required for the cold storage region. However, it also makes the option of combining hot and cold data on a single disk much more difficult (which for HDDs is the way to make optimal use of the limited IOPS vs. their huge capacity - I suspect Amazon / Google use this for their near-line storage solution). Moving from the 2+1 example to e.g. 4+1, to reduce cross region storage costs even more, becomes now a though call as it now goes hand in hand with an even larger increase in IOPS cost.

- The claimed "simplicity" of deleting data in the proposed scenario is rather relative. If they are using SMR drives, deleting data and reclaiming space are complex and expensive operations. They might reduce it to a non-distributed problem (which is still a significant gain, of course), but it is far from trivial.

Probably a lot of the finer, left-out details of their cross-region system address these issues, and if not, maybe the cross region system and the single region Magic Pocket solution will converge again in a later phase.
Build 2019 gives us so many exciting news today.

This year I switched my developer machine from Macbook to Thinkpad and so far it has been wonderful.
Next, please provide a Windows kernel for Linux or other open source operating systems. There are many of us whose biggest frustration running an open source OS is working around Windows executables, Windows only drivers, and Microsoft proprietary file formats.
Protecting democratic elections through secure, verifiable voting
It looks like they use something very similar to Erasure Coding in Ceph with RadosGW [1].

[1] https://ceph.com/planet/using-erasure-coding-with-radosgw/
Could you also make a filter that distills liquor?
The big annouce I mentioned above is that the source code is available open-source, at https://github.com/Microsoft/Terminal

If you'd like to skip ahead before real previews are available, you could always compile from source :)
Incredible pitch, I wish you luck. This would be an amazing alternative to batteries in areas where there would otherwise be renewable over-capacity. While it appears less efficient, it is transportable and easy to store.

Please keep us all updated on how it goes, I'm sure you will see a lot of excitement about what you are doing.
This is really cool! I hope that you can rise above the comments of the "this isn't good enough" or "zero carbon or bust" crowd. This type of innovation is what we need to move the needle in a realistic manner and that helps to build on the infrastructure that we already have in place.

I'm excited to see what comes of this in the coming years!
How does this true Linux Kernel talk with the rest of Windows? How does it access the Windows file system?
The terminal appears to be here, btw: https://github.com/Microsoft/Terminal
The same app that just got called out for scraping any data it can from the mobile device?

https://theoutline.com/post/5628/how-a-concert-ticket-steals...
It is not in use because it's basically illegal, and due to relieance on JavaScrip, a simple script blocker can take down your entire business.

The industry used fingerprinters, but for one it didn't really help them make more money (because you want to track users, not systems), and there was a big backlash.
Would get all gummed up with mud. But that's true of about any type of locomotion.

Overall, this seems very much designed for ideal environments - smooth, relatively dry, etc.
If the wealthiest are de facto not paying as much tax, proportionally, as the middle or poorest classes, then federal income tax is not truly progressive. It has been increasingly regressive since the peak marginal rates back in the 1950s. This includes the use of numerous loop holes in the tax code to avoid what should otherwise be a large tax, and those primarily benefit the wealthy. The overall tax burden is what counts. For instance, some states do not have income tax for anyone, but they get much of their revenue from sales tax. Sales tax is regressive because the wealthy spend a smaller proportion of their money on sales tax than those who live paycheck to paycheck.
How much of that is just survivalship bias though? As in, if you were to asked to bet on a 50-year-in-the-future model in 1970s, would you have picked this model?
Scott Hanselman demoed it on an iPad Pro, so iOS Safari is definitely covered.
I can't help but think that this is 10 years too late. I gave up on Windows a long time ago, as did many people I know. I know there are folks who find this valuable, but I think Microsoft is chasing a pool of power users that has been consistently shrinking year-over-year. With that said, perhaps the pool will get bigger as it exposes users to the power of command line :-)
It would still be very much preferable to not have to do it.
I can imagine that when this rolls over a green hose, it promptly tries to "kill" the hose.

And I don't want to think about what it does to slugs and snails...
An EV makes several times the motion from the same energy input.

> Even electric vehicles aren't carbon neutral, because they're mostly charged by coal power.Even electric vehicles aren't carbon neutral, because they're mostly charged by coal power.

Is thus an invalid/irrelevant argument.

I can get excited about jet fuel however, since battery powered planes are considerably less practical than their traditional counter parts with the current technology.
Patented, yes. You could do the fuel synthesis in water on a hobby level, and use a thermal still to get something flammable, but you wouldn't be able to use it in an engine. It's pretty fascinating to work on though.