Is it supposed to be a midway point between Model 3 and Model X? Or is it supposed to be the cheaper version of Model X? I can't tell exactly where it fits into the lineup since "midsize SUV" can mean a lot of different things and is pretty vague (especially since the model X is considered a "compact crossover SUV" per wikipedia).
When the output switches to rabbit the picture actually resembles a rabbit. I am unsure if this experiment was supposed to be a “haha look how stupid AI is” type thing or not, but it seems like the cloud vision api is performing as intended.
I don't think there's much to see here...it is a cool bug though that doesn't require a super high level understanding of security to figure out.
But a 6-9 month time to fix seems really long (also I would have thought a $1000 bug bounty is low for this type of exploit...but then again I'm not in this space too much to know the average rewards).
By competition do you mean other EVs? If so, I agree with your point. I’m taking “competition” to mean tradition gas powered vehicles/big car manufacturers. Imo I think Tesla is picking a fight with gas powered manufacturers since they’re offering something at the same price point (ish).
I see that point, but since Tesla has been around for a while now, consumers cannot keep giving them a pass solely because of the technical feats Tesla has achieved. They need to be held to the same criticism from the business standpoint as any other company would be (especially since Tesla is trying to position themselves as a middle-class-friendly option for EVs with the model 3).
I don't think necessarily GraphQL is hard to understand as a concept. It's just difficult to figure out how to use it in an actual app context. How do I handle more complicated things such as authentication and, more importantly, what are acceptable and secure ways to structure your queries for auth (and things like that). I can certainly hack around with `context`, I just don't know what is actually good or not.
Well yeah it assumes you don't have SSR. But that isn't a useful metric for this "study" since SSR just gives the bare html. This person is just measuring time to interactivity/fully loaded JS and costs from the JS perspective.
Idk about the blockchain stuff, but it is semi-featureful since it can extract text from images (I'm assuming its just using Tesseract OCR. At least it could get the text out of this http://www.antigrain.com/research/font_rasterization/msword_...), and I assume audio (but I am having difficulty testing it out). Tbh the formats it accepts as well as the fact that it is available over messenger are huge "selling" points for me and should be way more emphasized on the product page than blockchain and AI.
As a CS student, I agree it is really refreshing to see basic graph algorithms to be used in a practical, non academic/industry context. I never really see these basic algorithms used in small side projects, so thank you for this!
I guess unpopular opinion: I think this library is excellent especially for making readable regex match/replace code. Even as a frontend dev with 5+ years of experience, it's difficult to read regex by skimming it (perhaps that's just b/c I don't spend much time with it at all outside of matching user inputs). Hopefully, if this library catches on, it may make JS code using regex slightly more readable. Regardless, props to the author for making this library.
> Don’t make a substitute for Google Photos or use this API to create, train, or improve (directly or indirectly) a similar or competing product or service. For instance, if your app’s primary aim is to provide a general purpose photo gallery app, it’s a substitute for Google Photos.
Yay for an ethics component! Albeit, I have a strong feeling it'll be treated as a (for lack of a better term) BS class since the audience this caters to isn't necessarily those interested in academia but are more likely to do this track b/c it'll be more beneficial for jobs.
Really I can say that most frameworks are being misused by people who just learn X because it’s cool/new/trendy and everything else is automatically “bad” relative to that framework they learned. So don’t put much credence in claims of X being the best (chances are people didn’t look at Y and Z).
There are certain things react emphasizes which people think is the best thing since sliced bread, namely component based architecture and automagically updating views when there’s a change to state.
Only use it if you find jquery etc to be too painful. If you are fine as is, it’s a nice learning exercise but probably will cause more headache than anything else.
I teach javascript to students coming from Java and Python and, while I do agree npm could be better, students find it to be so much more intuitive rather than have some IDE handle packages (in the case of java) or be stored somewhere in your system path with python. Being able to see the dependency within node_modules and make that connection between you saying "i want to install this" and it appears in your project file system makes a bunch of sense for beginners.
Being nitpicky here: you mention this somewhat in your comment, but I just want to stress that redux is absolutely not necessary to your react application (though a lot of beginners think it is a "must know" because every blog article says you need to know it). React in and of itself allows you to achieve the same functionality of redux (and a fairly complex app) without the need for a bunch of boilerplate code. Of course, if you deeply understand redux and its purpose, it can make creating large apps less of a hassle, but there's nothing in react that says you must use redux to make a complex app.
I found CSPA to be an interesting proposal. I'm currently studying CS and Biology and found that the comparison of the exam to the "SAT" of computer science is a bit of a misnomer. The SAT requires minimal prior knowledge to take (albeit if you want to score well, you end up needing to study for it through test prep books etc). I think perhaps it may be more likened to an MCAT equivalent (or any professional school exam equivalent) because of the need to know about certain subject fields.
Someone also brought up a point regarding the validity of testing for skills in web development if test takers won't end up in those fields anyway. However, when looking at similar exams (e.g. MCAT), you can make the argument that the majority of doctors won't use Organic Chemistry or won't need to know about the minutiae of Psychology & Sociology to be successful. The MCAT becomes a successful discriminator of good vs bad test takers because of the amount of work and critical thinking skills that is needed to cover the litany of subjects tested. Similarly, the CSPA could follow a similar pattern as the MCAT by testing a range of subjects as a means of measuring one's ability to learn a large sample of topics.
The only thing I can really think of that CSPA can improve upon is providing more preparatory materials. Additionally, it'd be useful to see how people end up performing on the exam and if there is an actual "Bell Curve" like distribution of scores that results.
I teach a course at upenn on intro to javascript. Perhaps the most useful advice I give to my students is that often the simplest tools will get the job done i.e. you don't need React, Redux frontend stack because for most cases jquery will get the job done much quicker. Only worry about the frontend libraries when you feel it's getting out of hand, otherwise, the simple, straightforward tools will suffice.