Menu
Fragment Preview

Power, versatility & simplicity

Feature-packed and incredibly easy to work with, this theme, powered a drag & drop Page Builder, has you up and running in no-time.

Fully Responsive

Built with the principles of Mobile-first in mind, this theme is 100% responsive and looks great on any device, from smartphones to widescreen monitors.

Beautiful & Retina-ready

A truly unique, modern and eye-popping design, combined with smooth animations & razor-sharp graphics lets you stand out from the crowd.

Find out more about our company

Every branch of engineering and design has technical cultures. In most kinds of engineering, the unwritten traditions of the field are parts of a working practitioner’s education as important as (and, as experience grows, often more important than) the official handbooks and textbooks. Senior engineers develop huge bodies of implicit knowledge, which they pass to their juniors by (as Zen Buddhists put it) “a special transmission, outside the scriptures”. Software engineering is generally an exception to this rule; technology has changed so rapidly, software environments have come and gone so quickly, that technical cultures have been weak and ephemeral.

There are, however, exceptions to this exception. A very few software technologies have proved durable enough to evolve strong technical cultures, distinctive arts, and an associated design philosophy transmitted across generations of engineers. The Unix culture is one of these. The Internet culture is another — or, in the twenty-first century, arguably the same one. The two have grown increasingly difficult to separate since the early 1980s, and in this book we won’t try particularly hard.

Unix’s durability and adaptability have been nothing short of astonishing. Other technologies have come and gone like mayflies. Machines have increased a thousandfold in power, languages have mutated, industry practice has gone through multiple revolutions — and Unix hangs in there, still producing, still paying the bills, and still commanding loyalty from many of the best and brightest software technologists on the planet.

One of the many consequences of the exponential power-versus-time curve in computing, and the corresponding pace of software development, is that 50% of what one knows becomes obsolete over every 18 months. Unix does not abolish this phenomenon, but does do a good job of containing it. There’s a bedrock of unchanging basics — languages, system calls, and tool invocations — that one can actually keep using for years, even decades. Elsewhere it is impossible to predict what will be stable; even entire operating systems cycle out of use. Under Unix, there is a fairly sharp distinction between transient knowledge and lasting knowledge.

A brief overview of our clients

Customer satisfaction is our top priority

Confident predictions that Unix would wither away, or be crowded out by other operating systems, have been made yearly since its infancy. And yet Unix, in its present-day avatars as Linux and BSD and Solaris and MacOS X and half a dozen other variants, seems stronger than ever today.

Outsiders have frequently dismissed Unix as an academic toy or a hacker’s sandbox. One well-known polemic, the Unix Hater’s Handbook, follows an antagonistic line nearly as old as Unix itself in writing its devotees off as a cult religion of freaks and losers. Certainly the colossal and repeated blunders of AT&T, Sun, Novell, and other commercial vendors and standards consortia in mispositioning and mismarketing Unix have become legendary.

Even from within the Unix world, Unix has seemed to be teetering on the brink of universality for so long as to raise the suspicion that it will never actually get there. A skeptical outside observer’s conclusion might be that Unix is too useful to die but too awkward to break out of the back room; a perpetual niche operating system.

img-mac

Find out how we get the job done

What Unix Gets Wrong

But perhaps the most enduring objections to Unix are consequences of a feature of its philosophy first made explicit by the designers of the X windowing system. X strives to provide “mechanism, not policy”, supporting an extremely general set of graphics operations and deferring decisions about toolkits and interface look-and-feel (the policy) up to application level.

Unix’s other system-level services display similar tendencies; final choices about behavior are pushed as far toward the user as possible. Unix users can choose among multiple shells.

Get started
  • slide image
  • slide image
  • slide image

Today, that community is a powerful support group for all kinds of software development

The community that originally formed around the early Unix source distributions never went away

ALL THE SERVICES YOU KNOW AND LOVE

People liked Unix, so they built more programs for it that made it nicer to use.

State of the art interactive development.

The ‘fun’ factor is not trivial from a design point of view, either. The kind of people who become programmers and developers have ‘fun’ when the effort they have to put out to do a task challenges them, but is just within their capabilities. ‘Fun’ is therefore a sign of peak efficiency. Painful development environments waste labor and creativity; they extract huge hidden costs in time, money, and opportunity.

If Unix were a failure in every other way, the Unix engineering culture would be worth studying for the ways it keeps the fun in development — because that fun is a sign that it makes developers efficient, effective, and productive.

It’s hard to avoid programming overcomplicated monoliths if none of your programs can talk to each other.

Unix tradition strongly encourages writing programs that read and write simple, textual, stream-oriented, device-independent formats. Under classic Unix, as many programs as possible are written as simple filters, which take a simple text stream on input and process it into another simple text stream on output.

Laptops. Tablets. Phones. We build our products with compatibility in mind.

To make programs composable, make them independent.

A program should care as little as possible about the program on the other end. It should be made easy to replace one end with a completely different implementation without disturbing the other.

GUIs can be a very good thing. Complex binary data formats are sometimes unavoidable by any reasonable means.

img-mobile

Close

Sign up for our awesome service now

And receive the first three months 20% off!

Sign up now

overlay926481109 Play video

Meet the people who make it all happen

Software is said to be robust when it performs well under unexpected conditions which stress the designer’s assumptions, as well as under normal conditions.

Person

John Doe

Creative Director

We observed above that software is transparent when you can look at it and immediately see what is going on. It is simple when what is going on is uncomplicated enough for a human brain to reason about all the potential cases without strain.

 

