The Apostles James and John came with an outrageous question! It's as if they'd learned nothing at all from their time with the Lord. So He sets abouut teaching them again...cas

100lbs of spices - a glorious waste of spices! Your prayer and service - a glorious "waste" also but you'll find yourself experiencing the Resurrection!

"Saint Cosmas came from Bulgaria where his devout parents provided him with a good education in Slavonic and Greek. They wanted him to marry but he was drawn by the love of Christ and, unknown to them, made his way to the Holy Mountain of Athos to become a monk at the Bulgarian monastery of Zographou. On the feast of the Annunciation at the Monastery of Vatopedi, he saw a woman among those serving in the Church and in the refectory, and he was grieved at first to observe this breach of the monastic rule, but overjoyed when he realized that it was the Mother of God who had appeared to him in this way.   "He was clothed in the holy angelic Habit and, after some time, was ordained priest. One day, as he was praying before the icon of the Mother of God, asking her with tears how to achieve his salvation, he heard a voice saying, 'Let my servant withdraw to the desert outside the monastery.' He was obedient to the will of God and, with the blessing of his Abbot, lived in silence from then on. Some years later, he was found worthy of the grace of discernment of thoughts and of beholding things happening elsewhere, as well as of other spiritual gifts. In the course of many years, he was the spiritual helper of a great number of monks. At the end of his life, Christ appeared to him saying that he would shortly have a great trial to endure from the Devil. Indeed, the prince of demons made his appearance next day with a host of his servants bewailing and bemoaning their inability to annihilate their great enemy Cosmas, who had held them in check for so long and gained possession, by his virtue, of the throne in Heaven that had once been Lucifer's. Taking a heavy stick, the demon beat the Saint so violently that he left him half-dead. As God allowed, Saint Cosmas died in peace two days later, on 22 September 1323. When the fathers came from the monastery to bury him, the wild animals gathered round. They kept silent until the end of the service, but howled unusually loud as his body was covered with earth. Then having paid their respects, they made off into the wilderness. Forty days later, the monks came to take up the body of Saint Cosmas and translate it to the monastery, but it was no longer in the grave. Where it now is God alone knows." (Synaxarion)

Taking your first steps in UX? Welcome! In this straightforward guide, we're breaking down the concepts of 'User Journey' and 'User Flow' for you. Dive in to understand how a user journey outlines the broader experiences of your users, while a user flow zooms in on the specific actions they take on your platform. Let's simplify these essential UX elements together.

The post Simplifying User Journey vs User Flow for Newbies appeared first on Coaching and training to scale your copywriting business, plus programs for new copywriters, startups, and marketers.

“We have 0% customer churn.” – said no SaaS marketer ever. Instead, what I hear all the time is: “If only we could keep growing without churn growing with us.” “If only we could get new trials to actually USE the product, they’ll see how great it is.” And even this story someone shared on […]

The post I spent 60+ hours analyzing onboarding emails for 127 SaaS trials. This is how the top SaaS retain users. appeared first on Coaching and training to scale your copywriting business, plus programs for new copywriters, startups, and marketers.

See exactly where the available hotels are on a Google Map.

(screenshot)

Imagine the convenience of a hotel concierge, but with a recording that you can customize. That’s the draw of an at-home wake-up call service—which is far more affordable than booking a hotel room just to get access to a concierge. In any case, for less than the cost of a […]

The post How to Safely Set Up Your Own Wake Up Call Service appeared first on .

Watch the best shots from Matteo Manassero's nine-under-par third round as he takes a three-shot lead into the final round of the PGA Championship at Wentworth.

Herbie Farnworth delivers a superb performance that includes two tries as England wrap up a 2-0 Test series victory over Samoa at Headingley.

Watch highlights as a well-drilled England beat Samoa 34-18 in the first of two autumn Tests.

Watch highlights as Herbie Farnworth scores two tries to help England defeat Samoa 34-16 in the second autumn Test at Headingley Stadium.

