skysight-inc/HackerNews huggingface dataset:
Seems like the story of apple again.

Jeff has no real tech credibility, he is a old school boys network business guy with dodgy/bad performance rap.

https://www.forbes.com/sites/adamhartung/2017/03/28/ge-needs...

"At this point, it is probably too late to save GE. By losing sight of the need to grow, and instead focusing on optimizing the old business while selling assets to raise cash for reorganizations, Immelt has destroyed what was once a great innovation engine. Now that the activists have GE in their sites it is unlikely they will let it ever return to the company it once was - creating whole new markets by developing new technologies that people never before imagined. The future looks a lot more like figuring out how to maximize the value of each piece of meat as it's carved off the GE carcass."

Good luck to the folks that work at uber. You are going to need it.
None of Swift/Java/Kotlin/Dart/.NET are serious challengers for low-level systems work.

It's those "few use cases" you are talking about that interest me.

Cedar had a GC-free, type-safe subset that used the typesystem for memory safety.
Apologies. I didn't notice this was about preact specifically. I agree that switching to preact is unlikely to help with any patent issues. I don't think any free licenses indemnify you from third-party patent claims.
When you put it that way, I expect to see a secondary market for stake. This could be implemented by selling the private key or by delegation similar to a mining pool.
Broadly speaking, I agree with beagle3's point (probably above this comment). But the thing that keeps me from being willing to quite commit to it is that it is generally a bit unfair to expect someone to produce this alternative programming paradigm and immediately be better than the previous one, which may or may not be broken or better or worse but has certainly had five or six orders of magnitude more time poured into it.

If it's truly the "silver bullet" I'd still say I expect to see some evidence of that in some domain relatively quickly, because it is supposed to be the silver bullet after all. But it would take time to discover that.
Official PS4 Symbol Codes by BannerR3 (Bann3r) via HydrogenNGU
Wi-Fi Vacuum Robot Review
http://knowledge.seagate.com/articles/en_US/FAQ/186849en

Links to images of the power supply labels which tell you the power supply is 12v with - on the outside.

You can just use a universal adapter for that.
Hmmm, I really like the terseness and obviousness of that approach, I use it all the time :)

I have sometimes been caught out by doing `{somearray.length && thing}` though, which leaves `0` hanging out there in the false case...
Facebook's Challenge of a Gag Order Over Warrants Will Get a Public Hearing
Phantom Intersection Cause Traffic Gridlock
> The fact is that many lawyers, including the Apache Foundations lawyers, disagree with this assertion.

Incorrect. The ASF's objections had nothing to do with believing Facebook had any patents, and many ASF projects are looking to move to Preact, which is presumtively covered by the same patents React would be (if any).
Simple, fast and safe manual memory management
Wow, this is going to be bad.
I'll use a ternary if I want something in the "else" case, but otherwise the `&&` / `||` approach is more readable to me (there's more to read in a ternary to figure out that there's nothing happening in the else case, whereas it's obvious with the boolean approach without reading further).
> This is an RMS concern.

Stallman is on record as saying he's fine with the patent clause. :)
OpenBSD has been expanding the fork+exec model throughout its source tree, since the OpenSSH preauth work done by Damien Miller, many more followed. The list includes bgpd/ldpd/eigrpd/smtpd/relayd/ntpd/httpd/snmpd/ldapd and most recently slaacd & vmd.

A few remain but are being converted as they are discovered.
Sounds to me more like "shared source" that MS used to push.
I just didn't want to derail things into another "AA is bad because it's religious" discussion. To paraphrase Heinlein: If solemnly rubbing blue mud in my belly button would have gotten me sober, I would have done that. If something like Rational Recovery had been an option, I would have gone. But AA is free and there are meetings everywhere, nearly all the time.

It is kind of dismaying to get out of nearly a month of expensive treatment and then be told, "Welp, pretty much all we've got for you at this point is for you to attend a crapload of AA meetings, good luck." But I figure that desperation is an important part of staying sober, at least until you've fleshed out some kind of support.
https://smile.amazon.com/Adapter-Maxtor-OneTouch-Personal-St...
It's the old perspiration vs. inspiration. I would argue even in those other fields it's more perspiration. It may look like someone has this one off inspired idea, but then we're ignoring all the work they did to get the point where they could even have they idea.

This often occurs with athletic endeavors too. People remember Jordan's game winning shots and talk about his talent (which of course he had), but they forget about the hours and hours and hours of work he put. Kobe Bryants and Kevin Durants workouts are the things of legends.
The businesses that win in that way (VHS vs beta) do so because there is money flowing.

It is unclear that with docker they really have much income, and enterprise software projects that perhaps make up most of their income are frequently rewritten with new toolsets.

Therefore, it is uncertain there will be commercial traction in 5 years... particularly because docker has (according to this thread) already lost the open source feature set battle (targeting a demographic which, incidentally, tends to shun marketing).

Hence, house of cards.
John Sculley.

"Jeff [Immelt], do you want to sell planned-obsolescence dryers and weather derivatives the rest of your life?"
That was amazing. I love crotchety grizzled engineers more than anyone I think. This was classic and hilarious. I can't wait to share with everyone at work.
The abstract reads like something that could be generated by an automated paper generator.
What about paper wallets?
And then there's "Weird Al" Yankovic, who started out able to hold his own with many of the pop stars he parodied and put out more consistently brilliant work as he got older.
You don't have to use .vue files to actually write Vue[1].

.vue files are there for simple single file components[2].

[1]: https://jsfiddle.net/yyx990803/y91wy85p/?utm_source=website&...

[2]: https://vuejs.org/v2/guide/single-file-components.html
Sony bans your PlayStation Store account and you lose all your games when you do a chargeback[1]. Yet another reason to never buy digital downloads from Sony.

Edit: Steam puts your account in a restricted mode when you issue a chargeback[2].

[1] https://www.reddit.com/r/PS4/comments/2ivsz3/beware_if_you_s...

[2] https://support.steampowered.com/kb_article.php?ref=6687-HJV...
There is a problem with doing a chargeback to a console/platform exclusive service - they can give you your one refund then terminate your service and you lose access to the service. IIRC one of the big game services does this.
Allowing other browsers to be installed didn't stop Microsoft from losing an anti-trust suit.
How did they justify (to themselves) how their laundry list of must-do's became can-skip's?

Did it make a meaningful difference to the conclusions or strength of conclusions in your thesis?
I just want to cherry-pick one thing that you said without offering commentary on the rest of your comment.

> But "curing" pedophiles seems to be hard, similarly to how you can't "cure" homosexuals.

I understand what you mean here, but I think you could have made a better analogy. Homosexuality is not predatory. It doesn't seek to exploit anyone, even indirectly. Pedophilia, when practiced, exploits children (directly or indirectly). Certainly, you can be homosexual or a pedophile and reject the inclinations that you have. Being a "practicing" homosexual does not harm anyone--except perhaps those with delicate sensibilities--while being a "practicing" pedophile does. "Curing" homosexuality implies changing someone's harmless disposition. "Curing" pedophilia implies rehabilitation of someone who actively seeks to exploit children for their own pleasure. Governments and organizations have no place deciding whether someone should be "cured" of homosexuality because it doesn't affect or benefit any member of the public. There is no need. Governments have a responsibility to keep children safe, though, and rehabilitating sexual predators is a crucial part of that.

The distinction is an important one. A better analogy would perhaps be a comparison to addiction. Addiction is very hard to treat, and there is no truly successful cure for it. Addicts don't harm people, but the people procuring drugs like heroin and cocaine often do.
I don't know why actors are on his list, but speaking from my own experience, I think actors are one of those cases where some languages (Erlang in particular) got some stuff accidentally correct because they implemented actor-like stuff, but it wasn't necessarily the actors that did the good stuff. Go's runtime is theoretically somewhat similar here, and despite years of work in Erlang, I almost immediately found myself preferring to work in a relatively conventional imperative language where concurrency was cheap, rather than "an actor-based language".

