Sounds like this is locked into windows via the Media Foundation APIs
There may be lock in, but it's not exclusive to Microsoft:
Media Source Extensions (MSE)This specification extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.
Web Cryptography API (WebCrypto)This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption.
They're all W3C standards track specifications. The first two have editors from the same three corporations; Google, Microsoft and Netflix. Google, in particular, can't tolerate not being capable of playing Netflix (10% of the population of the US subscribes to this) on its platforms (Android and Chrome OS.) It already works on both and you can take it for granted that Google expects to achieve parity with these specifications.
The last specification is not specific to streaming; it's a general purpose Javascript API to perform common cryptographic operations.
the TSX compatibility timeline will take roughly that long
From the SiSoftware link you provided:
Hardware Lock Elision (HLE) is a legacy compatible instruction set extension, i.e. transparent to CPUs that do not support TSX. The very same code can execute on TSX-capable CPUs - and benefit - but also work on legacy CPUs without performance penalty.
Thus, HLE at least can be adopted immediately by operating systems, compilers and runtimes. That actually started over a year ago for GCC. Intel's compiler uses TSX as well. RTM requires a feature test for compatible use, but it can still be utilized, particularly in runtimes (JVM, CLR, v8, etc.)
So seven years is too pessimistic. Haswell users with recent compilers are already using TSX.
That is going to be an important feature when programmers eventually leverage it. Hardware assisted optimistic locking can make concurrency easier, safer and more efficient as the CPU takes care of coherency problems usually left to the programmer and CAS instructions. Imagine being able to give each of thousands or millions of actors in a simulation their own independent execution context (instruction pointer, stack, etc.,) all safely sharing state and interacting with each other using simple, bug free logic, as opposed to explicit and error prone locking and synchronization. This has been done with software transactional memory but it frequently fails to scale due to lock contention. Hardware based TM can prevent that contention by avoiding lock writes.
It is extremely cool that Intel is implementing this on x86.
That Bloomberg story is about the reactor pressure vessel or RPV, the part the contains the reactor core. These authors write poorly and got it wrong calling it the "containment vessel."
This Slashdot story is about the AP-1000 containment vessel, not the RPV. The vessel is 36 meters wide and 65 meters tall. Nothing on Earth can make a single piece of forged steel that large.
Reactor pressure vessels, which contain the nuclear fuel in nuclear power plants, are made of thick steel plates that are welded together.
RPVs for other common reactor designs such as CANDU or VVER are welded assemblies. Often forged steel steel rings are stacked and welded. Some RPVs use large forged plates and are axially welded.
Note that although the bottom of the AP-1000 RPV is a single piece it still has a separate head; the top of the RPV is gasketed and bolted to the vessel like every other PWR or BWR. It has to be to (re)fuel the reactor.
I do. I have been looking forward to Mint 15 for a while and so have a lot of others. I appreciate that it was posted on Slashdot and I hope others consider trying Mint as a result. Mint deserves the attention because Mint is an antidote to terrible Linux desktop environments.
The magic ju ju is the ARM business model. There is one trump card ARM holds that precludes Intel from many portable devices; chip makers can build custom SOCs in-house with whatever special circuits they want on the same die. Intel doesn't do that and they don't want to do it; it would mean licencing masks to other manufactures like ARM does. For example, the Apple A5, manufactured by Samsung, includes third party circuits like the Audience EarSmart noise-cancellation processor, among others. It is presently not feasible to imagine Intel handing over masks such that Apple could then contract with some foundry to manufacture custom x86 SOCs. This obviates Intel from many portable use cases.
That feature of the ARM business model might be very useful to large scale computing. One can imagine integrating a custom high-performance crossbar with an ARM core. Cores on separate dies could then communicate with the lowest possible latency. Using a general purpose ARM core to marshal data to and from high-performance SIMD circuits on the same die is another obvious possibility. A custom cryptography circuit might be hosted the same way.
Contemporary supercomputers are great aggregations of near-commodity components. However, supercomputing has a long history of custom circuit design and if the need arises for a highly specialized circuit then a designer may decide that integrating with ARM to do the less exotic leg work computing that is always necessary is a good choice.
One cause for the lack of demand of electrical engineers is that the hardware design and manufacturing is located to cheaper countries.
Can't be. Those are the jobs we're keeping here in the US because we all have $75k degrees. The low skill jerbs go to Asia and we keep all the high paying jobs because the Chinese are magically incapable of EE.
Shutting down White House tours is the same brand of statist petulance.
BTW, ordinarily around here the Blue Angles and their ilk are just jingoistic manifestations of the US Military Industrial Complex's hegemony over the victims of global capitalism, and stuff. We're supposed to believe you people suddenly give a damn about these airshow cowboys?
The comments look as though at some point Slashdot turned into a gathering of cantankerous change-haters.
There are a lot of malcontents around here. Not all of us, however.
There is plenty of room for a good systems programming language. No, we probably don't need another managed, exclusively garbage collected, JIT compiled, VM hosted, 'dynamic' application language. And we've certainly collected enough Javascript front-end languages recently. That's not the intent of Rust.
Prosperity. Economic growth. Energy is the ultimate raw material necessary for these things.
Don't assume everyone shares the premise that we need cheap, abundant and clean energy. You could live out your life inside a three mile radius of your yurt nursing a solar panel. Putting you there is an ideal to which many aspire.
To be clear, I am not among them. I've just shed any illusions about whom I'm dealing with. They've either got theirs or they don't want it (the former being the vastly larger group) and job #1 is stopping you.
Investigating, arresting and prosecuting people for violating these kinds of laws is unbelievably difficult and expensive and rarely nets more than wrist-slaps. Cases take years, litigators cost millions and there is and endless supply of replacement spammers to replace the prosecuted. Governments executives and their staffs know this and have better things to do.
Finding the least statist solution is my preferred remedy in any case; make the practice economically infeasible by creating a generic regulatory mechanism (white/black lists based on working caller ID and enforced by the network operator, perhaps) and leave the cops/prosecutors/courts/prisons out of it.
The carriers are a part of this as well. They facilitate spammers by deliberately not making caller ID work end-to-end in all cases like it should, streamlining mass account provisioning, etc. They get revenue from calls, spam or otherwise. Even your legislators are part of it; they exempt themselves from robocall laws and email spam laws creating all sorts of loop holes and special exceptions in the system that carriers can and do use to deflect blame.
I keep readingabout $600 smart phones in stories on this T-Mobile no-contract scheme. You can have an amazing unlocked no-contract quad-core Nexus 4 for $299-349 here. It's HSPA+ which is all you'll get with T-Mobile in most markets anyhow.
If the best argument against this deal is that unlocked iPhones cost too much then sign me up. Data coverage is the real problem with T-Mobile... but perhaps they're really solving that now.
I am for freedom. Including the freedom to fire whatever at-will employed asshole I chose for whatever reason I care to indulge.
Stop conflating rights as a citizen with employment. You can stand on a corner and voice as many double entendres as you want. You can even earn a living doing that if you're any good. That doesn't mean I have to employ you.
It's not economically sensible to ship regular, lower-grade coal for producing electricity all around the world.
This is factually incorrect. Coal used for power generation is called `steam coal' and the recent growth of US coal exports is due to steam coal.
You may expect all of this to accelerate rapidly. As the story points out, met coal is going to China from the East coast the hard way; via the Atlantic, Cape of Good Hope, etc. Our pollution outsourcing and de-industrialization needs are so great that the Panama Canal is being expanded to accommodate much larger ships. Simultaneously we're waving environmental regs right and left to dredge up East coast bays for those ships.
This will all be up and running in 2015.
Once "Super-Post-Panamax" shipping can haul coal from the East Coast to China via the Pacific we'll see huge growth in coal exports and more de-industrialization. Coal going that way and finished goods coming back.
but then i read some of the comments below and realized you were spot on
I noticed this behavior a few years ago when the Apple+Foxconn stories started to appear. After hunting through the comments of a few of those stories I came up with a comprehensive list of rationalizations.
We are comfortable office people steeped in self-loathing. We can equivocate any evil by dismissing criticism as hypocrisy. The fact that in the case of Chinese industry these arguments happen to align with the desire for low cost products produced well outside "the environment" is purely coincidental...
The free market, when and to the extent it is allowed to exist is EXTREMELY far-sighted.
The summary is a troll. Attributing the 'free market' to nuclear power indicates either ignorance or deceit and we're left to ponder which is worse.
Nuclear reactors represent astonishing amounts of wealth and coordination. It is a hallmark of advanced nations that such things are created. For a reactor to exist in the US it must have the blessing of all levels of government. Financing is often backed by one or more government entities. Federal and state governments must actively regulate it. First responders at each level are prepared for emergencies. Rate payers are involved in voting on proposals prior to construction and regulating on-going rates. The timeline (in contemporary Western nations and certain Asian nations) is at least a decade for construction and licensing is a matter of fractions of a century. People are sourced from rarified cohorts such as military navel reactor operators.
In the end the actual operator is a small and even negligible part of the equation. Invoking the 'free market' mantra when dealing with the troubles of nuclear power is a cop out.
I file an individual HTS classification for each line item
The HTS is a fascinating bit of work. For people that don't know, the Harmonized Tariff Schedule is a US government published document that classifies just about every conceivable good and assigns tariffs, duties, etc. It is huge and is now only published in electronic form.
As the parent wrote, most finished goods in the HTS are 0% tariff. There are many things in the HTS with tariffs, but if it's a finished good it is usually exempt from any cost whatsoever. Some exceptions include small arms and autos; the UAW negotiated a 25% domestic value-add requirement in the '80s if foreign manufacturers wish to avoid tariffs. That one requirement is the sole reason that all auto manufacturing hasn't evacuated the US. Today there are dozens of foreign owned auto plants in the southern US writing paychecks to thousands of US workers because of that law.
No other nation is as import friendly as the US. Unless your nation has imams and muftis actively operating uranium isotope centrifuges in a bunker somewhere then you too can export to the US tariff free. You can wreck the environment to whatever degree you wish, abuse, neglect or contaminate however many people you want and it won't even slow down your goods as they get whisked into the US.
That's what domestic manufacturers and the US working class have to compete with for 80% of all finished goods in the US.
I think guns are a protected industry in the US. I'm pretty sure that we're not allowed to import foreign made guns for sale.
We import many, many foreign guns. There are limits, however. The US doesn't allow Norico (the largest small arms manufacturer on Earth, a Chinese company) to import. Also, foreign small arms must get through the ATF points system which limits what can be imported. Also, there are tariffs. Most other imported finished goods have no tariffs.
The result is that although there are large numbers of imported small arms, the limitations and extra costs to importers allow domestic manufacturing to be viable. Thus, we have companies like Ruger and Smith and Wesson; big, successful manufacturers that build most or all of their products in the US. There are also a plethora of small manufacturers.
Domestic small arms manufacturing is among the best evidence that applying some resistance to imports allows domestic manufacturing to thrive.
then logic would dictate that [progress bars are] pointless
It's not about logic. It's about comfort. During a phone call there is a noise most people don't typically notice. It's called sidetone (comfort noise, in some cases) and the effect of it is to convey a feeling that the connection is 'working.' When that noise is absent the operator perceives that the connection is 'dead.' The phone doesn't sound 'live' somehow.
Logic would dictate that such subtleties are unnecessary. That pesky old Real World thinks otherwise, however, and expends extraordinary effort to perpetuate these irrationalities on nearly all audio systems including land lines, cells networks, radio, voip, etc.
Progress bars the are visual analog to comfort noise. When there is no progress bar, accurate or otherwise, the system appears dead and people become anxious. The progress bar limits that anxiety to mere impatience.
So 'logic' 'dictates' nothing here. It's about keeping people from pulling their hair out.
As to the original question, why is it so hard to make accurate progress bars, the answer is simple; the problem is exactly as hard as creating a time machine. The exact length of any non-trivial operation is unknown until after the operation is complete. When predicting the future becomes easy progress bars will become accurate.
Even the most basic understanding of mechanics and computing should make the answer obvious. I am genuinely astonished that anyone involved with operating a computer would wonder about it.
I tend to think that the high end ASUS boards are the best money can buy
My experience with ASUS has been frustration with low quality third party chips used to provide excessive numbers or SATA and USB ports and other features. These chips are never as good as the integrated Intel circuits. ASUS is the best of the non-Intel lot, but the others do the same thing; solder on whatever is cheapest and makes the specs look better, damn the bugs or driver issues. Intel also uses third party stuff but they're nowhere near as cavalier about it. Intel's work is not flawless, but they fix it when they screw up. If some Silicon Image chip on a Megasustrix motherboard doesn't work right they aren't going to fix it, or even acknowledge the problem.
I've always thought Intel motherboards only compete in the OEM sector.
That hasn't been true for years. On Newegg only ASUS has more (Intel based) motherboard models available than Intel; Intel has been very responsive to the market of people that want good boards. People like me have long since stopped debugging the poorly engineered products of all these little Taiwanese board makers. My last three personal machines were Intel boards and they're all still running perfectly. Two survived transition from XP to Windows 7 with no driver drama; the OS recognized all the important bits out-of-the-box, which is exactly what I expected and intended.
Dear ASUS, this is an opportunity beyond simply gobbling up the market Intel leaves behind. Now is the time to step up your engineering and qualification of components and produce a line of grown-up boards. I don't need or want 35 USB ports provided by 3 phy implementations, all different. I want conservative, well engineered boards that run cool and don't leak capacitor juice all over the place three years after I buy it. Thanks.
Java has a very small memory footprint by default.
Erm. No. Just no.
class Main {
public static void main(String[] args) {
while (true);
}
}
(jdk 1.7.0.6 x86_64 linux)
17M resident for that. 0.5G of virtual address space. The only other class referenced is java.lang.String.
The equivalent Perl is 1.7M. Node.js is 9M. Python is 4M. TCL is 1.9M.
EVERYTHING uses less RAM than bleeping Java. A lot less. And this isn't some fail test where Java gets better as applications scale. Go look over here and observe how almost every other language consumes less memory across a wide variety of algorithms. Anecdotal evidence from any app server admin will corroborate this.
Java is a RAM pig and it always has been. The problem, at least regarding initial memory footprint (and start-up time), is excessive class loading. This is not opinion. There has been a project to correct it on the books for almost four years.
Like everything else with Java, it has been neglected. Supposedly the results will appear in JDK 9..... sometime in 2015.
And don't cite Android as some exception. Dalvik isn't JRE.
It's clunky. That's the shortest correct explanation I can provide. The whole user experience is just awful.
The first thing you experience when you encounter a Java applet is a sinking feeling as the browser becomes unresponsive with a large gray void somewhere on the page that will eventually render the applet. Sometimes this is alleviated slightly by a progress indicator in some weird JVM font that looks like it was salvaged from OpenBoot. All this "loading" takes large amounts of RAM so the OS starts paging which creates more anxiety for the user as the drive LED indicates vast amounts of mysterious IO. In any case the process takes too long and by the time the applet has rendered something meaningful most users have lost patience.
At this point the applet has started rendering. Frequently this is a bad thing because many Java applets are tragically ugly. Repulsive, really. So bad they look like hastily made email phishing attempts. It would have been better if the "loading" had never ended leaving the user to seek alternatives. The moment a user sees those fonts they squint, groan a bit inside and consider calling someone for help. The GUI widgets look weird. Things don't work right, like copy and paste or common GUI hot keys. And everything lags; you can feel extra tens of milliseconds of lag with every UI operation; click, scroll, whatever. It all lags.
Finally whatever unfortunate task led our victim here has been accomplished and it's time to leave. You click 'home' or some link or whatever to be on your way and BOOM!, the browser segfaults and closes. Recent browsers mitigate this habit by isolating applets (and other plug-ins) in process sandboxes, but the user still gets that extra little poke in the eye to top off the rest of the 'experience.' The sort of effort required to make the JVM run smoothly inside common browsers has never been applied and to this day it is a fragile and crashy combination.
People that care about the user experience, people with tens or hundreds of millions of users using their site(s), don't tolerate this heinous shit. So Java applets die the death they deserve.
Site operators will block content if ads aren't served. Today, some sites will deliberately not function when ad blocking is detected, but this is not yet wide-spread. That policy is going to become ubiquitous if ISPs start blocking ads for all users.
Right now the arms race between advertisers and ad blockers is low intensity because ad blocking is limited to a small fraction of content consumers. Now that ISPs are monkeying around with ad blocking the race will escalate. The advertisers are going to demand that sites withhold content to ad blockers. They are paying the bills so one guess how that's going to go.
Slashdot Mirror
Sounds like this is locked into windows via the Media Foundation APIs
There may be lock in, but it's not exclusive to Microsoft:
Media Source Extensions (MSE) This specification extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.
Encrypted Media Extensions (EME) This proposal extends HTMLMediaElement providing APIs to control playback of protected content.
Web Cryptography API (WebCrypto) This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption.
They're all W3C standards track specifications. The first two have editors from the same three corporations; Google, Microsoft and Netflix. Google, in particular, can't tolerate not being capable of playing Netflix (10% of the population of the US subscribes to this) on its platforms (Android and Chrome OS.) It already works on both and you can take it for granted that Google expects to achieve parity with these specifications.
The last specification is not specific to streaming; it's a general purpose Javascript API to perform common cryptographic operations.
the TSX compatibility timeline will take roughly that long
From the SiSoftware link you provided:
Hardware Lock Elision (HLE) is a legacy compatible instruction set extension, i.e. transparent to CPUs that do not support TSX. The very same code can execute on TSX-capable CPUs - and benefit - but also work on legacy CPUs without performance penalty.
Thus, HLE at least can be adopted immediately by operating systems, compilers and runtimes. That actually started over a year ago for GCC. Intel's compiler uses TSX as well. RTM requires a feature test for compatible use, but it can still be utilized, particularly in runtimes (JVM, CLR, v8, etc.)
So seven years is too pessimistic. Haswell users with recent compilers are already using TSX.
Great benchmark link, BTW.
I'd imagine nobody codes for this. [TSE]
That is going to be an important feature when programmers eventually leverage it. Hardware assisted optimistic locking can make concurrency easier, safer and more efficient as the CPU takes care of coherency problems usually left to the programmer and CAS instructions. Imagine being able to give each of thousands or millions of actors in a simulation their own independent execution context (instruction pointer, stack, etc.,) all safely sharing state and interacting with each other using simple, bug free logic, as opposed to explicit and error prone locking and synchronization. This has been done with software transactional memory but it frequently fails to scale due to lock contention. Hardware based TM can prevent that contention by avoiding lock writes.
It is extremely cool that Intel is implementing this on x86.
That Bloomberg story is about the reactor pressure vessel or RPV, the part the contains the reactor core. These authors write poorly and got it wrong calling it the "containment vessel."
This Slashdot story is about the AP-1000 containment vessel, not the RPV. The vessel is 36 meters wide and 65 meters tall. Nothing on Earth can make a single piece of forged steel that large.
The RPVs specified for the AP-1000 are unusual. RPVs are traditionally welded.
Reactor pressure vessels, which contain the nuclear fuel in nuclear power plants, are made of thick steel plates that are welded together.
RPVs for other common reactor designs such as CANDU or VVER are welded assemblies. Often forged steel steel rings are stacked and welded. Some RPVs use large forged plates and are axially welded.
Note that although the bottom of the AP-1000 RPV is a single piece it still has a separate head; the top of the RPV is gasketed and bolted to the vessel like every other PWR or BWR. It has to be to (re)fuel the reactor.
Sure Linux Kernels, but beyond that, who cares?
I do. I have been looking forward to Mint 15 for a while and so have a lot of others. I appreciate that it was posted on Slashdot and I hope others consider trying Mint as a result. Mint deserves the attention because Mint is an antidote to terrible Linux desktop environments.
There's no magic ju ju in ARM designs.
The magic ju ju is the ARM business model. There is one trump card ARM holds that precludes Intel from many portable devices; chip makers can build custom SOCs in-house with whatever special circuits they want on the same die. Intel doesn't do that and they don't want to do it; it would mean licencing masks to other manufactures like ARM does. For example, the Apple A5, manufactured by Samsung, includes third party circuits like the Audience EarSmart noise-cancellation processor, among others. It is presently not feasible to imagine Intel handing over masks such that Apple could then contract with some foundry to manufacture custom x86 SOCs. This obviates Intel from many portable use cases.
That feature of the ARM business model might be very useful to large scale computing. One can imagine integrating a custom high-performance crossbar with an ARM core. Cores on separate dies could then communicate with the lowest possible latency. Using a general purpose ARM core to marshal data to and from high-performance SIMD circuits on the same die is another obvious possibility. A custom cryptography circuit might be hosted the same way.
Contemporary supercomputers are great aggregations of near-commodity components. However, supercomputing has a long history of custom circuit design and if the need arises for a highly specialized circuit then a designer may decide that integrating with ARM to do the less exotic leg work computing that is always necessary is a good choice.
People like Zuckerburg use to found colleges and universities in the US. Now they squabble with Congress for cheap imports.
One cause for the lack of demand of electrical engineers is that the hardware design and manufacturing is located to cheaper countries.
Can't be. Those are the jobs we're keeping here in the US because we all have $75k degrees. The low skill jerbs go to Asia and we keep all the high paying jobs because the Chinese are magically incapable of EE.
Right?
Remember: Education. It's the future.
"washington monument gambit"
Shutting down White House tours is the same brand of statist petulance.
BTW, ordinarily around here the Blue Angles and their ilk are just jingoistic manifestations of the US Military Industrial Complex's hegemony over the victims of global capitalism, and stuff. We're supposed to believe you people suddenly give a damn about these airshow cowboys?
LOL
The comments look as though at some point Slashdot turned into a gathering of cantankerous change-haters.
There are a lot of malcontents around here. Not all of us, however.
There is plenty of room for a good systems programming language. No, we probably don't need another managed, exclusively garbage collected, JIT compiled, VM hosted, 'dynamic' application language. And we've certainly collected enough Javascript front-end languages recently. That's not the intent of Rust.
Then what are you worried about?
Prosperity. Economic growth. Energy is the ultimate raw material necessary for these things.
Don't assume everyone shares the premise that we need cheap, abundant and clean energy. You could live out your life inside a three mile radius of your yurt nursing a solar panel. Putting you there is an ideal to which many aspire.
To be clear, I am not among them. I've just shed any illusions about whom I'm dealing with. They've either got theirs or they don't want it (the former being the vastly larger group) and job #1 is stopping you.
arrest the perp and send him to prison.
Investigating, arresting and prosecuting people for violating these kinds of laws is unbelievably difficult and expensive and rarely nets more than wrist-slaps. Cases take years, litigators cost millions and there is and endless supply of replacement spammers to replace the prosecuted. Governments executives and their staffs know this and have better things to do.
Finding the least statist solution is my preferred remedy in any case; make the practice economically infeasible by creating a generic regulatory mechanism (white/black lists based on working caller ID and enforced by the network operator, perhaps) and leave the cops/prosecutors/courts/prisons out of it.
The carriers are a part of this as well. They facilitate spammers by deliberately not making caller ID work end-to-end in all cases like it should, streamlining mass account provisioning, etc. They get revenue from calls, spam or otherwise. Even your legislators are part of it; they exempt themselves from robocall laws and email spam laws creating all sorts of loop holes and special exceptions in the system that carriers can and do use to deflect blame.
...the $600 price tags on phones
I keep reading about $600 smart phones in stories on this T-Mobile no-contract scheme. You can have an amazing unlocked no-contract quad-core Nexus 4 for $299-349 here. It's HSPA+ which is all you'll get with T-Mobile in most markets anyhow.
If the best argument against this deal is that unlocked iPhones cost too much then sign me up. Data coverage is the real problem with T-Mobile... but perhaps they're really solving that now.
There is *no* right not to be offended
There is no right to be employed either.
You are either for Free Speech
I am for freedom. Including the freedom to fire whatever at-will employed asshole I chose for whatever reason I care to indulge. Stop conflating rights as a citizen with employment. You can stand on a corner and voice as many double entendres as you want. You can even earn a living doing that if you're any good. That doesn't mean I have to employ you.
It's not economically sensible to ship regular, lower-grade coal for producing electricity all around the world.
This is factually incorrect. Coal used for power generation is called `steam coal' and the recent growth of US coal exports is due to steam coal.
You may expect all of this to accelerate rapidly. As the story points out, met coal is going to China from the East coast the hard way; via the Atlantic, Cape of Good Hope, etc. Our pollution outsourcing and de-industrialization needs are so great that the Panama Canal is being expanded to accommodate much larger ships. Simultaneously we're waving environmental regs right and left to dredge up East coast bays for those ships.
This will all be up and running in 2015.
Once "Super-Post-Panamax" shipping can haul coal from the East Coast to China via the Pacific we'll see huge growth in coal exports and more de-industrialization. Coal going that way and finished goods coming back.
but then i read some of the comments below and realized you were spot on
I noticed this behavior a few years ago when the Apple+Foxconn stories started to appear. After hunting through the comments of a few of those stories I came up with a comprehensive list of rationalizations.
We are comfortable office people steeped in self-loathing. We can equivocate any evil by dismissing criticism as hypocrisy. The fact that in the case of Chinese industry these arguments happen to align with the desire for low cost products produced well outside "the environment" is purely coincidental...
The free market, when and to the extent it is allowed to exist is EXTREMELY far-sighted.
The summary is a troll. Attributing the 'free market' to nuclear power indicates either ignorance or deceit and we're left to ponder which is worse.
Nuclear reactors represent astonishing amounts of wealth and coordination. It is a hallmark of advanced nations that such things are created. For a reactor to exist in the US it must have the blessing of all levels of government. Financing is often backed by one or more government entities. Federal and state governments must actively regulate it. First responders at each level are prepared for emergencies. Rate payers are involved in voting on proposals prior to construction and regulating on-going rates. The timeline (in contemporary Western nations and certain Asian nations) is at least a decade for construction and licensing is a matter of fractions of a century. People are sourced from rarified cohorts such as military navel reactor operators.
In the end the actual operator is a small and even negligible part of the equation. Invoking the 'free market' mantra when dealing with the troubles of nuclear power is a cop out.
I'm cute and I've probably forgotten more about the HTS and US trade than you'll ever know.
I file an individual HTS classification for each line item
The HTS is a fascinating bit of work. For people that don't know, the Harmonized Tariff Schedule is a US government published document that classifies just about every conceivable good and assigns tariffs, duties, etc. It is huge and is now only published in electronic form.
As the parent wrote, most finished goods in the HTS are 0% tariff. There are many things in the HTS with tariffs, but if it's a finished good it is usually exempt from any cost whatsoever. Some exceptions include small arms and autos; the UAW negotiated a 25% domestic value-add requirement in the '80s if foreign manufacturers wish to avoid tariffs. That one requirement is the sole reason that all auto manufacturing hasn't evacuated the US. Today there are dozens of foreign owned auto plants in the southern US writing paychecks to thousands of US workers because of that law.
No other nation is as import friendly as the US. Unless your nation has imams and muftis actively operating uranium isotope centrifuges in a bunker somewhere then you too can export to the US tariff free. You can wreck the environment to whatever degree you wish, abuse, neglect or contaminate however many people you want and it won't even slow down your goods as they get whisked into the US.
That's what domestic manufacturers and the US working class have to compete with for 80% of all finished goods in the US.
I think guns are a protected industry in the US. I'm pretty sure that we're not allowed to import foreign made guns for sale.
We import many, many foreign guns. There are limits, however. The US doesn't allow Norico (the largest small arms manufacturer on Earth, a Chinese company) to import. Also, foreign small arms must get through the ATF points system which limits what can be imported. Also, there are tariffs. Most other imported finished goods have no tariffs.
The result is that although there are large numbers of imported small arms, the limitations and extra costs to importers allow domestic manufacturing to be viable. Thus, we have companies like Ruger and Smith and Wesson; big, successful manufacturers that build most or all of their products in the US. There are also a plethora of small manufacturers.
Domestic small arms manufacturing is among the best evidence that applying some resistance to imports allows domestic manufacturing to thrive.
then logic would dictate that [progress bars are] pointless
It's not about logic. It's about comfort. During a phone call there is a noise most people don't typically notice. It's called sidetone (comfort noise, in some cases) and the effect of it is to convey a feeling that the connection is 'working.' When that noise is absent the operator perceives that the connection is 'dead.' The phone doesn't sound 'live' somehow.
Logic would dictate that such subtleties are unnecessary. That pesky old Real World thinks otherwise, however, and expends extraordinary effort to perpetuate these irrationalities on nearly all audio systems including land lines, cells networks, radio, voip, etc.
Progress bars the are visual analog to comfort noise. When there is no progress bar, accurate or otherwise, the system appears dead and people become anxious. The progress bar limits that anxiety to mere impatience.
So 'logic' 'dictates' nothing here. It's about keeping people from pulling their hair out.
As to the original question, why is it so hard to make accurate progress bars, the answer is simple; the problem is exactly as hard as creating a time machine. The exact length of any non-trivial operation is unknown until after the operation is complete. When predicting the future becomes easy progress bars will become accurate.
Even the most basic understanding of mechanics and computing should make the answer obvious. I am genuinely astonished that anyone involved with operating a computer would wonder about it.
I tend to think that the high end ASUS boards are the best money can buy
My experience with ASUS has been frustration with low quality third party chips used to provide excessive numbers or SATA and USB ports and other features. These chips are never as good as the integrated Intel circuits. ASUS is the best of the non-Intel lot, but the others do the same thing; solder on whatever is cheapest and makes the specs look better, damn the bugs or driver issues. Intel also uses third party stuff but they're nowhere near as cavalier about it. Intel's work is not flawless, but they fix it when they screw up. If some Silicon Image chip on a Megasustrix motherboard doesn't work right they aren't going to fix it, or even acknowledge the problem.
I've always thought Intel motherboards only compete in the OEM sector.
That hasn't been true for years. On Newegg only ASUS has more (Intel based) motherboard models available than Intel; Intel has been very responsive to the market of people that want good boards. People like me have long since stopped debugging the poorly engineered products of all these little Taiwanese board makers. My last three personal machines were Intel boards and they're all still running perfectly. Two survived transition from XP to Windows 7 with no driver drama; the OS recognized all the important bits out-of-the-box, which is exactly what I expected and intended.
Dear ASUS, this is an opportunity beyond simply gobbling up the market Intel leaves behind. Now is the time to step up your engineering and qualification of components and produce a line of grown-up boards. I don't need or want 35 USB ports provided by 3 phy implementations, all different. I want conservative, well engineered boards that run cool and don't leak capacitor juice all over the place three years after I buy it. Thanks.
Java has a very small memory footprint by default.
Erm. No. Just no.
class Main { public static void main(String[] args) { while (true); } }
(jdk 1.7.0.6 x86_64 linux)
17M resident for that. 0.5G of virtual address space. The only other class referenced is java.lang.String.
The equivalent Perl is 1.7M. Node.js is 9M. Python is 4M. TCL is 1.9M.
EVERYTHING uses less RAM than bleeping Java. A lot less. And this isn't some fail test where Java gets better as applications scale. Go look over here and observe how almost every other language consumes less memory across a wide variety of algorithms. Anecdotal evidence from any app server admin will corroborate this.
Java is a RAM pig and it always has been. The problem, at least regarding initial memory footprint (and start-up time), is excessive class loading. This is not opinion. There has been a project to correct it on the books for almost four years.
Like everything else with Java, it has been neglected. Supposedly the results will appear in JDK 9..... sometime in 2015.
And don't cite Android as some exception. Dalvik isn't JRE.
java on the web is effectively dead
What killed it?
It's clunky. That's the shortest correct explanation I can provide. The whole user experience is just awful.
The first thing you experience when you encounter a Java applet is a sinking feeling as the browser becomes unresponsive with a large gray void somewhere on the page that will eventually render the applet. Sometimes this is alleviated slightly by a progress indicator in some weird JVM font that looks like it was salvaged from OpenBoot. All this "loading" takes large amounts of RAM so the OS starts paging which creates more anxiety for the user as the drive LED indicates vast amounts of mysterious IO. In any case the process takes too long and by the time the applet has rendered something meaningful most users have lost patience.
At this point the applet has started rendering. Frequently this is a bad thing because many Java applets are tragically ugly. Repulsive, really. So bad they look like hastily made email phishing attempts. It would have been better if the "loading" had never ended leaving the user to seek alternatives. The moment a user sees those fonts they squint, groan a bit inside and consider calling someone for help. The GUI widgets look weird. Things don't work right, like copy and paste or common GUI hot keys. And everything lags; you can feel extra tens of milliseconds of lag with every UI operation; click, scroll, whatever. It all lags.
Finally whatever unfortunate task led our victim here has been accomplished and it's time to leave. You click 'home' or some link or whatever to be on your way and BOOM!, the browser segfaults and closes. Recent browsers mitigate this habit by isolating applets (and other plug-ins) in process sandboxes, but the user still gets that extra little poke in the eye to top off the rest of the 'experience.' The sort of effort required to make the JVM run smoothly inside common browsers has never been applied and to this day it is a fragile and crashy combination.
People that care about the user experience, people with tens or hundreds of millions of users using their site(s), don't tolerate this heinous shit. So Java applets die the death they deserve.
Site operators will block content if ads aren't served. Today, some sites will deliberately not function when ad blocking is detected, but this is not yet wide-spread. That policy is going to become ubiquitous if ISPs start blocking ads for all users.
Right now the arms race between advertisers and ad blockers is low intensity because ad blocking is limited to a small fraction of content consumers. Now that ISPs are monkeying around with ad blocking the race will escalate. The advertisers are going to demand that sites withhold content to ad blockers. They are paying the bills so one guess how that's going to go.
Enjoy your advertising-enforced interwebs.