The Commonwealth Games will take place in 2026 after Glasgow stepped in to host, but the stripped-back event has left some celebrating and others disappointed.

As Wales prepare to get their 2024 Autumn Nations Series under way this weekend, how well do you recall their last autumn campaign?

Form guide, facts and how to follow Wales who take on Fiji, Australia and South Africa this month.

Tiernan Lynch says he has "mixed emotions" after a late goal condemned Larne to a 2-1 defeat at home to St Gallen in the Uefa Conference League.

Pre-match favourites Kilcoo are pushed all the way by Crosserlough but do just enough to clinch a 0-15 to 1-10 win in the Ulster Club SFC quarter-final.

Scotland v England, day 1 of 1. England beat Scotland by 7 wickets

Leslie Lawrenson died and his partner became seriously ill with Covid after they refused vaccines.

Nikita Hand claims she was raped by MMA fighter Conor McGregor at a Dublin hotel.

Composer Errollyn Wallen talks about how her career as a composer has taken her around the world but always brings her back to Scotland.

Rita Purves was just 13 when she first took a seat at the organ in Morebattle in the Borders.

The charity says it is "confident" there will be no gap in the service before its new building is ready.

A deal has been agreed for the Darlington store to stay open.

Great North Air Ambulance says a green laser was shone into its helicopter on Monday evening.

Buildings that are normally inaccessible can now be explored virtually using smartphones.

Up to £991,000 will be spent on the major scheme to help reduce flooding.

Memorial services across the South West take place for Armistice Day on Monday.

Transport for Wales says the service will not operate on Tuesday due to trains needing repairs.

Counterterrorism police say the officer is suspected of expressing support for the proscribed group online.

Victims of David Pickthall recall him being a predator who abused his position as a successful musician.

A watchdog says a fire service is taking "significant steps" to address concerns raised a year ago.

Terry Clarkson and his granddaughter, Olivia, have raised thousands for the Royal British Legion.

The trial will give rural areas and passengers on the railway's route access to the internet.

The group also rammed a farmer's vehicle in a "terrifying" incident in Wiltshire, police said.

A Coventry teacher has written a play about the attempted murder of Humpty Dumpty.

Artificial Intelligence (AI) is changing how user experience design is handled across various industries by playing a vital role in developing tailored and seamless experiences for users. Starting from app […]

The post How AI is Transforming User Experience (UX)  appeared first on Tech Digest.

Live Drive, SDrive, Project M, Folders, FolderShare, Windows Live Sync, Live Mesh, SkyDrive, OneDrive. Yes, Microsoft has been at this file syncing game for a long time. The company bought FolderShare back in November of 2005, and has been …

Just recently, some front-end code Clearleft delivered to a client was making its way through acceptance testing. We were slightly surprised to discover that their standards required our code to be supported by the two latest versions of web browsers. And then we realised we didn’t have a browser support policy of our own – something we set about rectifying.

When considering browser versions, we were fairly sure our client didn’t mean, for example, versions 124 and 125 of Chrome (released on 16 April and 14 May 2024 respectively). Instead their support standard would most likely be harking back to the days when Internet Explorer was a thing, and major browsers were updated once a year at best. To put this in context, the final version of Internet Explorer shipped in 2013.

It’s at this point we noted that Clearleft didn’t have a written browser support policy to counter or complement that of our clients. We probably did in the dim and distant past, but in recent years we’ve just built accessible, progressively enhanced websites without feeling the need to codify what that means. For the sake of professionalism and good client relationships, we decided to rectify that.

But where to start? Using browser versions clearly doesn’t make any sense, so what do we turn to instead? As it turned out, Jeremy had already nailed it in a recent blog post. We wanted a browser support policy that would focus on outcomes for the user. Rather than being fixated on specific browsers, we needed to consider capabilities, using the mindset that sees modern coding use feature detection in preference to browser detection. It turns out there’s an initiative for that.

