Not really. It just shows that most police departments are lazy and rather revenge kill than protect. We've had standoffs last weeks when it involves private militia. The shooter was driven back into a hole and had no way out nor any hostages nor a viable target. He will run out of stamina, food, bullets eventually, but he already killed a cop so he must die that hour.
As a green card owner, the first several years (as long as you have the accent) your wages will be depressed, your employer has to jump through hoops (although minor) to file paperwork with DHS and you can't engage just about any job - jobs with security clearance (a lot of government, military and other contracts) or with extensive out-of-country travel is out of reach.
Depending on your jurisdiction and most HR departments will agree, don't ever say anything about anyone's work status. Could land you or your company in hot water if they say the wrong thing especially if they are your supervisor or higher ups. So they "screwed you over"? They get hit by a bus screws you over? That's a bad business model you got there.
Democrats do lean towards supporting tech companies. Not sure if you've seen the ACTUAL Dem platform - more H1B, attaching green cards to foreign students' diplomas, fewer taxes on the tech industry. The only people the Dems want paying taxes is the Republicans, not big companies but the middle and lower middle class that pays 95% of the taxes in this country.
Security has always been a factor in Unix, the freaking thing came out of an era where everybody shared the same resource (the CPU), was connected through terminals and networks and shouldn't be able to see into each other's business. Windows is the only OS still existent that was only geared towards the workstation or the single computer and thus didn't require permission levels, not even locally.
Many manufacturers use the same frame which includes electronics support for pretty much all their car models. That way you only make one base model, just put a different chassis over it. Additionally, electronics are much cheaper and easier to repair that running wiring everywhere. I once replaced the wiring in a 1940's VW (you know, the original beetle) - there is a bundle of wires about 2 inches thick going through the chassis for that simple of a car (nothing electronic, just lights, ignition etc). Imagine all our current bells and whistles (electronic brakes, 3rd brake lights, interior lights, door sensors, powered seats, heated mirrors etc) done by relays and straight up wiring.
unplugging never works. Security through obscurity is a bad plan especially when in the future your techs do need/want remote access.
There are plenty of Intel 32 bits systems being sold for embedded devices in factories etc. Intel is still developing 32-bit compatible processors (Quark)
That is what I meant, RF radiation. I work in MRI, no vendor I've seen uses anything standard except for open source software. Siemens doesn't even include a lot of tags so orientation after stripping requires physical markers.
That is because MRI data (at least in the US) is protected by HIPAA. You can reconstruct enough identifiable features from raw data plus you have to record quite a number of other features (age, weight etc. for radiation calculations) that almost all MRI data falls under HIPAA when it comes to redistributing the raw data. If you strip all that out (skull stripping, DICOM anonymize), it's no longer raw data AND it becomes very hard to distinguish things like image orientation.
Boss next year? Lol, she already is the boss. The "party" controls Obama and Hillary and Bush and Clinton, even Trump and whoever else, you won't get to power if you don't allow yourself to be controlled.
There are subsets of C and Java (C++, ObjC, Kotlin, Scala) that are older than 8 years and also 'largely semantics and tools that facilitate code conversion' yet we still have plenty of code being written in plain old C or Java.
A programming language is primarily semantics, changing the semantics implicates that it is a different language regardless of the similarity, if it were the same language, things would largely still work (perhaps with deprecation warnings).
Because Python 3 doesn't work (at least not with existing code). Python 3 is for all intents and purposes an entirely different language and why would any dev dump an existing/working codebase, experience and paradigms just because someone didn't think all that well about what a programming language needs in the past?
Everything fails, but most solid state parts have a MTBF of 100+ years. The compound and your anecdotal failure rate may be slightly higher, but given the staggering number of computing devices being sold every year and the fact that repair shops are almost non-existent and never were that good of a business model (I've worked for quite a bit of them), I would say that the majority of computing devices never failed.
Even spinning hard drives only have a 1% failure rate over their life spans. Most of the electronics purchased never fail, I still got working 10Mbps routers and even a Sun UltraSPARC II (circa 1999) for production use with working 30GB SCSI disks.
In most art, whether it is painting, music, wine; once you take away the show or the name, they cannot be objectively distinguished. For most other jobs, what matters is your technical skills. In Western culture women are babied and grow up thinking they 'can do anything' without much effort, the male will do their bidding to make it easy for them. They get promoted, especially in the tech field, through schools, jobs etc simply based on their gender, and that is not a recent diversity thing, for as long as I've been in the job market that has been the case, that was the case during the dotcom boom when I started working.
The Internet does not have/supply emergency services unless you have something like that in your agreement. Additionally, this is not about the ISP throttling your line if it doesn't have capacity, this is about your ISP throttling certain aspects of your line regardless of it's capacity. This would be similar to your phone line company only giving a dial tone to companies that have paid them and inserting artificial line drops when you contact companies that haven't.
QoS is not really an aspect of any (common) carrier, only the originator of a packet specifies QoS . You can thus set QoS bits as a customer (or end-point) and your (and other) ISPs may or may not follow it (depends largely on your agreement, business lines are more prone to listening to QoS bits but once outside the 'agreed upon' network, QoS pretty much gets ignored).
Net Neutrality is about your ISP not interfering with your QoS settings or otherwise not forcing QoS on your packets without your agreement. They should, unless you specify otherwise, treat all traffic as it did not have any QoS bits set.
BitTorrent is recognizable either through port selection of the client (688x and 6969) or because it opens a LOT of simultaneous connections or because not all trackers/clients are fully encrypted (I think most clients still default to opportunistic encryption, not strict requirement).
VPNs are recognizable as well by the same method (well-known ports, well-known sites or well-known unencrypted control/setup traffic).
They could also just throw "anything encrypted" into that class, the law allows them to do that as long as they give the excuse.
I don't know of any filter that blocks out the entire infrared spectrum (which does include a portion of nearly visible light - you can see a dim flicker in some remote controls in the dark). Most filters reduce it greatly but still allow some to pass through. You can test this by pointing an IR emitter at a CCD sensor and then placing the filter in front - reduced but still visible.
My dealership oil change is $250, is done yearly but includes a full multi-point inspection, a state inspection and minor repairs (filters, gaskets, light bulbs etc), not just an oil change. It's also paid for by the manufacturer for 5y.
Either way, the oil light can be manually turned off/reset in all cars. The other lights by OBD readers and sometimes a sequence of steering wheel or ignition key movements.
Sadly, these days, most people graduate with engineering degrees without knowing how to actually program. I work with grad students and student interns all the time, it's a very poor, sad situation in Collegeville. Only a few decades ago, when I graduated, we at least knew how to program a Z80 and a good portion of TurboPascal (and in some situations even C/C++). Engineering students I interact with see exactly 1 week per programming language (Verilog, C, MATLAB, Java...) and that is supposed to teach them how to code by simply making the program slightly more complicated each time they see another language, but they never expand on how to actually program beyond the "make text appear on the screen" and the most difficult thing they end up seeing is a few nested loops or recursive function calls.
Slashdot Mirror
So all those police that killed people on sight should just expect to get killed? That's basically what happened here, yet the police are now victims?
Not really. It just shows that most police departments are lazy and rather revenge kill than protect. We've had standoffs last weeks when it involves private militia. The shooter was driven back into a hole and had no way out nor any hostages nor a viable target. He will run out of stamina, food, bullets eventually, but he already killed a cop so he must die that hour.
Bernie lost and Obama isn't all that left leaning imho.
As a green card owner, the first several years (as long as you have the accent) your wages will be depressed, your employer has to jump through hoops (although minor) to file paperwork with DHS and you can't engage just about any job - jobs with security clearance (a lot of government, military and other contracts) or with extensive out-of-country travel is out of reach.
Depending on your jurisdiction and most HR departments will agree, don't ever say anything about anyone's work status. Could land you or your company in hot water if they say the wrong thing especially if they are your supervisor or higher ups. So they "screwed you over"? They get hit by a bus screws you over? That's a bad business model you got there.
Democrats do lean towards supporting tech companies. Not sure if you've seen the ACTUAL Dem platform - more H1B, attaching green cards to foreign students' diplomas, fewer taxes on the tech industry. The only people the Dems want paying taxes is the Republicans, not big companies but the middle and lower middle class that pays 95% of the taxes in this country.
Security has always been a factor in Unix, the freaking thing came out of an era where everybody shared the same resource (the CPU), was connected through terminals and networks and shouldn't be able to see into each other's business. Windows is the only OS still existent that was only geared towards the workstation or the single computer and thus didn't require permission levels, not even locally.
Many manufacturers use the same frame which includes electronics support for pretty much all their car models. That way you only make one base model, just put a different chassis over it. Additionally, electronics are much cheaper and easier to repair that running wiring everywhere. I once replaced the wiring in a 1940's VW (you know, the original beetle) - there is a bundle of wires about 2 inches thick going through the chassis for that simple of a car (nothing electronic, just lights, ignition etc). Imagine all our current bells and whistles (electronic brakes, 3rd brake lights, interior lights, door sensors, powered seats, heated mirrors etc) done by relays and straight up wiring.
unplugging never works. Security through obscurity is a bad plan especially when in the future your techs do need/want remote access.
There are plenty of Intel 32 bits systems being sold for embedded devices in factories etc. Intel is still developing 32-bit compatible processors (Quark)
That is what I meant, RF radiation. I work in MRI, no vendor I've seen uses anything standard except for open source software. Siemens doesn't even include a lot of tags so orientation after stripping requires physical markers.
That is because MRI data (at least in the US) is protected by HIPAA. You can reconstruct enough identifiable features from raw data plus you have to record quite a number of other features (age, weight etc. for radiation calculations) that almost all MRI data falls under HIPAA when it comes to redistributing the raw data. If you strip all that out (skull stripping, DICOM anonymize), it's no longer raw data AND it becomes very hard to distinguish things like image orientation.
Boss next year? Lol, she already is the boss. The "party" controls Obama and Hillary and Bush and Clinton, even Trump and whoever else, you won't get to power if you don't allow yourself to be controlled.
The law is there to control the poor, not the other way around.
There are subsets of C and Java (C++, ObjC, Kotlin, Scala) that are older than 8 years and also 'largely semantics and tools that facilitate code conversion' yet we still have plenty of code being written in plain old C or Java.
A programming language is primarily semantics, changing the semantics implicates that it is a different language regardless of the similarity, if it were the same language, things would largely still work (perhaps with deprecation warnings).
Frontier nor AT&T paid for those poles. Several layers of governments paid for those a really long time ago.
Because Python 3 doesn't work (at least not with existing code). Python 3 is for all intents and purposes an entirely different language and why would any dev dump an existing/working codebase, experience and paradigms just because someone didn't think all that well about what a programming language needs in the past?
Everything fails, but most solid state parts have a MTBF of 100+ years. The compound and your anecdotal failure rate may be slightly higher, but given the staggering number of computing devices being sold every year and the fact that repair shops are almost non-existent and never were that good of a business model (I've worked for quite a bit of them), I would say that the majority of computing devices never failed.
Even spinning hard drives only have a 1% failure rate over their life spans. Most of the electronics purchased never fail, I still got working 10Mbps routers and even a Sun UltraSPARC II (circa 1999) for production use with working 30GB SCSI disks.
Any computer without moving parts shouldn't wear out. Hell, most PC's with some moving parts don't fail for the first 20 years or so.
In most art, whether it is painting, music, wine; once you take away the show or the name, they cannot be objectively distinguished. For most other jobs, what matters is your technical skills. In Western culture women are babied and grow up thinking they 'can do anything' without much effort, the male will do their bidding to make it easy for them. They get promoted, especially in the tech field, through schools, jobs etc simply based on their gender, and that is not a recent diversity thing, for as long as I've been in the job market that has been the case, that was the case during the dotcom boom when I started working.
The Internet does not have/supply emergency services unless you have something like that in your agreement. Additionally, this is not about the ISP throttling your line if it doesn't have capacity, this is about your ISP throttling certain aspects of your line regardless of it's capacity. This would be similar to your phone line company only giving a dial tone to companies that have paid them and inserting artificial line drops when you contact companies that haven't.
QoS is not really an aspect of any (common) carrier, only the originator of a packet specifies QoS . You can thus set QoS bits as a customer (or end-point) and your (and other) ISPs may or may not follow it (depends largely on your agreement, business lines are more prone to listening to QoS bits but once outside the 'agreed upon' network, QoS pretty much gets ignored).
Net Neutrality is about your ISP not interfering with your QoS settings or otherwise not forcing QoS on your packets without your agreement. They should, unless you specify otherwise, treat all traffic as it did not have any QoS bits set.
BitTorrent is recognizable either through port selection of the client (688x and 6969) or because it opens a LOT of simultaneous connections or because not all trackers/clients are fully encrypted (I think most clients still default to opportunistic encryption, not strict requirement).
VPNs are recognizable as well by the same method (well-known ports, well-known sites or well-known unencrypted control/setup traffic).
They could also just throw "anything encrypted" into that class, the law allows them to do that as long as they give the excuse.
I don't know of any filter that blocks out the entire infrared spectrum (which does include a portion of nearly visible light - you can see a dim flicker in some remote controls in the dark). Most filters reduce it greatly but still allow some to pass through. You can test this by pointing an IR emitter at a CCD sensor and then placing the filter in front - reduced but still visible.
My dealership oil change is $250, is done yearly but includes a full multi-point inspection, a state inspection and minor repairs (filters, gaskets, light bulbs etc), not just an oil change. It's also paid for by the manufacturer for 5y.
Either way, the oil light can be manually turned off/reset in all cars. The other lights by OBD readers and sometimes a sequence of steering wheel or ignition key movements.
Sadly, these days, most people graduate with engineering degrees without knowing how to actually program. I work with grad students and student interns all the time, it's a very poor, sad situation in Collegeville. Only a few decades ago, when I graduated, we at least knew how to program a Z80 and a good portion of TurboPascal (and in some situations even C/C++). Engineering students I interact with see exactly 1 week per programming language (Verilog, C, MATLAB, Java...) and that is supposed to teach them how to code by simply making the program slightly more complicated each time they see another language, but they never expand on how to actually program beyond the "make text appear on the screen" and the most difficult thing they end up seeing is a few nested loops or recursive function calls.