Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Jonathan Allen on Dec 27, 2010
MonoDevelop has become the third IDE to support Microsoft’s F# language. With .NET support essentially dead on the Eclipse IDE and WebMatrix being targeted for causal developers, it is likely to be the last IDE to add support for it in the foreseeable future.
The feature list for MonoDevelop’s F# Plugin include:
- Identifier completion - The editor automatically suggests identifiers such as member names after the "." symbol. You can also hit Ctrl+Space to get all identifiers available in the current scope (such as variable and type names).
- Tool tips - When you place mouse pointer over an identifier, a tool tip with information about the identifier appears. Tool tips usually show type signatures, list of members of types etc.
- Background type-checking - The F# compiler runs as a background process and checks the edited file for parsing errors as well as type errors. Errors are immediately shown using red underlining.
- F# Interactive pad - The plugin adds F# Interactive as a new tool window to MonoDevelop. You can use it to interactively evaluate F# code written in the editor as well as for writing simple code snippets to test things.
The source code for F# on MonoDevelop is licensed under Apache 2.0 and can be found at https://github.com/fsharp.
MonoDevelop started as a fork of SharpDevelop, the only other general purpose .NET IDE not made by Microsoft. (Other .NET IDEs do exist, but are dedicated to a specific language such as Delphi Prism.) To better support Linux, SharpDevelop’s original user interface was ported to Gtk#. Since then MonoDevelop and SharpDevelop continued to diverge, with MonoDevelop becoming the IDE of choice for Novell’s commercial offerings such as MonoTouch. (Again, there are third-party IDEs that support MonoTouch development.) Meanwhile SharpDevelop remained a Windows-only product and is in the process of replacing the user interface with one built using WPF.
Troubleshoot Java/.NET performance while getting full visibility in production
Automating Error Reporting for .NET Applications
RDBMS to NoSQL: Managing the Transition
Visual Studio vNext: ALM features for Agile Planning, Team Collaboration
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply