skysight-inc/HackerNews huggingface dataset:
> I am never a fan of two way data binding as an alternative.

The author is wrong. Vue doesn't have two-way binding. It has one-way binding with events. Components can't force anything upon their parent's state with an event.
Refusing customers and irritating Google probably isn’t in their best interest.
I started doing this after I came back from living in Korea a couple of times. The only one who ever tried was, I think, Sprint or another carrier, who offered to put a hold on my account but they could only do that for some short number of months, so of course my next reply was "I'm not planning on coming back."
No. For lying to their customers.
Honourable mention for FANN - Fast Artificial NN, also in C,
has a nice set of features and was a pleasure to use.

https://github.com/libfann/fann
Again, results depend on the person and effort exerted.
Since "youtube-dl does not include support for services that specialize in infringing copyright", is there a fork, or addition, without this restriction?
You provided a specific example of a topic with existential importance. I responded to it.

I do not think you can make an argument against gay marriage which treats all sexualities equally, by very definition.

If you feel you have an argument about why the government should deny homosexuals the right to marriage, but that does not treat homosexuals as lesser than heterosexual people, I'm all ears!
I like the WebComponents integration, but the rest feels like Ember components to me.

React achieves much more with much less.
>Our workplace is illiterate, thus we cannot process your emails.
Another thing I'd like to add is that if you learn JS from the ground-up, methods in jQuery and lodash can be picked up on-the-fly in a matter of minutes; they are basically just sets of util functions for javascript.
> Have you examined the arguments and evidence, which thousands of experts have examined and been convinced by?

Which "thousands of experts", are you referring to, exactly?

Sure, there could be many thousands of "expert" historians. My point is, have you personally "examined the arguments and evidence" of those thousands of experts, who you claim have been convinced by said evidence? If not, why are you arguing on their behalf?

>What exactly do you object to?

I'm objecting to the fact that some of them (whose claims I have read in history or Sanskrit courses I studied in school), state things about people and events of centuries ago, as though they know for sure that those things happened in the way they claim - without providing evidence, except for their assertions, which anyone can make.

That's why I have a healthy skepticism about them.
> I’m not sure about this.

Which is why it's a policy disagreement. A lot of the people who want Facebook dead and gone still think it should be done via competition and technology rather than government regulation. Others may disagree. But neither position is any proof of being a shill for Facebook.

> Surveillance capitalism is the business model that Facebook and Google have chosen, but that doesn’t mean that we can’t have a social network or a search engine sustained though a different one.

Right, that's kind of the point. If we can build one on a different model and get people to use it then Facebook will wane without any requirement for government intervention, and a lot of people are actively working on that right now.

But if you pass new laws, they typically have unintended consequences. Normal non-surveillance businesses will still have their customers' IP addresses, names, email addresses, etc. for normal business reasons having nothing to do with data mining. If regulations require anyone with that kind of information to be a large established company in order to afford the compliance costs, you won't get new competitors anymore.
The ugly in this article isn't really the ugly, it's the good. Nobody's holding you back from writing a simple ES6 module that handles API requests for you. Vue is a view layer, nothing more and nothing less.
There is no such thing as a DevOps engineer
State management seems like inherently a different problem to solve than the problem React solves. What front-end framework out there has a single state management pattern that works for all sizes?

It’s easy to point out frustrating things or hard problems; it’s not easy to point to a way out.

Personally I love the explicit state flow react forces, and I would hate to move to a framework where I spend time figuring out how data goes from point A to point B.
Definitely. We're still following the first half of the book almost to the letter.

Teller once noted how effortlessly he talked to small children, then wondered if he employed the same knack to talk to everyone else...
Without hard data, this is pretty meaningless. If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint.

> I doubt this is the case since the users are keen and vocal. I get messages almost daily from them telling me the features they want to see.

