skysight-inc/HackerNews huggingface dataset:
Agree with the parent. Regarding yarn, it was created because npm started showing weaknesses in many things, with large and complex dependency trees: install was slow, sometimes unreliable and not cross-platform portable, and the codebase was difficult to refactor due to legacy code and backward compatibility, so it made more sense to create a new package manager without that burden and try to iteratively align with npm to become a drop-in replacement.

It's easy to fall into the fatigue due to new languages, tools etc. coming out each week but please think twice before posting dismissive comments like that.

I observe a lot of "I don't read HN anymore" sentiment lately among top tech Twitter users, partially due to that.

There's a lot of awesome stuff being given out for free and people are whining. (Yes, I'm a bit tired of constantly following and evaluating things, but I keep it for myself.)

The situation came to the point where some guys are thinking about not opensourcing their tools anymore due to constant criticism and maintenance fatigue. Read the two links below (accidentally, the first one is from yarn co-author!):

https://twitter.com/sebmck/status/879282797915119616

https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-...
Correct me if I'm wrong, but I can't add vdevs to a RAIDZ (RAID5/6ish) system in ZFS, which are probably the most common configurations for home NAS systems.

I'd love to run ZFS, but I can't because I need to be able to add more drives as I buy them.
True, something absolutely needs to be done about that. The only failsafe is a US soldier illegally disobeying orders. Actually, most soldiers that have a key would need to disobey orders, because it wouldn't take too many nukes to end life as we prefer it on earth.
Pornhub is doing more for this than many companies listed here if you check their homepage (still very minimal), which says a lot to me...
I am a fan of rust, but this article overstates the simplicity of C/rust integration.

A few examples:

* You may need to use PhantomData in your struct definitions to properly track lifetimes. Not sure I fully understand.

* C functions don't always return. Sometimes they longjmp (c.f. PostgreSQL). Calls into C code need to prepare for this and it's not trivial nor does it generalize to all projects.

* Integrating with the memory management scheme is probably possible but not trivial. For instance, Postgres memory contexts (regions/arenas) can hold any kind of object, and code can switch between them and create/destroy them at will. You could rely on rust to manage it's own memory, with circular references an Rc that might leak.

* Postgres has its own calling convention for SQL-callable functions and conventions for loadable modules. Integrating with this is a pain because macros are hygenic and can't make up new symbols. Maybe procedural macros will help when they arrive.

* Rich APIs that rust supports don't always translate well to C. When integrating with a large application that pushes you toward the lowest-common-denominator APIs.

* A lot of C macros don't translate well to rust and just including a C header in rust is a lot of work. Hoping procedural macros will help here too.
> If you have cash and while driving home you deposit the money at the bank you have 4,000 US$

This is an ideal world calculation that also assumes the owner working in and out every day, no hired managers, no shift workers, no sick or vacation time for the owner.

How are you making sure you have enough coins and dollar bills to cover change? How is the cost calculation impacted if a rogue employee steals, a robber demands all cash, or if sketchy customer passes a counterfeit bill?
Threats, bullying, lawsuits: tobacco industry's dirty war for the African market
Tesla to start offering tours of Gigafactory 1, Panasonic to hold event/tour
One of the nice things about React's component model is that it's fairly straightforward to wrap up imperative DOM manipulation like a jQuery plugin into a declarative React component (assuming the DOM manip is scoped and not page-wide).

The React docs recently added a section on integrating with non-React code [0], and I've got links to several more articles discussing integration and interop at [1].

[0] https://facebook.github.io/react/docs/integrating-with-other...

