grumblestumble

If you aren't using something like nopar or sinopia, you're really doing it wrong - I mean, if you're taking the micro-dependency route, surely you're not building your application as one monolithic chunk of code, right? So you need somewhere to publish your private modules to, anyway.

Couple of things:

* If you're in favor of the micro-module approach, you shouldn't be relying directly on NPM, and should have something like Sinopia in place. After all, external code isn't the only thing you're vendoring, right?

* Micro modules are fine - but your application code should depend on a privately published utils module whose entry point is a prebuilt distribution of all your external micro-modules exposed through a facade. Your utils module deps are all installed as dev dependencies to avoid the Fractal Nightmare.

* Yay, now you have your own 'standard library' which still manages to leverage the NPM philosophy of distributed code. And if some twit decides to throw a tantrum, it will only impact future builds of your custom std lib - and you'll know about it at build time.

...at the expense of slowing down the adoption of agreed-upon standards to the point that they can't be reliably utilized because of compatibility issues? This is not exactly a new scenario. At least Microsoft has moved on.

A point release every n months is utterly useless for on-the-ground web developers. Safari needs to move to the Firefox/Chrome deployment model if it wants to remain at all relevant.

since this has devolved into everyone's favorite tech-related parody accounts, i'll throw https://twitter.com/iamdevloper and https://twitter.com/NeckbeardHacker into the mix.

you say "only one project out of 5 are [sic] big enough to justify it", and then complain that the perks that tooling provides aren't part of the core language. do you see the inconsistency there?

ugh. as someone who wandered over to development after years of freelance design, this brings back terrible memories. you may want to check out http://www.nospec.com/ and spend some time ruminating on the ethical ramifications of the service you're offering.

Good to know. I read the original series about 20 years ago and was recently thinking of catching up on the rest of it.

If you like Sci-Fi, spoiler alert but Julian May's Pliocene Saga is set around this event.

3 things:

1. Much of it reads as"are you taking this approach? yes? don't take this approach. no? take this approach."

2. There are also a couple of flowchart errors ("are you working on a production app" appears twice for no reason).

3. The main reason React makes me sad is the need for excruciating flowcharts like this.

As a result, the entire thing comes across as self-parody. For context, I'm a developer who works on a large enterprise app with a full build toolchain (npm, babel, webpack, sass, etc ad infinitum).

Agreed. I was kind of shocked to open up the comments and see people taking this at face value. I know this isn't reddit, but "upvoted because React" seems to be just as much in play over here.

I haven't verified this, but I really doubt that this, or any other CSS-only solution, will work with elements constrained in an `overflow: hidden` block with a fixed height too short to display the tooltip. Which is a fairly common scenario when building app UIs. Most of the work done by Javascript tooltip libraries is figuring out the correct position relative to the <body> tag and appending the tooltip element outside of normal flow constraints.

Also, a good JS solution will dynamically reposition the tooltip if the requested orientation results in the tooltip being clipped by the viewport (eg. switch from right to left, top to bottom).

"Now, we should define an increment action." <TYPING INTENSIFIES>. 40 lines of code later, we can increment a variable.

if there's a meaningful semantic difference between what you just posted and Angular's 1.5 component syntax, I'm missing it.

Wow, I thought I was the only person alive who still remembered this. Tile-based MMO on a BBS... even if I ran into another player only about once a month. The gambling system was nicely exploitable, too :)

The web is far more ambitious than some proprietary walled garden. Personally, I'm willing to put up with a bit of suckage in the DOM API to support that.

If that's all you're using it for, you'd be better of with Hipchat, which serves as a functional notification channel and from what I recall is free for <10 users. I guess Slack would be worthwhile if you're using it for multiple projects, though.

I'm using fabricjs for annotations as well and it's a great library. The biggest downfall of using canvas as a renderer as opposed to svg is that it doesn't look great if you provide zoom controls. Lovely crisp SVG paths rendered as pixels on a canvas :/

yes, sorry, that's the one. It's been a good 5 years since I left .Net-land.

Google has been using Angular 1.x for DoubleClick since 2012 (http://angularjs.blogspot.com/2012/06/doubleclick-super-powe...). I think it's fair to say that it's one of their most important products.

Actually, when 'we didn't need any of this stuff', most of the heavy lifting was with server-side frameworks(Struts, Razor, Rails, etc). The rise of web applications, and in particular single page applications, which are expected to behave very much like desktop apps, initially led to insanely complicated jQuery monstrosities that quickly became unmaintainable. This created the need for front-end frameworks, which led to a lot of churn as people tried to figure out the right approach. Something like Dojo is not all that different from Angular/Ember in concept, it's just an order of magnitude more difficult to work with, or scale an application with.

There's nothing here that seems superfluous when creating a web application. If you want to take advantage of advances to the Javascript language, you're going to have to go either with Babel/Traceur or some other kind of ES6 transpiler, or Typescript, which while ostensibly is it's own language, seems more and more headed to becoming defacto ES7.

If you work with a team of developers and want a modular structure for developing components as opposed to 10,000 line js files, you're going to need some kind of module system / bundler. This is hardly new, it's baked into .Net web projects (forget the name), and stuff like require.js has been around for ages. Webpack is just the latest iteration of that concept.

If you're building an app of any complexity, you're probably going to want to do some unit testing. For that, you'll need a test runner. Karma's a decent choice.

If you consider a database something that is ACID-compliant, that move happened about a decade ago ;p

Really, React invented the idea of composition? Please, tell me more...

I'm pretty sure Doubleclick is far more 'critical' than gMail, from Google's perspective.

A lot of Angular 2 is optimized around using Typescript. A lot of the heavily-used Typescript features (eg. annotations) are on track for ES7, but not part of ES6.

you got me :)

I'm gonna go with "what is a white South African?" for $200 on this one, Alex.

order is huge for accessibility. eg, you want to render a sidebar (aside) menu on the left side of the screen, but screen readers should prioritize the actual screen content. Before flexbox, this involved all kinds of nasty positioning tricks, the order property makes it simple as pie.

have you tried vox ( http://coppertino.com/ ) ? I really like it, and it hearkens back to Winamp in a lot of really nice ways.

- render a list of items, with a panel showing additional details for the selected item.

- update the view when changes from a backend data source arrive, either via some sort of polling mechanism or a persistent connection.

- allow the user to edit fields on the selected item.

- automatically save any pending changes when navigating away from the page.

AKA every CRUD app ever. You are going to need a framework (most commonly MV*) to deal with this in a maintainable way. Whether you use a vendor or create your own, you will end up with a framework.