text:
So you have hot beats, your rhymes are on point and you even got major swag. What happens now? Is releasing 'good' music enough to get you signed?
Although much of the industry is revolutionizing how it does business, certain aspects of it have remained the same. Every act should be doing shows consistently and selling CD's along with merchandise. That being said, stay up to date with approaching new ways to sell your music. Artists need to see forward-thinking movement. One example is, state-of-the-art mobile apps that allow you to charge your fans by credit card, on the spot! If they just want mp3's, you can charge them right away and have a link automatically emailed to them to download your album. Selling units is of the utmost importance. Record companies want to see that you can move units without their help. The bottom line is, if you can't sell records on your own, labels no longer have the interest nor the resources to sign and develop you.
Are you completely inspired by Drake and want to sound just like him? I didn't think so. However, does his sound subconsciously influence how you sound? There is an interesting balance that should be considered here. Record label A&R's love to hear familiarity in acts they are scouting. However, don't (by any means) be a copycat. Borrowing elements of the hottest pop music of the moment can be used sparingly, but incorporate your own unique approach! Yes you are an artist, so you may feel inclined to write music that defies genres and sounds like it's from the year 2040. Just keep in mind that a good song is like a good meal. Most people who like pizza, may be apprehensive of trying a duck burger over their favorite pizza. The argument then becomes, who is your target audience? Yes, many people eat duck but statistically pizza is consumed by millions more (also due to availability, supply etc). In this case, we are talking about record label A&R's. They don't want to market and sell a duck burger, they'd rather take a pepperoni pizza, add a dash of duck to it and voila! It's all about a balance of pop appeal, uniqueness and believe it or not, talent. Just remember, you shouldn't be 10 steps ahead of radio, but make sure you are a good 2-3 steps ahead.
Social media is so unbelievably important to record labels considering signing a new artist. Immerse yourself into this invaluable tool now. There are so many different ways to expose your music on Facebook, Twitter, YouTube and other sites (including the 45,000 sites that will launch by the time I finish this sentence). Once you have a product, you must spend a large part of your day submitting your music to blogs. The exposure a positive blog review can get you, can help propel you to another level. One of the most effective online campaigns, comes in the form of viral videos. Shooting clips can be done on quite the budget nowadays, so explore this idea as much as your resources allow.
Always remember that networking is one of the most important aspects of your career in the music business. The corny record producer from your neighborhood that you don't like? Keep in touch with him. He may launch a label, get a distribution offer from Universal and be looking for music like yours! You never know, one person could change your life. All things considered, you absolutely should never burn bridges in this business.
If you take into account the aforementioned details and combine them with talent, hard work and persistence, there's no limit to what goals you can reach!
Here is a list of record labels that are currently looking for artists to sign.


text:
About this paper
The underground economy is thriving, thanks in part to new technologies and business models such as digital currencies and online marketplaces for freelance services. SAS fraud specialists reveal how government agencies can uncover these activities – and the tax obligations not reported from them. A former head of compliance for the country's fourth-largest state workers' comp program describes how a comprehensive analytics program found a tax gap of $718 million and was granted funding to double the team's size without even asking.
About SAS
SAS is the leader in analytics. Through innovative software and services, SAS empowers and inspires customers around the world to transform data into intelligence. SAS gives you THE POWER TO KNOW®.
¿Tiene un Perfil SAS? Para completar este formulario automáticamente Ingreso
Bienvenido, . Editar Perfil Salir

subset: commoncrawl


text:
Overview of current state
A module may export a certain list of public packages to any caller, or certain friend packages to an enumerated list of callers only, or no packages at all. Both Ant- and Maven-based build harnesses verify at build time that a calling module has permission to access packages from an API module via a regular "specification version" dependency, and the same check is done at runtime by the module system.
A spec dep is on a given specification version or newer, together with a major release version or (occasionally) range. The major release version is not related in any way to the specification version, but must be a natural number (if omitted it is typically considered to be zero). When compiling against m/1 2.3, the build harness will by default create a dep "m/1 > 2.3" matching any version of m with major equal to 1 and spec equal to 2.3 or higher. It is possible to explicitly request a major range like "m/1-2 > 2.3" matching m with major 1 and spec 2.3+, or m with major 2 and any spec. The expectation is that compatible API changes increment the spec version (somehow); whereas incompatible changes increment the major version (and perhaps also change the spec version): CompatibilityPolicy.
An implementation dep is on an exact implementation version of a module. By default that is generated by the build harness, e.g. as the current date, but it may be given explicitly, typically as a natural number (unrelated to either the major or spec versions). When using an impl dep, a public type in any package may be accessed (at build time and runtime).
Problems with current state
Usage from external modules
The most serious problem: external module developers frequently need to call some semi-API which is either not officially exported, or exported only to some friends. This is very common for IDE plugins, since plenty of widely used modules offer only friend packages: xml.multiview, gsf.testrunner, jumpto, and so on. The developer is usually implored to either ask for friend status from the maintainer of the API module, or to initiate a review of the module to make it public. Either way, this advice is useless for building against the current NetBeans release, and it discourages people from experimenting with potentially useful APIs which might be improved by their feedback. The problem is especially notable for API modules which are not actively maintained, both because getting changes made to the export metadata is hard, and because the API is probably not changing much from release to release anyway.
The usual workarounds are:
- Declaring an implementation dependency, and shipping a different copy of the importing module for each NetBeans release, even when (in the usual case) its code is unchanged. Makes it difficult to build the product in a single job when using the Maven harness, and essentially impossible when using the Ant harness.
- Like #1 but not bothering to ship different versions; users of a different NetBeans release must recompile the module from sources.
- Calling the entire API using reflection.
- Using reflection to hack into the NB module system and convince it that the importer is a "friend". (See https://bitbucket.org/jglick/yenta for example.) This has become the preferred technique for those who know about it, but of course it subverts the original intent of protecting a user from an unlinkable module - and introduces an unannounced dependency on internal implementation classes in the module system.
Version madness
Having three different kinds of versions that may control module-to-module dependencies - specification, major release, and implementation - is rather confusing. It is not obvious, for example, that upgrading from 1.1 -> 2.0 in spec version is not essentially any different than 1.1 -> 1.2; or that "m/1-2 > 1.3" will match m/2 in version 1.0.
Another minor point of confusion is that "m/1-2 > 1.3" matches 1.3 itself, i.e. '>' should really be '≥'.
Difficulties of implementation dependencies
Using impl deps is awkward in the best of circumstances. When the exporting module is cooperative, it will declare a numeric implementation version, then use spec.version.base to ensure that changes to that version automatically change the spec version too. (See DevFaqImplementationDependency for background.) Then the importer must declare an impl dep, which is difficult in the Maven harness (requires special metadata).
The importer might accidentally begin using packages which the exporter did not mean to make available even to this importer.
When publishing a numeric impl version, it is all too easy to forget to increment it when making changes, so some dependencies are often stuck on the same impl dep for years - even while the actual API has changed considerably.
Mixing public and friend packages
Declaring a list of friends for a module prevents you from also declaring public packages. (This is essentially because a module has just one version and we would not want to mark a major release version increment when only changing the friend packages: bug #54123 comment #6.) Since it is commonplace for an API module to need to export a special SPI to certain callers, but which should not be part of the general API, there are various workarounds known:
- Add a public package with a name implying implementation and hope only the right modules call it. If an incompatible change needs to be made in it, make a compatible-style increment to the spec version and just hope the calling modules are updated in tandem (since the module system will not understand). (e.g.: org.openide.util.lookup.implspi)
- Like #1, but override module.javadoc.packages so it does not appear in API documentation (but will still appear in code completion etc.). (e.g.: org.netbeans.modules.progress.spi)
- Like #1, but use ad-hoc techniques at runtime to prevent calls from unexpected places, like checking the name of a subclass or checking a stack trace. (e.g.: org.openide.util.lookup.implspi.AbstractServiceProviderProcessor)
- Try to factor the friend API code into a third module which both the public API module and SPI implementors will depend upon. Not always straightforward, and rarely done in practice.
- Declare an impl dep. This is forbidden in the platform cluster, especially due to the problems interoperating with OSGi, but still common in other clusters. (e.g.: org.netbeans.modules.project.uiapi)
Minor incompatible changes
Most incompatible API changes are quite small in scope and are likely to affect very few clients; if they were more important, effort would be put into avoiding them. Yet the module system has only a binary notion "compatible" vs. "incompatible" change. So the API developer who needs to make a slightly incompatible change is forced to choose between
- Make the API change and just mark a regular specification version increase. Increment the versions of any callers which are known to need updating and hope that users receive the updates. Hope that there are no other callers needing updates out there.
- Increment the major release version. Forces those callers which really needed updates to be updated, which is good. But forces the great majority of callers to declare a dep on the new version (or a range) and release a new binary, which is potentially very disruptive.
Long-lost friends
OpenIDE-Module-Friends lists can easily include obsolete entries, since there is no check for unused friends. The entries which are netbeans.org modules are useless, since you can just look them up using the golden file; those which are external modules are potentially useful if you want to confer with external module developers about possibly incompatible changes, but it is not necessarily clear whether such friends still exist, or even where they live. For example, org.netbeans.modules.scala.project has been moved around, org.netbeans.modules.fortress.project is essentially dead, and org.netbeans.modules.javafx.dataloader is gone, so the declared friend list for org.netbeans.modules.gsf is no longer very useful.
OSGi translation
Creating OSGi equivalents of module dependency declarations is challenging when the major release version is involved, resulting in hacks like translating NetBeans 1.1 to OSGi 101.1.
Friend packages are not possible in OSGi mode; they are treated as public.
Implementation dependencies are also not available in OSGi mode, so modules with an integral impl version are simply treated as exporting everything.
Proposal: package stability classifications
Rather than forcing a module to declare a single stability level for its entire exported surface, permit individual packages to be separately marked as stable, somewhat stable, or not stable at all. Drop the explicit list of friends. Enforce a uniform, intuitive version range model that matches these expectations; but provide a graceful way to deal with the relatively rare case of a dependency falling outside that range.
Marking stability of export
API Stability lists various stability classifications for APIs. We should permit a module developer to explicitly indicate on each package their expectations for its stability over time.
One attractive option is to mark this right in the source code, as suggested in MNBMODULE-148. The advantage is that the metadata stays close to the sources, and (with @Documented) becomes part of any generated Javadoc. For example, in package-info.java:
@Exported(Stability.STABLE) package org.netbeans.api.something; import org.openide.modules.Exported; import org.openide.modules.Stability;
where Stability could also be (say) DEVEL, or PRIVATE (the default if unmarked).
The build harness might need to collect stability classifications for the packages in the module and summarize them in the generated manifest; that depends on how they are consumed by importers and the module system (below).
TBD how to deal with binary packages included in a library wrapper module, which obviously could not be annotated in this way. Perhaps these could be listed manually in the source manifest in some way, or passed to the build harness.
A more conservative change would be to keep OpenIDE-Module-Public-Packages with its current meaning (assuming OpenIDE-Module-Friends is deprecated); and add OpenIDE-Module-Devel-Packages. A module could export public packages, devel packages, or both (but they may not overlap).
Marking stability of import
The next step is to determine what kinds of APIs a module is importing. Assume that major release versions and implementation versions are both deprecated (OpenIDE-Module-Build-Version taking over the informational role in the log file sometimes carried by OpenIDE-Module-Implementation-Version today), leaving the specification version as the sole determiner of API compatibility. (It is already the sole indication of an "upgrade" from the standpoint of Auto Update.)
For each exporter, i.e. module being compiled against, collect a list of packages actually being used. (See below about constants.) Pick the least stable such package, and include a dependency clause in the generated manifest according to the exporter's name, the exporter's current spec version (see policy below), and that minimum stability. Unlike current module dependencies, the stability would result in an implicit or explicit closed-open version range. Support the exporter is m 1.1 (~ 1.1.0); then
- stable -> [1.1,2.0)
- devel -> [1.1,1.2)
- private -> [1.1,1.1.1)
Thus a use of a stable (or "official") API would have a similar effect as a spec version dependency today (with no declared major release version range): 2.0 would be considered to break compatibility for the official API. This is similar to the conventions used in Semantic Versioning. Please note there is also semantic versioning defined by OSGi guys expressing this kind of proximity as well.
For a devel API (roughly comparable to friend packages today), routine trunk development could include incompatible changes if convenient, so long as the spec version is updated and importers are updated to match; patches made to a release branch would be assumed compatible for importers, so only the edited module needs to be published on Auto Update. In the case of private packages, it is assumed that any specification version change, even patch updates, might involve incompatible changes.
Note that there is no explicit friend list, so any external module developer is potentially on equal footing as far as using APIs which are not official but are in practice stable enough to be useful.
It is TBD what form this new dependency metadata would take. The most conservative approach is to keep the current header but permit the dependency clause to be richer, perhaps using a range syntax:
OpenIDE-Module-Module-Dependencies: org.openide.nodes ~ [7.2,8.0)
Another possibility is to begin using the OSGi header, which already supports this:
Require-Bundle: org.openide.nodes;bundle-version="[7.2,8.0)"
TBD whether the module system would accept arbitrary version ranges, or only the three specific kinds generated above: [x.y.z,x'.0.0) or [x.y.z,x.y'.0) or [x.y.z,x.y.z'). If restricted, then some non-range-based syntax could be devised, e.g. "1.1+" vs. "1.1.0+" vs. "184.108.40.206+" in the example above.
Handling possibly broken dependencies
(In this section we assume that an API developer updates the spec version of a module in accordance with the stability level of the package being changed; see policy below.)
Since incompatible API changes do happen, and on occasion an importer would actually be broken by the change, we want to ensure that a user is never offered a new or updated module which begins throwing linkage errors when it is loaded.
(You might think that a broken module would just throw one such error and then "stop", but this is not so. A module may have many functional entry points, and some may be invoked very frequently, not necessarily in response to an explicit user gesture. For example, an editor hint which made use of an unlinkable utility class could throw a fresh exception every time the editor pauses for a rescan!)
Conversely, since most incompatible changes do not affect most callers, we do not want to gratuitously prevent a user from loading a module which in fact would work fine just because the version numbers do not match.
The solution is to degrade gracefully. If the (spec) version of the exporter is within the importer's requested version range, permit it to be loaded as now without any further ado - trusting that versions have been updated in a compliant way. If it is older than the lower end of the range, mark the importer as unloadable, as now - the user should look for a newer version (usually one would have been offered by Auto Update anyway, or they are simply using too old a platform).
If the exporter's version is newer than the upper end of the importer's range, rather than immediately marking the importer as unloadable, go through all the classes in its module and try to resolve them. If any have linkage errors, mark the importer as incompatible as we do today and refuse to enable it; if not, go ahead and load it, while logging a warning. There are a few subtleties here:
- While this situation can be expected to be relatively uncommon, forcing resolution of every class in the importer during every startup is probably too expensive. Could be solved by caching the "known-good" state, with the cache to be invalidated on a subsequent startup if either the exporter or importer is changed.
- Once a class is resolved, it remains referenced by its class loader for the rest of the session, consuming valuable PermGen heap space. It may be feasible to use a special "throwaway" loader for doing these checks, so that no extra memory is permanently consumed.
- The JVM's binary compatibility specification perversely considers it compatible for an implementer of an interface if a method is added to the interface. Since this will still result in NoSuchMethodError's at runtime if called, which are just as unacceptable as any other linkage error, the compatibility checker would need to explicitly ensure that all methods from all nominally implemented interfaces are in fact implemented.
- Loading a class does not actually force resolution of everything used by all of its members. http://stackoverflow.com/a/9188781/12916 indicates that JustIce in BCEL works best.
- It would be desirable to check the existence of Java members referenced by XML layers (via newvalue and methodvalue attributes), since these often refer to factories in API modules.
- Usages of compile-time constants would not be detected; see below.
- Classes in Class-Path extensions often have unmet "optional" dependencies, so probably only the main module JAR should be verified.
The result is a balance of several objectives: the same startup performance as today for the usual case that everything is compatible; the ability to load potentially incompatible plugins at a small cost if they are not really broken; and a more or less polite way to refuse to load plugins which look like they are broken and need to be updated.
Behavioral API changes
This system only covers incompatibilities at the level of Java signatures; it does not handle incompatible changes to the behavior of methods, or to extralinguistic contracts such as XML layer locations or system properties. On the other hand, this may not be so bad:
- Most of the ways in which modules communicate with one another is through regular Java binary interfaces.
- Changes to behavior can be accompanied by changes in signature, which makes it clear at the language level what is different. In fact it is often possible and desirable to expose complex semantics in the Java signature, where it can be managed using common tools like Javadoc, Find Usages, and so on.
- If such contracts do get broken, the consequences are generally not as dire as a linkage error. The plugin might not work well or at all, but it is unlikely to ruin the whole application by throwing constant exceptions or the like.
Compile-time constants
Detecting packages in use by a build-time dependency could be done at the source level, but much more easily in bytecode after compilation. The main difference is that compile-time constants - static final fields of primitive or String type whose initializers follow certain restrictions - are inlined by current versions of javac, losing information about the source dependency. Uses of constants would also not be visible to a linkage checker.
Possible workarounds:
- Detect usages of constants in source code. Does not help with the linkage checker unless these are also recorded somewhere in the JAR.
- Try to get javac itself to stop inlining constants - perhaps a request for a JLS change with -target 8, but not viable in the short term.
- Force the field to not be initializable as a constant, so the caller's bytecode must refer to it. (Signature checkers could warn about fields with the ConstantValue attribute.) One downside is that you lose the ability to see the value of the constant in Javadoc. Possible by wrapping constant values in:
private static <T> T id(T t) { return t; }
This issue may not matter much anyway, since if the constant is inlined there will be no runtime reference either. The case of interest is when an API developer wishes to change a constant, which is typically an incompatible change that ought to be treated as such. In many such cases other parts of the API signature will be changed incompatibly as well.
TBD what the best way would be to transition from the current state. The module system should still be able to handle legacy release and implementation versions, and both impl and legacy (non-range) spec dependencies, and the generic build harnesses (both Ant and Maven) should continue to support legacy mode; but we would want to begin using the new convention for all netbeans.org modules and their interdependencies.
For modules declaring no major release version today, probably this is easy: deps on "m > 1.30" just switch quietly to (e.g.) "m ~ [1.30,2)" and keep similar semantics. OpenIDE-Module-Friends is dropped from the manifest, and the entries in OpenIDE-Module-Public-Packages are marked either stable or devel accordingly.
For modules declaring a major release version today, it is TBD whether that version should be dropped, or retained for compatibility with old external modules but ignored when creating new-style dependencies.
The relatively rare major release range dependencies can simply be replaced with a plain module dep (i.e. on the current version).
OpenIDE-Module-Implementation-Version would be removed from all modules explicitly declaring one (probably this should be made into a build error in projectized.xml if present), and all impl deps converted to plain module deps after ensuring that the packages actually being used are marked as devel. (Or, if appropriate, moving the necessary elements to a new devel package.) spec.version.base=1.5.0 would be converted back to plain OpenIDE-Module-Specification-Version: 1.6 (and again its usage should be made a build error for netbeans.org modules).
Conventional version numbers
TBD whether the current netbeans.org convention of x.y in trunk and x.y.z in release branches is compatible with this proposal. Using x.y.z in trunk would be more comfortable, since an update to x.y.z' could be used to push fixes to AU and/or mark a compatible change to a devel package. (Tracking compatibility of changes to private packages is probably unwieldy.)
Unfortunately that would not be compatible with the current convention for release branches, in which versions start at x.y.1, go to x.y.2 for the first patch or minor release, and so on. Either we could accept release branches being cut from x.y.z and the first release being x.y.z', etc.; or update to x.y'.0 in trunk, cut the branch (using initially x.y'.1), then update again in trunk to x.y".0.
Recording baseline version
#70917 in the Ant harness would mean source projects would no longer need to explicitly state the version of each dependency, which is very often wrong (usually too old) anyway.
CompatibilityPolicy#Versioning_impact could be simplified this way: when making an incompatible change, you would simply update the first component of the affected module's spec version, and that is all. Other modules in the same source tree would automatically begin to request the new version, so no patch to them would be needed, nor would they need to have been "prepared" using major release version ranges. Externally hosted modules would incur the one-time cost of a compatibility check unless and until recompiled against your new release.
In the case of the Maven harness, the exporter is picked out of the repository by the given version and compiled against, so it makes sense to just declare that as the base version. (Maven syntax actually permits version ranges, but these are useless for our purposes as they will result in the newest match being added to the compiler's classpath, whereas we would want the oldest.)
Permitted dependencies inside netbeans.org sources
The netbeans.org build harness (projectized.xml) should simply prohibit any dependencies on private packages. This means that the generic harness should have some configurable minimum stability level for all dependencies, below which package usage results in a build error.
The nbms-and-javadoc Hudson job already publishes a "golden" file [1] listing friend dependencies. The same format could track dependencies referring to devel packages.
Signature testing
A build harness could try to enforce change policy using signature tests. Currently the Hudson jobs permit any compatible change, sending a report from nbms-and-javadoc; and forbid any incompatible change relative to the last release.
For purposes of this proposal, it would be better to permit any compatible change so long as the specification version is incremented, and also any incompatible change so long as the spec version is incremented in the appropriate digit (according to the package's declared stability level), reporting either kind of change in nbms-and-javadoc. Doing this from the Maven harness would be easy enough (since older releases of a plugin are available in the repository), but it is trickier in an Ant build since you would need to somehow retain the signature file from the previous version.
Together with #Recording_baseline_version, a corollary is that making potentially incompatible changes to devel APIs would be both easier and safer than it is to do so today on friend packages. If you forget to update the spec of the exporter, sigtest complains. If you update the exporter but forget to update the spec of each importer affected by the change, the diachronic consistency test will complain. If you update specs of both exporter and all affected importers, everything will be fine, because the new importers will automatically request the new exporter, and unaffected importers will be found linkage-compatible at runtime. The same is true for incompatible changes to stable APIs, though of course these should be much rarer.
(This assumes that ConsistencyVerifier, used by the diachronic consistency test, performs the same linkage check as the module system would during startup: i.e. a dep on an exporter which is newer than the high end of the range should be permitted iff it in fact links.)
Usage warnings
When building an external module, i.e. the harness default when not used in netbeans.org sources, deps on private packages should be permitted but issue a warning. Deps on devel packages might merit an informational note but not a warning.
The Whitelist API could probably be used to warn the developer about usage of private APIs right in the Java editor: bug #201453.
The current tactic of compiling against build/public-package-jars/*.jar in the Ant harness would have to be dropped - the full module should be placed in the classpath instead. Note that this means that annotations using validateResource will begin permitting resources from non-API packages of other modules, which is not ideal but it does more closely match runtime behavior. The Maven plugin currently enforces public packages after compilation only, by emitting an error if needed; of course this would be switched to creating a dependency range.
(Alternately, permit deps on stable packages only by default, and force the user to explicitly enable deps on devel or private packages. This could be done in project.xml for the Ant harness, or plugin configuration for Maven.)
The current Add Dependency dialog for the Ant harness differentiates "API" from "Non-API" modules based on the existence of public packages, or friend packages for which the proposed importer is in fact a friend. This would probably need to be relaxed so that any module offering either stable or devel packages would be offered in the "API" list: by using one of the devel packages, you just create an accordingly limited dependency range.
TBD how the Maven plugin's current split between the org.netbeans.api and org.netbeans.modules group IDs should be modified; see: MavenNBM4#Dependency_management_and_project_structure
OSGi impact
When using NetBeansInOSGi, the MakeOSGi task would be able to directly translate NetBeans version range dependencies to Require-Bundle entries. An OSGi container would simply lack the graceful fallback for out-of-range dependencies. This would help align NetBeans and OSGi dependencies more closely.
OSGiAndNetBeans#Runtime could be simplified in the same way; unnatural dependencies like [2.1,100) would become the natural [2.1,3.0).
It is noteworthy that section 3.7.3 "Semantic Versioning" of the OSGi r4 4.3 specification describes a similar policy for version ranges, except that rather than stable or devel packages, it discusses consumer and provider APIs, which might be mixed together in a single package or even class (effectively precluding any automated way of determining who might be broken by a given signature change). Also the OSGi specification reserves micro-digit changes for those which "do not affect the API" but does not specify whether API changes compatible for both consumers and providers may increment just this digit.
Jigsaw interoperability
In the future it may be necessary to interoperate with Jigsaw (JDK 8 modules) in various ways - depending on JDK modules or third-party Jigsaw modules from NB modules, writing NB modules in Jigsaw format, or converting NBMs to Jigsaw format in batch mode. This spec is still under development, so the following discussion assumes something like the first draft, and omits various interoperability issues not relevant to package accessibility (such as how to define layer.xml locations).
Reducing module versions to just the specification version should simplify such efforts. Jigsaw supports version ranges in dependencies, albeit in more flexible form than proposed here.
Jigsaw offers "permits" clauses very much like NB's current friend packages. (#Mixing_public_and_friend_packages is possible using nondefault views with permits.) If present, Jigsaw itself would enforce the restriction. Permits would simply be discouraged in the case of NBMs written in Jigsaw format.
Jigsaw has a binary distinction between exported packages (or types within packages, though unlikely to be used in practice) and internal packages. Nonexported packages cannot be compiled against (when using javac in module mode), and are not accessible or even visible to other modules at runtime. This is clearly not a perfect match to the current proposal. Also, a module-info.java must specify version ranges of imports, preventing an NBM written in Jigsaw source format from taking advantage of automatic ranges as in #Marking_stability_of_import. (#Recording_baseline_version is irrelevant in this case since javac will compute the classpath according to module-info.java.)
The suggested policy for NBMs written as, or converted to, Jigsaw modules is that both PUBLIC and DEVEL packages be exported, though the @Stability annotation be retained; PRIVATE packages (whether so marked or not) should not be exported. For NBMs written in Jigsaw source format, this constraint must be verified somehow (using an annotation processor or some batch tool).
In the case of an NBM written in Jigsaw source format, the module-info.java should specify the desired version range of each dependency, e.g.
requires org.openide.filesystems @ >= 7.56 < 8; requires org.netbeans.modules.jumpto @ >= 1.28 < 1.29;
After compilation, some verification tool (run either in a per-module build script or in batch on a whole cluster or application) would check that all dependencies are either of the form ">= x.y.z < x'.0.0" or ">= x.y.z < x.y'.0"; and that for dependencies in the first form, no types from DEVEL packages are referenced. (Dependencies on JDK or third-party modules, i.e. those with no stability annotations at all, must be excluded from this check.)
For an NBM converted to Jigsaw module format, the translation tool need do nothing special - merely copy the version ranges recorded in the NBM manifest into the generated module-info.class.
In either case, importing PRIVATE packages would not be possible: such code would neither compile nor run, any more than code trying to use a package-private type from another module. Since using PRIVATE packages is a measure of last resort, and should be even less commonly needed when #Mixing_public_and_friend_packages is no longer an issue, this seems acceptable.
#Handling_possibly_broken_dependencies would be impossible in the case of an app running entirely under Jigsaw, except perhaps using some batch tool to retroactively expand version ranges in module-info.class after verifying binary compatibility. If running the NB module system with Jigsaw interoperation (akin to current Netigso/Netbinox), regular NBMs with dependencies on Jigsaw modules could benefit from runtime compatibility checks; whether native Jigsaw modules with too-old imports could be checked in this way as well would depend on whether Jigsaw exposes hooks for adjusting module metadata after parsing but before final resolution.
JEP #179 mentions that the JDK will include its own stability annotations.
Only stable packages should be published in Javadoc HTML form. These should carefully document all assumptions, include a changelog, etc.
Devel packages should include Javadoc comments but need not carry a changelog. A potential importer is expected to have access to the source code, so there is no need to publish HTML documentation (code completion popups suffice).
Documenting private packages is senseless except for comprehension by the module's own developer(s).
Entries in nbbuild/build.properties related to Javadoc (config.javadoc.*, javadoc.packages) could be dropped, as well as any module.javadoc.packages overrides; the build-javadoc target would simply run the javadoc target on all modules in the cluster config; a module with no stable packages would do nothing, and a module with some stable packages would create a documentation set for them (ignoring any additional devel or private packages).


text:
I can now shop till I "frock".....in comfort and style!
Thanks Nike ID.
Recent Posts
Wednesday, 3 November 2010
"Say hello to my leedl' friend..."
Posted by Reem Adeeb
This is about fashion, gossip and trends...sometimes it is more about travel,good food and where to eat it... but most of all,it is about humour with a pinch of sass.
Recent Posts
Copyright © 2009 frockanrolla, Powered by Blogger
CSS designed by Mohd Huzairy from MentariWorks
Blogger Templates created by Deluxe Templates


text:
From Homestar Runner Wiki
(→Inside References)
(undid revision 634687;The VCR has always been blinking 12:00)
|Line 263:
|Line 263:
*This contains another mention of [[pants]], [[underwear]], and [[showering]].
*This contains another mention of [[pants]], [[underwear]], and [[showering]].
*New Paper performed a calibration test because it was running out of ink, as stated in [[mini-golf]].
*New Paper performed a calibration test because it was running out of ink, as stated in [[mini-golf]].
===Real-World References===
===Real-World References===
Revision as of 19:00, 9 March 2009
|Strong Bad Email #176
Strong Bad helps John with his hygiene video problem with some help from Embarrassing Educational Films.
Cast (in order of appearance): Strong Bad, Homestar Runner, Strong Mad, Coach Z, Bubs, Pom Pom, The Sad Kids, Strong Badman (Easter Egg), Moth Mouth (Easter Egg)
Places: Computer Room, The Classroom (Easter egg)
Computer: Lappy 486
Date: Monday, August 27, 2007
Running Time: 4:06
Page Title: Lappy 486
DVD: strongbad_email.exe Disc Six
STRONG BAD: Step 1: You check an email down! Step 2: You tell some kid he's a dork!
subject: hygiene movie
Dear Strongbad,
In 5th grade I have to watch a lame hygiene movie. I was thinking you could make a better movie about hygiene than the cruddy school version.
Your friend,
John Katulla
{Strong Bad pronounces "Katulla" as "Katulalalalala"}
STRONG BAD: {typing} Fifth grade boys?!?!! Man, what happened to the hot college girls that used to email me? You ladies stop your be-pantied pillowfighting and drop me a line!
{clears screen}
STRONG BAD: Yeah, I suppose I could make a cruddy hygiene movie for you, John. But wouldn't it be so much more satisfying to make a cruddy hygiene movie about you?
{Cut through static to a blue background. Disco music plays. Yellow letters saying "Embarrassing Educational Films" fly into frame. Afterwards, the "E", "E", and "F" in the title light up and the word "presents" appears below them. Then we cut to another blue background with yellow letters that say "LESSON 1: SAY 'HI' TO HYGIENE"}
STRONG BAD: Meet John...
{The Text "john" appears and Homestar Runner as John pops up looking very dirty and unkempt}
STRONG BAD: John is a cruddy 5th grader. Hi, John.
{The Text "hi" appears over the text "john"}
HOMESTAR RUNNER AS JOHN: I'm a latchkey champion!
STRONG BAD: Meet Gene...
{The text "gene" appears. Strong Bad as Gene slides in. He has stylish blonde hair and a pink shirt.}
STRONG BAD: Gene is a beacon of light—
{Shows Gene in a lighthouse with the lighthouse shining. The lighthouse grows smaller and enters a stink cloud made by John}
STRONG BAD: —shining through the stink cloud generated by John. Hi, Gene.
{The Text "hi" appears over the text "gene"}
STRONG BAD AS GENE: TGIG y'all. Thank God I'm Gene.
{Cuts to Gene standing or floating next to Strong Mad, Coach Z, Bubs, and Pom Pom, all having the same hair as Gene}
STRONG BAD: Gene is popular and doesn't get good grades.
{Shows a Fridgin'-A brand refrigerator with a piece paper reading "G-, but sooo charming". Cuts to a closeup of John}
STRONG BAD: John has no friends—
{Shows John sitting in a desk surrounded by two empty desks}
STRONG BAD: —and sits in the front row.
{Cuts to John in a light brown box and Gene in a light blue box}
STRONG BAD: What is John missing that Gene has? Besides rich parents...
{Three bags of money drop in front of Gene}
STRONG BAD: That's right, hygiene!
{"HYGIENE" appears. Cuts to a closeup of Gene}
GENE: Hi, gals.
STRONG BAD: Hygiene—
{A dictionary pops up. A note is taped over the definition of hygiene}
STRONG BAD: —is defined as how close people are willing to stand next to you.
{Cuts to a closeup of John's chest, with his star bent}
STRONG BAD: John wears shabby clothes that smell like chocolate milk—
{A chocolate milk carton with a thermometer in its mouth and squinted eyes pops up}
STRONG BAD: —with a stomach virus.
{John blows his nose on his star. He puts it back on. It has boogers on it and slides downwards. Cuts to Gene in front of the "Big Ol' Mall". Two bags fall in next to him, reading "styles upon styles"}
STRONG BAD: Gene's mom buys all of his clothes, but she is young and hot enough for that to be okay.
{An exaggerated feminine hand with a ring emerges from the left. The hand is holding some keys.}
GENE'S MOM: {voice} Mommy's got a grown-up headache, Gene. Why don't you take the boat out for a while?
{Gene eagerly reaches for the keys. Cuts to a bathroom and John walks in. He briefly holds up a washcloth and a bar of soap before dropping them.}
STRONG BAD: Every morning, John wakes up and forgets to wash his stupid—
{Cuts to more of a closeup of John's face. It gets closer and closer and closer}
STRONG BAD: —dumb, stinking, {yelling} fat, smelly, stupid, du—
{The screen displays static, then cuts to a closeup of Gene's face, radiating energy}
STRONG BAD: Every morning, the radiant energy from Gene's face—
{Gene attaches two electricity generating wires to his cheeks, connecting them to a red light bulb on a pad}
STRONG BAD: —powers a small light bulb.
{The light bulb makes a buzzer noise and lights up. Cuts to a closeup of John's face}
STRONG BAD: John's mouth is an ecological trainwreck.
{John opens his mouth, which has a spider web in it. Stink lines come out of it. Black liquid drips from his mouth}
STRONG BAD: And has a nest of rare South American moths living inside it.
{John burps and a moth flies out of it}
JOHN: Now you be back before din-din, Chauncey.
{Cuts to Gene's face. His mouth is shining}
STRONG BAD: Gene's mouth is a national park...
{A sign pops up showing a smile, two trees, two mountains and the words "Gene's Clean Mouth National Park". It also has the same hair as Gene's on top.}
STRONG BAD: And his saliva is sold—
{Gene spits and it forms into a bottle that says "El Gene's Spit" over South America}
STRONG BAD: —in South America as a wonder drug.
{Cuts to John's room. John is sitting on his bed. There are milkshakes, french fries and bowls of cereal scattered all around the room}
STRONG BAD: John leaves food out all over his room.
{Scrolls around the room. Cuts back to the middle}
STRONG BAD: And a family of squatters have taken up residence in a nearby laundry cave.
{Shows The Sad Kids standing in front a pile of laundry carved into a cave. Cuts to Gene's room with a pennant saying "A sport!" and a wardrobe}
STRONG BAD: Gene's Room has a sixteen car pile-up of race car beds.
{Shows sixteen race car beds stacked on each other. 5 special effects artists with "THX" on their chests and 5 maids appear above the pile of race car beds}
STRONG BAD: And a family of 10 maids and special effect artists keep it realistically smoldering and burning.
{The pile of race car beds catches fire}
STRONG BAD: Oh, they also live in a nearby cave.
{Shows the five maids and five special effects artists standing in front of a cave waving. Cuts to a tube and two jars of cream, powder, and paste}
STRONG BAD: What can John do to change his hygiene?
{Cuts to John dropping the tube and two jars}
STRONG BAD: Nothing at this point. {John looks shocked} By fifth grade the damage is already done.
{Shows a pie chart with the Heading "What 5th Graders Remember You For". "Your Stink" is the biggest section, "Your Stonk" after that, followed by "Hot Mom", "Video Games", and "Cool Headband"}
STRONG BAD: And everyone will remember him as a smelly loser no matter what he does.
{Cuts back to John. Two pennants appear reading "Out of State U!" and "Go Non-Residents!"}
STRONG BAD: He'll probably have to wait and go to an out of state college, where he can reinvent himself.
{John transforms into a more typical-looking Homestar, with a small beard and a college shirt reading "OoSU Non-Residents"}
JOHN: Hooray.
{Cuts to Gene}
STRONG BAD: Gene, on the other hand, better keep up the status quo. {a hand starts poking him} If he slips up the slightest bit, and gets lice {shows his hair with lice jumping up and down}, or has an accident at school, {Gene covers his pants with his hands. Cut to Strong Mad, Coach Z, Bubs, and Pom Pom, all with menacing eyebrows and bright blonde hair. The camera slowly zooms in as the background turns red and the music becomes menacing.} those fifth graders will just descend on him like a ravenous {Cuts to Gene, looking nervous} pack of hygiene wolves. And tear him to shreds.
GENE: Hooray...? {Gulps}
{Cut to Gene standing next to the words "bye gene".}
STRONG BAD: Bye, Gene!
{Cuts back to the blue background. Disco music plays again. Yellow letters saying "Embarrassing Educational Films" fly into frame. Afterwards, the "E", "E", and "F" in the title light up and the word "presents" appears below them. Then we cut to another blue background with yellow letters that say "LESSON 2: PANTS PROBLEMS". Cuts through static back to the Lappy}
STRONG BAD: {typing} Okay John, all done. I hope your classmates like my video. And don't worry, in 8 or 9 years you can just hide behind your new identity as a raver, a greaser, or a whatever ancient Egyptian teenagers called themselves. Now get outta here! None of the college hotties'll show up if you're hanging around, Mothmouth.
{New Paper comes down, showing alternating colors below the words "Calibration test". "Click here to email Strong Bad" is nowhere to be seen.}
STRONG BAD: You know, New Paper, you keep sucking just enough to stay interesting.
Easter Eggs
- At the end, click on "whatever" to see what Coach Z thinks of Strong Bad's video.
- {Coach Z and Strong Bad are in the classroom. Strong Bad stands beside a TV stand. The television reads "Embarrassing Educational Films". Coach Z is sitting on a chair in front of the TV.}
- COACH Z: I love it! Where can I get me some of this hygiene?
- STRONG BAD: You know, for a guy that lives about ten feet from a bunch of showers, you'd think you'd be a little more familiar.
- COACH Z: What showers?
- STRONG BAD: Uh, that big tiled room with all the shower heads coming out of the wall?
- COACH Z: I thought thems were my drippy broken speakers! I got mad four-inch tweeters, B!
- At the end, click on "ancient" to see a tribute to Matt and Jackie's recently deceased cat, Mabel.
- At the end, click on "Mothmouth" to see a Strong Badman comic cover about Moth Mouth.
Fun Facts
- A calibration test is a test performed on many color printers to help the user adjust the colors it produces, and aid alignment of the heads of ink or toner cartridges.
- Tweeters are speakers designed to produce high-pitched frequencies.
- A raver is a person who goes to raves, all night parties which often feature illegal drugs. These parties and the music associated with them peaked primarily in Europe in the early 1990s.
- Greasers were a subculture that originated in the 1950s and saw a revival in the 1970s. Their distinguishing characteristics were jeans, leather jackets and slicked back hair.
- Gene was popping his collar, a popular trend among the preppy social classes in the mid-1980s and early 2000s.
- John's line "I'm a latchkey champion" refers to latchkey kids, a term applied to children that are often left alone in the house.
- TGIG, or "Thank God I'm Gene", comes from the acronym TGIF, or "Thank God It's Friday".
- When Gene's mom mentions a "grown-up headache", she is most likely referring to a hangover.
- The printed definition of hygiene obscured beneath the handwritten one is: "Conditions and practices that serve to promote or preserve health", which is the second definition listed in the American Heritage Dictionary.
- Most of the time during the hygiene video, Strong Bad as Gene is seen smiling, as well as 5th grade Strong Mad.
- The summary for the Podstar Runner RSS feed reads, "Strong Bad and Embarrassing Educational Films present a movie on hygiene for some 5th grader."
- At the end, the New Paper prints out a calibration test resembling that from older HP DeskJet printers. However, you can still click on the lines to email Strong Bad.
- Coach Z has been seen taking a shower before in the second deleted scene of In Search of the Yello Dello, making reference to "showering up" in the email flashback (which may or may not have actually happened), is later seen taking a shower in Jibblies 2, and having the world record for "longest time without shower" (implying that he has showered before).
- Coach Z also claimed to be "lookin' out for all yer hygienes" in senior prom when adding Listerine to the punch, so he is familiar with hygiene.
- The floppy disk Strong Bad put in the New Paper in the previous email is no longer there.
- When John blows his nose on his star, his tongue is visible.
- During the week of this email's release, there was both a "new strong bad email" Main Page Message for this email and a "strong bad email" Message for the one that preceeded it.
- When John's hat is backward, part of the bottom of the bill is cut off.
- When John looks in the mirror, his reflection blinks a split second after his counterpart.
- When the camera zooms in on Gene when all the fifth graders descend upon him, Gene's hairdo sinks behind his head slightly.
Inside References
- The way Strong Bad pronounces John Katulla's name is a reference to retirement.
- The cat seen in the Easter egg is Mabel, Matt and Jackie's pet, who was previously seen in website.
- John's room is littered with bowls of crispy puffed-rice cereal, last seen in candy product.
- Also in John's room, there are baskets of fries and a Melt Shake.
- Gene's shopping bags are marked Styles Upon Styles.
- Coach Z uses Homestar's TeeBee to watch the film.
- A bug previously took residence in Homestar Runner's mouth in Bug In Mouth Disease.
- "Stonk" was a word originally heard in the Quote of the Week of December 7, 2006.
- John's laundry cave uses the same sweatshirt designs as Homestar's Swe atshirt Float from Fall Float Parade.
- Race-car beds were previously mentioned in Marzipan's Answering Machine Version 10.2 and secret identity.
- Gene's grade of G- is a reference to the letter G.
- This contains another mention of pants, underwear, and showering.
- New Paper performed a calibration test because it was running out of ink, as stated in mini-golf.
Real-World References
- THX is a set of high-end criteria for audio reproduction - predominantly used in movies. It is a trademark of Lucasfilm.
- The video parodies a style of educational film known as Goofus & Gallant, where two characters are used to contrast good and bad social behavior accompanied by heavy handed narration. This style of film was most commonly used in the 1950s and 1960s.
- The Strong Badman Easter egg is an homage to the cover of Uncanny X-Men #28.
- The Styles Upon Styles bags are based on the department store Bloomingdale's shopping bags, which they call "brown bags".
Fast Forward
- In pizza joint, Strong Bad makes an ecstatic reply when he receives an email from "a typical college girl".
DVD Version
- All the Easter eggs are missing from the end.
- The DVD version features hidden creators' commentary. To access it, switch your DVD player's audio language selection while watching.


text:
Learn what it's like to work in our Sydney HQ.
We (heart) Sydney
Walk into our beautiful heritage office in Sydney and you might wonder how this collection of cutting-edge thinkers and talented tinkerers ever ended up amongst the marble and mahogany of one of the CBD's oldest buildings. But we love life's little contradictions. And we're passionately building something of our own inside, every bit as unique as our sumptuous surroundings.
Atlassian is a community of creative, hard-working people hell-bent on making cool things together. In Sydney, our designers, engineers and growth hackers–from over 30 nationalities–combine to chase down the ultimate experience for our customers. And despite the onsite fitness, bike repair and towel service, working with awesome people every day is the best perk of all.
Crash our Big Bash
Hear ye, hear ye: to all who harbor a secret desire to don chainmail, joust, sword fight like a knight, "test" a cure for black plague, or consider a go on the rack. Game of Codes (aka Big Bash) is a play land designed to satisfy your fix for all things medieval.
Sometimes, Harbour cruises
At Atlassian, there's a sense of mateship that gives us something special and makes us (officially!) one of Australia's Best Workplaces. From card games to footy, circus classes to full-scale carnivals, and even our annual Melbourne Cup celebration we like to have fun. All in a decidedly non-corporate environment where sockless feet are more common than sensible shoes.
Are you keen on...
From snacks and drinks to yoga and group exercise, we take our office "perks" seriously. And, with bike repair, sit/stand desks at the ready, and flexible working arrangements available when needed, it's our goal to make sure every Atlassian feels at home here.
Life in the CBD
The Sydney office is walking distance to the harbour. That means mid-day breaks under a banyan tree in the Royal Botanic Gardens, and coffee with a teammate on the steps of the Opera House. And for those with a heartier nature, you can even bike from the office to Bondi beach.
"We're the best place to work in Australia, and on top of that, the work you get to do helps millions of customers on a daily basis."


text:
DAR honors Ernestine Thompson
Description: Announcement for the reception when the Daughters of the American Revolution (D.A.R.) honored Ernestine Thompson with the Community Service Award at the W.H. Passon Historical Society on May 21, 2006. Ernestine collected artifacts for the Jacob Fontaine Religious Museum.
Date: May 21, 2006
Item Type: Refine your search to only Text
Partner: Jacob Fontaine Religious Museum


text:
"People who refuse to say what their band sounds like, I feel, are doing themselves a disservice," he said in a recent interview. "People are going to compartmentalize you in their brain, so you might as well do it for them with a term that you put out there."
And the term that Dave W. chose was "space rock," littering early promo materials for White Hills with the phrase to make sure the tag stuck. And stuck it has, but not necessarily because of Dave W.'s persistence, but because space rock is the perfect way to describe the band's psychedelic take on 70s fuzz rock and improvisation, combining elements of both Hawkwind and Can with an updated take.
White Hills was born out of Dave W.'s frustration with his music career, playing in various band in New York City, but not necessarily playing anything he actually wanted to hear. So he holed himself up in his apartment and recorded an album. (Dave W. and the rest of White Hills have since put out numerous homemade recordings, many of which are impossible to find these day – even Dave W. admitted to being unable to track down some of them.) Bassist Ego Sensation quickly joined the band, and the core of White Hills was set.
That was during the middle part of the last decade, and their first album, They've Got Blood Like We've Got Blood, caught the attention of Englishman Julian Cope, who re-released the album on his British imprint. In 2007, Heads on Fire was released on Rocket Recordings, and Glitter Glamour Atrocity quickly followed.
Earlier this year, White Hills made their debut on stateside label Thrill Jockey, releasing the self-titled White Hills. The album was recorded in Oneida's Brooklyn studio, The Ocropolis, and even features Oneida's Kid Millions on drums.
While Dave W. personally termed the music of White Hills "space rock," their music is actually hard to pigeonhole. While the band does dabble in long free-form jams, they are also capable of locking down a heavy riff, and every album the band has released has its own flavor.
"I'm very conscious about making the records sound very different from each other," said Dave W. "I don't want our albums to sound the same."
White Hills is probably the band's most far-ranging album to date, and represents a huge leap in defining the White Hills sound – a rare combination of heavy, powerful music that manages to meander and ramble and explore more far-flung concepts.
Because many of White Hills albums were released on labels overseas, the band has spent a considerable amount of time touring Europe, where Dave W. says audiences are generally more appreciative of live music, explaining that even if you play a small city in a European country, there's a good chance the entire town is going to come to the show.
"If you have the choice of playing Columbus, Ohio, to 25 people, or playing a small town in Italy that is the equivalent of Columbus, Ohio, but know that 250 people are going to come see you, you are of course going to play the podunk town in Italy," he said. "There's just a very different attitude to the arts in Europe."
That said, Dave W. said he is looking forward to playing in front of more American audiences. In fact, White Hills will be playing a show in Brooklyn on May 29 at Glasslands.
And according to Dave W., a White Hills concert is all about entertainment. While some bands prefer to play live versions of their records, Dave W. prefers to paint his face silver and put on a real show, expanding on the recorded versions of the songs and providing an experience for the audience that is separate from listening to their albums.
"There are things that you can do with an album that you can choose to either do or not do in a live show," he said. "I think the album and the live show are two separate things; the live show should be entertainment."


text:
A hacking contest slated for next month will award cash prizes of $10,000 to anyone who can break into the most popular smartphones, including Apple's iPhone and Research in Motion's BlackBerry.
The PWN2OWN contest, which will kick off March 18 at the CanSecWest security conference in Vancouver, British Columbia, will offer a dual-track hacking challenge for the first time, said Terri Forslof, security response manager at 3Com's TippingPoint, the contest sponsor.
PWN2OWN has made headlines in its two previous years for hacks of Apple's Mac OS X and Microsoft's Windows. But this year, the content will focus on mobile devices and Web browsers, said Forslof.
"Mobile is a new frontier of sorts," said Forslof. "We've seen mobile exploits in the past, but we still don't see a lot of focus in that area. More and more, people are taking computing on the go and rely on these devices for e-mail and accessing the Web. So it seemed prudent to have a look at them, and the contest is a good forum for that."
The contest will pit hackers against five smartphone operating systems, including Windows Mobile, Google Inc.'s Android, Symbian, and the OSes used by the iPhone and BlackBerry. The first to break into any of the five smartphones gets to keep that device with a one-year service contract, but each successful exploit pays out $10,000. TippingPoint, which operates the Zero Day Initiative (ZDI) bug-bounty program, and purchases the rights to the vulnerabilities and exploit code used during the contest, has not capped the number of bugs it will buy.
"We're not going to limit it this year," Forslof said. "In the first year, we had a one bug-one winner kind of contest. Last year it was sort of similar, although we offered three prizes."
PWN2OWN's second track will feature a battle between hackers and browsers on Windows and Mac OS X. Attacks against Internet Explorer 8 (IE8), which recently reached "release candidate" status, Firefox and Chrome will play out on a Sony Vaio laptop running Windows 7, while a MacBook will host Safari and Firefox on Apple's operating system.
TippingPoint will award cash prizes of US$5,000 for each browser bug successfully exploited, and give the targeted laptop to the first hacker who breaks into any of the browsers.


text:
Stunning blue stone was mined locally in Nevada and set in hammered sterling silver.
On the inside of the band is my logo which authenticates the originality.
Turquoise encourages conviction and personal power while purifying the chakras. It dispels negative energy and can be worn to protect against outside influences or pollutants in the atmosphere. Turquoise balances and aligns- stabilizing mood swings and instilling inner calm.
The ring size is 8
This piece is one of a kind and handmade.


text:
It's 7:30 a.m. and 65º. This morning will be cloudy and damp, but it will become mostly sunny by the afternoon. Details here.
San Francisco has banned public nudity, requiring those who bare all to pay a fine of $100 for a first offense and $200 for a second in a 12-month period. About time, or an attack on personal expression?
Today we begin a series called "Giving Thanks," a collection of profiles of places in the Mission that do great things for the community — places that we, and many others, are thankful for. Be sure to keep an eye on the series throughout the week, and let us know who you are thankful for this holiday season.
And finally, for a good laugh, check out these awkward family Thanksgiving photos.


text:
New user?
Provide your account email address to receive an email to reset your password.
You have no items in your Cart
in stock
For Winter, we have designed this season's most functional and beautiful outerwear… for your Stokke® stroller. The Winter Kit is a stylish way to keep your baby warm when temperatures drop. Your child will stay snug and protected from cold weather and wind, while enjoying the wonders of winter. We have been thinking of you as well; warm mittens that attach to the stroller handle with genuine sheepskin rims and soft fleece lining keep your hands toasty during your strolls together. The Winter Kit Collection for the seat of Stokke® Crusi™, Stokke® Trailz™ and the Seat and Carry Cot of Stokke® Xplory® includes sleek quilted detailing and is available in Pearl White, Onyx Black and brand new Bronze Brown. The textiles have a subtle shine for a sophisticated look. Our designers have carefully coordinated absolutely everything you need to stay warm and look hot this winter!
Not compatible with Stokke® Xplory® 6 or Stokke® Trailz™ Black.


text:
Volunteers drawn to opportunity to transcribe history
The Earl Gregg Swem Library is commemorating the 150th anniversary of the end of the Civil War in a very special way, and with a little help from their friends. Librarians and volunteers will transcribe 3,000 to 5,000 letters, diaries and other documents from the Era for a project called "Fights to Rights: The Long Road to a More Perfect Union".
"When you're in the middle of a Civil War, you know you're a part of a big event, so a lot of families kept their documents," said Susan Riggs, manuscripts and rare book librarian at Swem Library. "It's not something that you look back on and think, that was probably important. They knew they were in the middle of something important."
Started July 1, the project has acquired more than 200 volunteers. Still, many more are needed to help the library reach its goal of completing the project in 2015.
"Volunteering is as simple as picking the document you wish to transcribe on the Swem website," said Amy Schindler, university archivist. "People can see the images of the documents in either a black and white PDF or a color scan, and then they just pick, let us know, and get started."
The documents that are being transcribed have come to special collections from a variety of sources over the years. Some they have purchased, but a lot have come to the College via donation. Upon arrival, the documents are uploaded to a database on the Swem website so those interested in volunteering can view them quite easily.
Once the transcription is complete, a volunteer at the library will check the text to make sure it is accurate and follows the guidelines found on the website. Once approved, the transcriptions are then entered into the database.
"So far, we have about 100 transcriptions finished," said Riggs. "We have about 55 students currently volunteering, as well as faculty and even people from other states. People have responded to our updates on Facebook and Twitter and we have folks from California, Texas and New Hampshire currently transcribing for us."
Two of the volunteers are a couple from Texas, Ann Woolley '75 and Mark Woolley '77. The couple has been transcribing for a few months now and has found that their family and friends love to help them untangle the sometimes hard-to-read cursive.
"Although the penmanship can sometimes be challenging to decipher, the detailed information provided is compelling," said Mrs. Woolley. "The project truly brings history to life."
Another volunteer, Mark Reardon, got involved in the project after reading a letter to the editor in the Virginia Gazette from Swem Library expressing the need for volunteers. Reardon is recently retired and was looking for something to get involved in that would satisfy his interest in American history. This project seemed to fit perfectly.
"All of these documents give a fascinating insight into the real life of people during the Civil War that cannot be gained from simply reading history books about battles and politics as written by historians," Reardon said.
Reardon and the Woolley's both agree that at times the documents are hard to read because they are faded and worn; however, both declared how rewarding and interesting the project is.
"The satisfaction of helping to make these documents available to the public is very gratifying," said Reardon. "The joy of reading what people living through this war a century and a half ago actually saw, believed, felt and said is very exciting."
"These letters fill in some of the details of daily activities and bring the life of the average citizen into focus," Mrs. Woolley explained.
Riggs and Schindler are hoping the volunteers will work on the project for several months or even years, and that more volunteers will join so that they can reach their goal of a 2015 completion date. And the work doesn't have to stop there. Once volunteers finish the Civil War portion of documents, they can leap forward in time to the documents from the Civil Rights Movement and begin transcribing those.
The "Fights to Rights" project is something very new to Special Collections. This is the first time they ever requested volunteers to help them transcribe old documents.
"The software available makes it possible to push the content out and ask people to help because it is something we do not have the resources to do alone," Schindler said. "By putting the documents online, we have really expanded our reach which is extremely important to us."
Information about the transcription project can be found on the Swem Library website. Find out more about "Fights to Rights: The Long Road to a More Perfect Union".


text:
- For the Storm Peaks NPC, see Goblin Sapper.
Goblin sappers are trios of kamikaze Goblins that were once deployed as ground troops for the Horde during the Second War, well versed in sneaking up to a fortress and setting off deadly charges[1] (DotD 64), as seen in Warcraft II: Tides of Darkness/Warcraft II: Beyond the Dark Portal, and Warcraft III: Reign of Chaos/The Frozen Throne.
The Goblin Sappers were known for their mischievous streak and aptitude for destruction and once the most lethal of demolitions groups known in the Horde. Even with the explosive reputation of Goblin Engineers, the Sappers were some of the first to bring Goblin explosives into wartimes and to utilize their instability successfully.
Sapper groups were first enlisted into the Horde during the Second War, despite their reluctance to obey orders and adhere to authority. They were composed of a group of three Goblins adorning bandoliers of dynamite and armed with barrels of TNT, detonators, and a vast array of other volatile explosives. The tactic of these demolition squads was pure suicide: trigger the destructive equipment while charging head-on toward the target or obstacle. Despite the mortality rate of the Sapper's technique, their specialty in destroying enemies, buildings, and even sheer rock is barely matched by Dwarven Demolition.
With the end of the Third War and the Neutrality the Goblins have taken, the need for Sappers has come to virtually a halt. It is possible that the only remaining Goblin Sapper teams that operate are for excavation purposes and that the newer generations of Goblins have harnessed their destructive capabilities towards mastering and teaching the technique of explosives through Engineering.
A great number of sappers - primarily goblin sappers - perished during the last war, mostly as a result of their overzealous use of too many explosives at once. Those who survived have become much more focused in their art, preferring precision to risks. Generally, the older a sapper is, the more careful and cautious he is - and the more respect his associates give him. Goblins are likely candidates for this class, since goblins like making things go boom! The Horde made heavy use of goblin sappers in the Second War; indeed, goblin sappers were a key aspect of the Horde's strategy. Thus, the Horde knows how effective this class can be. In an adventuring party, a sapper often takes the role of a rogue or ranged combat support. [2] (APG 58)
Warcraft II: Tides of DarknessThis section concerns content exclusive to Warcraft II: Tides of Darkness.
- For stats, see Warcraft II units.
The mischievous Goblin Sappers are known throughout the Horde for their incredible aptitude for destruction. These diabolical Goblins are invariably armed with extremely volatile explosives; which enable them to level enemy structures and weapon emplacements. Although the Sappers are highly unpredictable and insubordinate, they have become necessary to the plans of conquest maintained by the Horde.[3] (W2Man 74)
Warcraft III: Reign of ChaosThis section concerns content exclusive to Warcraft III.
- Main article: Goblin Sapper (Warcraft III)
Explosive Team of Goblin Sappers. Particularly effective against buildings. Goblin Sappers cannot be loaded into Goblin Zeppelins or Transports.
World of WarcraftThis section concerns content exclusive to Wrath of the Lich King.
- Main article: Goblin Sapper
There are a few Goblin Sappers to be found in Northrend, at K3 in The Storm Peaks. They are in the southernmost building, just standing around. Also notable is the nearby Sparksocket Minefield, west of K3... which is full of explosives, and explosions.


text:
Wednesday, December 7, 2011
Preschool Fun: Gingerbread Play Dough
8 comments:
Ah how sweet! And perfect for the Christmas season.ReplyDelete
Thanks for sharing on Kids Get Crafty!
I love the gingerbread playdough! It smells fantastic! I'm going to have to try making it with the boiling water, it would be so much easier!ReplyDelete
Sounds like something fun to try! Can you let it dry out like regular play-doh? Just thinking how cute their gingerbread men look...ReplyDelete
This is cute. Our elf is going to bring a gingerbread house for my son, so this would be a fun activity to go along with it.ReplyDelete
Love this!ReplyDelete
Pinned two of the photos from your post with direct links back to you on my Run, Run As Fast as You Can...board on Pinterest:
Have a happy rest of your week!
:) Colleen
Aww, those are adorable!ReplyDelete
Popping in from Play Academy Linky :)
They look so good that I can practically smell them through the computer!ReplyDelete
- AnonymousDecember 17, 2013 at 2:37 PM
The kids at our preschool really enjoyed this. If out too long it does seem to dry out a little, not sure what to add to it so it does not dry out so soon. Any suggestions???ReplyDelete
Thanks for taking the time to visit Mom to 2 Posh Lil Divas! I hope you will stay awhile to explore all we have to offer!


text:
Create a Ning Network!
554 members
Alex Marcelo has not received any gifts yet
Give a Gift
Join Tennisopolis : Tennis Social Network
Hi- I'm in your area, looking for match play, am a 4.0, but will play anyone if it's a good matchup. Call me if game... Michael 818 703 8415
Welcome toTennisopolis : Tennis Social Network
Sign Up (free)or Sign In
© 2020 Created by Mark / The Mayor.
Powered by
Badges |
Report an Issue |
Terms of Service
Please check your browser settings or contact your system administrator.


text:
What's new in CLZ Comics for iOS?
CLZ Comics (iOS)
v5.4.3: Fix for value fields
April 16th, 2020
- When a comic was edited, empty 'value', 'purchase price' and 'cover price' fields were set to 0.00.
Recent changes
Sneak Preview: version 6.0 of all 5 CLZ mobile apps! July 21st, 2020 v5.6: Better barcode recognition for older comics! May 29th, 2020 v5.5 New folder options for Creators and Characters May 14th, 2020 v5.4 Faster CLZ Cloud syncing! March 18th, 2020 v5.3 Easily add and report comics with "unrecognized barcodes" March 2nd, 2020 v5.2.1: Search folders, sort folders by count and and faster syncing February 20th, 2020 v5.1: Better barcode scanning! January 29th, 2020 v5.0.8: Added 4 new folder options and some fixes January 8th, 2020 v5.0.5: Several user interface improvements October 9th, 2019 v5.0.4: New: Statistics screen September 19th, 2019 CLZ Comics 5.0: Automatic values, more fields, multiple collections and more September 9th, 2019 v4.14.2: New design for resizable panels in Add Screen December 17th, 2018 v4.14.1: New for iPad layout: Resizable panels December 7th, 2018 v4.13.1: Redesigned app icon November 9th, 2018 v4.11.3: Moved some buttons to more logical places August 26th, 2018 v4.11: More editable fields! June 21st, 2018 v4.10.4: Bigger and easier to spot Add button! May 9th, 2018 v4.10: Many new sort options and a redesigned Select Sort Order screen April 13th, 2018 v4.9: Improved search features February 21st, 2018 v4.8.1: Automatic CLZ Cloud syncing! January 10th, 2018 v4.5.13: Further improvements to the Add Comics screen November 8th, 2017 v4.5.12: Optimized layout for iPad Pro October 19th, 2017 v4.5.10: Redesigned Selection Mode October 15th, 2017 v4.5.5: New preview templates and better navigation after adding June 11th, 2017 v4.5.2: New "Clear" templates added April 26th, 2017


text:
New boro trash fees amount to back door tax increase
January 13, 2009
In 2008 Mount Oliver homeowners paid the fourth highest tax rate of the 130 municipalities in Allegheny County (www.alleghenycounty.us/treasure/millmuni.asp). For 2009, Mount Oliver Council, with a sleight of hand and apparently some magic dust, announces Mount Oliver homeowners will have no tax increase (South Pittsburgh Reporter, November 25, 2008).
The problem with this is that in 2008 a homeowner with a house assessed at $40,000 in Mount Oliver paid $540 in borough property taxes including trash collection and in 2009 the same homeowner now pays the same $540 plus an additional $120 for trash collection. This is a "no tax increase" tax increase of 22.2 percent and now the highest tax rate in all of Allegheny County.
Property taxes received are allocated by mills for specific functions. Through 2008 certain mills were dedicated for general services and police protection. Other mills were dedicated for the Mount Oliver Volunteer Fire Department, street repairs and maintenance, and debt reduction. Additionally two mills paid for residential trash pickup. Each mill represents approximately $70,000.00 and this $140,000.00 ensured the collection of the fees for the trash service.
Years ago the borough attempted to collect quarterly trash service fees directly from the property owner. This proved not to work as a large number of property owners simply did not pay the trash bill. Trash collection fees were then added at the rate of two mills to the property tax bill to ensure collection.
For 2009 we are now back to the same unproven method of attempting to collect the trash service fees. It did not work then. Why should it work now?
If the same collection rates occur in 2009 as the borough experienced when it attempted to collect trash service charges in the past the situation gets even worse. Waste Management will insist to be paid by the borough regardless of how much is actually collected for trash pickup. The borough will not have enough to pay Waste Management. Then another "no tax increase" tax increase will be placed upon the homeowners.
The two mills, which had previously been allocated for trash service, have been removed from the 13.5 mill distribution for 2009 yet the tax rate remains the same. Where did the $140,000 that was previously allocated for trash service go?
If there is some spectacular new use for this $140.000 which greatly benefits the taxpayers let us all see it. We should all see where our tax money is being spent. If there is a reason the taxpayers are not going to be told where this $140,000 is going, do the taxpayers have to wonder if this is Mount Oliver Council's "bailout money" for financial irresponsibility?
If it is the latter, the only "bailout" for the borough is some day for the borough to become part of the City of Pittsburgh. And this has been discussed in recent years. "Bailout" the borough and there is no more council. No more police department. No more fire department. No more street department. And then where are we?
Our nation is in a recession and millions of American workers out of work. The private and public sectors are making hard decisions every day to keep costs under control and to survive. Most businesses and industries and almost every state, county, and municipality nationwide are making tough budgetary decisions including spending and personnel cuts. Yet it appears Mount Oliver has more employees and vehicles today than just a few years ago.
Clara asked, "Where's the beef?" I ask, "Where's the $140,000?"
Don Cornelius
Mount Oliver
(The writer is a former member of the Mount Oliver Borough Council)


text:
International Leisure
It's time for, to paraphrase Al Lowe's memorable line, the first videotape from his son's new kidnappers. How are the Leeds' very own Team 17 looking after Larry?
Wan… I mean, Thanks GameTrailers!
For the record, RPS' favourite Gears of War advert parody remains the one a mate of mine did a year ago.


text:
Stationery has historically meant a wide gamut of materials: paper and office supplies, writing implements, greeting cards, glue, pencil case etc. Originally the term "stationary" referred to all products sold by a stationer, whose name indicates that his book shop was on a fixed spot, usually near a university, and permanent, while medieval trading was mainly ambulant, by peddlers and othersat non-permanent markets such as fairs.
Stationery was a special term used between the 13th and 15th centuries in the manuscript culture. The Stationers Company formerly held a monopoly over the publishing industry in England and was responsible for copyright regulations.
Tags : sabari books and stationery , Office stationery, school stationery items & products, computer stationery wholesale, printable school stationary, Pen, Pencil, Rubber, Geomentary box, Scale, Note books, Dealer, Distributor, Whole sale supplier, Vendor, seller, sale, suppliers, school stationery manufactures / importers, children's stationery, stationery items shopping, school stationary items list , wholesale stationery, list office stationary, back school stationery


text:
Microsoft Boosts Dividend by 22%
Microsoft unveiled a $40 billion share buyback plan and boosted its quarterly dividend by 22%, continuing the shareholder-friendly moves it has pushed in recent years. Don Clark reports. Photo: AP.
This transcript has been automatically generated and may not be 100% accurate.
... the the ... it will boost its quarterly dividend by twenty two cents ... a sign that the tech giant is moving to please shareholders amid a flurry of change ... joining me now for some Cisco will Street dolls ... technology deputy bureau chief Don Clark ... Sean thank you for joining us on the show ... are there ... so it's it's not just a dividend increase is share buyback as well ... and to the question on everyone's mind is the will of this makes the investors happy ... but it certainly doesn't become said you know they had they like money they like that this gal people ... Micra soft is Ardi big pay out dividends ... that normal increase this time years about fifteen percent so twenty two percent ... is can assign Micra soft is coming going the extra mile here ... the comes amid ... shareholder pressure they had to give a board seat to ValueAct ... an activist investor ... that lot people thinking that though the company can do more and it's got a lot of money in the bank ... and why does have a lot of money and the bank and it has done very well historically ... on selling ... things to all the business is the supple be debated business to business ... cited side of things and now it sort of trying to stop opp and aunts that ... he can see my business plan it ... has had one success which is a state gaming console ... but it's also have a lot of failures like its tablets I'm it's it's fun again and other areas to write ... that's right and then they just announced a big deal to buy Nokia's handset business which ... will effectively puts them in the hardware ... and computer this is quite a big way in the consumer market ... and that which is a controversial move so ... good even doubling down on the consumer device bets and that it's a controversial play ... and it is a controversial plan ... I'm it's one am lacking in its consumer business this ... selling things to consumers they really happened done ... very well why I mean people sites to stick to what you do while right why are they doing this why are they going in that direction ... well I think one thing is that the people's business lines in the consumer lives they will merge in a user smartphone in business the same one used to call your kids ... and if that Micra soft Kinder realizes that there's this consumerization MIT that ... a lot of the cool stuff is coming to consumers the first but then it became plays a big role in the art industry so it's ... hard to really ... be a big factor in the corporate world without having the consumer play as well I think that Serbia ... okay and dumb ... I miss some forty billion dollars share buyback ... and the and and and the dividends ... but OBC will keep invested every copy of the now for a while to what they were they won his they want to see a bit of an ad supported White we have a growing timing is right ... yet mean that the earnings aren't bad in a truffle and Cashman much at seventy seven billion in the bank ... the trouble is they just somehow become a growth trajectory they had a of some years ago ... so it so it's a good kind of annuity business but they wanna see the signs of growth the kind of a ... Micra soft ... growth above some years past a candidate that ... Apple has seen in Google has seen in the Android and those kinds of things and that the on line services so ... they just they just want more signs of growth ... Spokane ... twelve sons of broke up when I got


text:
This was published 7 years ago
Solar industry faces squeeze after review
Australia's nascent solar power industry is likely to face fresh obstacles after an independent federal agency backed further reductions in incentives for the sector although large-scale generators applauded the overall recommendations.
The Climate Change Authority today released its final report on its review of the Renewable Energy Target, which sets a goal for the electricity industry to draw 20 per cent of its power from renewable sources such as wind and solar energy.
As expected the agency left the target for large-scale generators unchanged at 41,000 gigawatt hours per year by 2020, a goal that has fostered a surge in investment in renewable energy. As overall demand for power drops, the 41,000 GW-hour figure would amount to about 26 per cent of the sector by 2020.
Stability in the overall target would "provide a degree of certainty and predictability to investors in renewables", Bernie Fraser, chairman of the Authority, told a media conference.
Large generators of renewable energy applauded the recommendation to leave their target unchanged.
Securing investor certainty "has been the key problem of our industry," Miles George, chief executive of Infigen Energy, said. "The recommendations in the final report will help enormously to reduce that regulatory uncertainty."
The main changes - if adopted by the Gillard government - will come for the small-scale renewable energy scheme (SRES), such as roof-top solar photovoltaic panels.
Groups such as the Australian Solar Council say that proposed changes to how much roof-top solar can be installed on buildings such as shopping centres and school will only add to uncertainty for that segment of the market.
Household costs
The CCA recommended a number of measures to contain SRES costs. All up, the renewable energy scheme will add between $12 and $64 a year to household bills - or 1 per cent to 4 per cent of the total - between now and 2020, Mr Fraser said.
"One (change) is to lower the SRES eligibility threshold for small-scale solar photovoltaic units below its current level of 100 (kilowatts) to, say, 10kW to reduce the risk of a surge in solar PV installations on commercial buildings driving up costs," Mr Fraser said in a statement.
Generous feed-in tariffs offered by state governments and tumbling prices for PVs have seen almost 1 million Australian homes take up solar power. The roll-back of incentives, though, has seen the industry's growth slow and attention shift instead to potential commercial customers.
2013 has all the hallmarks of being a turnaround year for the renewable energy industry
"The Authority recommends that the Australian government consult with stakeholders to determine an appropriate revised threshold; units above this threshold would be included in the capped large-scale scheme," the statement said.
"This is one step forward, one step back for solar" John Grimes, Chief Executive of the Australian Solar Council, said.
"The proposal to move solar systems above 10 kilowatts into the Large-scale Renewable Energy Target will significantly undermine investor certainty and lead to business plans being ripped up," he said. "We need to encourage larger power users to invest in solar and this will be a backward step."
Fewer reviews
In order to to bolster confidence in the overall RET scheme, the Authority also recommended reviews of the scheme occur once every four years, rather than every two years as currently legislated. This approach would see the next scheduled review of the RET scheme occur in 2016.
The Authority's recommendations will be considered by the government, which has as long as six months to settle on a final decision.
Greg Combet, Minister for Climate Change and Energy Efficiency, said: "The government recognises the importance of stability in the nation's climate change policies in delivering clean energy investment and opportunities."
"To support investment certainty the government will respond to the Authority's detailed recommendations early in 2013," Mr Combet said in a statement.
"As the (Authority) has confirmed, the cost of this policy to consumers is around 4.5 per cent of their electricity bills - very modest considering the benefits it will deliver in protecting us from the rising cost of fossil fuels over the long term," Kane Thornton, Deputy Chief Executive of the Clean Energy Council, said.
"Let's lock it in and get on with the job of delivering what people consistently say they want – more clean energy."
Fossil-fuel based industries, though, are likely to protest against the recommendations. The Australian Coal Association earlier today released a study criticising the RET scheme.
"These renewable sources are currently more expensive than other sources such as coal," Nikki Williams, the association's chief executive officer, said in a statement. "Therefore the quota amounts to a tax on consumers and fossil fuel generators, to subsidise renewable generators."
Renewables jump
Large and small investment in renewable energy topped $5 billion in 2011, the agency said. The Clean Energy Council, an industrial group, estimates that another $18 billion is in the pipeline - assuming the RET target for large-scale generators remains unchanged.
"The review is done. Now is the time to get on with the business of transitioning to clean energy," Lane Crockett, Pacific Hydro general manager for Australia, said in response to today's decision. "There is no reason to delay; we just have to get on with the job."
"The challenge for renewables has always been certainty – so we can get on with the job of building projects," said Mr Crockett in a statement.
"With this latest review behind us, 2013 has all the hallmarks of being a turnaround year for the renewable energy industry."
Renewable energy now supplies about 10 per cent of the Australia's total power generation. Under the existing arrangements, renewable energy generation is projected to more than double from about 30,000 GW-hours to about 65,000 GW-hours in 2020-21.
Greenhouse gas emissions will be reduced by 102 million tonnes over the same period, the agency said. That reduction compares with annual emissions of about 190 million tonnes from the electricity sector.
Not enough
The government and the Coalition have said they back the 20 per cent RET goal. The Greens and environmental groups have called for the target to be raised.
"I hope the Climate Change Authority stands firm in the face of fossil-fuel lobbying," Greens leader Christine Milne said on Tuesday. "What we actually need is to shift to 100 per cent renewable energy as soon as possible, so we should set a minimum goal of 50 per cent by 2030."
The Australian Conservation Foundation called on the government to reject the CCA's "weak recommendation" that Australia not set a 2030 renewable energy target until after a review in 2016.
"A business-as-usual response to the urgent problem of climate change is not good enough," Claire Maries, ACF climate campaigner, said in a statement.
"In the last few weeks scientific authorities and famously conservative institutions like the World Bank, Bloomberg Businessweek and the International Energy Agency have confirmed that a status quo approach will see us heading for a world that is hotter and more dangerous by the end of this century," Ms Maries said.
"That's a world where heat-related deaths are much more common, where there are more catastrophic bushfires, more floods and more frequent droughts."
The recommendation not to increase the RET target "is emblematic of a systemic failure to take the threat seriously."
Some nations are seeking more ambitious targets for renewable energy, such as Scotland's goal of sourcing half its power by 2020 from renewable activities.
Germany aims for 35 per cent by then and a reduction in energy consumption by 10 per cent, although a report out overnight suggests current policies will see achievements fall short of those goals.
Peter Hannam writes on environment issues for The Sydney Morning Herald and The Age.