7777fps

Another example is running SQL commands directly against a live database, which is frequently given as advice of something that should never be done.

So why should I get excited about the ability to live edit when it's held up as bad practice in one of the few areas it's possible.

I miss a time when people read articles before commenting on them. Just skimming the introduction could have told you that the title is not a reflection of an argument forwarded by the article.

The author also equates "late nights" with hard work in point (2) which is a dangerous malpractice in itself.

How long can nuclear weapons be kept without being used?

We are as close as ever to nuclear war according to the doomsday clock, just two minutes to midnight.

My take (speculation):

Eschewing ICANN would likely not be freedom in any sense, any replacement would not be the work of open and trustless bodies, for any serious replacement would have to come from a swift coup by google, cloudflare and Amazon.

I predict any replacement would likely be open in name only and instead tightly controlled by those three entities at least from the outset. It would be no more "open" than AMP is; even if protocols and specifications are open that's irrelevant if there's a de-facto central source.

It is only by a quirk of history that ISPs not google handle most DNS and DoH "fixes" that.

It would be easy for google to remove ICANN from the loop, it would be almost impossible for anyone else to do so without google's backing. That doesn't lend itself to an open and trustless replacement.

The internet hasn't proven it's "willing or capable" to do anything not delivered via Chrome for a very long time now.

It's easier than ever to rent your own servers, it's harder than ever to run your own servers.

There was a time when you could serve anything from a home ISP connection.

It's just wrong isn't it? It says Jan 20 is a Tuesday. It isn't.

[OT] It's clearly a slow news day today but what's with almost all the submissions today being very content-lite?

Very little actual news or explanation, just links to wikis or other content without any context.

Perhaps it's often like this but there is fewer people to shape the front-page today.

Perhaps submitter could explain the submission?

But the article linked wasn't posted. A different new article was posted and the link changed to this one.

I think most the article is newer:

> By Simon Hradecky, created Thursday, Jan 10th 2019 23:32Z, last updated Thursday, Dec 26th 2019 16:24Z

While the incident itself might have been a year ago, it was clearly updated on the basis of the recent report.

A calendar?

Yes. I'm surprised they could develop it as quickly as a year in fact.

Calendars are difficult, there is a lot of hidden complexity in the way that users use calendars. They are iceberg products, they look simple from the outset but if you try making one you'll run into the myriad of edge cases.

I was wondering why there was any need to move the \ character but then I looked up where it is in the US layout and it seems bizarre.

The UK layout has an advantage, it's to the left of the Z and is easy to type.

The UK layout has a whole extra key which also makes # easier to type because it does not require a shift.

> We were running 4,000 Node containers (or "workers") for our bank integration service. The service was originally designed such that each worker would process only a single request at a time. This design lessened the impact of integrations that accidentally blocked the event loop, and allowed us to ignore the variability in resource usage across different integrations. But since our total capacity was capped at 4,000 concurrent requests, the system did not gracefully scale.

I can't be the only person who reads stories like this and wonders how they arrived at that solution in the first place?

Failing to scale because their previous approach to scaling was a worker per request, a model which was roundly moved away from, because that's how CGI and Apache modules worked and it didn't scale well.

I thought one of the key selling points with Node was an fully async standard library, enabling better scaling in process.

But then you read stories like this, and I find it hard to relate to the original problem.

Worse, everything.anything is now treated as a domain, leading to accidentally trying to browse when watching to search for dot separated programming terms such as libraries.

The author also verified it, if you had the decency of actually reading the article rather than exiting as soon as you found some way to state that you know better.

But sharing salary information is still heresy, it's attempted in secret across opaque unverifiable websites that companies themselves like to game.

Ironically enough in firefox the google search is broken when searching for that term: https://www.google.com/search?q=the+handmaid%27s+tale

I see a large gray box and little else!

I wondered about input format.

Does it support SVG?

Perhaps you could edit for clarity, as you seem to be suggesting that the Sun is the center of the universe.

As far as I know, that was only an accepted point of view for a few hundred years.

If Google didn't own AMP then I might be less critical of this change. But they do, and I bet they don't rate any AMP pages served from the Google cache as slow.

They're determined to make AMP the de-facto way of publishing content and this feels like just another way of making AMP more appealing.

You're implying a single exchange moving the market needs cash to move it.

If the ecosystem has decided one exchange is the lead price, then they manipulate the price without needing the underlying assets.

Furthermore, bitcoin is one of the only markets I've seen which rewards "whales" instead of punishing them, because in most markets moving the market you will lose money to slippage. The market price will retract after you bump it. In bitcoin markets if you move out the price no-one is trading the 'fundamentals' so it just stays at the new price. Instead of losing money to slippage you gain money from it.

Magic internet money indeed!

And if that works, and we restore a more normal cycle, how do we avert the next ice-age with all that space junk?

It's almost a shame the idea of having a sitemap.xml which the browser could parse and provide native navigation for never took off.

Of course it didn't because native controls are the first thing any designer changes because native controls on the web were always associated with amateur websites.

If you're re-writing tests you're not refactoring you're just rewriting.

If tests need to be rewritten to support a refactor those aren't tests, they're at best just testing the implementation rather than requirements and at worst just a second implementation.

I think it's fair to say that, "Javascript's packaging is as bad as in C".

While ES6 modules make minor improvements in syntax, the entire npm ecosystem relies on commonjs resolutions which aren't that far under the hood to including header files wholesale.

Then you have the build system which you have to know your way around babel, webpack, and a whole suite of arcane tools each of which with very fragile equivalents to make files with similar nonsense errors when builds fail.

Javascript isn't C, but the ecosystem is a nightmare compared to modern languages with modern language features such as first class package management.