RegW

Even FB will make a wrong turn one day. Every time it buys a new name it gets bigger. Eventually it will be a fat man standing behind a lamp post

Perhaps in 2005 we were still able to call across browser frames and abusing the one thread per frame model.

async / await isn't really concurrency. It's a mechanism for picking up the job after something else has been done (perhaps like a callback). In a way it's been an advantage of Javascript: one or two threads do all the work in a timely way without all that messy thread scheduling and context switches.

In a factory setting I would have thought existing robots would suffice.

Looking at the wider group, I would think there's lots of roles for robotics in construction. Delivery of heavy items across uneven terrain or up stairs - may be something like a robotic hod carrier.

> You may get alerts about: severe flooding, fires, explosions, terrorist incidents, public health emergencies

So not a dispersal order then.

[Edit for format and dreadful spelling].

Are you saying that this 2018 article should have been updated to reflect the changing situation, or that children are still being separated from their families under Biden?

A little disappointed not to find Llandow, the WWII airfield I grew up near in South Wales. After the war its great open streaches of runway became the focus of much unofficial (then later offical) motorsport. Traders and scrap merchants took over the hangers and it grew into a trading estate. It turned from a patch of open farmland into a shabby, noisy but interesting place.

https://duckduckgo.com/?t=ffsb&q=llandow+&ia=images&iax=imag...

> investigative journalism ... “When you tell me that a lot of rich people aren't paying tax, I’m shocked but I’m not surprised because I know that. I don’t want to read another article that tells me that”. What I want is an article that tells me why, when I’m told that, nothing happens and nothing changes.

Well that's a big ask. Who do we hold responsible for nothing changing?

Hmm. May be it's me. Not sure I'm up for getting out and confronting the police today.

... but remarkably good humoured! (Or are those teeth gritted?:-)

Well for starters, each component's API can be published and versioned separately from its implementation.

The build of a component would only have access to the API's of the other components (and this can include not having knowledge of the container it runs in).

The implementation can then change rapidly, with the API that the other teams develop against moving more slowly.

Even so, code reviews can be critical. The things to look out for (and block if possible) are hidden or poorly defined parameters like database connections/transactions, thread local storage and general bag parameters.

In some languages dependency injection should be useful here. Unfortunately DI tools like Spring can actually expose the internals of components, introduce container based hidden parameters and usually end up being a versioned dependency of every component.

All devices in our house are creatures: griphook, fawkes, crookshanks, pigwidgeon, hedwig, aragog, firenze, grawp, etc.

Well apparently javascript can be used to modify the favicon dynamically: https://stackoverflow.com/questions/260857/changing-website-... - presumably this will then have the same interactions with the cache.

Perhaps you could just rely on the user navigating across a number of pages on your attack site.

In the case of the ZX Spectrum +3 there wasn't enough disk or memory to hold the uncompressed word list, nevermind some form of tree structure.

The search method involved uncompressing each word (one at a time) until either the word was found or one that should follow it.

However, I did intend to use a binary search of the word list on the floppy. I arranged it so any zeroes in the list indicated the start of a word from which decompression could start. Under maximum compression there would be only 26 zero bytes in the list, but by selecting short words at regular intervals I could spinkle zeros throughout the list (approx 1 per block). A binary search could scan for the zeros, decompress the associated word and find the section that should contain the target word.

Tasman didn't go for this. They sorted all the words to be checked in memory, then opened the file and did a complete scan.

The list was used with permission.

I don't know/remember the terms under which this happened. I do remember that when I was trimming it down I found the list contained the trademarks of a competitor. These were removed.

I wrote a spelling checker in the 1980's

In my first job I worked for Tasman in Leeds and produced a Word Processor for IBM PC compatibles in 8086 assembler with some help, and then a spelling checker.

For the spelling checker I did a whole load of analysis on a 70,000 word list from Collins and produced a list of tokens to represent common strings of letters. However, in the end I really had to cut the original word list down to get the whole thing onto a single 360K floppy.

After I left Tasman, I was lying in bed one night still thinking about it and realised where I had gone wrong. The tokenising thing, which someone else had put me onto had blinded me. I had stared at word lists for months and hadn't pinned down the obvious pattern. All but 26 words in the 70,000 word list shares the bulk of their characters with the word before it.

So the solution is use 5 bits of the first byte as a count of chars from the word before, 3 bits indicate commons enddings (ship, s, ing) or that the following bytes are tokens for the rest of the word. With this I got the word list compressed to less than 2 bytes per word.

I took this back to Tasman. They put all 70,000 words and the spelling checker onto a 175K floppy for the ZX Spectrum +3.

[Edited for typos]

I didn't know "Sign in With Apple" existed - I wonder why?

Need Amazon to stop replacing the "Continue" button with "Continue with Prime".

Keep cancelling it, but they keep tricking me again.

Fk! We haven't even started cleaning up the Great Pacific garbage patch or stopped burning the Amazon. Does anyone really think that any government is really going to stop dumping crap into space where no one gets hurt.

However they now have to be trusted. It might have been better to have figured out which you trust and only use those.

No. I concede that wiki rot is a problem, but just because no one has used a page for a year and all those involved have left the company doesn't mean the info isn't important.

Better solution: stop using big branded, overly clever and difficult to use wiki software. Have a single wiki, not split artificially by project, that can be searched as a single entity.

As a developer I'm a fan of checking the documentation into the same source code repo alongside the code.

If the code branches the documentation branches, if it merges the documentation merges. Documentation can then made to be part of "code complete" for developers. Think README.md

However, there's always resistance to this wacky idea. Chief being the lack of tools and management fear of editing text files. This article also adds searchability to the negatives.

Interesting, but a bit old (5 years). A number of these appear to be no longer active.

> a lot of sites deliberately make it hard to opt out

Amusingly I've just followed a link on HN to The Economist [https://www.economist.com] - their popup offers a link to "manage your cookies" where you can untick huge numbers of them or click "Opt Out All". Great - did that, however on returning to the page found the popup still covers part of the page :-)

However, we must remember Hanlon's Razor.

> Each one of there tokens ...

What are "there tokens"? Aw come on. How do you expect me to take any of this seriously with grammatical mistakes like this?

Correct.

Summary: won't fix - not a bug.

> This is the rocket that will launch ... a handful of artists on a trip around the moon in the 2020s.

... and so programmed to crash just like Golgafrinchan Ark Fleet Ship B?

A few years ago some idiot marked up pretty much every walk way in my town as a cycle way. As a keen cyclist who lives in a town with a somewhat poor provision for cycling, this is somewhat irritating as it makes our local government look like it is doing well.

I followed the feedback link and reported a whole heap of these, including links to Streetview showing the "No Cycling" signs in some places. I got automated replies to say that someone would deal with my report - but nothing happended. They are all still showing up.

Perhaps even Google doesn't care about Google.

I'm sorry - did I offend someone. Or did limited mobility cause a click on the fiddly and untitled downvote link instead of following the link :-)

You could start here: https://www.w3.org/standards/webdesign/accessibility

This not necessarily a problem. There's nothing to stop the website operator calling out to an ad provider, with the ip/location of the user, and getting an ad to embed.

The upside for the user is that location and whatever the one site is able to determine about the user is all that can be shared. If the user hasn't logged in with their real name - that probably isn't much.