That's not the point of this. This is not about disabling JS as a user of websites.
Heydon is a developer, and an influencer of developers. He's saying: web development is now absolutely obsessed with JavaScript, and it in no way has to be. The basics, HTML, CSS. That's what's important.
This is all, totally, flagrantly wrong. It's all to be provocative.
Firstly, Chicago is one of the top economic cities in the world. Pensions are a big problem, but they are not going to wreck it. The algebra is fine.
Violent crime is another big problem, but it's a big problem everywhere in US. Cities, and Chicago isn't even near the top, per-capita. It's almost entirely gang-related. The big problem, as everywhere, is the red-lining of the past, drugs, and no opportunities. Illinois just legalized weed, will release tons of people for drug-related crimes, and this might help the hood a lot.
The suburbs are not dying. Real estate isn't great, but guess what, other than a few markets on the west coast, this is what home prices are going to do everywhere. The baby boomers got to have their houses triple, quintuple in value, millennials will not.
The population loss of Chicago is only in areas that, frankly, need population loss. There's no reason to live in some of these communities that are beset with drug problems and have no opportunities. These days people have cell-phones and the internet, they can move to better places all over the country. It's the reverse of the great migration and it's because the country hasn't helped these people ever in their entire history. Meanwhile middle-income and high-income 20 somethings are still flocking to Chicago.
JB Pritzker is the new governor. He is the absolute opposite of a "bored billionaire" who has never accomplished anything in his life. He has guided the Pritzker funds in a huge amount of charity work all over Chicago including, this audience might want to know, huge investment in startups in Chicago.
We are nowhere even close to the normalization of corruption as Russia, that's just stupid.
Edit: I also want to add that I've seen this narrative from three places -- journalists trying to be provocative; Chigoans that like to complain about politics but not get involved (favorite pastime); and Hanity trolls trying to stir up reasons why Democrat havens are poorly run / liberal policies supposedly fail.
Credit ratings keep getting worse. (Illinois is worst in the US)
New sources of taxes enacted. (Weed, gambling)
It's all right there, man. I don't like it anymore than you but sadly every warning sign, every symptom is right there staring at you in the face. If I asked someone to generally describe a death spiral this is what they would describe. And it's not like these are modest problems, we often rank DFL in the country for most of these things.
State/City assets should be sold. Why should the state operate any assets?
Weed and gambling taxes are a good thing, not a bad thing.
Population loss is indeed continuing but it's to be expected. Older people moving to Florida is a big reason. Another reason, Chicago is more expensive than neighboring states. And unless you value big city amenities, there is no reason to stay.
Oh I read it, you're just wrong, unconditionally wedded to politics. I can't argue with people who insist the sky is red, why waste my time...it's a nice day out.
The co-sleeping seems to stem from all the SIDS research / literature which when you go and read seems especially questionable. The topic of SIDS was hit so hard by our hospital and pediatrician. It scares the shit out of you. And then you go read the sources, and it's... well underwhelming at best.
That's why they tend to talk about Sudden Unexpected Infant Death these days.
My understanding is that the primary concern is the ability of the child to breathe normally. Anything which restricts that ability can be life threatening.
Having their face covered (very easy to do when they sleep between two adults who pull the covers up when they're cold) or pushing their face up against a non-breathable material (windproof bassinets, pillows, soft toys) leads to a lack of air circulation which can lead to CO2 buildup. This is particularly a problem when their muscles aren't strong enough to turn their head or roll over.
The most compelling use-case for me is the web-api deprecation. It very clearly tells you when a service will no longer be available. Currently there are no standard mechanisms for this and are mostly driven by documentation. If an api used this then a consumer could look for these and raise alarm bells.
There are also plenty of services that host user content, but only for a short period of time. Pastebin entries with a set expiration could for example set this header to inform clients about the expiration date. That way software can detect links to content that will expire and act accordingly.
Yes, and I think that's the smartness of this is they clearly came from a stance of Deprecation and realized they could make it more general. Good work, imo.
That is the first thing I thought of. We had several case of partners API being deprecated and we were not notified in a timely manner. This could be used to trigger monitoring alerts.
The Rust Python bindings are actually pretty good, I hacked together a project to let you deploy Rust micro services in Lambda via Python module bindings a while back.
Or use Polymer/LitElement, where it's just all in one file... I swear people are just reinventing react methods to eventually get to where Web Components have been for the past 4 years.
While there are certainly plenty of people who need more storage than is practical to put in-memory, most people don't. E.g. it's rare enough to find people with single datasets in the 1TB+ range. Most databases I've come across at clients max out in the tens to hundreds of GB range. Many more could be easily split (e.g. they may be multi-TB or above, but are that way because of aggregation of data that is logically separate, such as relating to different customers, and can easily be sharded) - though whether or not that's worthwhile is a separate issue.
So while you're right, for most people it's not going to be a practical problem. Query performance tends to be a bigger problem in practice, and IO bandwidth is often the main cost driver for servers (with NVMe SSDs providing so much additional IO bandwidth that they often pay for themselves several times over by reducing number of servers needed for people who insist on "traditional" disk focused databases), pushing server costs into ranges where spending more on RAM but needing fewer servers to handle the IO load, is more and more often a good tradeoff.
The latency doesn't sound that bad. It's 200ns to access memory on another local NUMA node, and 500ns to access memory on another machine using NUMAlink.
Fascinating tech. I had no idea this could be done with Xeons.
Explore, Expand, Exploit, Exterminate