Mazda addressed both of those issues, Rotax addressed both of those issues, Norton addressed both of those issues, NSU addressed both of those issues, Comotor addressed both of those issues...
The issues remain fundamental, and largely unaddressed.
> While the sheriff's department said protesters at one point blocked entrances and exits at the hospital, no videos or photos confirmed that was the case.
[snip, most of the article about the shooting itself]
> Rather, video footage showed a handful of deputies standing in a driveway (apparently an entrance to the hospital’s emergency room), while the small group of protesters paced up and down a sidewalk feet away from them.
> At one point, deputies detained a journalist with LA’s NPR station, KPCC, who was reporting on the small protest, as well as a male protester who “refused to comply” with deputies’ demands to leave the area.
> The sheriff’s department said the reporter, Josie Huang, ignored deputies’ repeated commands and did not present “proper” press credentials. But she said and videos of her arrest show she didn’t have time or space to react to deputies orders before they shoved her and forcefully took her into custody. In one video, she can be heard shouting “I’m a reporter… I’m with KPCC” as officers push her to the ground. They cited her with obstructing justice, though KPCC is urging authorities to drop the charge.
Adding onto this to say that the LA Sheriff's Department has less than zero credibility when it comes to any matter concerning either race or protests against police action. They literally have violent and racist gangs operating in that department. There is a reason why "Google LASD Gangs" has become a meme in LA and LA-centric circles of the internet. It is a known problem and almost no one in power is working to fix it.
That makes it futile (for someone as big as Rogan anyway), yes. But Young still made the ask. It's the ask I find objectionable. He could have just taken his ball and gone home, but he went farther than that.
Then why does he care if it's on spotify? Bit of cognitive dissonance going on here eh?
This is absolutely Young pulling an authoritarian "You're not allowed to hear things I don't like" move. There's really no other way to spin it. Disagreement with people is great, to then take the next step and say that others should not get access to the things I do not like.... well that's just a step another rung up the authoritarian/fascist ladder. It's a elitist control freak mindset.
It's so opposite of what his music is supposedly about you have wonder whether he's just been a sellout this whole time.
I'm curious if you've found any GUI frameworks for any OS, in any language, that have ripped out all their legacy code and/or the design tradeoffs and hacks their legacy code required.
>I'm curious if you've found any GUI frameworks for any OS, in any language, that have ripped out all their legacy code and/or the design tradeoffs and hacks their legacy code required.
Yes, Qt4 is not compatible with Qt3 , Adobe Flex4 was not compatible with Flex3 , I only used at that time this new versions and did not had to work or learn the old stuff. Old projects continued to use the old stuff and continued to work.
Add a little line noise for the average 30-70y/o house wiring and you get 43 hours for 33.6 or 50 hours for 28.8. It took running a brand new line in order for me to get 56k. So, the parent comment is accurate.
It was absolutely prohibitive for the average person with a shared line, and the direct comparison to shared line today is a metered connection. Even in the US it can be as much as $30 per gigabyte which would make that 60MB download cost $1.80.
There's a proxy polyfill. And if you really wanted there's at least one pcre2 wasm build you could wrap to make a polyfill, lol. Barely anyone uses lookahead/lookbehind even in pcre, though.
Proxy polyfill: assuming you are referring to this [0], since I haven't seen anything else like this, then I'll paste here what the readme says:
> The polyfill supports just a limited number of proxy 'traps'. It also works by calling seal on the object passed to Proxy. This means that the properties you want to proxy must be known at creation time.
i.e. that's not a polyfill for Proxy. It's a polyfill for a subset of the thing, maybe that's useful for somebody, but it's useless for the use cases I had for Proxy so far.
Shipping an entire regex engine with your app: right, that's the only way to do something like that. Not that that's actually the same thing though, I can't just load this and use lookarounds as normal, i.e. it's not a polyfill.
For all practical purposes these features are not polyfillable. If your idea of a polyfill includes not actually polyfilling the entire thing or shipping an entire engine with your app then sure, anything is polyfillable, you could even run Java in the browser.
Electron does not weigh 300+ MB for starter, and one means basically statically linking your app so that it ships with its own dependencies and works more consistently, while the other means shipping a language because the one you have to use is not implemented properly by the platform, pretty different things when you look at them. I'll give you though that in both cases you are shipping a big engine with your app, so it kinda sounds like the same thing.
The key leak could just as easily be incompetence. Accidentally committed to git, or in their travis setup in such a way as to be easily obtainable, or a bunch of other options.
High effort for high reward like this is not surprising but it could all start with incompetence.
Blaster was a worm (self-transmitting and replicating without user interaction.) I was in IT when it came out.
XP SP2 had the firewall enabled by default in 2001, which blocked incoming SMB protocol requests and other related ports by default ("file and printer sharing" exception checkbox.)
Additionally, a security patch for Blaster was released July 16 2003. Blaster itself showed up August 11 2003, so you had almost an entire month to evaluate the security patch.
So in order to be affected by Blaster they had to
1. enable sharing of folders on client machines (connecting to servers does not require this firewall exception.)
and
2. fail to apply a security patch for a wormable exploit in a timely fashion.
That's not wide-open, that's (if they have control of client machines) IT department failure to act responsibly.
I remember, around 2003, laptops getting infected just by getting connected to the Internet. It can be appropriate to use the expression «a wide-open door for malware».