[1] https://github.com/markerikson/react-redux-links/blob/master...
Except printer dots are a printer specific serial number. If it was printed on a recent printer then that might be concrete proof of forgery (i.e. if the supposed original document was submitted as evidence as having been contemporaneous of the document's date but was shown to have been printed much more recently because of printer dots).

If you see what I mean...

And I'm not really commenting on the current case (not familiar with it at all)... just positing a possible way to prove a document's date as inaccurate.
That's not at all what I am saying and you know it. It's also a gross misrepresentation of both home-schooling and standard school life.
> natural monopoly

I don't think so. Here in Germany I can choose my provider for power and natural gas provider freely although there is only one line for each to my house. For the last mile, we have mandatory must-route rules which work quite well.
China Will Reportedly Ban Personal VPNs by February 2018 – ExtremeTech
You're dreaming up a completely non-existent and totally hypothetical

Yes, my examples were only intended as illustrations. But isn't that also the case with the topic under discussion, net neutrality? I mean, it is not the case that any carrier has unfairly shaped traffic to the extent that they're determining winners and losers, and innovation with new products becomes impossible. This fear is totally hypothetical as well.

the status quo already has exception handling mechanisms for, and providing it as a reason for ignoring much more systemic and plausible harms

I think you're falling victim to fundamental attribution error. It seems like you're damning your opponent for a particular problem, while excusing the same problems for your own team:

The federal, state, and/or local government step in and provide disaster relief, including access to ice and/or medications.

Yes, but the official channels have been frequently shown not to work. Consider Hurricane Katrina. The FEMA help was ... not so helpful, and much of the initial response was actually courtesy of WalMart. I recall one store manager, trying to help people in critical need of medication actually taking a bulldozer and knocking down a wall of the store to get at it.

The government contingencies didn't work. The private sector doesn't always work out either, but much of the time it does a better job. It's silly to pretend that the private sector cannot do it, and the government can be depended on with complete confidence.

But my example of ice in a disaster was all just one example to show the thought process. There are of course examples in plenty other places.

Regarding my example of remote surgery data transmission, the responses from other folks here regarding QoS protocols was pretty constructive. However, I'm left with the view that none of us fully understands how Net Neutrality affects (or doesn't affect) its usage.
Dude, are you kidding me? "If you're not paying for it, you're the product" is taking about free for the user. There's so many ways in which this question is incredibly stupid, but here's an easy one: In what way is usage not free for every one of the billions of people who are untaxed by the USG? Or are you under the impression that GPS only works if you show your US passport first?
The thing about Vulkan is it moves a lot of the boilerplate out of the driver and into your app. That way you can just tell the hardware what to do (and not to do) without the driver trying to read your mind via API calls and optimizing that way.
Maybe because we sell dreams?

Many people think they will get damn rich with their app idea, but not so many can really build it.
Lambdu, Unison, etc. are all great in principle but share the same fatal flaw: no layering.

It's just one monolithic component trying to take on type systems, effect systems, syntax, version control, compiling, editing, distributed execution, etc.

All of these problems taken decades just to get to the shitty everything-is-text/worse-is-better state we're in now. I'm skeptical that any single team can solve them all at once, even with the most radical vision and competence.
I agree, snapshots are amazing for / on a linux machine. Makes backups actually work right, and be very inexpensive (computationally).

But, the tooling is still rather new and untested. At work we are still stamping out upstream bugs that really shouldn't exist, but the ecosystem is certainly getting better. It's only been a couple years since the ZFS on Linux project has gotten remotely any uptake by the distro folks, and even now that interest is rather tepid due to the licensing issues.

If ZFS was GPL I think it would have been the default filesystem on Linux for quite some time now.
Looks interesting! Any pointers on how one could actually get it though? :)

At this moment it seems only available for business users who opt in for the early adopter program.

Source: https://gsuite.google.com/campaigns/index__drive-fs-eap.html
One-month sugar detox: A nutritionist explains how and why
The 2019 Audi A8 Will Drive Itself Up to 37 Mph – ExtremeTech
Wow. Hard to say what might work here.

Do you have a demo video that shows everything your platform can do? If not create one and find 10 people in the restaurant business to look at it.

