EF Core has been available in dotnet core for quite some time and is now on version 3.0 and will use C#8 features.
You might find this enlightening.
82 posts • joined 5 Feb 2008
I expect my lock-screen to be impenetrable, with the exception of *only* apps with permission to make lock-screen notifications. That it's possible to install software that allows the spawning of any non-permissioned app over a lock-screen isn't an app developer problem... It's an operating system design flaw. The flaws in the OS that allow this that should really be addressed by alpha-goog-whatever-they're-called, not patched over in apps written by careless 3rd parties.
Here's a somewhat better camera making the same journey at night. The video of the incident is a complete con.
Having now seen the in-car video of the accident (it's a challenging watch), I find myself asking the same question I asked at the start. It really doesn't look like the human was engaged in any sort of meaningful supervisory role at all.
Assuming that the camera from the footage isn't anywhere near as light-sensitive as a human, it looks to me like there would have been enough time for an attentive driver to make the collision survivable or even avoid it altogether.
I wonder why the tests mandated any human in the car? It might give a veneer of safety, but they must know that the amount of attention a human is able to pay to the road when they've got nothing to do tends towards zero.
My Sennheiser Momentum M2 AEBT cans were my favourite tech-purchase last year. I've burned through a lot of headphones in my time, and these ones sound peachy-delicious. In listening tests at the shop where I bought them, I thought they beat the Bose, but they don't cancel noise quite so well...
...but they were jolly expensive, so I probably have chronic confirmation bias. Ignore me.
As an anecdote about software failings, the Toyota accelerator pedal really isn't a very good example.
On Wikipedia, we find a somewhat different version of events:
'On February 8, 2011, the NHTSA, in collaboration with NASA, released its findings into the investigation on the Toyota drive-by-wire throttle system. After a 10-month search, NASA and NHTSA scientists found no electronic defect in Toyota vehicles. Driver error or pedal misapplication was found responsible for most of the incidents. The report ended stating, "Our conclusion is Toyota's problems were mechanical, not electrical." This included sticking accelerator pedals, and pedals caught under floor mats.'
Bad design (maybe), bad pedal layout (maybe), but bad software? Fake news.
"People [could do bad things...] It’s a realistic possibility, granted that a lot of machine learning software is open source"
I'd offer that these statements form a non-sequitur.
Isn't this what people used to say about encryption? Proprietary = more secure? That didn't work out too well, did it?
Better that vulnerabilities are out in the open, rather than being quietly exploited by those "in-the-know".
This kind of research is possible specifically because the algorithms are so accessible.
...cold, wet food that has shared 40 minutes in a sweaty box with the other orders that happened to be vaguely along the way to your house.
For me, there's something rather appealing about the accountability of the restaurant (when it owns the whole process from kitchen to front doorstep) as opposed to the passing of the delivery process over to the scalpers.
...you dare to use non-Apple software for your work? Think again, motherfuckers. We have the levers to make your life difficult, and we just chose to pull them.
"Windows is a bad platform for dealing with media" is an important piece of disinformation that continues to propagate despite its evident untruthiness. However, in pulling this plug without warning, Apple can certainly reinforce this perception.
This post has been deleted by a moderator
A new IE6 for the next generation. Sufficient time has passed that a whole younger generation of devs and users don't remember why a browser monopoly is a fucking terrible idea.
I use Firefox because it isn't Chrome and it isn't IE (both of which have serious issues with the commercial concerns of their respective owners and the agendas that they are trying to push). Let's not remove that choice.
... trend of software vendors turning my browsing machine into a bunch of exploitable web-services.
So they make a browser that also has an accompanying service that listens for HTTP requests on localhost for "commands". That's quite a wide attack surface for a "locked-down" browser.
It does make me wonder how safe the spotify client is, given that it operates in a surprisingly similar fashion in order to interact with web-pages.
caused by using regular expressions to filter HTML content. Regular expressions are very poorly suited to the job of dealing with HTML and getting the filtering right becomes a game of whack-a-mole, as we can see here. If the content's going to a browser, it should be parsed with the same tools that a browser uses. To suppose that a "parser" built using completely different technology can stay current is talk from imagination-land.
...if we pay the ISP to record this data, or it's handed out from some government budget? The net spend will be the same. Saying that "the government" should pay for this is exactly equivalent to saying that the public should pay for this. Whether or not this comes from the public purse or through increased ISP fees, I imagine the net effect on my pocket will be approximately identical.
A simple check of stackoverflow.com reveals that there's a huge reluctance among developers to accept security best practices.
That's 730 pages of results. Ouch.
This problem has been solved in almost every credible web-platform by off-the-shelf, well tested login systems... yet a certain, highly prevalent breed of developer always thinks they can do better.
Sadly, the issue of security is very poorly understood by tiers of middle-management who allow these idiots to carry on breaking the web.
After entering my card details incorrectly on a reputable UK site, I was redirected to the security confirmation. I flagged the transaction to the site owners because the security question was "Please enter your ATM pin to proceed". They got back to me and told me that I had entered the wrong details and that the confirmation was a legitimate page from an Indian bank. If this level of security is the norm, I probably wouldn't want to bank there.
Biting the hand that feeds IT © 1998–2020