C does not have a boolean type. Instead it tests for truthiness by checking whether the value is zero (false) or non-zero (true). That bit of code might not make sense, but it will compile.
The first few x86 processor models came as follows:
8086: 16-bit registers, 16-bit data bus, 20-bit address bus
8088: cost-reduced version of the 8086 with 8-bit data bus
80186: new architecture, aimed at embedded applications, contains a lot of glue logic that required separate hardware on 8086 systems, same register/data/address sizes
80188: same as above but with 8-bit data bus
80286: new architecture, 24-bit address bus, protected mode
"I won't get into any pros or cons of that aspect, but just mention it to explain the significance of the quad channel DDR4. The way AMD has designed these smaller "packages" to work together as one CPU is, to put it very simply, to have them communicate through the DDR4 bus."
Wait... no, that's not right. The cores talk to each other via Infinity Fabric. To talk to cores on a separate module or to access memory managed by a different memory controller (Threadripper has two, Epyc has four), Infinity Fabric uses PCIe inside the package. Epyc dedicated 64 lanes for this purpose, so I assume that Threadripper uses 32 lanes. The memory buses never come into it.
"However what really disturb me from a comparison stand-point is that they gave the i7 5960X 2133 MHz DDR4 vs 2933 MHz DDR4 for the Ryzen 7 1800X, that give the 1800X another opportunity to shine since infinity fabric run at the same clock as RAM but why wasn't the 5960X also given the same speed RAM? It can't run it?"
Per Intel's ARK, the i7 5960X supports up to 2133 MHz DDR4. It has four memory channels, though, giving it more memory bandwidth on paper. The 1800X still makes do with only two memory channels, so the fact that it matches the i7 in speed is quite impressive.
Given that many DSLRs nowadays feature Wi-Fi tethering, it should be possible to have a mobile phone download the images off the camera immediately after exposure and delete them from there after uploading them to ${CLOUD}. There's still the issue that such tethering usually is done unencrypted, though, so they'd need to add TLS and preferably a way for the user to install/change/generate the keys/certs and use client cert authentication.
The first Athlon CPU models from AMD used the EV6 bus from DEC (albeit on a slot connector like the Pentium 2/3), and plans floated around to build motherboards compatible with both Athlon and DEC Alpha 21264 CPUs only requiring a firmware swap (and an adapter card for the 21264).
I also hazily recall some computer vendor that came out around the time of the original BeBox that sold a computer claimed to have a modular motherboard, with expansion slots, memory, CPU bus, etc. on separate modules, but the name escapes me.
It can't be that much different from emulating the games in some other language or platform. You'd have to emulate the CPU and chipset, collect input from the user (keyboard and mouse at least, and holy shit joysticks too!), and output the graphics (HTML5 Canvas) and sound (HTML5 audio) to the browser. Given that the MC68000 family of processors and the Amiga chipset have been emulated many times before already, plenty of inspiration exists to get you started.
I don't see Philadelphia in the list of future or even potential cities for expansion. Shit, not even a single city within a six-hour drive. Nothing in the Northeast. The closest seems to be Raleigh-Durham. At this rate, it just looks like yet another half-assed Google project ready to go on the chopping block.
It depended on smart compilers that just did not work. It's one advantage was a large memory space and AMD took that away. It was one of two big fumbles that Intel made at the time, the other was Netburst.
Intel had already ventured into the depend-on-smart-compilers rabbit hole before IA64 and Netburst with the 432, a ridiculous 32-bit stack-based object-oriented processor released before the 80386. The 432 failed, in part, because none of the compilers available for it could optimize code sufficiently well to work around its many crippling features (16-bit ALU, 16-bit data buses, 16-bit segment offsets, slow clock speeds) and it ended up slower than the 8086.
Of course if Motorla had an inexpensive 68000 available and IBM had used it in the PC we would all have been much better off.
Indeed.
The same is true if Apple, Atari, and Commodore had use the 6809 but the 6502 was also cheaper.
Not quite. Yes, it was cheaper, but the 6502 was by all accounts just as good as the 6809. Nevertheless, Apple, Atari, and Commodore all ended up migrating to the 68000 family in the end with the Lisa/Macintosh*, ST/TT/Falcon, and Amiga.
If water enters the exhaust and the engine is running, this is usually not a big deal because the air pressure from the engine will push it back out. Also, the exhaust valves don't suck in air so it will take some serious water pressure to get past those.
One only has to look at the wet exhaust systems used in boats for an example of what happens when water enters the exhaust. Hell, they even introduce water in them deliberately.
This 1 TB/day threshold rang a bell as I remembered a BSD trumpeting a similar record, albeit in the opposite direction, in the late 1990s... and sure enough, Slashdot covered it back then:
Back then people had serious discussions about what sort of storage controller, network interface, and upstream connectivity was needed to achieve this result. Nowadays we can stuff that same performance in a trouser pocket. What an age to live in.
Just a short list of ideas off the top of my head:
* UTF-8. I used to get around it by using HTML entities, but nobody ain't got time for that now, and it's been a source of complaints for over a decade.
* Click-bait headlines have no place in a site dedicated to serious technical subjects (or that at least takes technical subjects more or less seriously).
* CmdrTaco, Hemos, and the rest of the original crew used to occasionally become involved in the discussions and rarely felt the need to withhold their opinions (iPod, anyone?), which gave the site a more personal feel -- a hybrid between a blog and a news site. This still can be seen in sites like some of the sites run by Gawker Media, and it seems effective in maintaining the readers involved.
* If there will be editors, they ought to edit.
I'm afraid you got it backwards. The Bulldozer architecture has a single FPU for each two-core module, so an eight-core processor has eight instruction pipelines and integer units but only four FPUs.
True, Nokia was in trouble well before the WinPho fiasco, but Symbian was just a sympton rather than the disease. Management had allowed the company to branch off into different product lines and encouraged competition between them with apparently little fiscal oversight and paying no attention to the third-party developer community. So, they had S40 engineers working on almost-smartphone handsets to challenge low-end S60/Symbian handsets, S60 engineers trying to widen their product range, and Maemo/MeeGo engineers trying and failing to prove that their otherwise unwanted bastard child was a much better platform. While the managers had their heads firmly esconced in their rectums, Elop took advantage of their indecision and gave them a false sense of hope.
Or, maybe not. There's a theory out there that Nokia management knew that they had a shit sandwich on their hands before Elop came along, and sought a way to wipe the slate clean without taking the blame directly if things went wrong. Microsoft and Elop appeared at the right time with an offer that they would happily not refuse: take a large amount of money in exchange for them taking out the trash for you, money that you'll be able to use to restart your phone business from the ground up in a relatively short time frame.
greenend.co.uk is the official domain for PuTTY (specifically, www.chiark.greenend.co.uk). Simon Tatham has hosted it there from the start. I'd be more suspicious of putty.org, honestly.
Because they do have a tendency to improve. Jerry Pournelle used to write regularly about his problems with ATI cards in his column on BYTE. They typically followed the same pattern: install new card; install drivers; see computer crash regularly; upgrade drivers; see computer crash less often; upgrade drivers again; see computer run more or less stably.
Then he'd upgrade to the next shiny ATI card and do it all over again, since the new drivers bore little resemblance to the old ones.
Slashdot Mirror
Congratulations you invented LOGO!
Or, they could've dug through their own software catalogue:
https://en.wikipedia.org/wiki/HyperCard
C does not have a boolean type. Instead it tests for truthiness by checking whether the value is zero (false) or non-zero (true). That bit of code might not make sense, but it will compile.
The first few x86 processor models came as follows: 8086: 16-bit registers, 16-bit data bus, 20-bit address bus 8088: cost-reduced version of the 8086 with 8-bit data bus 80186: new architecture, aimed at embedded applications, contains a lot of glue logic that required separate hardware on 8086 systems, same register/data/address sizes 80188: same as above but with 8-bit data bus 80286: new architecture, 24-bit address bus, protected mode
No way an OBDS has a four-digit ID. I'll have you know that I have a two-story residence, thankyouverymuch.
"I won't get into any pros or cons of that aspect, but just mention it to explain the significance of the quad channel DDR4. The way AMD has designed these smaller "packages" to work together as one CPU is, to put it very simply, to have them communicate through the DDR4 bus." Wait... no, that's not right. The cores talk to each other via Infinity Fabric. To talk to cores on a separate module or to access memory managed by a different memory controller (Threadripper has two, Epyc has four), Infinity Fabric uses PCIe inside the package. Epyc dedicated 64 lanes for this purpose, so I assume that Threadripper uses 32 lanes. The memory buses never come into it.
"However what really disturb me from a comparison stand-point is that they gave the i7 5960X 2133 MHz DDR4 vs 2933 MHz DDR4 for the Ryzen 7 1800X, that give the 1800X another opportunity to shine since infinity fabric run at the same clock as RAM but why wasn't the 5960X also given the same speed RAM? It can't run it?"
Per Intel's ARK, the i7 5960X supports up to 2133 MHz DDR4. It has four memory channels, though, giving it more memory bandwidth on paper. The 1800X still makes do with only two memory channels, so the fact that it matches the i7 in speed is quite impressive.
Given that many DSLRs nowadays feature Wi-Fi tethering, it should be possible to have a mobile phone download the images off the camera immediately after exposure and delete them from there after uploading them to ${CLOUD}. There's still the issue that such tethering usually is done unencrypted, though, so they'd need to add TLS and preferably a way for the user to install/change/generate the keys/certs and use client cert authentication.
Of course, this change makes using vi damn near impossible. This is all part of the Eric Conspiracy to force us to use Emacs.
The first Athlon CPU models from AMD used the EV6 bus from DEC (albeit on a slot connector like the Pentium 2/3), and plans floated around to build motherboards compatible with both Athlon and DEC Alpha 21264 CPUs only requiring a firmware swap (and an adapter card for the 21264).
I also hazily recall some computer vendor that came out around the time of the original BeBox that sold a computer claimed to have a modular motherboard, with expansion slots, memory, CPU bus, etc. on separate modules, but the name escapes me.
Thanks! Very cool. It does say "heavily based on WinUAE" right there on the front page.
It can't be that much different from emulating the games in some other language or platform. You'd have to emulate the CPU and chipset, collect input from the user (keyboard and mouse at least, and holy shit joysticks too!), and output the graphics (HTML5 Canvas) and sound (HTML5 audio) to the browser. Given that the MC68000 family of processors and the Amiga chipset have been emulated many times before already, plenty of inspiration exists to get you started.
I don't see Philadelphia in the list of future or even potential cities for expansion. Shit, not even a single city within a six-hour drive. Nothing in the Northeast. The closest seems to be Raleigh-Durham. At this rate, it just looks like yet another half-assed Google project ready to go on the chopping block.
Intel had already ventured into the depend-on-smart-compilers rabbit hole before IA64 and Netburst with the 432, a ridiculous 32-bit stack-based object-oriented processor released before the 80386. The 432 failed, in part, because none of the compilers available for it could optimize code sufficiently well to work around its many crippling features (16-bit ALU, 16-bit data buses, 16-bit segment offsets, slow clock speeds) and it ended up slower than the 8086.
Indeed.
Not quite. Yes, it was cheaper, but the 6502 was by all accounts just as good as the 6809. Nevertheless, Apple, Atari, and Commodore all ended up migrating to the 68000 family in the end with the Lisa/Macintosh*, ST/TT/Falcon, and Amiga.
* the II GS was a dead-end
If water enters the exhaust and the engine is running, this is usually not a big deal because the air pressure from the engine will push it back out. Also, the exhaust valves don't suck in air so it will take some serious water pressure to get past those.
One only has to look at the wet exhaust systems used in boats for an example of what happens when water enters the exhaust. Hell, they even introduce water in them deliberately.
jwz said it best: "Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can."
rd Ãoe\\.\%appdata%\com4.{241D7C96-F8BF-4F85-B01F-E2B043341A4B}Ã /S
Either add support for UTF-8 to Slash or edit your copypasta to remove broken quotes. Don't just throw your hands in the air.
This 1 TB/day threshold rang a bell as I remembered a BSD trumpeting a similar record, albeit in the opposite direction, in the late 1990s... and sure enough, Slashdot covered it back then:
Wcarchive Does 1.39tb In 24 Hours
Back then people had serious discussions about what sort of storage controller, network interface, and upstream connectivity was needed to achieve this result. Nowadays we can stuff that same performance in a trouser pocket. What an age to live in.
Just a short list of ideas off the top of my head: * UTF-8. I used to get around it by using HTML entities, but nobody ain't got time for that now, and it's been a source of complaints for over a decade. * Click-bait headlines have no place in a site dedicated to serious technical subjects (or that at least takes technical subjects more or less seriously). * CmdrTaco, Hemos, and the rest of the original crew used to occasionally become involved in the discussions and rarely felt the need to withhold their opinions (iPod, anyone?), which gave the site a more personal feel -- a hybrid between a blog and a news site. This still can be seen in sites like some of the sites run by Gawker Media, and it seems effective in maintaining the readers involved. * If there will be editors, they ought to edit.
I'm afraid you got it backwards. The Bulldozer architecture has a single FPU for each two-core module, so an eight-core processor has eight instruction pipelines and integer units but only four FPUs.
And now we know what to expect from the new overlords.
Given that the ARM core in AMD APUs conform to ARM TrustZone, which seems better documented than IME, I'd assume that yes, AMD documents it.
True, Nokia was in trouble well before the WinPho fiasco, but Symbian was just a sympton rather than the disease. Management had allowed the company to branch off into different product lines and encouraged competition between them with apparently little fiscal oversight and paying no attention to the third-party developer community. So, they had S40 engineers working on almost-smartphone handsets to challenge low-end S60/Symbian handsets, S60 engineers trying to widen their product range, and Maemo/MeeGo engineers trying and failing to prove that their otherwise unwanted bastard child was a much better platform. While the managers had their heads firmly esconced in their rectums, Elop took advantage of their indecision and gave them a false sense of hope. Or, maybe not. There's a theory out there that Nokia management knew that they had a shit sandwich on their hands before Elop came along, and sought a way to wipe the slate clean without taking the blame directly if things went wrong. Microsoft and Elop appeared at the right time with an offer that they would happily not refuse: take a large amount of money in exchange for them taking out the trash for you, money that you'll be able to use to restart your phone business from the ground up in a relatively short time frame.
greenend.co.uk is the official domain for PuTTY (specifically, www.chiark.greenend.co.uk). Simon Tatham has hosted it there from the start. I'd be more suspicious of putty.org, honestly.
"We use a custom-made encryption algorithm with organic S-boxes and artisanal feistels. You probably have never heard of it."
Because they do have a tendency to improve. Jerry Pournelle used to write regularly about his problems with ATI cards in his column on BYTE. They typically followed the same pattern: install new card; install drivers; see computer crash regularly; upgrade drivers; see computer crash less often; upgrade drivers again; see computer run more or less stably.
Then he'd upgrade to the next shiny ATI card and do it all over again, since the new drivers bore little resemblance to the old ones.