Perhaps the core problem is that no matter how you slice it, the nature of being an actor-based system means that cross-actor calls are simply more runtime and cognitively expensive than a conventional function call, and across the sum total of the system, that ends up adding a lot of drag. It may be the case that "cheap concurrency" added value, and actors actually net removed value, but the sum total was positive in the end. (I'm spitballing a bit here, to be clear.)

To really see the cheap concurrency in play, Haskell is a great place to play. It has a ton of mechanisms for concurrency and ways of composing them together, which kind of makes it an interesting cage match environment for what concurrency primitives are useful. Actors would be really easy in Haskell, and they basically go unused. I suspect this means something.
I think the bad idea stigma stems from people XORing from the same source. That totally is a bad idea, but if two sources are wholly independent, the maximum entropy in the combined systems is maintained.

To the people that just say it's never a good idea and scoff at any reasoning I'd remind them about OTPs. They are a special case related to this principle of XORing two independent sources together where only one input is random and it is proven mathematically to work.
As a freelance developer at the low end of the market (ie. where most apps and developers live), I can assure you that the logic layer is usually so small that the benefits of making only it cross-platform would be minimal. Most of the code in most of my apps is UI code. RN saves me roughly 80% compared to two entirely separate native codebases. A cross-platform business logic core saves me perhaps 20%.
Actually my major complaint of React is the state of state. There seems to be no common knowledge about how to do this right. I just joined a team that has two React projects that development started about two months ago (I just joined like a week ago). There is a a large component that I am working on that is completely bound to Redux. There are major state update issues and the team had opted to assign IDs and data to the DOM elements and use those to look up state in the redux store before modifying it. On top of all that, the application is completely unable to handle 2 instances of any component they wrote. I am trying to re-write some of it to encapsulate the state in at the component level. It's pretty awful compared to the Angular (not AngularJS) app I recently rolled off of.

Edit : Also wanted to add, while I think a lot of people really don't like JSX, I actually do like it but I think someone could take that aspect and come up with a better state management system outside of redux and friends. I think something along the lines of Angular (not AngularJS) with JSX would be great.
These questions are largely unanswerable in their current form. Like"estimate the probably of disease in a city given Nationwide has a low probability". Like, what the heck does that even mean. I could imagine a dozen answers. I can only guess they are trying to get you to think about Bayes probability an event occurs given X independent identical trial). But that's ludicrous, because on what world has anyone proved disease occurs uniformly at random?
Let's see what our tests in 20 years say. Olympic marathons have have been dropping winners for years and years as tests improved.
But suppose you DON'T try to patent it. You just invent it and try use it or sell it. What then?
On the other hand be careful with chargebacks especially against a retailer (Sony PlayStation store) that you would like to keep your account with. They could very easily just close your account and then your PlayStation is mostly worthless.
It's not entirely wrong. If you get into a patent dispute with them, you lose the patent grant to React, which means if they have any (none have been seen yet) patents related to React, they can very quickly countersue you, making the patent suit from your end, while still valid, a guaranteed financial ruin for any business not on their scale. We're not saying the license + patents combination explicitly grants Facebook the right to infringe on your patents, but rather it's a trap clause that makes it impossible to survive a patent lawsuit against them by virtue of using React, which in _effect_ is like a patent grant back to them.
That article is a bit biased, especially given that it ignores that not only has GE has paid out around $15 in dividends since Immelt took over, and that GE stock was in a huge bubble at the time.

Uber doesn't need tech leadership, it needs adult leadership. It's wounds are all entirely self inflicted.
I always assumed the answer was "because Sony is a hardware company that has never understood the first thing about software."

Turns out I was right.
In that case I won't waste my time reading this, but submit my outline of a Useful Theory of Software Engineering:

It comes down to making a good choice in each of the following areas. (My choice is in parens, along with my comments.)

Cloud Platform
(For historical reasons I am on Azure. I have some experience with Google. It does not hurt of course to work in several, but the cognitive overhead of gaining a real in depth devops knowledge on very many platforms will be overwhelming for many people, especially as the vendors invent stuff on the fly.)

Relational Database Management System
(Strive to learn SQL and 1 or 2 platforms, mine is SQL Server, as best as possible. There is only one useful data model, and it is the relational model. You will store data with other means over your career, but learning them is mostly trivial, and if your are intentionally using a different data model than relational, you should have a good reason. Also learn to data model using natural keys. This is a huge topic unto itself. The main justification is it will simplify the queries you end up using. A friend of mine is working on a book on nat keys. There is a real shortage of good literature on this topic.)

An application programming language
(Mine is F#. Learn one or 2 languages well, chosen because the compiler and canonical workflows do so much to keep you out of trouble. You will have to know 1 or 2 scripting languages our of necessity. Given the other areas you need real expertise in, I am not a fan of spending a lot of time with the language of the month club. Become an expert in the language(s) you use. It's a career-long pursuit.)

Project Management
(Recently saw a good overview video of the "no estimates" approach. I was sceptical before I saw it. Not really impressed by Agile, but I don't want to wade into that swamp.)

Specification Language
(A new area for me. I am interested in TLA+, but I'm still learning it. The idea of a specification language that delivers an unambiguous spec at an arbitrary level of granularity that you can manipulate and refactor is very appealing to my sense of propriety. We spend too much time going straight to prototype in our favorite language, refactoring it, etc. TLA+ forces you to focus on actual spec and not implementation details. The prototype approach leads us all to confuse implementation and spec.)
This is personally one of my major pet peeves, because I like to write secure code, and I think you very rapidly end up half-reconstructing capabilities work if you do, and it is not hard to notice that you basically get no help whatsoever from languages. It is still clearly a nearly-invisible problem to the vast majority of developers. You need something almost Haskell class simply to assert "Please, at least provide me some evidence that you ran some sort of permission check." to access a resource.
Yes, let's separate people who disagree and avoid letting them talk about their disagreements in person. It's much safer to avoid anyone you disagree with, and minimizes hurt feelings.
Also you can do with just JavaScript. With render-function.

h('ul', [ h('li', 'one'), h('li', 'two') ])

And use native array methods instead of v-for v-if and filtering data with component methods
Because they desperately need a grown up. Uber doesn't need to be innovative, it needs to execute without continuing to shooting off it's toes.
A lot of people will have a bundle that they've transpiled, but use the global React object from pulling in React and ReactDOM from a CDN. Other folks will use a library that offers syntax like:

elem.div(elem(Component, {prop: 'value'}), {className: 'foo'})

It's surprisingly common, and it's listed not too far down on the React installation page:

https://facebook.github.io/react/docs/installation.html
This is most relevant (and troubling) among younger people. While its just as possible for older people to get wrapped up with their smart phones and social media sites, at least they weren't completely absorbed their formative years when their brains were developing. We are in the midst of a massive social experiment with a generation of children being raised with these devices, social media, and all the many things that are entailed. How it is going to turn out anyone's guess.
this is a great parody of the alt right. It is not casualty that alt right is born in USA, compared to other industrialized nations, education levels are low
My point is the web frontend target is such an obvious one here. Specially given the dart to javascript compiler history.
Why do you think the problem can not be fixed?

Also, have you looked at the redo tool redo-ifcreate? http://news.dieweltistgarnichtso.net/bin/redo-sh.html
Why? He can't be anywhere near as bad as Kalanick.
Lyft would love this.
How to Win More Clients by Using Images in Your Event Proposals
Should Immelt become CEO this would be a huge culture shock not only to UBER employees but also drivers given the button downed culture Immelt originates from. He is also very financially focused so not sure we would continue to see pricing that we are accustomed to in the long-term. On the plus side, he comes with a reputation of integrity and professionalism which may help Uber gain entrance to cities and other areas that have previously been inaccessible.

I realize Immelt fits the picture that the Board is looking for (professional, intelligent, organizational, experienced, etc) but given SV's tendency towards men under 40, Immelt does not fit that bill at all. Would be interesting to see how well he would be accepted at all the tech conferences, events etc.
Sounds like they might be trying to push a special interest bill. Wonder what company has a "compliant" crypto currency waiting in the wings while they try to get this law passed to give it an advantage in the marketplace.
"and operate within EU's laws, guidelines and cultural frameworks -- giving it a much wider perspective than 10.000 Americans (+ some wannabe Americans that came there to study/work) in a building in San Francisco."

10 years ago I would have disagreed with that statement. Now I can't. SV has gone nearly ideologically monolithic. It may be literally the greatest danger facing SV right now, not that anyone in SV sees it that way of course. I don't live in SV, and I am starting to see people in my real life (not just on the internet, where all kinds of crazy things get said that don't really mean anything) start naming it as a problem. I haven't had to reassure anyone that I work for 'an SV company, but not that kind of SV company' yet but it's probably less than a year away at this rate.
12v 3 amp, center +, direct current, as written on the label
Agreeing to use social consensus to enforce the protocol doesn't give a green light to using it to change the protocol. As the DAO and the BCH hard fork showed, having an objective proof of work consensus protocol doesn't protect the blockchain from a social consensus to change the protocol.

That being said, depending social consensus to determine what happened could make it more likely that a faction will use it to determine what should have happened. I personally don't think it will make it very likely, given the inertia of the original chain, but we'll see.
Didn't say or imply that there weren't consequences.

If you aren't rich enough for appeals court then none of your rights matter and it is helpful to be aware of what the collective conscious believes is legal / illegal.
Also, better shoes and track surfaces.
How to Overcome the Biggest Remote Work Challenges
It depends what you mean 'on top of'. If you mean adding some RN to an existing app, that is conceptually easy but practically quite messy (https://facebook.github.io/react-native/docs/integration-wit...).

If you mean adding native modules into an essentially RN app, that's practically very simple (https://facebook.github.io/react-native/docs/native-modules-...) but still requires some conceptual care (like any API design).
This is just trying to elbow your way into an established community of <skilled individuals> without proving your mettle. This is exactly the wrong way to try and earn respect. Whatever you do, don't try surfing. With that attitude, you will get into a fight in the water with people that fight in the water, and you will lose the fight. Or if you don't get into a fight in the water, they will follow you out and fight you on land. Yes, it can be childish, yes it can be stupid. Of course not always, but it does happen. But that's surfing, and that's just the way it goes.
Technology news aggregrator of aggregrators
According to some of the comments on the post this is supposed to be satire.
It's gradual typing. Yes, it's full of holes, that's the whole point.

There are other languages with strong, powerful type systems that compile to efficient JavaScript, such as (in order of power) Elm, OCaml, PureScript and Idris. Those four are just arbitrary examples however, there are quite a few more.
> I wish there was a language that embraced mutability instead

IMHO Rust manages to do this really well - the system of ownership and borrowing brings all the safety of immutability to mutable data. Check out the "Why Rust" video: http://intorust.com/

It's not really viable to use in place of JS yet (only via Emscripten, which results in a huge bundle) but the future looks bright for Rust.
It's possible both can be bad for different reasons. To be fair, the GP didn't specify what "bad" meant.
The UK Royal Society, a Case Study – Risks of GMOs Systematically Misrepresented
let's see:

- Blockstream pushing AML complaint payment channels over the Lightning Network (bitcoin, any bitcoin fork)

- Goldman Sachs who has a filed a patent on basically a bitcoin-clone

- Ripple

- maybe Waves
Show HN: Storage on GitHub for Ghost