What the heck happened to that notation? I typed this:...you don't call a GIF a "{g}if" because "the "G" stands for "graphics." It's pronounced "Jiff," like the peanut butter more moms prefer.
Could be. I am a Centaur/VIA/WinChip enthusiast. Today I still run a VIA Esther, which is also known as the VIA C7. It is essentially an enhanced C3 and it would be interesting to see what's going on there. They're still a RISC core emulating x86 and I would guess that this exploit is probably still present.
These Centaur-derived VIA processors continue to be produced by VIA. When VIA bought Centaur and Cyrix, they ditched Cyrix and continued to evolve the Centaur platform. Some of the personnel from both companies stayed at VIA to work on the Centaur platform. VIA went on to sell the Cyrix IP to AMD who continues the Cyrix platform. The code names of the chips get blurred here when VIA worked on a couple of Cyrix chips that had Jewish code names which are assigned to Centaur chips.
Fun things to know and tell: Cyrix was a reverse-engineered CISC re-implementation of the Intel architecture, starting with math coprocessors and moving on to CPUs. In contrast, VIA/Centaur was an emulation of the Intel architecture actually running on a RISC core.
In most places where I have worked in 1099 contractor roles, the customer cannot tell you when to show up to work. They just pay you for hours worked.
However, if you are W2 and work for a B2B firm as a contractor to the prime, your hours are dictated by the B2B firm. If you are 1099 and work for a B2B your hours cannot be dictated.
Working as a W2 is very expensive for the employer. I doubt that option would be a good choice for a prime who is offering gigs on a freelance site since rates would be much higher. They might as well get their own 1099 from a B2B firm.
I'm not sure how this counts as news. Freelance sites have been doing this for years. It's at the option of the people offering the gig. The most common was just a webcam that took your picture every minute or so.
I agree. HFT is so unfair and I was surprised that none of the trading platforms have taken steps to ban the practice and return to one-second resolution.
I guess that the trading platforms are only allowing subsecond HFT because they offer their customers to co-locate in hyper-local data rooms very close by main trading platform, also owned by the trading platform, at massively high prices.
Obvious cash-grab is obvious. I wonder what kind of regulations will come about in the future to deal with this.
Only liquid water impedes microwaves. Vapor doesn't, nor does ice and snow. Even then, liquid water only marginally affects frequencies above 2 GHz. It's a big problem above 11 GHz in the Ku- and Ka-bands as satellite TV and satellite internet users are well aware.
Terrestrial point-to-point microwave is a little above 3 GHz, which has been demonstrated to be unaffected at all by liquid water, and completely unaffected by humidity. The problem is that this article doesn't even bother to mention the frequency used.
Humidity doesn't affect anything. The problem, from my humble perspective, would be processor throttling due to high heat at the receiving site. More so, the BER, or Bit Error Rate, is not even mentioned in the article even though it's the chief factor used to judge how a digital link functions.
We solved the human-computer interface by the 1990s.
The problem is that everyone insists that the old ideas are bad and only new ideas are good.
All of this bending over backwards to get JavaScript and the single-threaded DOM become "single screen applications" ignores that we already had all this almost thirty years ago.
As mentioned by others, it's not finalized and tested enough for the new ATSC 3 standard.
Also, remember that ATSC is the same organization that famously rejected the superior COFDM modulation when designing ATSC 1. ATSC has only now conceded that COFDM was the right choice all along.
That poor decision to use 8VSB instead of COFDM is why ATSC 1 suffers from multipath and it's also why multiple transmitters can't share frequencies. Sharing frequencies is something that the competing DVB-T standard has always done on its COFDM platform. As an aside, both Sirius and XM Satellite Radio have thousands of terrestrial repeaters that share the identical frequency nationwide because they use COFDM.
ATSC 1 is also why you can't view HDTV in a moving vehicle because of the Doppler Effect. A half-assed ATSC-M/H specification was hastily approved that almost nobody ended up using because mobile data ended up being the de-facto choice for mobile video consumers.
Slashdot Mirror
What the heck happened to that notation? I typed this: ...you don't call a GIF a "{g}if" because "the "G" stands for "graphics." It's pronounced "Jiff," like the peanut butter more moms prefer.
You don't call a JPEG a "Jay-/f/eg" because the "P" stands for "Photographic."
Just like you don't call a GIF a "âYgâY©if" because "the "G" stands for "graphics." It's pronounced "Jiff," like the peanut butter more moms prefer.
Could be. I am a Centaur/VIA/WinChip enthusiast. Today I still run a VIA Esther, which is also known as the VIA C7. It is essentially an enhanced C3 and it would be interesting to see what's going on there. They're still a RISC core emulating x86 and I would guess that this exploit is probably still present.
These Centaur-derived VIA processors continue to be produced by VIA. When VIA bought Centaur and Cyrix, they ditched Cyrix and continued to evolve the Centaur platform. Some of the personnel from both companies stayed at VIA to work on the Centaur platform. VIA went on to sell the Cyrix IP to AMD who continues the Cyrix platform. The code names of the chips get blurred here when VIA worked on a couple of Cyrix chips that had Jewish code names which are assigned to Centaur chips.
Fun things to know and tell: Cyrix was a reverse-engineered CISC re-implementation of the Intel architecture, starting with math coprocessors and moving on to CPUs. In contrast, VIA/Centaur was an emulation of the Intel architecture actually running on a RISC core.
History says both approaches were right.
We decommission and dispose of nuclear submarines all the time.
We'll figure it out.
It's tradition, like how we call the Acela "High-Speed Rail"
In most places where I have worked in 1099 contractor roles, the customer cannot tell you when to show up to work. They just pay you for hours worked.
However, if you are W2 and work for a B2B firm as a contractor to the prime, your hours are dictated by the B2B firm. If you are 1099 and work for a B2B your hours cannot be dictated.
Working as a W2 is very expensive for the employer. I doubt that option would be a good choice for a prime who is offering gigs on a freelance site since rates would be much higher. They might as well get their own 1099 from a B2B firm.
I'm not sure how this counts as news. Freelance sites have been doing this for years. It's at the option of the people offering the gig. The most common was just a webcam that took your picture every minute or so.
It's been like this for at least ten years.
> I'm just an amature[sic] (figuratively, given the topic of discussion!)
Even so, humidity, liquid water, and frozen water has no effect at those low frequencies. My point stands.
I agree. HFT is so unfair and I was surprised that none of the trading platforms have taken steps to ban the practice and return to one-second resolution.
I guess that the trading platforms are only allowing subsecond HFT because they offer their customers to co-locate in hyper-local data rooms very close by main trading platform, also owned by the trading platform, at massively high prices.
Obvious cash-grab is obvious. I wonder what kind of regulations will come about in the future to deal with this.
Only liquid water impedes microwaves. Vapor doesn't, nor does ice and snow. Even then, liquid water only marginally affects frequencies above 2 GHz. It's a big problem above 11 GHz in the Ku- and Ka-bands as satellite TV and satellite internet users are well aware.
Terrestrial point-to-point microwave is a little above 3 GHz, which has been demonstrated to be unaffected at all by liquid water, and completely unaffected by humidity. The problem is that this article doesn't even bother to mention the frequency used.
Humidity doesn't affect anything. The problem, from my humble perspective, would be processor throttling due to high heat at the receiving site. More so, the BER, or Bit Error Rate, is not even mentioned in the article even though it's the chief factor used to judge how a digital link functions.
We solved the human-computer interface by the 1990s.
The problem is that everyone insists that the old ideas are bad and only new ideas are good.
All of this bending over backwards to get JavaScript and the single-threaded DOM become "single screen applications" ignores that we already had all this almost thirty years ago.
Explain to me how LXQt is not a lightweight distro. Go.
Why not SPARC?
I want to like ReactOS, but the desktop environment needs to be replaced with something modern and Aero-like.
Maybe Stardock will do the trick.
Ironic since the BSDs were the first free x86 UN*X distributions to support USB.
I'm going to say "just" four more times: just, just, just, just.
NetBSD just received USB 3.0 support just now?
I had to check that. FreeBSD has had it since 2011.
Surface has some flaws, but not this many. We enjoy a USB-A port and SD Card reader, but, inexplicably, no USB-C.
Come join us.
Don't we all now know that every non-domestic company in China is a joint venture with the state?
This is perplexing because the pay is so low and pilots have to pool their housing.
Kind suggestion for Slashdot editors: please mention how the organics were destroyed in the lede. You say they were destroyed but you don't say how.
As mentioned by others, it's not finalized and tested enough for the new ATSC 3 standard.
Also, remember that ATSC is the same organization that famously rejected the superior COFDM modulation when designing ATSC 1. ATSC has only now conceded that COFDM was the right choice all along.
That poor decision to use 8VSB instead of COFDM is why ATSC 1 suffers from multipath and it's also why multiple transmitters can't share frequencies. Sharing frequencies is something that the competing DVB-T standard has always done on its COFDM platform. As an aside, both Sirius and XM Satellite Radio have thousands of terrestrial repeaters that share the identical frequency nationwide because they use COFDM.
ATSC 1 is also why you can't view HDTV in a moving vehicle because of the Doppler Effect. A half-assed ATSC-M/H specification was hastily approved that almost nobody ended up using because mobile data ended up being the de-facto choice for mobile video consumers.
The my.yahoo.com feeds disappear and reappear all the time. It's especially annoying because they're controlled by Yahoo.
Kubrick's explanation wasn't necessary because the book had already presented the ending with a thorough treatment and a complete explanation.
It does not appear that the author of this article actually read the book.
Wiki entry:
http://uncyclopedia.wikia.com/...!