We Don’t Require an Uptick Rule
This is a unproblematic issue.
It applyed to be that you couldn’t inadequate a stock unless there was an uptick. The idea was that this uptick rule would keep inadequate sellers from piling on a stock and laboring the price down. So the uptick rule was removed. It got permissable to take up shares of stock and trade them whether or not the stock had clicked up or not. The result ? Nothing. Not a darn thing modifyed.
Well companies operated on their companies good. They recognised that little sellers just now made succeeding demand for their stocks. If they forced the price down to young lows, it exactly produced an opportunity for investors to purchase the company at inexpensive prices. Hence be it. Dear companies aren’t defined by their stock prices, they are defined by their operations.
On the flipside are badly handled companies. Badly carryed off companies ever take for granted the current business environment will abide the way it is. The heavy investment banks opined they could ever lift capital and deploy it at higher returns. Which is a swell model to pry up to mash every potential nickel out. It forms it well-heeled to catch your bonus and constitutes shareholders who but devote attention to the stock price well-chosen.
Except that leverage is risk. E’er has been, e’er will be. When you dont handle your risk easily, you give the consequences.
The problem with the likes of Lehmans, Bear Stearns et al, wasn’t that their stock prices were forced down, it was that they had suited unforesightful and excessively leveraged. They had not debated all potential negatively charged scenarios. When they were thrust to compose down assets and couldnt take access to loans because no one commited their balance sheets, they were without capital. When they were without capital, they were SOL. Deleveraging fetched their intact business models going down down on with their stock prices. Lehman went away, the rest produced government bailouts or were born on to be corrupted out.
(more…)December 9, 2008
Project Jigsaw: Java Modularity and JSR changes
It was of late denoted that the Java Module System(JSR-277) would be put on hold until after Java SE 7. This has further implications on Java’s modularity future and other developments like OSGi(JSR-291) and the super-packages spec(JSR-294). This post by Neil Bartlett tots up up the ramifications of these changes and what Sun will at present ring project Jigsaw.
Related Posts:
For Sale: 4242 Castle Ave., Spring Hill, FL 34609 USA / US$ 99,900
PE Obama’s 1st Big Mistake
In-Store Price-Look into Options
December 6, 2008
I’m Moving Retentive Right Today
I could be an idiot. But I conceive at present is the time. I place 8 pct of my last worth in DIAmond puts at 11000, as a hedge, and simply betrayed them at a very skillful gain. Very skillful. Today Im unawares casts that I sold in not close as large a position, but skillful.
Im plumping long.
Im not plumping to gift you some historic perspective. The SEC bolted down any historic relevance when they stoped over shorts on 900 stocks. Im purchasing because the only existent uncertainty I reckon staying is from the economy. Thusly
One thing I cognise is that geting going tomorrow the shorts can get rearward in the market.
When I look at the credit markets. The Fed and Treasury and even external agencies are pointing that they will be the lender of the first and last resort. We visit little term treasuries trading as if traders are starting up to catch comfy with credit and liquidity. I mean that although banks dont amply desire lending to each other even so, they are puting to work to set unitedly the scenarios under which they will merchandise. They are pitching up.
(more…)December 4, 2008
EJB 3.1 and JSF 2.0 with GlassFish
GlassFish v.3 will admit support for both EJB 3.1 and JSF 2.0, both of which defend major milestones in the Java EE space. This post by Matthias Rüedlinger brings home the bacon step by step instructions on making a mere CRUD application with EJB 3.1 and JSF 2.0.
Related Posts:
Fω^C: a symmetrically classic variant of System Fω
PE Obama’s 1st Prominent Mistake
December 2, 2008
Diagnosing OSGi habituates conflicts
One of the basal keys to building OSGi enabled applications is the creation of MANIFEST.MF files with the right OSGi headers. This post by Rob Harrop requires a look at the ‘uses’ keyword used in OSGi headers and how to diagnose conflicts.
November 25, 2008
Speaking Youtube Live
This past Nov 22nd Youtube had its first major unrecorded event. A concert boasting HDNet fave Joe Satriani , Katy Perry Will.I.Am and others. Of course everyone involved in the space is maundering or so whether or not the show was a success.
According to Mogulus , the live internet broadcast under the weather at about 700k co-occurrent users. That’s immense for an internet audience. I think by any traditional Youtube measure , you have to ring it a success, with some major gotchas.
First the reasons why it was a success:
700k would be a with child audience for a little cable network. Particularly for a 1 off show.
MORE IMPORTANT than the audience size was the amount of money that Youtube had to expend to yield that audience. My guess is that they but advanced it on their site and via traditional PR.
A traditional minor cable network would have had to pass several million dollars in off network promotions (radio, tv , net, mag, newspaper) in order to bring forth that size audience and and then they would gloat some how it was one of its largest audiences e’er.If Youtube can try out that it can generate this size audience on a hebdomadal or monthly basis, it has a Brobdingnagian hit machine on its hands.
In finicky, the audience was believably right in the 18 to 34 gratifying spot that advertisers covet. More honest news. They will be capable to trade a ton of ads in and around their shows.
(more…)November 23, 2008
Fω^C: a symmetrically authoritative variant of System Fω
Lengrand & Miquel (2008). Greco-Roman Fω, orthogonality and symmetric candidates. Annals of Pure and Put on Logic 153:3-20.
We portray a version of system Fω, bade Fω^C, in which the layer of type
constructors is fundamentally the traditional one of Fω, whereas provability
of types is Hellenic. The proof-term calculus accounting for the Graeco-Roman
reasoning is a variant of Barbanera and Berardi’s symmetrical λ-calculus.
We testify that the hale calculus is powerfully normalising. For the
layer of type constructors, we utilize Tait and Girard’s reducibility method
combined with orthogonality techniques. For the (authoritative) layer of terms,
we expend Barbanera and Berardi’s method based on a symmetrical notion of
reducibility candidate. We examine that orthogonality does not catch the
fixpoint construction of symmetrical candidates.We plant the consistency of Fω^C, and bear on the calculus to the
traditional system Fω, likewise when the latter is extended with axioms for
Greco-Roman logic.
November 21, 2008
Fω^C: a symmetrically classic variant of System Fω
Lengrand & Miquel (2008). Graeco-Roman Fω, orthogonality and symmetrical candidates. Annals of Pure and Put on Logic 153:3-20.
We portray a version of system Fω, bade Fω^C, in which the layer of type
constructors is fundamentally the traditional one of Fω, whereas provability
of types is classic. The proof-term calculus accounting for the Graeco-Roman
reasoning is a variant of Barbanera and Berardi’s symmetrical λ-calculus.
We show that the hale calculus is powerfully normalising. For the
layer of type constructors, we utilize Tait and Girard’s reducibility method
combined with orthogonality techniques. For the (classic) layer of terms,
we expend Barbanera and Berardi’s method based on a symmetrical notion of
reducibility candidate. We try that orthogonality does not catch the
fixpoint construction of symmetrical candidates.We found the consistency of Fω^C, and pertain the calculus to the
traditional system Fω, as well when the latter is extended with axioms for
classic logic.
November 17, 2008
What Does that .NET Namespace Mean: System.* and Microsoft.*
I take your feedback… I am chatting with some co-workers about the perception of in the.NET Community of what the System.* and Microsoft.* namespaces mean. So I had the wild idea of but expecting you!
For this exercise, I’d care you to flirt with a newfangled "feature area" of the.NET Framework… Would you instinctively make any conclusions about that area grounded on if the namespace where System.* or Microsoft.*? If that feature area were in the Silverlight subset of.NET, would that interchange your mind at all?
There are fundamentally three schools of thought among my co-workers — which one is closer to your perception?
1) They are the same or it truly doesn’t matter. The root namespace between System.* and Microsoft.* have no meaning… Microsoft seems to be arbitrary about when functionality gos in one or the other.
2) Part of the Framework vs. Addons.
(more…)System.* argues stuff that is logically part of the framework. It is 100% sustained, self-coloured-longsighted term design that will not call for to moil, good to look on, stable, probably will catch outstanding joyriding support. Contrived to be very interoperable and could act anyplace.NET is. This may embark as part of the redist or perhaps an out of band (such as ASP.NET MVC, ASP.NET AJAX, etc).
Microsoft.* is the runing edge stuff or value-add. It is typically very nerveless stuff that supplies on to the framework and raises it, but perchance a work in progress… over time you might require some of those concepts to enter the framework. As an example, the outstanding work patterns and practices does a great deal falls under this bucket.
November 16, 2008
Fω^C: a symmetrically authoritative variant of System Fω
Lengrand & Miquel (2008). Hellenic Fω, orthogonality and symmetrical candidates. Annals of Pure and Put on Logic 153:3-20.
We portray a version of system Fω, bade Fω^C, in which the layer of type
constructors is fundamentally the traditional one of Fω, whereas provability
of types is Graeco-Roman. The proof-term calculus accounting for the Greco-Roman
reasoning is a variant of Barbanera and Berardi’s symmetrical λ-calculus.
We bear witness that the hale calculus is powerfully normalising. For the
layer of type constructors, we apply Tait and Girard’s reducibility method
combined with orthogonality techniques. For the (definitive) layer of terms,
we expend Barbanera and Berardi’s method based on a symmetrical notion of
reducibility candidate. We try that orthogonality does not catch the
fixpoint construction of symmetrical candidates.We plant the consistency of Fω^C, and have-to doe with the calculus to the
traditional system Fω, too when the latter is extended with axioms for
Hellenic logic.
Related Posts:
Fω^C: a symmetrically definitive variant of System Fω
I’m Moving Recollective Right Nowadays
Get free blog up and running in minutes with Blogsome
Theme designed by Hadley Wickham
