It's like with any big company:
they'll have a bunch of SREs and SWEs working on it and trying to solve this asap, but it's probably too technical to give more details than "we're investigating".
It seems with these "Big Provider" outages its a cascading failure across a few systems as opposed to a single point failure which makes debugging a bit harder.
I think you meant "paid customers". Pretty much all the people wrote here are "customers" one way or the other. By "updates" if you meant the message in GSuite Admin account notification section, it's no more insight than what's describing here:
https://www.google.com/appsstatus#hl=en&v=issue&sid=2&iid=cc...
I guess the point is you might already own a PC, and you could use that for developing Android apps, for example. But if you also want to use Xcode and develop iOS apps as well then you have to buy a Mac.
No, you don't need a Windows license to develop for Windows. That's the whole point here. You can code and compile binaries for Windows, Linux, Android, etc. from many IDEs and virtually any platform under the sun. You can code and compile binaries for Apple products from exactly one IDE and exactly one platform: Apple's.
It's possible this has already been reported to the police, but we all know they don;t tend to move to fast on things like this, and it's likely Deliveroo doesn't want to risk hurting it's own reputation by shutting out restaurants it suspects are taking part in this scam without enough solid proof that they are definitely in on it
I mean if they keep using the same exact "restaurant" whose address ends up being an Apartment... It would be really suspect. Not saying this is the case, but it'd be more obvious if it were.
If they put the FSA "Scores on the Doors" (and local council) food standards ratings on, the act of looking up the address would tell them something was up.
"Address given is not registered as a restaurant or food outlet" (aka: they're not registered with the local council).
I've gotten into the habit of checking 'Scores, just because of the sheer number of poor quality food places on Deliveroo, Just Eat and so on.
By the sounds of it this is a simple credential reuse attack (it's even states as such in the article) so I really don't see where these accusations of a "data breach", and "encryption, which appears not to have been in place” come from. If these fraudulent transactions are the result of credential reuse I really don't see the GDPR violation here.
Yeah, not to defend Deliveroo (that's still abhorrent customer service), but I fail to see how they can back up the allegations of the various breaches. How do they know encryption was not in place?
Don't see it either. Nobody said there was an actual breach. Of course a change of delivery address/email/phone or when combined with unusual orders (large amounts) should be flagged and cause 2FA or some other mechanism to request confirmation to the account holder of record.
Pretty neat but it seems the letters do not line up correctly. In such a small space any slight misalignment is really obvious.
I noticed the <Margin on the left is 16px, on the right is 17px. Similarly from the top is 21px and the bottom is 20px. It makes it look really off (to me).
If you are a site operator with a certificate issued by a Symantec CA prior to June 1, 2016, then prior to the release of Chrome 66, you will need to replace the existing certificate with a new certificate from any Certificate Authority trusted by Chrome.
It's great to see companies doing more to help charitable causes, but considering the price difference ($749 vs $649 for the base iPhone) I'd like to know exactly how much of that extra $100 goes to the supported charities...
Avoids taxes, donates to charities. This is a way to let billionaires and corporations dictate public policy.
Don't like military spending? Defund it by donating all your taxes to the arts instead. Public school programs not teaching enough creation theory? Take their money away and give it to churches. Charity spending is seen as an enormous loophole by quite a few people. And that doesn't even get into scams such as donor advised funds.
I'm not as clued up as I used to be about this stuff, but wouldn't this have a pretty serious impact on the performance of the individual cards? Seems like splitting 4 16x cards off one 4x bus would limit the available bandwidth somewhat.
Though amfeltec is sadly a pretty unknown company. Probably best known for their "squid" PCIe "split" cards for multiple M.2 drives in one x16 slot. I've used one of them.
I suppose if you're just working on a data set that's already stored in memory on the GPU(s) the initial work involved in getting that data to the card would be impacted but everything after that benefits from having an absurd amount of computing power
It would be interesting to see this kind of graph created for other languages like Python, Node.js, etc. to see how they all compare. It would be neat to visualise which language/framework has the worst case of dependency hell
Rust is somewhere between Ruby and Node here: leaning towards small modules (one of my crates is in this graph, and it exports four functions), but not to the same level.
> It would be neat to visualise which language/framework has
> the worst case of dependency hell
So, one thing I've come to realize is that different people have different opinions on what "dependency hell" even means. If you have a lot of dependencies, but your tooling reliably makes it easy to get them, build them, and upgrade them, is that hell?
There are a number of objective measures of cyclomatic complexity in software. These metrics show that the higher the complexity, the lower the cohesion of the code[1].
Code that is complex, and has low cohesion, is harder to understand, and therefore harder to change. It's the elephant you have to push on every time you want your program to do something new[2].
"Dependency hell" might be subjective, but tools that reduce the upfront cost of increased dependencies don't remove the other burdens from you, the developer. In fact they often allow you to produce an impenetrable, unrecoverable tangle more quickly than doing without them.
Edit: Just realized who I responded to... "But, you knew all that."
So, what's interesting is, I would often consider many small bits to have a _lower_ cyclomatic complexity number. That is, whenever I've used tools that measure this kind of thing, the solution is always to take the big things and break them up into many, smaller bits. It's possible that this is bias in the tooling, though.
I think some of this comes down to individual preference as well. It's like that joke, would you rather fight one horse-sized duck or 100 duck-sized horses? In this admittedly very stretched metaphor, the former are relatively monolithic codebases, and the latter are relatively modular ones. I know that I used to prefer one hundred-line class to ten ten-line classes, but now, much much prefer the latter. My experience talking to people about this is that people fall somewhere on this line, often in different places, and that makes it harder to understand. The action that I'm taking to reduce complexity can often be perceived as increasing complexity, depending on where the other person falls on that line.
Lots-of-little-ones (LOLO? LOLO) is the right answer in a number of cases. One big god service? No; microservices (lots-of-little-ones). Large many-lined functions with copious branching and conditionals? No, LOLO. Big teams with multi-hour status meetings? No... LOLO. One big integration at the end of the project? No...
That dependency diagram for Servo actually looked relatively clean. You can clearly see which elements are library or utility code. The visualization would probably be better as a three-dimensional model with weighting.
For OO practice, state of the art is SOLID (with a sprinkling of RAII if you happen to be using C++). SOLID leads you straight down the path of LOLO. Small increments FTW.
Dependency hell for me is when I have one target depending on two or more libraries that result in conflicts that can not be resolved without resorting to butchering one or more of the libraries.
One nice example that springs to mind here is that there is a package in some linux C library that defines a 'list', which in turn conflicts with lots of other libraries and applications that also wish to define 'list' but in their own scope.
> but your tooling reliably makes it easy to get them, build them, and upgrade them, is that hell?
Dependencies are never free. If you have a bunch of dependencies and not have too much resources it's still hell.
Managing dependencies is not hard because of the tooling. It's hard because a dependency upgrade could cause pain, or the current version is buggy but the fix inside the upgrade works, but there will be another bug and so on.
Right, this is what I mean: different people mean different things by "dependency hell". Difficulty of upgrading is certainly a possible meaning, but it's not a unified term.
actually people just trust too much other people. but since you don't know anything about other people you should not trust them and especially not trust their ability to create good code.
> It would be neat to visualise which language/framework has the worst case of dependency hell
I've worked on very large projects in Ruby, Node.js, and Java. In my experience, Java programs tend to have the most dependencies, especially if you use Spring, but also the best tools for managing dependencies.
People like to rag on Maven, and there is a lot of truth to the criticisms, but I've had a much easier time resolving dependency problems with Maven than with other systems, and I find that it helps me avoid a lot of problems proactively. For example, you can exclude transitive dependencies from imports, if they will conflict with other versions you already have in your project. The result of this is that some of the Java projects I work on have 10x the number of dependencies as some of the Ruby projects, but far fewer dependency problems.
I see nothing wrong with having lots of dependencies, even on small projects, as long as you have the right tooling to manage them and can guarantee reproducible builds.
I think these graphs should have multiple colours: One for language built-ins and one for each third party origin. A deep graph isn't such a big deal, but I'd assume that a very colourful graph can be.
I check dependencies like this from time to time on the projects I work with in Java.
I use it to see if there is anything I can shave away. (After embracing the fact that we are deploying to a Java EE server builds have been steadily shrinking and I now think the main war is has shrunk by 60% and I have a POC that should shave another 10%)
(For maven/Netbeans users it is trivially simple, just open the pom file and find the dependencies view in the "pr file/ toolbar".)
I find it interesting that they list ad blockers under "largely unused, resource hogging" features. I'm pretty sure that preventing countless JavaScript files, images and (admittedly very rare) flash files from loading and bogging down the rendering engine improves browser performance?
Other than that I really like the idea of this browser, and it looks decent to boot! I'll definitely have to check it out when I get home.