Get some feedback from more people in the industry ASAP.
I see a lot of shills posting their anti-Network Neutrality stuff here, so I wanted to chime in reminding folks of a few things:
Telco's were forced at one point to share phone lines. Remember all those DSL startups? Remember speakeasy? This was called local loop unbundling. What did the Telco's do? everything possible to break or interfere with these startup service provides. The telco's felt that it was "their lines". Customers were angry and eventually local loop unbundling was dismantled. Ironically - France, South Korea and other nations copied this idea for their high speed network providers - and it actually worked! You can get high speed internet in these countries from a variety of providers. Competition! If the FTC/FCC wasn't completely under regulatory capture, and telcos like AT&T were punished for this behaviour and competitors were allowed to provide services over last mile connections then yes, we might not need something like Network Neutrality.
Instead we have entrenched ISP monopolies and no competition. So we need consumer protections like TitleII and Network Neutrality. We also need community owned fiber networks springing up everywhere, which then over time could lessen the need for regulation as market forces would prevail. However, entrenched monopolies like Comcast and AT&T have to be shackled. It's the only way.
> We don't like it either

But.. but.. Scheme macros are so nice!
Just to add to this statement, even in cases where externs will still be necessary, adding CLJSJS packages[1] to your project's classpath will result in those externs being used even if you don't use the libraries that the packages provide.

http://github.com/cljsjs/packages
Verizon FIOS and Netflix at the same time, too.
Did Airbnb kill the mountain town?
https://www.reddit.com/r/programming/comments/6mvcol/firefox...
UGH this is a problem with all Hondas before ~2014. Drives me nuts. It's even worse when using it with Google Maps since the audio is delayed.
Sacramento, emerging from Bay Area’s shadow, becoming booming urban alternative
http://www.scality.com/products/ring/
But you do realise that pressuring distributions in that way (when there are still issues with integrating cargo and crates into our existing build systems) won't result in Rust being properly supported right? There will be some hack to get Rust to work "well enough" to build Firefox, and if someone wants to start packaging more Rust stuff then all of the work would either need to be redone or started from scratch.

I'm saying this as someone who has started writing their projects in Rust and has plans to ship said projects as part of openSUSE and eventually SLES. If you cannot satisfactorily maintain a Rust package inside OBS then it's a non-starter. I imagine that many other distributions feel this way. We were burned with Ruby (and continue to be burned by it) and I doubt that anyone is going to jump on the "just auto-generate an RPM for every version of every crate we need" solution.

It's great that Firefox will have Rust code, but I'm not convinced that will make the situation better for distributions. It'll just make the packagers more stressed out.
He would have to avoid triggering the 25th:

Whenever the Vice President and a majority of either the principal officers of the executive departments or of such other body as Congress may by law provide, transmit to the President pro tempore of the Senate and the Speaker of the House of Representatives their written declaration that the President is unable to discharge the powers and duties of his office, the Vice President shall immediately assume the powers and duties of the office as Acting President.

I.e. he must convince the Vice President et al. that ending all human life on Earth is a good idea.
I think so. I mean, aside from Node based projects, how many people are really doing pure-javascript apps? The pattern is typically JS on the front and something else on the back.

I guess if you can split out Node, React Native, and whatever other thing people are doing with Javascript that is pure Javascript, that would be a little bit more fair.
Almost entirely in developing nations from indoor cooking smoke. Dirty coal plants and electric ovens (or better, gas ovens and natgas fraking) would vastly improve the average air quality for these people.
You're a radio guy, I have two questions:

- Are there similar close range wireless protocols that are stupid simple (say like IR communications but on Radio spectrum)

- Could someone or some team something stupid that could be handled by todays micro controlers (esp32 is 7€ for a dual core 32bit processor, I suppose it can be used as a dedicated comm. proc)

In a way, wifi is perfect for 0-50m~, we just need a similar idea for 0-10 and low bandwidth.
>You really don't want non-profits filing patents. Really.

>This is pretty much the most horrible thing i can think of.

>It's infinitely easier to keep them from going bad (Example:

