skysight-inc/HackerNews huggingface dataset:
The difference is that a "react server" can actually render the dynamic react content. I don't know of a way to do this in django, unless you are able to run javascript code somehow. If you do this, you are kind of making your django app a "react server" though, since it renders all of your react components.

What usually happens in a react app is that the server delivers static content (html, js, css). When everything is loaded, react starts working on the browser and renders / fetches data.

If the server that delivers the html doesn't just deliver a static page, but actually fetches data and renders it first, the browser can instantly display the data and react is smart enough to know that it doesn't even need to do a new render, because the components are already rendered to html.
"""
On May 31 and June 1, 1921, hundreds of whites led a racially motivated attack on the black community of Greenwood in Tulsa, Oklahoma, killing some 300 people, mostly blacks. The attack, carried out on the ground and by air, destroyed more than 35 blocks of the district, then the wealthiest black community in the nation. More than 800 people were admitted to hospitals and more than 6,000 black residents were arrested and detained, some for as many as eight days. [2] The official count of the dead by the Oklahoma Bureau of Vital Statistics was 39.
"""
https://en.wikipedia.org/wiki/Tulsa_race_riot
Most of those are once-off costs though. They may be expensive but I doubt they're all that expensive relative to the cost of the rocket.
> to teach my class how to serialize itself into JSON, I can compile com.fasterxml.jackson annotations into it, but by doing so I've made a particular JSON library a dependency of myproject-datatypes

Right, because at the moment, there is no standard cross-library convention for that. One day, there will be, as there is for serializing to XML:

http://docs.oracle.com/javaee/7/api/javax/xml/bind/annotatio...
Some ISP turn over their Residential IP Blocks to Blacklist providers to add automatically to the blacklists.

ISP state in their TOS you are not to run "servers" from your home connection, as such they simply blacklist all Residential IP;s from the start, because if you are running a email server on a Residential Connection it is either a Botnet, or you are violating the TOS of your plan.
Hasn't there always been a Mathematical tug of war between theorists and practitioners? Theorists get big dopamine responses when discovering new abstractions and models. Practitioners get similar responses when solving real-world problems.

As long as the theorists don't run too far away, the practitioners are happy. And, theorists are happy as long as they have enough food, water, and shelter to allow them to continue to think about stuff. :-)

As a (mostly) practitioner, I don't feel that a lot of the abstractions that the author identifies are helping me write better code faster. For instance, 90% of my time is taken up by just a few things:

- Transforming data from one structure to another.

- Moving data around.

- Writing and re-writing similar business rules and domain logic in different libraries and languages.

- Writing 'adapters' to get one library to work with another.

- Trying to find 'the right' data structure or algorithm.

- Discovering that the many different implementations of the same data structure or algorithm in different languages don't 'do' the one thing that I need them to do (and having to write my own implementation).

- Reading other people's code.

- Debugging other people's code.
You have the alternative of posting a meaningful comment which disagrees with his...
I suggest replying with counterarguments, that will work much better than downvoting as I can clarify eventual misunderstandings.
> How about we give people the benefit of the doubt before assuming malice.

I think considering how harmful voting rings and blogspam can be, and how easily a community can deteriorate as a result, it's probably prudent to assume malice in these cases and to be corrected by someone such as yourself. Much as I wish things to be different.
Looks like it only supports the english wikipedia: https://github.com/muffinista/gopherpedia.com/blob/master/fe...
Several of the most advanced GEO commsats use that as their main way to get into orbit. By beefing up the ion engine enough to circularize the orbit at GEO you make for cheaper launch costs and a longer lived vehicle.
Generational Garbage Collection, Write Barriers and Userfaultfd(2)
I often see packages or solutions to problems related to browsers/servers on hackernews. Why don't people who make browsers or servers implement these things as a standard? IE. There seems to be so many people using jquery/react. Why not just implement some of their functionalities natively into the browser?

There seems to be a trend of making un-opinionated software that acts as more of a sandbox for down-stream developers. I think that's great because we are now seeing the great solutions coming out of that sandbox. But at what point do we start to have a general consensus and implement some of these great solutions natively to remove the resource overhead?
Hillary Clinton is the expert here ¯\_(ツ)_/¯
Vue has a lot of great ideas. I originally found it to have just enough power over Backbone, without the heft of Angular. Despite a great premise, my time with Vue was turbulent.

Vue version updates are tremendous time sinks. API thrashing was common from the original 0.x.x releases to 1.0.0

This was justified as all versions under 1.0.0 being "under development". That's fine, but call it what is, "non-production-ready software". A public beta that should have a prominent disclaimer.

The removal of the built in event system was also handled poorly. There was no migration path other than build-your-own shim using the Vue constructor.

My beef with Vue these days is the growing Vue-specific tooling. I'm not fond of the single file .vue approach as it doesn't make it easy to separate components into different contexts.

