Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Yahoo Mail moving to React

slideshare.net

Post reply on HN
Print view View original

231–240 of 301 posts

Re: Yahoo Mail moving to React

#231

Post by greenleafjacob »

edwinnathaniel wrote: post #190
peterwwillis wrote: post #90

Earlier quoted context omitted.

I'm not sure if this is a troll, or if you actually think any non-web developers would volunteer to learn Javascript just to write application code.

I'm a 70%-90% back-end guy with 10-30% front-end work (when necessary). As the companies I work(ed) for evolve from JS => jQuery => Backbone.JS => Backbone.JS + Marionette => EmberJS, so does my skill have to evolve. I also have to write some JS code on top of PhantomJS + CasperJS (not for automation testing but instead for performance monitoring) to support enterprise product at the moment. I used to hate JS with pa…

Can you describe your "performance monitoring"?

Re: Yahoo Mail moving to React

#232

Post by AgentME »

romaniv wrote: post #120
mygreetings wrote: post #9

Little bit off topic but is there anyone like me in community having a problem with liking javascript? I have worked with javascript for years but it was always for DOM manipulation. When it comes to building an app with javascript, i feel like it is too fragile to depend on. Anyone can help me to get rid of this feeling?

Same here, to a greater extent. Why? At the highest level, because it's a language that was chosen based on a whim (not merit) and is now being extensively worked on and showed down everyone's throats. I like languages, plural. I like new languages. I like to have a choice. (And no, I cannot "simply chose something else" if I have to work with people who say every other choice is invalid by default . And yes, this is…

>Imagine someone minifying PHP for faster parsing and then asking everyone to use some source mapping technology for debugging. They would be laughed out of any conference or discussion.

Source maps or debugging symbols have been accepted for compiled languages for a long time.

Re: Yahoo Mail moving to React

#233

Post by Todd »

dan15 wrote: post #168
Todd wrote: post #76

Earlier quoted context omitted.

I've experimented with it. I think it's a great solution if you really want to stay with a uniform stack (as much as is possible, anyway). What I came to realize, though, is that the Razor views were just scaffolding. You would need to re-implement any such scaffolding in your client-side views. The next problem is the router. Any client-side routes will need to be mirrored on the server if you want isomorphism. This…

Hey, I'm the developer of ReactJS.NET. Thanks for trying it out! > Any client-side routes will need to be mirrored on the server if you want isomorphism. This means you're using two routers. A while back I worked on a library called [RouteJs]( http://dan.cx/projects/routejs ) that would expose certain ASP.NET MVC routes to JavaScript. The use case here was to have a way to build URLs client-side rather than hard-codi…

Hi Dan, I think ReactJS.Net is a great project. I've got to say, it was very reassuring to see that it was there when I began exploring React. This is definitely the approach that I will use when not building an SPA. The criticism about routers was not directed at this project. It was a more general criticism of some of the JS routers that I've seen, which are sometimes light on documentation. Cheers!

Re: Yahoo Mail moving to React

#234

Post by Todd »

xtrumanx wrote: post #124
Todd wrote: post #76

Earlier quoted context omitted.

I've experimented with it. I think it's a great solution if you really want to stay with a uniform stack (as much as is possible, anyway). What I came to realize, though, is that the Razor views were just scaffolding. You would need to re-implement any such scaffolding in your client-side views. The next problem is the router. Any client-side routes will need to be mirrored on the server if you want isomorphism. This…

I haven't really given the routing issue too much thought regarding ReactJS.NET. I assumed it would work just as well as my isomorphic apps in NodeJS; one route in server-side land that handles all URLs and returns a View that contains the server-side rendered React app. I maybe missing something for why that wouldn't work in ASP.NET land but like I said, I haven't worked with it that much. react-router is all right…

It looks like they may have recently solved the issue with async rendering on the server (4 days ago):

https://github.com/rackt/react-router/wiki/Announcements#wha...

One of the exciting things about React, and Node.js more generally, is how quickly it is moving. This usually means that there are sharp edges and rough patches and that's been my experience so far. I'll take that any day over a backwater that gets no attention.

I am going to spend some time with react-router, since it looks like the one that is gaining the most traction. To my comment above, they do support nested views, which appears to solve the layout issue for me.

Re: Yahoo Mail moving to React

#235

Post by adamors »

Kiro wrote: post #156
bad_user wrote: post #135

Earlier quoted context omitted.

Facebook Flow or TypeScript - still weak. On require/modules, that's a freaking mess. Ambiguous/unexpected behavior... nothing fixes it. To make matters worse, there's always the promise of some magical library or tool that's going to fix your problems, until you discover that it sucks, or that it is unmaintained, or that it doesn't interoperate with another library and then you're back to search between thousands of…

> Facebook Flow or TypeScript - still weak. How is it weak?

Flow was released literally last week. I guess calling it weak is going too far, but people in this comment thread refer to it like it's age old tech.

Re: Yahoo Mail moving to React

#236

Post by skeletonjelly »

bsimpson wrote: post #71

I was hoping to see a conversation around the points addressed in the slides (e.g. how to handle async data in Flux). Instead, it's a bunch of neckbeards whining about people using Node.

What's with the neckbeard shaming?!

But seriously you're on HN and you're upset about people arguing/discussing a web technology? I don't even see one mention of "m'lady"

Re: Yahoo Mail moving to React

#237

Post by jbergens »

CitizenKane wrote: post #169
dschiptsov wrote: post #89

Why on Earth people who aren't merely enthusiasts of "cool async JavaScript with V8" or those who began as a webdevs and knows nothing better than JS and PHP, could choose a single-threaded solution, which blocks the whole app if a single function blocks, and forces programmers to write spaghetti wrappers around asynchronous call-back hells in a non-functional but GC'ed language? I am really too stupid to get it. "Si…

It's honestly not as much of an issue as it's often made out to be. There are a ton of ways to manage asynchronous code out there including but not limited to all the various promise libraries such as when.js( https://github.com/cujojs/when ), q ( https://github.com/kriskowal/q ), and bluebird ( https://github.com/petkaantonov/bluebird ). Not to mention the Async library ( https://github.com/caolan/async ) which is f…

Actually I think that even a lot of CPU intensive tasks could run on Node. Split them into smaller tasks (which you probably have to do anyway if you want to use multiple threads with another language) and run those as promises. Of course js is bad for most numerical calculation but for some things it might work. Or combine it with Dart or Asm.js.

Re: Yahoo Mail moving to React

#238

Post by hokkos »

LunaSea wrote: post #214
edwinnathaniel wrote: post #190

Earlier quoted context omitted.

I'm a 70%-90% back-end guy with 10-30% front-end work (when necessary). As the companies I work(ed) for evolve from JS => jQuery => Backbone.JS => Backbone.JS + Marionette => EmberJS, so does my skill have to evolve. I also have to write some JS code on top of PhantomJS + CasperJS (not for automation testing but instead for performance monitoring) to support enterprise product at the moment. I used to hate JS with pa…

I'm not sure why you consider the JavaScript ecosystem unstable ? JS has: - awesome dependency management systems like NPM and Bower - awesome task runners like Grunt and Gulp - NPM has thousands of plugins, more than Java's Maven and Ruby Gems [1] - Github badge support for builds, test coverage, dependency versions and NPM - Close second best StackOverflow support behind Java (without taking into account Node.js) […

What annoys me in the Javascript world in those "and", there is always an "and" with many commas before, to many options, when you suffer from big choice paralysis like me you lose a lot of time setting your stack and being productive.

Re: Yahoo Mail moving to React

#239

Post by hokkos »

delluminatus wrote: post #196
xeromal wrote: post #175

Earlier quoted context omitted.

I switched from WPF, C# dev to Angular JS with Typescript and Web API with relative ease and I'm digging it. Typescript definitely helped though. I know I have plenty more to learn, but it's not as shitty as people make it out to be.

If you're using Web API (built on ASP.NET) then you're not using Node, which is a Web server written in Javascript. But I do think it's cool that someone can transition from WPF to Web development with Angular without feeling too lost. Dynamic Web development used to be a very, very different ballgame from client application development.

Angular looks at lot like WPF (on the surface)

Re: Yahoo Mail moving to React

#240

Post by LunaSea »

peterwwillis wrote: post #229
LunaSea wrote: post #214

Earlier quoted context omitted.

I'm not sure why you consider the JavaScript ecosystem unstable ? JS has: - awesome dependency management systems like NPM and Bower - awesome task runners like Grunt and Gulp - NPM has thousands of plugins, more than Java's Maven and Ruby Gems [1] - Github badge support for builds, test coverage, dependency versions and NPM - Close second best StackOverflow support behind Java (without taking into account Node.js) […

'Most modern' ecosystem? That's likely, though it's honestly got the same things as every other programming ecosystem. I think the Perl ecosystem might be the most 'complete' programming ecosystem that exists today, in terms of implementing modern aspects of a programming ecosystem. 'Most stable' ecosystem? How do you figure that? It's only been around a short while in its current form. Other languages have had their…

'Most stable' in the sense that both NPM and Bower are quite reliable.

'That's likely, though it's honestly got the same things as every other programming ecosystem'

I disagree on this point because dependency systems like Gems (for Ruby) and PIP (for Python) are miles behind NPM and Bower.

I'm also not aware of popular task runners on other programming languages in the same way Grunt or Gulp are.

Perl isn't a language I know well so I can't argue on that.

By 'Most evolved' I didn't mean Node.js but really the NPM / Bower module ecosystem. You rarely if ever have to write something from scratch due tu a lack of plugins.

I agree with you thought that thanks to V8, JavaScript has a performance level that is close to compiled, lower level code.

Post reply on HN