>MPEG-LA) if you can make their corporate bylaws, etc,

>prevent them from filing patents.

? Non-profits are corporations. They have by-laws. They also have several advantages over for-profits in the case of dissolution; eg, you can set up a non-profit so that the IP they hold is not simply sold to the highest bidder.

FTR, Xiph.Org is a registered 501(c)3 non-profit, and we hold patents.
> So, in our experience, Rust doesn't really offer us much except an alternative to automatic memory management that imposes a significant cognitive burden.

And zero runtime overhead.

> If you have this kind of programming background, the tradeoffs that Rust offers are not at all attractive.

I think you underestimate the attractiveness of zero overhead abstractions.
I worked for a client years ago, Dropbox was source control. It wasn't as bad as none, but you lost changes at the 30 day mark.
Everything that Arthur Schopenhauer wrote.

It's a lot about finding purpose in life.

I started reading his stuff and then I became angry at him and at me.

At him because he showed me that I'm a slave of nature and at me because I started questioning life and humanity.

Then I started to disprove his thesis and found my own purpose in life, not only that, it also gave me a much better understanding of human nature, which can be used in marketing or product design.
Having to wrap your logic with `(let [value (...)] ...)` in order make a new local variable is unnecessarily painful.

You can have more than one value in a let and it typically does not cause problems. If you do find it causes problems, it is trivial to change the language and invent your own, expression for defining local variables.

Its fine to have your reasons for hating lisp, but if this is the only thing that puts you off, I recommend giving it another try.
Lmao. Bluetooth is so random about working or not! So many conflicting views in this thread.
Thats what I am referring to - the certain quality of service and especially no throttling part of it. Of course technically no one can guarantee certain speed, but they can try to hinder it intentionally.
I'd start with a good hospital. And how you defines good is going to be personal. For me, I'd lean towards larger teaching hospitals in larger cities because I think teaching hospitals generally have good values that resonate with me.
Exactly that. I can essentially add/remove drives on a whim (for any reasonable definition of "on a whim") using btrfs and run a rebalance command afterward and I'm done.

That, of course, is really not a concern for enterprise use cases.
Now also imagine most people in the US only have one choice of hearing aid manufacturer. Also, that manufacturer happens to produce some of the radio programs whose volume the hearing aid manipulates.
Very interesting analysis. It seems to correspond with reality quite a bit more than the Bernhardsson analysis.
ahem gluster? ceph? really?

ceph is horrifically slow, and only has a rudimentary posix interface.

gluster is just well, terrible.

first things first a SOHO office cannot support a clustered filesystem, unless one of the people happens to be a storage specialist.

yea I hear lots of noise about how self healing they both are. That is mostly fancy talk for "I don't have backups"

Supposedly they both do HA. But yeah, its not something I'd want to support.

If you look at gitlab's setup, and their proposed setup (https://about.gitlab.com/2016/12/11/proposed-server-purchase...)

32 file servers to serve ~480TBs of disk. Seriously? 4 file servers, GPFS and 4 MD3060e. Thats about a petabyte of usable storage with a streaming throughput of about 40 gigabits a second.

"modern" clustered filesystems are mainly just toys. if you want speed, use lustre, if you want sexy software defines awesomeness with next level raid, use GPFS.
Let me make the following point. It seems to me that law enforcement should be able to utilize all statistics, facts, and research, just as a business person or stock trader would. These aggregate details are important, and throwing them out for fear of labels, or social justice backlash is counterproductive to keeping citizens safe.
Other than it being almost a complete waste of time with all the nonsense spam clickbait articles there nowadays, I don't see what other benefits there are from avoiding it really. Jealousy at people's fake lives perhaps?
Exactly my thoughts, you might see there something with better/more reviews.
"Survivorship bias or survival bias is the logical error of concentrating on the people or things that made it past some selection process and overlooking those that did not"
That's a ridiculous suggestion. It's blatantly ageist.
I can't understand why AirDrop is as unreliable as it is. It's abysmal and only Apple is to blame.
Most of the comments here are talking about previous predictions that failed to come true.

