29 karma · joined September 11, 2012
If a lot of workers quit then the wages (and prices) rise, and workers move from other jobs to do the higher paid ones. There is only a shortage of labor when there are wage or price controls imposed on the businesses by legislation.
As long as people are griping and complaining instead of quitting we know we're in good shape.
Not in America.
> US rallies for some causes where it seems to suit US interests.
Yes, we act in support of national interests, like every country.
> There are so many countries that need help but in recent years whether a country gets US presence seems largely dependent on whether there is oil there and US is all too happy to turn their face away if the government of the oil-rich country is collaborating with US.
America is not out to save the world and this is a good thing. There is nothing worse than some outsider coming in to save the poor savages from their own evil selves. It’s not our job to pass judgement on others or to fix every problem in the world, unless it is in the national interest (even then I’d say the US has too many interests but that’s another issue).
> This unfortunately adds fire to the trouble in the Middle East. If you are islamic radical it is extremely easy to recruit people by showing them factual, real, undeniable misbehavior of US.
This is laughable. Compare The US to the regimes in that area in terms of “misbehavior”. America has nothing to be ashamed of there.
My bet is on individuals to act in their own best interest. Likewise, politicians have every incentive to act in ways that benefit themselves and their friends at the expense of everyone else. In both cases I acknowledge the capabilities of these humans to use their own brains to think, but only politicians have an incentive become corrupt.
The argument was that the FDA never made sense, not even when it was first established in America, and for precisely that reason -- Americans were not illiterate.
I see no reason why an individual should not be allowed to build their house with whatever inspection regimen they desire (even none at all). A poorly built house, a house without the endorsement of a respected engineering body, will surely have this reflected in the sale price. I don't see a problem here that needs to be solved.
Easily. Simply allow the private sector to provide the services currently under the exclusive domain of the FDA, for example.
> Trusting private corporations or companies with public safety is insane.
I agree 100%. However, companies are not in a position to provide public safety anyway. It's consumers who make up the public, through their choices, who provide for the public safety. They are perfectly capable of being safe without needing the government to interfere in their affairs.
> You know, instead of reforming it or fixing the problems we have.
What's really sad here is the belief that if only we had smarter experts in Washington D.C. they could make the perfect set of rules to regulate everyone's lives, and we would not have any problems. This is utterly naive, and is quite impossible in practice. No matter how smart an expert is, they simply can't know enough to make the optimal balance for you or me. They don't know anything about my life, so how could they evaluate all the trade-offs to make optimal choices for me? There are just too many variables and life is too dynamic.
This is exactly why free markets are great, they provide the distributed feedback that democracy can't. Individuals are free to choose the services and goods that provide the most value, and collectively these preference signals propagate through the market to guide producers, who are in turn free to innovate and create new services they think I will prefer. This "invisible hand" guides the interactions of millions of people across the globe, but it requires freedom.
Wherever there is a free market we see innovation and prosperity. The evidence is all around you.
"Peoples lives matter" is meaningless nonsense, and even taken at face value does not imply standards should be high. Remember that high costs and overly restrictive rules introduce delays and prevent drugs from reaching the consumer, and people are harmed and die because of this.
How do we know when the FDA procedures are too restrictive? Well, we can't! Only the consumer can make those tradeoffs for him/herself and communicate their needs and desires via their preferences when selecting products where there are alternatives. With the FDA being a government monopoly there is no such feedback loop, so we just don't know how well their procedures actually align with what the people need.
It's depressing to see how many Americans believe that if something "matters" the only option is to have the government micromanage it. If you're not American then I understand, of course.
The Car & Truck Administration (CTA) approval process
ensures both that cars and trucks perform an intended
function, and that cars and trucks don't harm people.
Part of the expense of this process is making sure that
both of these aspects are performed to sufficient
standards.
And yet, we don't seem to need an FDA of cars and trucks costing auto manufacturers $1.4B to develop a new car, and our cars don't explode and kill us. The reason? A car maker who makes unsafe cars goes out of business. Consider Ralph Nader's "Unsafe At Any Speed" did to the Corvair corporation.So in practice things are only recompiled when they need to be recompiled. Even though the watcher task is firing, no real work is done unless it needs to be done.
I think that generally the files you're dealing with will fit in memory, but you still wouldn't probably want to have everything in memory all the time, you'd need to stream them (consider an uberjar that's 10M as a JAR, but might contain contents that are 10x that size uncompressed).
This brings us to the second point. No existing JVM tools are prepared to accept files via pipes. Tooling on the JVM looks for things on the class path and in JAR files. We definitely don't want to have to rewrite every tool to use some in-memory pipe system.
The fileset and pod abstractions provided by boot work together to give you the best of both worlds--an immutable representation of the filesystem and class path combined with full interop with the existing JVM ecosystem.
Another issue with Unix pipes is that they are not awesome for tree-like things. In bash you pipe lines of text from one program to another, but tree processing is very difficult. Consider xml processing by pipes, or my jsawk library for processing JSON in the shell. These suffer from memory issues because it's hard to stream trees (if you have a 2G JSON file that is a single object jsawk can't even read it in).
In boot tasks don't fish around in the filesystem to find things. Not for input nor output. Tasks obtain the list of files they can access via functions: boot.core/src-files, boot.core/tgt-files, et al. These functions return immutable sets of java.io.File objects. However, these Files are usually temp files managed by boot.
Boot does things like symlinking (actually we use hard links to get structural sharing, and the files are owned by boot so we don't have cross-filesystem issues to worry about), and we shuffle around with classpath directories and pods.
So stay tuned for the write-up of the filesystem stuff, I think it might be right up your alley!
(deftask build-jar
"Build project jar file."
[]
(comp (pom) (add-src) (jar) (install)))
When you build the jar file you just do boot build-jar
This ensures repeatability, etc.But we don't only use boot for repeatable builds! Boot is in a unique position in that it's on the intersection of application and environment. That is to say, boot can be used to "bootstrap" the application. With boot we can create sort of self-configuring applications, where the entry point of the application is the build.boot file. This is a very clear win, for example, when running Clojure applications in docker on Elastic Beanstalk, etc. (We'll write that up, too.)
We can't control the fact that the CLJS compiler, for example, is looking for source files on the classpath instead of in some FileSet object proxy. If we admit the use of tools written by the Java community at large we suffer by adding another leaking half-abstraction to the mix.
We actually did some experiments with fuse filesystems but the performance is just not there yet. When fuse performance becomes comparable to Java NIO it may become a viable option, and would solve all of these problems. You could then have a "membrane" approach, where the JVM is only manipulating a filesystem proxy, and you have complete control over when and how to reify that and write to the filesystem.