I’d think it’s one of Boeings stockholders who had a judge against him speaking out.
3,522 karma · joined May 20, 2014
I’d think it’s one of Boeings stockholders who had a judge against him speaking out.
But thru multiple forced relocations and unceded land take over, the reservation was gradually taken over.
>Slowly, from 1886 to 1902, Indigenous peoples were removed from their traditional village sites and homes and required to live on reserves. As the City grew around them, legislation was enacted that required all Indigenous peoples on reserve be removed if the population around them exceeded 1,000 settlers. In 1913, this happened at Sen̓áḵw. A barge arrived, and the residents were instructed to board the barge to receive funds from the Indian Agent. Once everyone from the village had boarded the barge, it was pulled from the beach and set adrift into English Bay. The village was then set on fire and burned to the ground. The owner of Cates Tugs, seeing the barge drifting precariously in the Bay, went to the rescue and towed the barge to Capilano Reserve, located in North Vancouver.
https://bardonthebeach.org/history-of-senakw/
It was only thru recent lawsuit and legislation that part of the reserve (an awkward T shape in the middle of wide stroads) was returned.
The 10acre of land in this article- https://www.google.com/maps/place/Kitsilano+6,+Vancouver,+BC...
https://www.cbc.ca/news/canada/british-columbia/little-known...
1. Most of the new CVEs have potential security concerns. At the very least, they would have been assigned a CVE if they were reported by an external researcher.
2. Many of them don't affect the older LTS branches.
3. I found 1 (1!) CVE that has a remote exploitation possibility. The rest are mostly local privilege exploit or DoS or crashes.
4. This Greg dude (heh) is backtracking to 2021 to flag bugs that have since been fixed. If your kernel repository is even semi up to date, you would have cut down the CVE count by 1/3.
In my company, the majority consensus amongst the kernel developers is 'patch your shit and do rolling release. We are too busy to evaluate all the CVEs.' On the opposite end, are embedded hardware kernel developers who barely had their kernels working on existing hardware. Both sides make good arguments and I don't have any opinion I'd share.
There are other ways to lessen the CVE workload.
1. Disable unused components with defconf or make menuconfig.
2. Don't stay on the bleeding edge branch (ie. 6.x)
3. Implement automatic minor version commit merges
Your mileage may vary, but with these implemented, the workload is managable imo.
Yes, by telling the NTSB to ask the door specialists "which of you installed the door", instead of having proper documentation on who did exactly what work. If the workers can't answer the question, now Boeing can wash its hands clean and blame the workers.
I doubt the workers themselves keep track of which specific planes they worked on- and they shouldn't need to, this is project management.
By 'proactively and transparently' I assume Boeing means telling NTSB 'we don't know anything so we can't answer your questions lalala.'
>"Early in the investigation, we provided the NTSB with names of Boeing employees, including door specialists, who we believed would have relevant information. We have now provided the full list of individuals on the 737 door team, in response to a recent request," Greenwood said.
Boeing throwing its employees under the bus- 'no we don't have any record of the work. Why don't you bother our plant crew instead. They would know everything because someone does, and it's not us Boeing.'
I once had the misfortune of generating a batch of defective enterprise-grade SSD from a S company. That S company requires all RMA to go through the sales channel you bought the SSD from, but the sales company we used was out of business.
S has refused all attempts to RMA by stonewalling us saying that we need to return the drives thru the bankrupted company. When we explained that the company is bankrupted, S just ignored us. When we created a new RMA request, S's rep says we already have an open case, and that we need to return the drives blah blah blah.
After 5 months, in a fit of rage I typed up a 2000 words complaint, gathered all the emails/phone calls/photo evidences, and submitted a complaint to CRT ($75 fee). I wasn't expecting much, but within 3 weeks I got a call from a corporate lawyer in S company's Toronto office, asked me for the situation, apologized profusely, and asked if I can drop the case if they RMA all affected SSDs.
That day was great, to say the least.
Aside:
The CRT posts all their cases (that reached arbitration) here- https://decisions.civilresolutionbc.ca/crt/en/nav.do
Reading the cases is quite am entertaining time passer.
We more or less hiked (no trails) till sunset, when I suggested we should turn back before dark. The island was more or less deserted except for a newly built public housing estate at a pier. Being stuck on a (almost) wilderness mountain surrounded by abandoned tombs at night was not my idea of fun.
Ok
>Photos from the interior repair that show the lack of bolts
Huh. Well that's conclusive.
Of course he is going to say whatever is needed to save his job, but in my eyes Boeing should move on and choose someone else. Time is running out.
/I asked the same question and got this from the dev.
And the world yell the same thing to USA. Canada, Italy, and England etc. all subsides their world-class universities with public funding. Where do the students go after graduation? US.
Whereas I worked on Chrome's V8 C++ code for a year and I still could not say I understand more than half of it. Its complexity is a factor more than the Linux kernel.
I just want to add that the food delivery bikers don't ride on the sidewalks solely because they can't go fast on the poorly maintained NYC sidewalks. If they could they would go at 30 miles/hour on sidewalks.
EDIT: I am working in an office at Time Square right now. I just looked down the window and counted 2 delivery bikers going at ~15miles/h on the sidewalk (The buildings are new and their developers fixed the sidewalk.)
At 4.0 the gap widen. While IE's rendering speed got even faster, its integration with Active Desktop etc. slowed down the start up in Windows 98. Netscape got even slower across the board. It's funny that even without the fancy features Netscape 4 was slower than IE4.
By 5 the dust was largely settled. Netscape was on rapid decline and IE5 optimized/got rid of all the IE4 crap in Windows 98SE. My desktop (Pentium III 800Mhz) was faster with 98SE' IE5 than IE4, which was much better than Netscape 4.0.
Operating margin dropped to 9.6% from 14.6% YoY. Not great.
Earning beats estimate by $0.91/share vs $0.80/share. Better than 2022Q2's 0.76 though.
Production rate YoY growth is 86%, from 258,580 to 479,700.
What I find more interesting is the FX impact of $0.6bil. Since China's renminbi is so weak, you would think Tesla would gain from China's export; but instead it lost money on FX.
Have you ever heard of the Geforce 8 Series "Bumpgate"?
1. Windows Defender anti-virus checking the binary and contacting MS' server for binary signing/black list
2. Kernel32 trampolines
3. All sorts of security mitigation techniques such as stack cookies setup etc.
4. Telemetry
5. Hardware accelerated GUI initiation vs 'dump everything to frame buffer in kernel GUI32 library'
6. Load fonts, graphics etc. that can work well beyond 640x480
7. Deal with the scheduler juggling hundreds of processes that let you from accessing winsock2 lib immediately, to have multiplex sound mixing, to system restore, all in the background.
Because we are in generation 1. What about X generations later?
As for the UI change. That's a completely different topic and I am not sure why you are bringing this up. The UI change doesn't change the content/moderation of the communities.
>It'll become a problem when mod quality is obviously, significantly worse, and no sooner than that.
And I am predicting the mod (thus content) quality will eventually be significantly worse because of this action by the CEO.
Edit: The parent post edited his post so the arguments are now don't quite directly counter his points. Now it seems like I am strawman-ing. Why would you do that?
Because the current batch of moderation work well enough.
Now imagine the current batch leave, and the new ones take over are worse (and they will be worse since Reddit has shown that Reddit has direct control over the Moderators' position safety, if the actions are not aligned with Reddit's CEO. Some reasonable people will not like that.)
Eventually the remaining good ones will be replace again, and after a few generation, only the bad moderators are left.
For example, just look at every dictatorship government in the world. No dictator starts out hiring only bad officials. Everyone's benevolent with good intention. Eventually, the good officials gradually get push out and sycophants fill the rank.
When Musk took over and pissed off everyone, the only protest the users can do is to leave the platform. Some did but not enough to hurt Twitter. That's because the management (ie modding) is done by Twitter staff already. With a strong brand, Twitter survived.
For reddit, the core value is the unpaid moderators. If those moderators leave, you now have a bunch of communities with no management. History shows any communities entering an anarchy (or worse sycophants assigned by Reddit) will not last long, or at least, will stop their organic growth and decline.
https://www.tesla.com/blog/opening-north-american-charging-s...
I do agree that the connector needs to be a public standard and the licensing fee needs to be kept to a minimal.
(I am against free solely to cover the cost of standard validation similar to WiFi. As we see from USB-C, having 1000 companies of various quality developing charging cable is a disaster, but now it's 400V 500Amp connector.)
1. Tesla already opened up the NACS connector for others to use. We don't know the detail yet but the license fee is probably minimal if Ford and GM agree to join.
2. the CSS1 connector is monstrous compare to NACS, with design deficiencies that are more or less not fixable.
3. Your USB example would be more like manufacturers sticking with Serial port (with manual configuration and payment done by the user) vs plug-and-play USB 1.0 (still a pain but it's a huge improvement.)
4. Tesla has a larger and better charging infrastructure than EA etc. What's wrong with giving infrastructure subsidies to companies who proved they have a superior product? Or do you think that everyone deserves a piece of the pie, regardless of their technical competency?