Hacker Newsnew | past | comments | ask | show | jobs | submit | drapper's commentslogin

Someone should make an opinionated, batteries-included JS/TS framework like Elm, based on TS, React, Flux.


The JavaScript world doesn't like that. That's why no one has made a carbon copy of Rails.

Even React, Flux, Router and etc comes in several parts.

I know railties are modular but at least they come from the same project and repo and update together.


Yeah, the JS world currently is very pro-modularization, but I already saw some discussions on Twitter from the React/Flux people how that creates too big barrier of entry for the newcomers. One of the things that draw people to Angular is that it has almost everything that you need included - it's easier to say to someone "just use Angular", than "try React, with Redux, and Router, and Webpack - it will take some time to configure it, but it's worth it".


Well, it has it's benefits. I don't like Redux and I like Reflux so it allows me to do that.

Then again Rails does let you switch out compatible parts. By compatible I mean if it adheres to "Railties", e.g. using ActiveModel for replacing Pgsql with MongoDB.


Ember would be the Rails equivalent in JS-land


can you link to any such research? that's a topic I'd love to read more about, but don't know where to start even. thx!


Perusing Brendan Nyhan's papers will get you a lot of reading in short order: http://www.dartmouth.edu/~nyhan/.

This is one paper on the topic from another group: http://pss.sagepub.com/content/early/2010/10/12/095679761038...

This paper from Yale is pretty interesting: http://www.motherjones.com/files/kahan_paper_cultural_cognit...


OK, this looked rather scary and also rather unbelievable so I did a quick research and unsurprisingly it turned out this is blown way out of proportion (if not downright wrong).

The article claims DiagTrack collects "your name, email address, preferences and interests; browsing, search and file history; phone call and SMS data; device configuration and sensor data; and application usage". That description is credited to Microsoft itself ("As Microsoft explained"). But if you follow the link it turns out it's not really Microsoft's explanation, but just what some user on official Windows forum wrote. My guess: Windows Technical Preview did (or had ability to do) that and user confused one thing with another.

Next thing, DiagTrack came to Windows (TP) via update KB3022345, so let's check that update: https://support.microsoft.com/en-us/kb/3022345

"The Diagnostic and Telemetry service collects diagnostics information about functional issues on Windows systems that participate in the Windows Customer Experience Improvement Program (CEIP). CEIP reports don't contain contact information, such as your name, address, or telephone number. This means CEIP won't ask you to participate in surveys or to read junk email, and you won't be contacted in any other way."

Of course, it's still possible there's some foul play here, but I'd prefer it would be investigated first and accusations thrown later, not the other way around.


Years and years ago I used to read The Register, as it had good content. Now, it's just a tabloid - a technology-oriented one, but a tabloid nevertheless.

Unless I'm mistaken, what The Register have said in the article would constitute libel, right?


That would take longer


Never mind the product, look at that list of React components (https://github.com/Automattic/wp-calypso/tree/master/client/...)! Any chance this will become a separate framework?


I don't know if I would call it a framework per se, but absolutely we want to break off individual pieces that can be separately re-used and make them available for everyone. In the meantime if you see something in particular that you're itching for, open a new issue and let us know. You may also want to check out the library of modules here. https://github.com/Automattic/wp-calypso/tree/master/client/...


The whole project is GPLv2.

https://github.com/Automattic/wp-calypso/blob/master/LICENSE...

I don't have anything against GPL. It just closes a lot of doors for no real reason.


I think not, but Meteor or Keystone.js might get there some day.


Possibly decorators proposed for ES7 would be a solution here? Babel and TypeScript already support them.

By the way, TypeScript recently (in nightly) gained support for JSX, so we can now have all of this ES6 stuff + types on top of it.


That reminds me of what Vivaldi is trying to do (https://vivaldi.com/)


that happens now already, so we need to fight with it anyway


Maybe government should tell companies that they need to treat "full time" workers differently from contractors and companies would gladly employ their workers full time.


When I was using Angular I thought doing something like

  setTimeout(function() { $scope.$digest(); }, 0);
was an ugly hack and a sign of angular's leaky abstractionism showing up. Is this considered a good practice now (or always was)?

Edit: just to clarify, I'm asking because in OP this was given as a one of the way to fix Angular speed issues.


That's a sign someone has fundamentally misunderstood Angular and is hacking around their misunderstanding.


Why do you say that? What about it makes it fundamentally misunderstanding?


You should never have to use $scope.digest() unless you're testing a directive. You should never have to fire a digest loop manually.


It's the same thing as using $timeout; It runs a digest at the end after a setTimeout. I wouldn't call it a good practice, but it wouldn't bother me either if I saw it in a codebase. You are also welcome to use things like $evalAsync.


It's not the same thing, as the author points out since using `$timeout` in the example without an isolate scope was the source of the original problem. Instead he's suggesting you use $timeout without it's default behaviour (something that's possible now through the false argument or by calling setTimeout directly).

This is absolutely a leaky abstraction, and whether or not it's necessary sometimes when using Angular, it should still bother you.


No.


"This archive shows the inner workings of an influential multinational corporation. It is newsworthy and at the centre of a geo-political conflict. It belongs in the public domain."

Yeah, right. Some of is of public interest, sure, but then find it, edit it and publish the results. Ah, I forgot, it's not how wikileaks operate. For them making everything public is good in itself (except, of course, when it's about themselves).


The armchair historian and anthropologist in me wishes we had something like this for the corporations of the 1800s. To a historian or anthropologist, the mundane, everyday interactions are every bit as important to study as the momentous occasions.


My browser history might be useful, but I dont want you looking at it until my children are dead.


I initially read your comment somewhat differently to how it was intended I suspect.


This pleases me.


>The armchair historian and anthropologist in me wishes we had something like this for the corporations of the 1800s.

What we do have from this time though are a huge number of private journals written/kept by very powerful and influential people. We also have huge troves of their mail correspondence that, without a doubt, was intended to be kept private.

We have since made these things public, written books about them, published the letters reprinted, etc.

So perhaps the release of such correspondence is merely a function of the time since its authorship, or the time since the author (and recipient?) died. The way things operate today though, the future historians are unlikely to get such content.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: