Why did the three women not get arrested for filing false police reports? Especially for falsely claiming that the man had a gun. There have been many, many reports of what happens when the police arrive on scene thinking there's an armed person for these women to not know what could happen. Also, accusing someone of being a pedophile and participating in drive by shootings?
If you haven't seen it yet, I highly recommend Henry Zhu's (Babel core team) talk from React Rally[1]. He talks candidly about the struggles of maintaining an extremely popular library and the demands and stress it puts on his life; especially now that he quit his job to work on Babel full time.
If your company uses Babel (which it probably does), please donate to Henry[2] or at the least, send him a thank you for his work.
Henry is a wonderful person, and this talk was excellent. I second the recommendation.
I posted my own thoughts about over-committing and potential burnout a few months back: https://blog.isquaredsoftware.com/2018/06/redux-writing-resp... . Since then, I've stepped back from trying to keep up with recurring treadmill tasks like cataloging articles and links, and am focusing my maintainer time on some specific Redux/React-Redux issues. Feeling a lot better as a result.
Not to shamelessly plug but if you're in the Bay Area on June 28, we're giving a talk that's a bit about performance, a bit about Netflix engineering culture: https://jstalks2018.splashthat.com/.
TV's would be one (of many) limiting factors here. Most consumer televisions have, relative to most other computing devices, low processing power and disk space. Plus you have to factor the additional bandwidth load of downloading a 4K television show that you may not watch and then multiply that cost by 30 or 40.
Yes, it would be like a Netflix box (maybe branded under their Roku brand name) that's similar to Tivo. A Tivo Bolt Premier can be had for $299 with a 1TB drive.
The key is signing a lower cost deal with Verizon/ATT LTE or Dish Satellite to do some sort of the multicast broadcasting similar to Over the Air broadcasting but over the internet. Or do unicast transmissions but during off peak hours and blast it out over the LTE/Satellite network over the span of a week between the hours of 1AM to 5AM. The Netflix Top 100 is probably like 95% of what people are watching.
That way not everyone is congested from 5PM to 11PM every night and the mobile operators have additional revenue from existing wireless/satellite infrastructure.
You authenticate to Plaid with your bank credentials, so it's not much different than the data you can get directly from the bank through OFX (like Quicken and other things do). Plaid just simplified it and put a better API on it.
That's pretty close. For our use case (and many others), the biggest culprit for increased TTI is the sheer size of the JavaScript payload and the time the browser takes to parse the whole bundle[1]. We still use React and other libraries on the server to generate the HTML but rather than sending all that JS down, Tony worked out exactly which client interactions still needed JS and wrote those in plain JS which resulted in a big TTI win as the browser simply had less data to parse.
I'd love to sit and talk React with you and your team. We're always particularly interested in performance optimizations so maybe we can swap some knowledge.
Not aware of any team that is actively avoiding React but we're a fairly prolific bunch when it comes to public speaking and knowledge sharing so perhaps I missed some announcement from another UI team. A few of my colleagues will be speaking at the SFHTML5 meetup[1] in a few weeks if you'd like to come hang out and talk shop or feel free to drop me a line at [email protected] :).
> Equifax discovered the unauthorized access on July 29
Well over a month later and they're just now getting around to telling people about a security breach that could affect almost half of all Americans...
Discovering a breach is only a fraction of what has to happen before customers/public should be notified of said breach. It's not very helpful to anyone if you put out a press release that just says "we discovered a breach but have no idea who, if anyone, was affected, we have no idea what was stolen, and we have no idea who did it." There have to be investigations that happen prior to any of that being known/released. Investigations to find this type of stuff out usually takes months, and typically involves the FBI or other agencies, which sometimes will actually ask you to keep news of the breach quiet if it might help them track down the perpetrators. You also want time to fix the issue before you go tell the entire world that there's a hole in your security.
I work in cybersec and I would actually say that under 1.5 months from discovery of unauthorized access to releasing this press release (and already having the equifaxsecurity2017 website up and running) is astonishingly fast work.
That seems reasonable, up to a point, but it also looks potentially self-serving and open to abuse (especially given the news about stock sales by insiders.) If a company in a position with this level of risk cannot staunch the leak within hours, it should be required to curtail its activities to the extent necessary to stop further leakage, until it has the proximate cause of the problem under control.
Nor should the instigation of credit monitoring be delayed until the investigation is complete. To pick a contemporary analogy, it would be like not informing the public of an approaching hurricane until its precise point of landfall has been determined.
Building off your analogy, you don't order mandatory evacuations every time you see a tropical depression form out in the Atlantic. It's only when the tropical depression actually turns into a hurricane and is on a collision course that you warn the public.
Data breaches are the same. If you put out a press release every time your infosec team discovered an attack, you'd be putting out releases every single day, multiple times a day, even though most of those breaches would turn out to be inconsequential after investigation. The public would become totally desensitized to them. That's why the investigation has to be done to determine if there actually is something to notify the public about.
Now, there's surely a point in the investigation where you "know" that the public needs to be notified, but you aren't completely done with the investigation yet. It would probably be in the public interest to notify then rather than waiting, but I think companies are scared to do this because many companies in the past have been lambasted by the public for doing just that. Apparently people don't like it when you release a statement saying "we had a major breach and some customers are affected but we don't know who yet", so it seems that companies are opting to get all the facts before saying anything.
In this context, there are two sorts of black-hat hackers: those who already know of the exploit, and those who do not. If it takes over a month to shut out the latter, then there is another problem.
NYC is still smaller than the Bay Area. And if you're comparing it to the Bay you need to include Jersey/CT/LI -- where $100k will go a long way along a train line.
It's a "national health crisis" because of the ethnicity and locations of the people it's affecting. Today, politicians are proposing more treatments and going after the pharmaceutical companies[1]. Back in the 80's and 90's, the response to the crack epidemic was harsher prison sentences for users and sellers because it was largely minorities who were affected[2].
Not arguing that treatments shouldn't be made available but it's important to keep all this in mind if someone ever suggests that all are equal in the eyes of the law when it comes to drug offenses.