the current species extinction rate is estimated to be orders of magnitude higher than the baseline rate. I.e. this is not a prediction of the future, this is an estimate of what has been happening in recent history, based on observations of reality.
I realize that not everyone lives in the world of enterprise storage, so I appreciate your question.

ZFS is a filesystem (and also kind of a volume manager) and is designed to be fairly versatile and to run alongside an OS and applications. ZFS includes some impressive features long found in enterprise arrays, including snapshots, mirroring, replication, RAID, and data protection.

Dedicated storage arrays have long supported many more specialized features, and I urge you to read up on cool products like Pure FlashArray, NetApp SolidFire, EMC Unity, EMC Isilon, HPE Nimble Storage, Tintri, etc. You'll see that most/all have awesome hybrid (flash/disk) capabilities, all-flash tuning, integration with VMware, Windows Server, and Docker, scale-out capability, etc.

It's a pretty amazing field, and that's why I've dedicated my professional career specializing in enterprise storage. Maybe a good place to start is the Storage Field Day video series on YouTube: https://www.youtube.com/results?search_query=%22Storage%20Fi...
These "real customer pain points" seem pretty specific and isolated to me.
After issuing their threat, and getting "no" back, they would say -- "We do not negotiate with terrorists" and go in with the guns. Collateral damage be damned.

That's how wars happen, and why it's a bad idea to make ultimatums to the US government.
Also Tree-Style-Tabs is no longer supported. TST arranges the browser tabs in a vertical hierarchy, which has the dual benefit of logically arranging the tabs themselves and providing more vertical space (important on a 16:9 aspect ratio monitor).
why not? what if it is programmed to replicate itself to provide redundancy?
> Programmers like to come up with mathematical plans like this, but you would likely run into the Voting Rights Act!

More generally, many mathematically inclined people eventually come to the conclusion that we should have some sort of multi-member scheme but that too is bared by federal law -- 2 USC 2c (https://www.law.cornell.edu/uscode/text/2/2c)
Free to Read Albeit Horrible Interface Version: http://rdcu.be/t9oS
"Digital Sharecropping" is Nicholas Carr's term.

https://www.theatlantic.com/business/archive/2017/07/connect...

http://www.roughtype.com/?p=634
Eh, I would say Vulkan decreases reliability.

Precisely because Vulkan drivers are much thinner and do no error checking, it becomes very likely that you will end up writing code that works on one system but fails on the next.

Granted, OpenGL has some of the same issues. It's incredibly frustrating when vendor B accepts some GLSL that is forbidden by the spec, and then some application fails on the more conformant driver of vendor A because the developer failed to test properly.

The thing is, Vulkan multiplies these issues significantly. You still have a compiler in the driver, so you still get the same potential for shader incompatibilities. But you also get to manage barriers and texture transitions yourself, and boy is it likely that you'll get something wrong there. And since memory models are different across vendors (and even different between different generations of hardware from the same vendor), it is extremely likely that you end up with code that works on card A but fails subtly on card B.

There are tools that try to catch these kinds of errors, but they're far from perfect.

On the issue of memory management, I am unaware of any OpenGL issues here that make applications unreliable. Sure, drivers may not always manage memory optimally, but having an application that runs a bit less than optimally is very different from an application that renders garbage because you failed to allocate your textures with sufficient alignment -- which is something you can do in Vulkan.

So really, at the end of the day, Vulkan is about giving graphics developers foot-guns in order to reduce CPU overhead. That was explicitly its mission statement from the beginning!
You pick three industries that have a high potential for negative externalities as your examples, bitch about regulation, and then assume a political motivation for my objection. I think that "a few sentences" was more than sufficient for us to judge you.
I think Microsoft rolled this out as standard for OneDrive in a version of Windows (8? 8.1?), only to revert the change due to customer confusion.