By this logic Tesla does not have "autonomous vehicles" either. They just do adjustments after the car crashes and kills someone instead of doing it online.
357 karma · joined March 26, 2018
At this point you may as well give up, because those people have access to (years old) 0-day exploits, which work flawlessly regardless of "security measures" used by phone manufacturer.
How much of farmland is situated close to cities (main cause of aquifer deterioration)? Would that farmland still have enough water after aquifers are caput?
The real problem with Flutter is it's tendency to attract bottom-of-the-barrel cheapskate customers. I don't want to double down on my earlier mistakes and box myself into lower-paid 10% of already lower-paid (compared to iOS) Android development market.
Is eval() a mistake?
In practice, if there is a mobile app, there is an API. Whether it's creators object to your usage is mostly their own problem.
Uhh... Those two matters are pretty much unrelated to each other. Scraping is becoming non-existing because the era of static web pages has ended. No need to "scrap" when you have a nice, performant JSON REST API provided for you.
YouTube is a humongous monster with their own network backbone and video storage boxes co-hosted by countless ISPs. Multiple major governments would like to unseat YouTube, but they simply can't. YouTube's competitors are Netflix and (to lesser extent) classic TV networks.
Reddit is a web forum hosting platform, that can be wholly bankrolled by a single upper-class US citizen (assuming that your drop their awful video-hosting). Reddit's competitors are WordPress and phpBB.
One of them is somewhat of necessary evil. Another hardly deserves to have it's own custom clients to begin with.
This is actually my biggest takeaway from the article.
This is an oversimplification... How many countries have built nuclear power plants and missile assembly lines in their colonies?
That only works when you have infinite memory (or infinite CPU resources).
> It's very easy to make a reference counting scheme not stop the world. It's a bit more difficult to make a GC implementation so.
Only if by "not stopping the world" you mean your previous suggestion (leaking unbounded amount of memory to free() everything at some later point). When your memory is bounded, you will eventually have to stop/crash once you have run out of it.
AFAIK, the best modern state of art garbage collectors have stop-the-world pauses, proportional to size of root set and/or thread count. I'd love to see an RC implementation, that does not have stop-the-world pauses at all, but that sounds as audacious as claims of perpetual motion machine.
They do whatever Microsoft tells them to do, because the alternative is being forced to pay extra $200 per laptop sold.
Unless you are drinking a tap water (pretty extreme thing to do!), the effect is probably non-existing:
Upstream Git client says "Binary files a/filename and b/filename differ" whenever it detects changes a binary file. This is mentioned in output of 'git diff', 'git status', 'git show' and other commands.
They are (albeit not as prominently as they should). And you can add your own diff engines to show full diffs for different binary formats.
Jaotc, — Graal's sole mainstreamed part, — has been recently removed from OpenJDK in 17th release, and Oracle says [1], that they are "considering the possibility of using C2 for ahead-of-time"
1: https://mail.openjdk.java.net/pipermail/discuss/2020-Novembe...
Well-written code does not need it. Poorly written code can not trigger it, because the JIT is too dumb and isn't getting better.
There is no sane test to determine whether a piece of code will be inlined in Java. In practice anything more complex than byte array is unlikely to be inlined. Even built-in ByteBuffers aren't! Meanwhile Go compiler treats Go slices just as nicely or better than arrays.
If the database fits onto client hard drive and the modifications are rare, preloading everything is almost always better.
If you have a dynamically changing system such as bug tracker, it is still possible to go fully local, but that would require considerable cooperation from server side. When the back-end does not have a fast, efficient API for sending diffs, you may get stuck waiting for it to be implemented. But that's a purely organizational problem.
Of course, all of above applies to actually saving data to permanent storage. Storing everything in memory is a sin by itself.
Most compilers assume that emitting the code in certain modes (SSE/AVX etc.) have particular cost. That cost may drastically change depending on how the implementation of the hypervisors handles the registers in question.
Billions of people have been using computers for decades. They are not going blind. There is no epidemic of insomnia. At the same time, there are thousands, who claim, that looking at monitor with adjusted gamma feels more pleasing and helps their sleep. Why are they saying so?
Instead of studying the actual phenomena (different monitor gamma acting as signal to sleep) the "researchers" went out of they way to confirm something, their sponsors wanted them to confirm. Circadian rhythms? Nah, never heard about those — let's just check for retina damage and eye strain after brief 2hr period.
I don't understand, why people think so. Banks hire good developers. They don't pay them well (by banks' own standards), but they still pay enough to hire competent programmers.
Unfortunately, working in bank is highly competitive environment, that fosters sycophants and rewards socially adept people, good at obeying orders to letter. Who cares, what the programmers think, they are at the bottom of command chain anyway.
The fraud prevention is often split into it's own department. As for "computer security" department, it is a fang-less security circus, that exists to satisfy PCI DSS. In some banks it outright pretends, that web sites and mobile apps don't exist. All your data will be processed in "secure server enclave", managed by "certified professionals", while sending hashes of credit card numbers to Google Analytics.
Good news: your society isn't collapsing. Bad news: it looks like it is going to shit.
The logic of GOPATH and "go get" just so happen to revolve around building packages, fetched from source code repository. This logic used to be a stop-gap, written during early stages of Golang development, and makes it awkward (at best) to distribute proprietary Go libraries. I assume, that Google is introducing module system (and aggressively deprecating GOPATH) to work around this issue (among others).
I stand corrected.