Maybe existing users (and even for that, I'm skeptical), but how many potential users did you lose because they couldn't even open your app?

I'm not saying you are wrong, just that "users didn't complain" != "users weren't affected".
I don't get the thing about ReactJS boilerplate where he says "Moving from React to Vue seems like a breath of fresh air. No more bind(this) or setState() everywhere. Yay! "

Surely there's better ways of doing ReactJS rather than lots of setState? Of course I use setState but try to avoid it generally.

And I almost never, ever use bind() - don't es2015 fat arrows make it obsolete?
"If there’s a need for this we’ll build it."

There's a need for this. Please build it.

"neither scenario has materialized yet."

Well yeah, it's a young product. Only a matter of time before it's abused.

"The other option would be to have threads go live in X hours unless someone opts out."

Substitute "hours" with "days" and I might be okay with this. "Hours" is way too short.
Why don't they build sites with many small productised nuclear sub propulsion type reactors, as opposed to a single monstrous and pretty much bespoke reactor? I'm sure there's a good reason but on the surface it seems like commodity reactors would be a far cheaper approach in the end.
True. But if you listen to his interview it is clear that he is neither pessimistic nor optimistic. He recognizes that unanticipated breakthroughs are likely. His point is that there are too many unsolved problems for a quick development of useful driverless cars. He goes through the issues in some detail, but to offer one: real world drivers need to break the law all the time in order to not get stuck in traffic. How do you decide when it is OK to break the law? Who will accept the liability associated with a car that sometimes breaks the law. Etc.
judging from where i work, that has already happened to a large degree, and i would guess elsewhere too... as alan kay would say "its all a pop culture"

edit: spelling mistake
From the abstract “... testosterone increases positive attitudes toward positional goods when they are described as status-enhancing, but not when they are described as power-enhancing or high in quality.”

I would think power-enhancing things would improve one’s ability to achieve social dominance, but the effect they uncovered here seems to be even more crude and instead only has effect on stimulating a desire for immediate “improved” perception.
That's true, but it's also a balancing act since after a certain point the body converts protein into glucose.

I remember how, after years of eating high-carb low-fat foods, I discovered how satiating protein-rich meal could be. Well, that and one high in fat. No longer did I feel the constant craving, but at the same time it became easy to go "woohoo!" and eat way more protein than was necessary. I'm sure years from now doctors will ask me what the hell I was doing when they find my kidneys have been wrecked.
Version with debug enabled:

<script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>

Production version:

<script src="https://cdn.jsdelivr.net/npm/vue"></script>

If you need something more complex, vue-cli has webpack inbuilt:

vue init webpack my-project
cd my-project
npm install
npm run dev

Or if you need webpack, but not the complexity, swap the word 'webpack' in the above command to 'webpack-simple'.

... Vue has already done the hard work of getting the build apps configured for you.
Use Typescript. Use async/await. Use ES6 classes, don’t do the other class-like patterns. Oh and use ES6 features in general, like fat arrows. And don’t write “var”.

Don’t use unnecessary compile-to-js syntaxes like Coffeescript since they will just be a burden in the long run. TS and JSX is an exception, those are worth it.

Don’t write “undefined” in your code, just write “null”, and treat those values the same. Some programmers will assign different meanings to “undefined” versus “null” but usually these meanings are arbitrary and silly. In most situations you don’t even need one kind of null, let alone two.
but would not that make you feel a little guilty as you are lying to the person just to cancel a subscription?
> I know of no more encouraging fact than the ability of a man to elevate his life by conscious endeavor. It is something to paint a particular picture, or to carve a statue, and so make a few objects beautiful. It is far more glorious to carve and paint the very atmosphere and medium through which we look. This morally we can do.

-- Henry David Thoreau
Yeah, there are equivalents in the yellow/white pages industry, from what I've heard. That wikipedia page shows that it doesn't always work, but it is an interesting idea.
> Robotaxis stand to challenge the economics of personal vehicle ownership

I have yet to hear a compelling reason why I would give up my car, and if I did why public transit isn't a better option.
With some assertions missing to assure there are no actions upon null pointers (e. g. return by failed init functions).
Is this intended as hyperbole, or is there really a billion dollar salamander I should know about?
That doesn't really answer the question. :) How does Vue let you deal with "simple (but rapidly changing) requirements" better than React?
How Three Teenagers Helped Nintendo Create Star Fox
There's also the fact that Hofstadter persistently equates strong AI with grandmaster-level chess-playing, and the entire chapter of nothing but totally unscientific, unfounded, incredibly wrong, biology-free speculation about how the human brain works.
That's exactly what Nix does! Nix is wonderful tech that unfortunately seems doomed to low adoption due to poor usability. My belief is that this stems the fact that maintaining the package tree is obscenely costly of contributor time, leaving almost no time or energy to make progress on "niceties" like improving the core CLI experience and the continuous integration system.
Why should we feel guilty when companies like this do their best to hide important things from the people they're billing?
I don't. The only reason why this deception is necessary is because of the company's scummy cancellation policies. Heck, one could argue that it actually reduces labor costs because emails are usually less time consuming than phone calls.
>How can it be, when it’s a willing participant in the PRISM program, which lets the CIA and NSA siphon whatever data their spies need directly from Apple’s data centers?

Isn't this a bit of a oversimplification? Is Apple really just opening their entire data center as described?

For an article that wants us to look deeper or take a more critical look quotes like that seem really dumb if Apple isn't just opening it all up.
Out of curiosity, what are you using instead of JSX? Plain `React.createElement()` calls, `createElement` aliased to a shorter variable like `e`, or something like the `react-hyperscript-helpers` library?
Nice, but is the "pro" version really necessary?
Not everything needs to be monetised..
H1-B is dual intent.
That doesn't answer my question. What about Vue actually made it a better choice for those requirements? In my experience, the fact that React is a simple view library makes it the perfect choice for small shops. You're taking on considerable risk when you use a technology without a vested backer (Facebook is heavily vested in React, look at Angular 1 for an example of a framework with a big backer than is not vested, the API was completely broken in a rewrite). Smaller frameworks also suffer from a lack of sustained development.
People aready hated on this with React, why should they stop with Vue? :D

I guess Ember and Angular are more of one-stop-shops in that way.
Generally, I like his evidence-based protocols over the predecessor, but #2 (in your list) is troubling (as implemented.

Hes's a corruptocrat and must go ... but I actually like the (general) balance (Cost-Benefit) of most (most! not all!) of his diktat moves.

Sometimes it feels as if that agency was arguing over parts in a million vs parts in a quadrilion. At some point - it just becomes too expensive to implement for no benefit except to guarantee jobs to a lifeless bureaucrat. (Well, I guess that was an assessment, so I should say: It seems so to me.)
Call me what you want, but I kinda get it. The world has a lot of places... nations, they all expect you to cooperate, is that Apple's problem to solve by sitting out? Does that really do anything?
Amazon doesn’t “lock you in” with VPS hosting. If that’s what is costing you, you can access all of AWSs other services over the internet. You can setup a VPN from your colo center to AWS and still access all of thier managed services.

How is it less complex to host your own database servers, load balancers, queuing system, redundant storage, CI/CD servers, ELk stack, redundant memcache or Redis servers, distributed job scheduler (I’ve used Hashicorps Nomad in the past), configuration servers, etc. These are just the services that you don’t have to manage the underlying servers and you get redundancy.

I’m first and foremost a developer. But the money the company I work for saves by not having to hire dedicated people to manage and babysit servers more than makes up for the cost of AWS.

It just so happens that I know AWS well enough and have experience as an “architect” (and have the certifications to give them a warm and fuzzy) to be competent at the netops and devops side of things.
This is my only account, just signed up recently, and the name was just spur of the moment.
Sorry if it comes across as trolling, that wasn't my intention.
I just know a bit about Rodney Brooks, am a fan of his work, so I gave my 2 cents.
I don't think the point of the article was that EFF should _not_ fight government on privacy, but that it _isn't_ also fighting the same fight, for the same privacy, against corporations. At least, that's how I read it.
It then goes on about how current copyright laws are broken and that SEPA was an attempt to fix that, which should have been heralded. Personally I do not fully agree with this, but the main point of the article (again, for me) was the "hypocrisy".
I havent read all responses above, so excuse me if this is repeated information.

To answer your question, you have to understand how VCs operate. How they raise money from other institutional investors, rich folks etc and how they need to return that money in a finite time (4-5 years) Everything comes down to money for that reason.
I think the answer is that there is no right or wrong answer. Something that has worked well for me was to put my API calls in a seperate module and call this module whenever I need it (either in Vuex or a Vue component). Very simple.
Completely agree. Aside from learning the basics of the language (which if you already know any other "C like" language isn't difficult), gaining a good understanding of async flows (Promises then async/await) is absolutely key in JS and is probably the biggest hangup I see people run into.

Where I work I'm considered the JS "expert", my coworkers consist of a few older seniors that mostly do backend work that think JS is bad/confusing language, and a few juniors that really only have experience with languages they learned in school (which probably doesn't include JS). And 90% of the issues I help them with are caused by a lack of understanding of async JS -- "why is this value undefined?" or "how do I get the data out of a Promise" and for the latter telling them "well, you don't get the data out of a Promise, you would chain it with .then(data => data) to operate/use the data" is usually met with even more confused looks. Though async/await helps a ton with how they use the data from a resolved async operation, you still need to understand promises (at least a little) since it's built on top of them (e.g. in a try/catch async block the lines after the await are essentially the function that gets passed to promise.then() and the lines in the catch block being the function that gets passed to promise.catch()).

Two other things I'd like to mention (which could be under "learning the language") that I think really help with really understanding JS and being able to use it well are:

1. Understand the Event Loop[1]. Learning this will make a lot of JS's oddities make sense, and is something you should learn even before learning about async JS as it will explain how your async function actually works under the hood (i.e. the non-blocking nature of JS).

2. Closures/Scoping

[1] https://www.youtube.com/watch?v=8aGhZQkoFbQ
No plan survives first contact with the enemy?
Not really. It’s all the same set of problems.
Sometimes accelerationism is the only way
>If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint.

And I wouldn't miss you.

I can make the service better faster if I don't support the lowest common denominator. I'm sure I'd lose more users if the website was bloated with fallback code and my development speed was such that features are a year behind where they are now.
Sort of. The nicest-looking approach is to use the Stage 3 Class Properties syntax to write class methods using arrow functions, which auto-binds them to the component instance as it's created (the equivalent of calling `.bind()` in the constructor).
Perfect! California leading the way, cancelling subscriptions shouldn't be an issue at all, sadly business use fraudulent ways with it.
If I find myself dramatically diverging from someone's perspective, I make it a point to internalize exactly what they are saying to the point it makes sense to me.

The worst that can happen is the next time we disagree, I understand both sides. It's sometimes emotionally destabilizing to do such a thing, but it sure is nice to understand almost every person no matter what walk of life they come from.

I've picked up on doing this from some very smart people, and the hilarious thing is, when you get used to it, it's like you can't recognize people from 'that tribe' of thinking directly.

I miss socializing, I feel lonely often. But the level I understand people, shrug. Sparse connections between people. Sparse, but very strong ones.
I've used React full-time at work for a year and a half now, and I did a personal project in Vue for a while to try it out, before converting it to React.

There are some things I really, really hate about React. It is not kind or accommodating (Vue is both of these things), but it gives you control. I was head-over-heels for the first few days of using Vue; "breath of fresh air" is exactly the phrase I'd use. But the project I was using it for was an IDE of sorts, and eventually I just needed more control than it allowed for.

If someone told me they were going to build a basic website - not a web app - with React instead of Vue, I would laugh at them. Vue truly is a successor to jQuery for the reactive age. But for really complex applications, it's too "magical" in my opinion.
Funny thing is, React uses that API because two-way-binding is considered bad practice.

But I guess old habits die hard...
At a previous employer that provides a subscription-based online digital service one task I was given was removing the ability to cancel said subscriptions via the website and replacing everything with calls to customer service. (Apparently it had a quite measurable impact on retention. To quote one of the managers, the people trying to cancel didn't actually want to cancel, what they really needed were "instructional opportunities" that customer service could do over the phone. And to be fair, I do think there was an element of "I don't know how to do thing X, I'll just cancel" in some of the cancellations. But not all.)

It was among a handful of similar reasons that caused me to leave for public sector work which isn't based on used car sales type manipulation and evil BS.
And if you are asking me if I have examined the evidence of those historians, what is your evidence for making this statement (in an earlier comment above, by you)? :

>it wasn't due to lots of Sanskrit speakers vacationing in France.

It may be true or false, but have you examined the evidence for it, if any? If not, how are you saying it categorically, and questioning my doing the same on another point (about historians)?
The software that is just a better init system continues to not be.
Amazing write up. I have been through it (now in a second startup) and can relate to most of it. This is like the book I can read as summary of my journey through startup world.
It seems his resignation was directly related to his "administrative choices". It wasn't coincidence that his resignation came minutes after a NYT story alleged that he ordered the deletion of records that are mandated for preservation by federal law:

https://nytimes.com/2018/07/05/climate/pruitt-epa-calendar-m...
Deriving the Y Combinator in JavaScript
From benchmarks I've seen elsewhere, native code is generally roughly 2x faster than WASM, so I doubt that's the case. I'm sure it depends on a lot of factors, though.
A Physicist's Proof of the Central Limit Theorem
The author's main points are:

* The dialogs are overlong and obtuse
* Some specific metaphors don't click
* The author attacks various things which he feels Hofstadter belittles (avant-garde music, Zen)

He may be right about the dialogs, though as others have said perhaps it's better to read the chapters backwards. Or, even, metaphorically like the Crab Canon: dialog, chapter, and then dialog again.

He's clearly projecting his own perspective without thinking about the perspective of others when it comes to the metaphors. This won a Pulitzer, not everyone has a mathematical background and can straight up understand Godel when directly explained.

But it's the third part that is most troubling. These days it's fashionable to take some earlier cultural artefact, and assassinate it on the basis that every point of view is valid, genuine, and can't be criticised. I smell that same pattern in his counter-attacks on "avant-garde social commentary masquerading as music" and Zen. Hofstadter has an opinion on these. A strong, negative opinion. Attacking Hofstadter the way he does to me more smacks of a post-hoc character assassination than intelligent engagement with the material.

As an aside: I read Hofstadter (somewhere) say that he has spent a lot of his life after GEB trying to hammer home that it was about self-reference, self-reference, and nothing but self-reference. I think he even described "I am a Strange Loop" as being GEB but much more direct (I still need to read that one).
Finally! It's nice to see an attempt at a level-headed response, and from the person it was actually directed to (and that you had actually put thought into this). Funny enough, though, no one's actually answered the question I actually asked, which I still have... which is whether this is legal?