this article is a bit tough... feels like a marketing piece for some Google report.
did I read that wrong or was this whole analysis based on percentages... like what does 76% -> 24% drop in memory related bugs mean in terms of nominal bugs or nominal bugs / kloc
also, it mostly credited memory safe languages but then also just threw this out from the Google report
> Based on what we've learned, it's become clear that we do not need to throw away or rewrite all our existing memory-unsafe code
tl;dr android may be producing less memory-related vulnerabilities and it's not exactly clear how
maybe Ubuntu? the web development flow (so closely tied to firebase) might suffer a little bit, but I imagine a fork for non-web env's would be quick and welcome
Mostly linux agnostic, but in case it helps, its was all right for me. The practice exercises at the end of each section offer some hands-on help with some linux tools
Thank you. This was an amazing explanation. I am new to SVM's but did not make the connection that margin points (observations along the margin of the hyperplane) become your support vectors. This makes a lot more sense.
And if I am following correctly, it would make sense that the final step would then be:
We would maximize the dot product of a new observation with the support vectors to determine its classification (red or blue)
I know this price is pretty on par with the likes of Northwestern and other great schools that offer similar online programs. But it seems a bit insulting when schools like Georgia Tech are offering a $7k online Masters CS. A lot of the infrastructure of modern college is online anyways, so I'm not sure that putting the lectures online and removing the facilities completely is progressive. Learning to scale these classrooms efficiently and continually reducing the fixed cost per student seems to be what we're (me, without the dedication/job willing to pay for this degree) waiting for. Especially, if the goal really is to provide an education available to all online
In my opinion, this is simply making a concerted effort to like this person, and start comfortable dialogue. Even knowing this is a script, I'm excited to talk to this guy, rather than the usual challenging, testosterone-filled reactions I deal with on a regular basis. However distasteful and/or transparent, at least its a positive environment for conversation. Nothing is worse than talking to someone and thinking, their guard is already up
did I read that wrong or was this whole analysis based on percentages... like what does 76% -> 24% drop in memory related bugs mean in terms of nominal bugs or nominal bugs / kloc
also, it mostly credited memory safe languages but then also just threw this out from the Google report
> Based on what we've learned, it's become clear that we do not need to throw away or rewrite all our existing memory-unsafe code
tl;dr android may be producing less memory-related vulnerabilities and it's not exactly clear how