The standard rebuttal for this complaint is "but JavaScript, CSS, and templates are the same context." I agree that the approach of scoping CSS and template to a component is great. Not being able to use separate files leads to a lot of noise. I don't need to see the CSS when I'm working on the component JavaScript. The best solution I've had in the meantime is using my editor's "block folding" feature.

Combine this with a .vue specific syntax highlighting, and a .vue eslint configuration.

It's really not what I signed up for in the beginning. I sense I'm coming off as entitled. Evan's countless hours of work is commendable and I'm grateful for his vision.

I hope Vue will find that illusive balance of configuration and opinion in its lifetime.
You're arguing that the (probability) x (impact) of a claimed benefit is in question. But your argument merely mitigates the good that is provided by software transparency.

What are the bad effects to society for software transparency? Because if open software offers noisy positives with minor negatives, then we should prefer open as the default heuristic until circumstantial information says otherwise.

Some projects, whether open or closed, are more valued by institutions or businesses, and consequently some projects will justify more money and eyeballs. Also, what businesses and institutions value can be unintuitive. When there's a bug in Linux, that might immediately degrade a business product, whereas a security problem with SSH might not ever impact a business -- even if important customer data is stolen. I doubt Target experienced a real business problem after its large data theft incident with customer financial data.

Therefore, 3rd parties contributing to software will probably be far more prompt for bugs in projects that directly impact business success vs. OpenSSH, but at least the door for extra benefits is open, whereas for closed software the door is shut.
So, you don't like React because Electron which has nothing to do with React?
http://en.arguman.org/about
> And Qt is getting really better and better each day, and right now is pretty portable, so you don't have to write 3 different versions of apps for different operating systems.

Assuming you want to write an app in C++ that doesn't need it, and are comfortable with not having any of Electron's sandboxing features. While JS isn't my preferred language, it does beat doing everything in native code with full filesystem access.
And apparently Qt is so much better, which is in the process of integrating a full browser engine for Qt Quick, which is… somehow better than using a full browser engine directly? Okay.
Scala.js was largely done by a single student on top of his other university duties.

I think it's mostly down to determination. Some things are hard, but need to be done.

Haskell people just seem to give up more easily - see all the half-working projects. Nobody finishes stuff, the next dev just starts his own new project, and abandons it later.

Scala.js handily beats JavaScript in terms of IDE support and tooling
Your domain provider, your hosting provider or your ISP can still be targeted if someone in power doesn't like it. Yes, it would be much more difficult than talking to Zukerberg and giving him directions on what is allowed this election season, but it is not very much so.
Good methods for what? Not certainly to certify that each combination of inputs gives a certain output, as you can read from that paper.
And that is the only way that would have ensured that the guy on the tesla didn't die.
That methodology furthermore has nothing to do with open source.
React itself is pretty simple and very nice to work with. The whole react/redux/react-redux/react-router/react-router-redux/webpack/babel/flow agglomeration on the other hand is a lot more complex and subject to a lot of api churn. But you can actually get pretty far just using React by itself. Don't adopt other parts of this stack until you actually really need them and you can go pretty far with just a few concepts.

And yes, React is as much a technique for building UI as it is a particular implementation. Learning and using React has also improved the iOS code I write.
No, point of OP was hype, and those two together are hyped.
Doing forms in PDF directly is not the most unreasonable idea.

The problem is it's not one, but three ridiculously overcomplex specification: https://en.wikipedia.org/wiki/Portable_Document_Format#Inter...
Pretty annoying that you can't select text to copy/paste and quote it.
Related question : how to get push notifications from a self hosted MTA? The closest option I know of is app called CloudMagic
I have a rule, if you mention Therac 25 then you lose.

It's a cliche. If it was an example of a common problem then it wouldn't have to be mentioned every single time.
PyQt?
I agree open source software has more chance of being safer, but the article does not do good job of arguing it. Anecdotal evidence fallacy is not good science, e.g. "Meanwhile, there has been not a single example yet about use of GPLv3 software that has harmed anyone".
1 million+ downloads on NPM at 125k~150k per month

But doesn't Node download from NPM every time it runs? Hence the left-pad debacle. So this "downloads" figure doesn't necessarily mean what someone used to a more conventional language might think it means.
Do open source developers actually want to take on the liability that comes from distributing software for use in safety-critical environments? One mistake could leave someone with a lifetime of medical bills, and they'll sue anyone with money involved in it.
"He especially loved wines that predated the phylloxera epidemic of the late nineteenth century, when a grape-vine pest decimated Europe’s vineyards, forcing growers to replant with phylloxera-resistant rootstocks from North America."