The Baseline initiative is a joint effort by Google, Microsoft, Apple, and Mozilla to categorise browser support for web standards. Baseline provides clear information about which web standards features are ready to use in websites. It designates new features into two categories:

• Newly available – a feature is supported by the latest versions of all core browsers
• Widely available – a feature has been supported across browsers for at least 30 months

We use the Baseline project to determine which browser features to use in production. If a feature is widely available according to Baseline, we can use it.

Quoting directly from our browser support policy:

Progressive enhancement

If a feature is newly available, we might still use it, but we’ll ask a follow-up question:

“Can this feature be used as a progressive enhancement?”

In other words, will using this feature harm browsers that don’t support it? If a newly-available feature can be used as a progressive enhancement, we might well use it. If not, we’ll wait until the feature becomes widely available and choose a different method in the meantime.

This approach restricts usage of new features to nice-to-have additions rather than mission-critical requirements. But it also means we don’t necessarily have to wait for every browser to support a feature before using it.

Access for all

Underlying our browser support policy are two foundational principles:

1. Website content and core functionality should be accessible to everyone.
2. It’s okay for websites to look different in different browsers.

If content is unreadable in some browsers, that’s a bug that we will fix. If content is displayed slightly differently in some browsers, we consider that to be a facet of the web, not a bug. This means that there will sometimes be subtle visual and functional differences from browser to browser. We deem this acceptable provided that content and core functionality are unaffected.

We think this the right approach to browser support, and it’s something we believe the whole industry should follow in principle. To that end we’ve made our browser support policy available under a Creative Commons license, meaning you can use it for your own purposes if you find it helpful.

Originally published on the Clearleft blog.

Read or add comments

Meander your way across a dock.

Listen to the podcast for November 11, 2011 insertAdjacentHTML Mozilla has a nice overview of insertAdjacentHTML, a DOM function that's intended to supplement innerHTML. It's a bit less destructive and plays nicely with content that's already in the DOM. For instance, whereas innerHTML completely blows away whatever is inside the ...

No es fácil ser traductor o intérprete freelance en la era de la IA. Pero tampoco es imposible. Si quieres saber cómo salir adelante y triunfar en estos momentos, sigue leyendo. Si alguien te dijo alguna vez que ser traductor o intérprete freelance es fácil, te engañó....

La entrada Ser freelance en la era de la IA aparece primero en Traducción Jurídica.

Son tiempos difíciles para todos y también para los traductores jurados. A pesar de que el teletrabajo es habitual en nuestra profesión, el coronavirus o COVID-19 ha parado la economía de todo el mundo...

The post Ser traductor jurado en tiempos de coronavirus appeared first on El Blog del Traductor Jurado.

There has been a set of discussions about lock-in around Platform-as-a-Service (PaaS): Joe McKendrick and Lori MacVittie in particular bring out some of the real challenges here.

Lori brings out the difference between portability and mobility. While I'm not in 100% agreement with Lori's definitions, there is a key point here: its not just code, its the services that the code relies on that buy lock-in into a cloud.

So for example, if you use Amazon SQS, Force.com Chatter Collaboration, Google App Engine's bigtable data store, all of these tie you into the cloud you are deployed onto. Amazon isn't really a PaaS yet, so the tie-in is minimal, but Google App Engine (GAE) is based on Authentication, Logging, Data, Cache and other core services. Its almost impossible to imagine building an app without these, and they all tie you into GAE. Similarly, VMForce relies on a set of services from force.com.

But its not just about mobility between force.com and Google: between two PaaSes. The typical enterprise needs a private cloud as much as public cloud. So there is a bigger question:

Can you move your application from a private PaaS to a public Paas and back again?

In other words, even if Google and Force got together and defined a mobility layer, can I then take an app I built and run it internally? Neither Google nor Force is offering a private PaaS.

The second key question is this:

How can I leverage standard Enterprise Architecture in a PaaS?

