akdetrick

The average worker is 5x more productive than they were 30 years ago, but wages have been basically flat.

In the last 10 years, the federal minimum wage has not risen, effectively reducing the minimum wage by about $1 due to inflation.

The richest 500 people in the world grew their wealth by $1.2 trillion in 2019, a 25% increase over a period of one year.

The minority build their wealth on the labor and taxes of the majority, but sure, adjusting the tax code is "stealing".

and the word "Brutalism" originally referred to the material, béton brut (poured concrete), not a philosophy of being brutal.

To help clarify why this is a big deal, I'd like to share why I've been so excited about this project...

[tl;dr] - This is the first tool I'm aware of that actually allows you to generate both API docs and design tools from the same source.

Static documentation is a lie waiting to happen. Once docs are even slightly out of date, people lose trust and eventually abandon them.

On the engineering side of the dev/design process, this is easy to work around. We generate documentation from code and structured comments, which allows us to trust our docs as an up-to-date point of truth.

If you're building a design system that both engineers and designers will work with, there's no real solution to keeping sketch symbols and React components in sync. You're essentially stuck maintaining "static documentation" for designers in the form of a sketch file.

More often than not, things get busy, or someone forgets to commit a change to the sketch file, and the sketch symbols fall behind the code used in production.

Developers start to receive mocks that don't match the "standard" components they're using. Designers start to wonder why fidelity is lost by the time features make it to production. The design system falls apart.

`sketch-reactapp` will help us deal with the static documentation problem the same way we deal with it on the engineering side of things: generate from source.

This is the first tool I'm aware of that actually allows you to generate both API docs and design tools from the same source.

Congratulations on the launch!

melt equal parts syntactic sugar and water...

While very well executed, the basic idea of delivering a document that doesn't make sense without javascript just seems wrong to me.

I've always thought the real promise of responsive design is "mobile first", delivering a basic document that works on its own, then enhancing layout/resolution for larger viewports and browser capabilities using CSS. This approach basically does the opposite.

I've seen these blimps in NYC, Boston, and Chicago to name a few places that are notably far from Akron and Miami. I've always wondered - I'd love to know if the blimps are flown from their base locations to other cities, or if they're somehow trucked in and inflated on location.

The fact that they're considering zeppelins leads me to believe that the normal procedure is to fly them to events, which seems crazy given how slow they appear to be...

I agree that it's a bad tool in many ways, but even if the language (and environments) were beautiful, the problem at hand is often the way that people use it.

In this case, a poor craftsman uses his tools to do the things that the browser already does for you.

I've seen some JS that reinvents lots of what the browser rendering engine should handle (recalculating & reflowing heights of elements every time something was added or subtracted from the DOM, for example). Expand this kind of thinking to an entire project, and you start to find yourself in the kind of mess described in the slides.

If/when Dart replaces JS, some of the enforced structure may help prevent badly organized or buggy code, but it won't fix poor assumptions of what concerns scripting should and should not handle.

I agree, but the caveat for any city/town where you can get by without a car is "affordable".

full disclosure: I've lived in NYC without a car for 10 years, but grew up in Ohio completely car-dependent.

Edit: There are in fact many places that do meet the requirements of affordable and walkable, but a new concern in an age of urbanization is keeping them affordable. The desire for such neighborhoods is growing, but the supply is too low as of 2013.

This article is missing an image of an old map with red lines connecting Italy, Guam, Hawaii, and Chicago.