So we are all drinking New World wines. I was unaware of this and I find it sort of satisfying to know about.
Show HN: Interactive Y combinator in ruby running in the browser
Fully-agree. From the start, Netflix was talking about React being useful because you can drop it in to various pages without affecting other UI views.

I use it at work on a page-by-page basis-- it drastically reduces the mental overhead of class naming, JQuery spaghetti, maintaining the DOM etc. Sometimes I even surprise myself when something "just works" because of React's well-controlled model.
Well, this is a blog post in a whole blog full of links to articles and books, so can check for yourself.
Anecdotally, I read through things occasionally. I once was curious about something in the xnu kernel and noticed a bug in the code, just from reading it. I sent Apple a bug report and eventually they fixed it (though I think it took a couple years).
The way things are going, they could probably introduce the threatened species to eastern Ontario, which is slowly becoming a desert it seems.
NPM modules only download when explicitly fetched with `npm install`
Smalltalk has a strength and a weakness in its 'image' approach. Smalltalk doesn't really have source code and object code, it has an 'image' full of objects which you can run, and which contains all of the standard library, the development environment, and your code. You work in this image, and save changes as you go along.

That makes Smalltalk super easy and convenient to develop in, and very consistent across platforms. But it's a roadblock to publishing code, working as a team, deploying, and the other things you need to do with software that isn't a toy. The Smalltalk environment and community certainly have ways of doing all those things, but they can be clunky, and some of them are quite recent.

Meanwhile, C++ was a bit of a pain to write, but once you'd written it, sharing it was as easy as emailing a file, or checking it into RCS (or that hot new CVS thing), and building a production release was a matter of running 'make' and going for lunch.

Java kept C++'s simple approach. Smalltalkers at the time laughed at how caveman-like the experience was. But it turned out that that simplicity was exactly what you needed to grow virally on the then-nascent web.
> ISP state in their TOS you are not to run "servers" from your home connection

I don't know what evil ISP that is but running your own server is 1) encouraged by my ISP since forever (XS4ALL, the Netherlands) and 2) these days it's illegal to tell people not to run servers because of net neutrality laws.
Explaining the Example in “The Secret Life of Objects” of Eloquent JavaScript
Ignore the react bit, the site is interesting in itself.

http://en.arguman.org/

The post is bait-and-switch, react is a bite, time for a switch. :-)
How is the value of the Tanzanian shilling relative to the dollar a problem to solve with a startup?
What is this nonsense?

> It's marketed to developers by billion dollar Facebook, a company historically intent on squashing startups.

This is a poisoning the well fallacy.

> The benefits of using a virtual DOM over the actual DOM are theoretical at best. The problems that React supposedly solves are theoretical at best.

This "argument" contains zero information.

> That's why there's Redux!

Redux and react don't solve the same problem.

> It solves problems you'll never encounter because you don't have Facebook scale.

The client doesn't scale like the backend. Not to mention it's in contradiction with this other "argument":

> React becomes counterproductive when developing apps that aren't mere demos.

Do people actually take this serious?
> I have no idea where does hate for React come from, it's >> just << an open source library

I think most developers (at least seasoned ones), come to appreciate tools as a solution to the problems that they solve.

There's always going to be a vocal minority that is strongly against whatever has the most hype at any given moment. Their reasoning is probably as varied as the people themselves, and a some of the criticism may be valid, but this is the nature of developer culture.

Having both groups is probably a net positive.
> The fact that I do not have (nor want) any single Electron app installed on my computer tells something

Not really. Besides, React has nothing to do with Electron.

I am into software development, and I use React daily for frontend-applications. While I'm not swooned as much as most people, I still thinks it has great value.
> Most importantly, it ignores the fact that proprietary software in cars is at least equally, if not more, dangerous.

To me it seems that he is suggesting that the proprietary software can be more dangerous than open source one.
So from there you can infer that he believes that open source software can be more safe than proprietary one.

If death(proprietary) >= death(OSS) then !death(OSS) <= !death(proprietary)
I see some point-missing arguments being made here.

React isn't for scale. And it isn't to side step learning about html and css. It's main reason for existence is to make complex UIs easy to manage.

Pretty much the only argument I can think of against React is that it's a boil-the-ocean system.

Once you start doing your UI with it, you pretty much need to make the entire thing use react to really benefit from its model. Having different interlinked components mixed between react and query and what-not is asking for trouble.

But. Building your UI as a description of your current state is so incredibly useful to reason about and prevent bugs, that it's usually worth it to go completely into the system.

The only other major gripe I have is getting time-based elements like animations to play well within the system.
Well, there's plenty of IPv6 around. My ISP gives out /48 blocks to all customers together with a single, static v4 address. The difference in number of public addresses is incredible.
It's fine if it's the easiest method available with universal support. In this case in failed on both counts.
No thank you. None of the other "discussions" are worth wasting time over. Just people bringing feelings, sophisms and misinformation to an argument fight. It's no better than a reddit thread.
You don't seem to realize that the software license means no warranty, but that does not preclude anyone from giving support and warranty on the product.