Person

Ben Randolph

Senior Art Director

Data is more tractable than program logic. It follows that where you see a choice between complexity in data structures and complexity in code, choose the former. More: in evolving a design, you should actively seek ways to shift complexity from code to data.

Person

Grey Shaun

Lead Developer

The easiest programs to use are those that demand the least new learning from the user — or, to put it another way, the easiest programs to use are those that most effectively connect to the user’s pre-existing knowledge.

Person

Tibby Rodney

Back-End Developer

Pay attention to your expected audience. They may be end users, they may be other programmers, or they may be system administrators. What is least surprising can differ among these groups.

Person

Gale Bridger

Front-End Developer

One of Unix’s oldest and most persistent design rules is that when a program has nothing interesting or surprising to say, it should shut up. Well-behaved Unix programs do their jobs unobtrusively, with a minimum of fuss and bother. Silence is golden.

Person

Arlie Davis

Administration

Software should be transparent in the way that it fails, as well as in normal operation. It’s best when software can cope with unexpected conditions by adapting to them, but the worst kinds of bugs are those in which the repair doesn’t succeed and the problem quietly causes corruption.

Our working process. Simple, yet effective!

Go Premium. New!

1. Briefing and planning

Well-designed programs treat the user’s attention and concentration as a precious and limited resource, only to be claimed when necessary.

3. Visual and UX Design

These philosophical principles aren’t just vague generalities. In the Unix world they come straight from experience and lead to specific prescriptions.

2. Idea and concept

In the Unix tradition, code generators are heavily used to automate error-prone detail work. Parser/lexer generators are the classic examples.

4. Development and testing

We’ll see the Unix design rules, and the prescriptions that derive from them, applied over and over again in the remainder of this book. Unsurprisingly, they tend to converge.

Get maximum value now!

Well-designed programs treat the user’s attention and concentration as a precious and limited resource, only to be claimed when necessary.

img-browser

The Unix tradition of lightweight development and informal methods also began at its beginning.

 

 
 
 

Have a look at our previous work

Not even Microsoft’s awesome marketing clout has been able to dent Unix’s lock on the Internet.

The trouble with heuristics is that they proliferate special cases and edge cases

To design for compactness and orthogonality, start from zero. Zen teaches that attachment leads to suffering

Check out our blog for a look behind the scenes

An analogous choice shows up in a lot of different contexts

Top-Down versus Bottom-Up

My secret to a long, healthy life is to always keep working. It keeps me busy and happy, and gives me a reason to stay alive

  • Gallery Image 4
  • Gallery Image 3
  • Gallery Image 2
  • Gallery Image 1
Coding for Modularity

Write a big program only when it is clear by demonstration that nothing else will do

Because debugging often occupies three-quarters or more of development time, work done early to ease debugging can be a very good investment.

Our competitive prices can’t be found anywhere else

In the Unix tradition, code generators are heavily used to automate error-prone detail work. Parser/lexer generators are the classic examples.

Starter$19/mo

  • 10GB Storage
  • Up to 10 Users
  • 5 Domains
  • Free Setup
  • 1-year Free support *

STANDARD$29/mo

  • 20GB Storage
  • Up to 20 Users
  • 10 Domains
  • Free Setup
  • 2-year Free support *

BEST VALUE!ULTIMATE$69/mo

  • 150GB Storage
  • Unlimited Users
  • 50 Domains
  • Free Setup
  • 5-year Free support *

BUSINESS$49/mo

  • 40GB Storage
  • Up to 40 Users
  • 25 Domains
  • Free Setup
  • 3-year Free support *

How long are your contracts?

Unix has wired into it an assumption that the programmer knows best. It doesn’t stop you or request confirmation.

Is there a discount for yearly service?

The strength of an operating system’s internal boundaries is not merely an abstract issue of design: It has important practical consequences.

Do I need another webhost?

Unix files have neither record structure nor attributes. In some operating systems, files have an associated record structure.

How do I sign up?

OS-level record structures are generally an optimization hack, and do little more than complicate APIs and programmers’ lives.

How do I cancel service?

Even if a command-line interface, scripting, and pipes are supported, very few filters will evolve.

Can I switch plans?

To design the perfect anti-Unix, make all file formats binary and opaque, and require heavyweight tools to read and edit them.

Close

Pay us a visit, our doors are always open!

Our offices are located at:
795 Folsom Ave, Suite 700
San Francisco, CA 94107

overlay1820011341 Show map

We’d love to hear from you

We do have to be a bit careful about not embedding a colon in any of the textual fields

Get in touch.

Looking for a partner for your exciting new project or do you just want to inquire about our services? In any case, send us a message at info@fragment.com or use the contact form below and we’ll get back to you ASAP!

“The fact that structural information is conveyed by field position rather than an explicit tag makes this format faster to read and write.”

 Gregg Timothy

Gregg TimothyCEO at Pixar

“Usenet news is a worldwide distributed bulletin-board system that anticipated today’s P2P networking by two decades.”

 Roosevelt Terrence

Roosevelt TerrenceFounder at Trello

“Non-Unix programmers might have automatically tried to design a fast binary format in which each newsgroup status was described.”

 Errol Geoff

Errol GeoffDesigner at Apple

Our contact info.

795 Folsom Ave, Suite 700 San Francisco, CA 94107

info@fragment.net

+020 - 850 51 52

 

Our partners.

github

 

bootstrap

 

sublime