What I'm getting at here is that as the world starts to implement PaaS, does this fit with existing models? Force.com and Google App Engine have effectively designed their own world view. VMForce and the recent Spring/Google App Engine announcement address one aspect of that - what Lori calls portability. By using Spring as an application model, there is at least a passing similarity to current programming models in Enterprises. But Enterprise Architectures are not just about Java code: what about an ESB? What about a Business Process engine (BPMS)? What about a standard XACML-based entitlement engine? So far PaaS has generally only addressed the most basic requirements of Enterprise core services: databases and a identity model.

So my contention is this: you need a PaaS that supports the same core services that a modern Enterprise architecture has: ESB, BPMS, Authentication/Authorization, Portal, Data, Cache, etc. And you need a PaaS that works inside your organization as well as in a public Cloud. And if you really don't want any lock-in.... hadn't that PaaS better be Open Source as well? And yes, this is a hint of things coming very soon!

Yesterday we announced something I believe is a game-changer: WSO2 Stratos. What is Stratos?

WSO2 Stratos is a complete SOA and developer platform offered as a self-service, multi-tenant, elastic runtime for private and public cloud infrastructures.

What that means is that our complete SOA platform - now enhanced with Tomcat and Webapp support - is available as a  "cloud native" runtime that you can either use on the Web (yes - you can try it out right now), on Amazon VPC, or on your own internal private cloud based on Ubuntu Enterprise Cloud, Eucalyptus and (coming soon) vmWare vSphere. It is a complete Platform-as-a-Service for private and public clouds.

I'll be writing more about Stratos over the coming weeks and months, and I'll also provide links and tweets to other Stratos blogs, but in this blog I want to simply answer three questions:

1. I'm already talking to {vmWare, Eucalyptus, Ubuntu, Savvis, Joyent} about private cloud - what does WSO2 add that they don't have?
2. What is the difference between Stratos and the Cloud Images that WSO2 already ships?
3. Why would I choose WSO2 over the other vendors offering Platform-as-a-Service?

In order to answer the first question, lets look at the cloud computing space, which is most easily divided up into:

• Infrastructure-as-a-Service (IaaS): this is where Amazon, Eucalyptus, vmWare, Saavis and Joyent play
• Platform-as-a-Service (PaaS): Google App Engine, vmForce, Tibco Silver and now WSO2 Stratos play in this space.
• Software-as-a-Service (SaaS): Google Apps, Google Mail, Microsoft Office Live, Salesforce, SugarOnDemand - these and many more make up the SaaS category.

To generalize wildly, most people talking about public cloud today are talking about SaaS. And most people talking about private cloud today are talking about IaaS.

SaaS is fantastic for quick productivity and low cost. WSO2 uses Google Apps, Sugar on Demand and several other SaaS apps. But SaaS doesn't create competitive advantage. Mule also uses Google Apps. They may well use Salesforce. SaaS cannot produce competitive advantage because your competitors get access to exactly the same low-cost services you do. In order to create competitive advantage you need to build as well as buy. For example, we use our Mashup Server together with our Sugar Business Messaging Adapter to provide insight and management of our pipeline that goes beyond what Sugar offers.

IaaS is of course a great basis to build apps. But it's just infrastructure. Yes - you get your VM hosted quicker. But someone has to create a useful VM. And that is where PaaS comes in. PaaS is how to speed up cloud development.

What does Stratos give you on top of an IaaS? It gives you an Application Server, Registry, Identity Server, Portal, ESB, Business Activity Monitor and Mashup Server. And it gives you these as-a-Service: completely self-service, elasticly scalable, and granularly metered and monitored. Someone in your team needs an ESB - they can provision one for themselves instantly. And because it's multi-tenant, it costs nothing to run until it gets used. How do you know how it's used? The metering and monitoring tells you exactly how much each tenant uses.

2. What is the difference between Stratos and the existing WSO2 Cloud Images?

The cloud images we started shipping in December are not Cloud Native. Stratos is Cloud Native. In practice, this means that when you log into Stratos (go on try it now) you can instantly provision your own domain, together with a set of Stratos services. This saves memory - instead of allocating a new VM and minimum half a gigabyte of memory to each new server you get a new ESB with zero extra memory cost. And it's much easier. The new ESB will automatically be governed and monitored. It's automatically elastically clustered.

3. Why would I choose WSO2 over other PaaS vendors?

Firstly, if you look at PaaS as a whole there is a huge divide between Public PaaS and Private PaaS. The public PaaS vendors simply don't offer private options. You can't run force.com or Google App Engine applications internally, even if you want to. WSO2 bridges that gap with a PaaS you can use in the public Web, on a virtual private cloud, or on premises.

The second big differentiator between WSO2 and the existing PaaS offerings is the architecture. Mostly PaaS is a way of building webapps. WSO2 offers a complete enterprise architecture - governance, business process, integration, portal, identity and mashups. And we support the common Enterprise Programming Model (not just Java, WebApp, JAX-WS, but also BPEL, XSLT, XPath, Google Gadgets, WSDL, etc). The only other PaaS that I know of that offers a full Enterprise architecture is Tibco Silver.

The third and most important differentiator is about lock-in. Software vendors love lock-in - and Cloud vendors love it even more. So if you code to Google App Engine, you are tied into Google's identity model, Google's Bigtable, etc. If you code to force.com or vmForce - you are tied to force's infrastructure services. If you code to Tibco Silver, you are tied to Tibco. WSO2 fights this in three ways:

• No code lock-in: we use standards-based coding (WAR, JAX-WS, POJO) and Stratos is 100% Apache License Open Source.
• No model lock-in: we use standards-based services: 
• Identity is based on OpenID, OAuth, XACML, WS-Trust
• Registry is based on AtomPub and REST
• Business Process is based on BPEL, etc
• No hosting lock-in: you can take you apps and data from our public PaaS and re-deploy internally or on your own virtual private cloud anytime you like.

I hope you found this a useful introduction to Stratos. If you want more information, contact me paul@wso2.com, or check out the Stratos website or code.

Ponencia presentada por Julia Benseñor en el III CONGRESO LATINOAMERICANO DE TRADUCCIÓN E INTERPRETACIÓN, CTPBA, Buenos Aires, abril de 2001

Inmediatamente, cabe organizar la estructura interna del equipo, es decir, asignar el papel que desempeñará cada integrante sobre la base de la noción de "estaciones de trabajo". La propuesta de nuestro Centro, producto de nuestra experiencia en el campo editorial, consiste en dividir el trabajo en cinco etapas o estaciones, en donde la traducción propiamente dicha es sólo un eslabón en el proceso. Estas cinco estaciones de trabajo son: a) la gestión terminológica, b) la traducción propiamente dicha, c) la corrección de estilo, d) la revisión técnica y e) la corrección de galeras o proofreading.

De este modo, hemos explicado cómo el traductor, a través de una adecuada planificación, está en condiciones de organizar su trabajo de manera tal de cumplir con las nuevas y exigentes demandas del mercado actual. Para ello, debemos comenzar por concebir al traductor como gerente de sus propios proyectos.

Hoy comparto contigo información sobre una iniciativa de Fundación Occident: las becas de grado Jesús Serra, que se convocan por primera vez en 2024. Además […]

Origen

Advances in mobile technologies are opening new possibilities to support collaborative activities through mobile devices. Unfortunately, mobile collaborative systems have been difficult to conceive, design and implement. These difficulties are caused in part by their unclear requirements and developers' lack of experience with this type of systems. However, several requirements involved in the collaborative back-end of these products are recurrent and should be considered in every development. This paper introduces a characterization of mobile collaboration and a framework that specifies a list of general requirements to be considered during the conception and design of a system in order to increase its probability of success. This framework was used in the development of two mobile collaborative systems, providing developers with a base of back-end requirements to aid system design and implementation. The systems were positively evaluated by their users.