So yes, GPL'ed software may be used on critical applications the same way as every other piece of hardware and software: via special contracts.
Alcohol is far, far worse. Many more people get trapped by it, and it destroys careers, relationships, and lives. Sometimes directly, through DUI and other violent crimes committed while drunk. But we as a society recognized that the hazards of making alcohol illegal far outweighed those of having it legal. We need to learn to treat other drugs the same way.
Encryption battle: France in global call to “deal with” messaging apps
A newbie explains for newbies. The example in chapter 6 of Eloquent JavaScript, The Secret Life of Objects
Evee.js – The lightweight ES6 event library
Except the City Of London, which refuses to cede some 1000 year old power it extorted from some king or other.
This is the same stuff people have been saying about React since its inception. Putting opinions into Arguman doesn't make them factual statements.
> It was about async io, handling everything in a process and a handful of threads, instead of spawning a new thread for every request (and paying for OS context switch)

Given that the data, and the events about the movement of data, come from the kernel, there are still just as many context switches with lightweight threads.

The only real advantage of lightweight threads, as pcwalton pointed on recently in another discussion, is that they can have much smaller stacks, so you can have many more of them before you run out of address space.

The biggest advantage of Node.js, though, is that it let people who know JavaScript write server-side code with reasonable performance and scalability. If you already know Java, there's no reason to use Node.js. If you only know JavaScript, or JavaScript plus some 'slow' server-side language like Ruby, the Node.js is an easy way to get more performance and scalability.

Go is filling a similar niche. If you know Java or C# or C++, Go is pointless, but if you only know JavaScript, Ruby, Python, etc, then the ease of learning Go makes it a viable option on the server side.
A number of the core jquery innovations have been implemented in the browser. document.querySelector is the clearest example I think.

The big push in browser standards is the Extensible Web Manifesto[1]. The idea being that we should first give web developers powerful and general purpose primitives to explore and build solutions with, because there are many more web devs than there are browser implementors, and the standardization process is slow. We can then explore standardizing the most successful and useful results.

This project is using service worker, one of the canonical extensible web APIs as it gives sites tremendous control over their network use.

[1] https://www.w3.org/community/nextweb/2013/06/11/the-extensib...
You're implying that this is not advisable to do because any such fallback could snoop the data?

I'm sorry I'm not sure I quite understand what you say the problem is and how it relates to the unencrypted nature of email.
Why not take your comment a step further? That is, you can get pretty far using plain js `createElement` and similar functions. In fact I've created a fairly complex SPA without using any external libraries. Don't use react until you absolutely need it!

Back in the day, jQuery was amazing because it made selecting and manipulating DOM elements easy. But now, plain JS has mostly caught up to that functionality, to the point that it rarely makes sense to use jQuery over plain JS. I wonder if in a few years the same will be true of much of the functionality in react.
Baltimore's Anguish
Thanks for sharing the link. Fascinating stories.

Lessons form the history
https://twitter.com/ontouchstart/status/764790460900581376
It’s actually just 267 bytes compressed with brotli, 305 gzipped.

OTOH, the entire jQuery 2.2.4 is just 26k brotli compressed, 29k gzipped.
Thoughts about WebGL-Next
Scotland Yard creates 'Twitter Squad' to investigate online threats
Aeron: Efficient reliable UDP unicast, UDP multicast, and IPC message transport
src: https://groups.google.com/forum/#!forum/mechanical-sympathy
Generally downvotes are best used not to indicate disagreement, but to punish comments that detract from or add little to the discussion. If we downvoted everyone who disagrees with us, discussion wouldn't be very meaningful. But if we downvote those who do not add to the discussion, we can maintain high signal to noise ratio.

Let's not turn HN into Reddit.
Evan gave a recent talk at Laracon about Vue.js
https://streamacon.com/video/laracon-us/evan-you-vuejs-works...
I realise that. Hell, I've done that. As a licensed engineer, I would just be very concerned about contributing to an open source project that controlled critical systems in cars. That sounds like all the liability of my actual employment, but none of the pay.
I really don't give a shit what anyone says, for me personally ReactJS makes front end great fun to program and an absolute blast and empowers me like never before to build powerful, interactive front end apps with a code base that is well structured, understandable and makes sense.

Until React I dreaded front end development, painful, weird, quirky, hard to organise and generally problemtic. With React I feel like a front end guru.

AngularJS felt like some sort of weird computer science project developed by Phd's who had spent their university days studying Java - it hurt to learn it.

Call me a hipster fanboy if you want but I choose technology to work with because it is easy and make sense. I don't have much time so I have to commit my limited resource to the optimum set of technologies. At the front end that is React.