Why TIBET? Less Risk, More Reward

Less Risk, More Reward

JavaScript is here to stay. From the server to the desktop, from mobile to IoT, more and more applications depend on JavaScript and skilled JavaScript developers.

Unfortunately, demand for JavaScript skills consistently outpaces supply, a condition that's been true since the dawn of the AJAX/Web2.0 era.

In May of 2006, at one of the earliest JavaScript conferences, keynote speaker Scott Dietzen, then CEO of Zimbra and former CTO of BEA, asked the audience "Q: What's the hardest AJAX problem? A: Recruiting." Nothing in the intervening decade has changed that answer, in fact, in many ways the JavaScript recruiting problem keeps getting worse.

Most modern frameworks actually increase demand for JavaScript skills; some go further and add additional requirements for languages like TypeScript forcing you to hire from an even smaller pool of developers. Choices like these actually increase business risk.

The good news is there's a solution...the same one that allowed the web to grow to almost 5 Billion pages in 25 years. The solution? Authoring primarily in markup, markup augmented by JavaScript, not embedded in it.

The popularity of Angular1's tag-aware design; experiments like Google Polymer; the W3C's WebComponent specification; numerous initiatives point to a future where applications are built in markup, a future that doesn't rely on expensive and elusive JavaScript coders, a future where you can drag, drop, and edit markup-based components to create new applications.

Interestingly, we presented markup-based authoring at that May 2006 conference. In our talk introducing TIBET™ 3.0 we showed how tags backed by object-oriented types make markup-based applications a reality, essentially turning markup into a powerful macro language.

TIBET 5.0 represents over a decade of refinement on that early vision - a fully-tooled, fully-supported, full-stack solution that lets you author complex applications primarily in markup.

Welcome to the future.


The TIBET Difference

TIBET is unique in focusing on the business problems we've seen plaguing project after project throughout our over 20 years building complex single-page web applications.

Virtually all frameworks "work" from a technical perspective but most fail to address the three biggest risks to your project: staffing, stability, and support.

  • Staffing: It's been called "the hardest AJAX problem" and frameworks that force you to hire from perpetually undersized pools of skilled JavaScript or TypeScript programmers only make it worse. TIBET lets you get more done with a smaller, more balanced staff.

  • Stability: "Buy vs. build"; it's really that simple. TIBET lets you focus on your app, not your stack, by providing the web's most comprehensive stack and the web's most innovative tool chain; a stable, integrated, platform you can count on over time.

  • Support: "Backed by ..."; it's a phrase you often see with respect to popular frameworks. The harsh reality is if you can't buy support it's not "backed by", it's authored by; a state often followed by "abandoned by". Yahoo! walked away from YUI and Mojito. Google has "backed" Closure, GWT, Dart, Polymer, and Angular1. Now it's Angular2. TIBET is different. TIBET is fully-supported by the vendor who authored it.

Of course, TIBET isn't short on technical innovation, it's just innovation focused on solving the real problems that cause the majority of web project pain: staffing, stability, and support.


Staffing - The #1 Problem For Web Development Projects

Over the years we've spoken with dozens of decision makers about the issues they face with their web projects. In discussing their challenges they never focus on things like "callbacks are complicated", "we need static typing", or "everything would be fine if JavaScript had modules".

In fact, without exception they never mention technical issues at all. On the other hand, they universally complain about one issue: "Hiring good JavaScript coders is impossible."

TIBET solves "the hardest AJAX problem" in several ways:

  • TIBET's authoring pyramid design aligns the skill requirements for TIBET development with the natural distribution of UI, application, and framework level JS skills in the market.
  • TIBET's markup-first approach shifts development to markup, not code.
  • TIBET's immersive IDE enables graphical, top-down, tag-centric development.

Each of these elements reduces your dependence on JavaScript, replacing it with a scalable markup-first approach that's easier to staff for and maintain over time.

Ask yourself this...when you build your second, third, or fifth project with your current framework will you still be doing all the work in code?

With most frameworks the answer is yes. TIBET frees you and your projects from a perpetual reliance on JavaScript coding, solving "the hardest AJAX problem".


Stability - Avoiding The Pain Of À La Carte Development

Selecting, integrating, and maintaining a custom stack and toolchain requires time, effort, and a skilled team, increasing staffing pressure. Choosing à la carte development is also the root cause of another business problem: platform instability.

TIBET saves you from the pain of à la carte JavaScript development at every level:

TIBET is truly "The sum of the parts, not some of the parts.™", providing you with the most comprehensive and integrated platform available for modern web development.

With TIBET you have a single, unified platform built to provide a stable foundation over time; a platform originating in the IE4/Nav4 era; a platform which still excels today. That's stability.


Support - Authored By !== Supported By

TIBET is Open Source and fully supported by the vendor who built it.

In contrast, most of today's prominent frameworks are unsupported. They're popular, powerful, and often authored by prominent companies...but there's a catch.

The core business for today's prominent framework authors is not frameworks. They don't "back them"; they merely authored them. There's no SLA. They're free to abandon them, and you. A perfect example is the Angular1 to Angular2 transition, a change so dramatic it stranded Angular1 projects on a framework they'll have to port off of eventually.

The thing is, abandoned frameworks are nothing new.

Yahoo! walked away from both YUI and Mojito. Similarly, Google has gone through Closure, GWT, and Angular1. The jury's still out on Dart and Polymer. Today's offering is Angular2x but with WebAssembly and WebComponents on the horizon there'll almost certainly be more churn and more potential for license pain as these companies compete in their core businesses.

Technical Pursuit is different. Since 1999 our only business has been the design and development of business web applications and tools. This is what we do. It's all we do.

When we say TIBET is supported we mean it; our business and your project depend on it.

Speed And Simplicity

Speed and Simplicity - The Bonus Round

TIBET development is an immersive, top-down experience that's fast and easy.

At the center of that experience is the Sherpa™, an immersive, interactive IDE designed specifically to speed development by letting you focus on tags rather than files.

Most web development tools retain a long-standing development tool focus on editing files. Files of markup, files of JavaScript, files of CSS, files files files. The thing is, the essence of web applications isn't found in files...it's found in tags...tags with containment hierarchies, tags with event handlers, tags with style. Tags are the "quantum of web development".

The Sherpa™ lets you focus on tags; creating them, moving them, styling them, giving them behavior, sharing them across projects, even using them as commands.

By focusing on tags instead of files the Sherpa changes the fundamental nature of web development. Give TIBET 15 minutes and we're convinced you'll agree...

...or take the plunge, install TIBET, and dive into the TIBET Quickstart Guide.

We think you're going to love working with TIBET!

The Pup

Contact us for more information or to discuss how we can assist you.