gloderworks.com

Choose a hosting plan by matching four things to your site: the type of hosting (shared, VPS, semi-dedicated, or dedicated), the resources you actually need (disk space, traffic, email accounts, domains), the storage and uptime guarantees, and whether you can test before paying. Lonex illustrates this well — it offers four hosting tiers plus VPS, semi-dedicated, and dedicated servers, all web hosting packages and semi-dedicated servers include a 30-day free trial with no credit card required, and the platform runs on 100% NVMe storage with a 99.9% uptime target and 24/7 tech support. Use the sections below to decide which tier fits your situation.

What web hosting actually provides

Web hosting is the server space and infrastructure that keeps your website online. When you buy a plan, you're renting a slice of a machine (or the whole machine) plus the software layer that serves your files to visitors. The core features to check on any plan:

• Disk space — where your files, databases, and emails live. Lonex advertises unlimited disk space on its web hosting packages.
• Monthly traffic (bandwidth) — how much data visitors can pull from your site each month. Lonex lists unlimited traffic on its hosting plans.
• Hosted domains — how many separate websites one plan can run.
• Email accounts — mailboxes tied to your domain, useful if you want [email protected] instead of a free email address.
• Control panel — the dashboard where you manage files, domains, email, and installs. Lonex uses the Hepsia control panel and includes a free web apps installer for one-click setups.

If a plan lists "unlimited" disk space or traffic, read the acceptable-use terms — unlimited usually means "within normal use," not "host unlimited video streaming."

Match the hosting type to your situation

The four common types differ mainly in how much of the server you control and how much you share with other sites.

A practical rule: start on shared hosting if you're launching. Move to VPS when you hit consistent CPU or memory limits, or when you need root-level control. Choose semi-dedicated when traffic is high but you don't want to manage a server. Choose dedicated when you need the whole machine for performance, isolation, or custom configuration.

Use the free trial to test before committing

Lonex's 30-day free trial applies to all web hosting packages and semi-dedicated servers, and no credit card is required. That's a meaningful signal because it lets you verify real-world performance before spending anything.

During the trial, test the things marketing pages can't tell you:

1. Load speed — time your site from a few locations. NVMe storage should make disk reads fast, but network routing matters too.
2. Control panel usability — install a web app through the free installer and see whether the Hepsia panel fits how you work.
3. Support responsiveness — open a ticket with a real question and note the response time. Lonex advertises 24/7 tech support; the trial is when you confirm it.
4. Uptime — a 99.9% target allows roughly 43 minutes of downtime per month. Watch for gaps during your trial.

If the trial ends and the plan still fits, you convert; if not, you've lost nothing but time.

Decision factors beyond price

Price is the easiest number to compare and the least useful on its own. Weigh these instead:

• Storage technology — NVMe drives handle database queries and file reads faster than older SATA SSDs or spinning disks. Lonex runs 100% NVMe across its hosting.
• Uptime commitment — 99.9% is a common baseline. Anything lower deserves scrutiny for a business site.
• Support hours — 24/7 matters if your site earns money overnight or across time zones.
• Scalability path — can you move from shared to VPS to dedicated without migrating to a new provider? Lonex offers all four tiers plus VPS (OpenVZ and KVM), so upgrading stays in-house.
• Included extras — a free control panel, one-click app installer, and website builder reduce what you'd otherwise pay for separately.

Matching a plan to a specific use case

• Personal site or blog — shared hosting with unlimited disk and traffic covers it. The Personal Plan tier fits here.
• Startup or small business site — shared or cloud hosting with email accounts and a hosted domain. Lonex's Business Plan tier targets this.
• Growing business with rising traffic — VPS at $17.00/mo gives dedicated CPU and RAM so a traffic spike on one site doesn't drag down others.
• High-traffic site without server admin — semi-dedicated at $30.00/mo, with the same 30-day free trial.
• Resource-heavy or isolation-critical site — dedicated server at $67.50/mo with a full Xeon CPU, 240GB disk, and 16GB RAM.

Start with the smallest tier that meets your current needs, confirm it during the free trial, and upgrade along the same provider's ladder when you outgrow it. That keeps migration costs low and lets real performance data — not spec sheets — drive the decision.

raylib is a simple, easy-to-use programming library for making videogames, written for C and usable from C++. It is code-first: there is no fancy interface, no visual helpers, no GUI tools or editors — you build games by writing code. That makes it a good fit if you already know some C or C++ and want direct control without an engine's editor layer, or if you want a small library you can learn from a cheatsheet and a pile of examples. If you want a drag-and-drop scene editor, raylib is deliberately not that.

What raylib actually is

raylib is a library, not a game engine. You write a program, call raylib functions for windows, input, graphics, audio, and math, and compile it like any other C program. The project describes itself as "a programming library to enjoy videogames programming; no fancy interface, no visual helpers, no gui tools or editors... just coding in pure spartan-programmers way."

Two consequences follow from that design:

• You learn by reading code. The project states it does not provide the typical API documentation or a big set of tutorials. Instead, it is meant to be learned from a cheatsheet covering the required functionality plus a large collection of examples.
• You bring your own structure. There is no editor to organize scenes, assets, or build settings, so project layout and build steps are yours to set up.

How it differs from Unity or Godot

The practical difference is where the work happens.

Neither column is "better" in the abstract. Choose raylib when you want to write the game as a program and keep the toolchain small. Choose an editor-based engine when you want visual scene assembly, asset pipelines, and a guided project structure.

The recommended learning path

The project points to a specific route rather than a tutorial series:

1. Start with the cheatsheet. It lists the functionality you need, so you can see the available calls without reading full API docs.
2. Read the examples. The project's stated position is that the best way to learn to code is reading code, and the examples show how each piece of functionality is used.
3. Use the raylib game template if the options overwhelm you. It provides some structure and a Makefile that are quick to pick up, which is useful when you want a working layout instead of assembling one yourself.
4. Join the Discord community. The project recommends it for staying up to date on raylib news and asking for help. Community-made tutorials also exist outside the official materials.

A concrete first task looks like this: install raylib, open one example that draws something and responds to input, compile and run it unchanged, then modify one value and recompile to confirm your build loop works. That verifies your setup before you write anything original.

Platforms and language bindings

raylib has been tested on multiple target platforms. The project notes that technically any platform supporting the C language and OpenGL graphics (or similar) can run raylib, or can be ported to it fairly easily.

You are not limited to C and C++. There are more than 60 language bindings, so you can use raylib from many other programming languages. If your preferred language is not C, check whether a binding exists before assuming you need to switch languages.

Extending it and what it powers

raylib can be combined with extra libraries for additional functionality. Some of those libraries are already used internally by raylib, while others are provided for you to integrate; most are single-file, header-only, and have no external dependencies — which keeps them easy to drop into a project.

raylib is also the base technology behind the raylib technologies tools: several multiplatform tools have been built with raylib and raygui. That is a useful signal if you want to see what the library looks like at application scale rather than in minimal examples.

Getting started checklist

• Confirm you are comfortable writing and compiling C or C++ (or pick one of the 60+ bindings for a language you already know).
• Accept that there is no editor: your project structure and build configuration are your responsibility.
• Learn from the cheatsheet and the examples rather than expecting full API documentation.
• Use the raylib game template if you want a ready-made structure and Makefile.
• Join the Discord community for news and help.
• Check the extra libraries before writing utility code that may already exist as a single-file dependency.

If that workflow sounds appealing — code, compile, read examples, iterate — raylib is designed exactly for it. If you want a visual editor and a guided project structure, an editor-based engine will get you to a running game with less setup work.

GloDerWorks is a full-service web design, programming, eMarketing, and hosting company founded by Gloria Hansen and Derry Thompson. It serves individuals, commercial clients, and not-for-profit organizations, with most clients located in the UK Midlands (Bewdley, Wyre Forest, Worcestershire, and Kidderminster) and in the Princeton / Central New Jersey area of the USA. If you want a small site to establish a web presence, or a custom database-driven site, and you prefer working with a small studio rather than a large agency, GloDerWorks is positioned for exactly that.

Who GloDerWorks Is Built For

The company describes its objective as providing a "premium service that is second to none," and its site states it delivers "premium web sites without high agency fees." That framing points to a specific fit:

• Individuals establishing a first web presence
• Commercial clients needing e-commerce, membership, or content-managed sites
• Not-for-profit organizations needing member, event, or newsletter systems
• Arts and crafts clients, particularly quilt and fiber artists and related businesses and organizations, which the site highlights with a dedicated portfolio

If your project is outside those regions or sectors, the company still works with clients internationally — its site notes experience with clients in the USA, the UK, and several other countries.

Core Services

GloDerWorks lists a broad service range under the heading "Built By Us and Customized to Your Needs":

The site also notes domain expertise in consumer finance (including loans and mortgages), recruitment/jobs/careers across industries, and arts and crafts with an emphasis on fiber art.

The GloDerWorks CMS: What It Actually Changes

The most consequential part of the offering is the in-house CMS. According to the company, after building a design, it creates a CMS written by GloDerWorks and customized to the client's needs. The practical claims are:

• You can update one page, several pages, or the entire site's text and images
• Updates can happen daily, weekly, monthly, or on whatever schedule you choose
• No HTML knowledge is required
• No additional expense and no maintenance fees are incurred for updates
• You eliminate the need for a "webmaster"

That last point is the real decision factor. If your site changes often — new events, new products, new member content — a CMS that removes per-update fees changes the long-term cost structure compared with paying a developer each time. If your site is essentially static, that advantage matters less.

How It Works With Clients

The site describes a straightforward path:

1. Request a free quote — the site provides this as the entry point for new work.
2. Design and build — GloDerWorks creates the design and the accompanying CMS.
3. Client login area — existing clients have a login area for ongoing access.
4. Self-managed updates — after launch, you update content yourself through the CMS.

The company states its sites are "completely built by us" and that it does not outsource. For clients who care about who actually does the work, that is a stated differentiator.

What the Site Does Not Tell You

A few things you would need to confirm directly, because the available site information does not cover them:

• Pricing — the site uses the word "premium" and offers a free quote, but no rates, packages, or payment platforms are published. Do not assume any price level or that anything is free beyond the quote itself.
• Hosting terms — hosting is listed as a service, but plan details, storage, uptime commitments, and costs are not specified.
• Timelines — no project durations or turnaround estimates are given.
• Technology specifics — the site's keywords mention ASP and XHTML, but current stack choices for a new project would need to be discussed.

Is GloDerWorks a Good Fit?

Choose GloDerWorks if you are in the UK Midlands or Central New Jersey area (or comfortable working remotely), you want a small studio that builds everything in-house, and you value a CMS that lets you update content without ongoing maintenance fees or HTML skills.

Look elsewhere if you need published, transparent pricing up front, a large agency with a broad in-house team across many disciplines, or a platform-specific solution that the site does not list.

The most reliable next step is to use the site's free quote request and ask directly about pricing, hosting terms, and timelines — the three areas the public site leaves open.

ASP (Active Server Pages) is Microsoft's server-side scripting technology for generating dynamic web pages. When a browser requests an .asp page, the web server runs the script inside it, produces plain HTML, and sends that HTML back to the visitor. You would use ASP when you need pages whose content changes based on user input, database data, or session state — for example a login area, a form submission handler, or a product listing pulled from a database. It requires a Windows-based server running IIS (Internet Explorer-era Microsoft web server stack), which is the main practical constraint today.

How ASP works

The core mechanism is simple: the server executes code, the browser only ever sees the result.

1. A visitor requests a page such as contact.asp.
2. IIS recognizes the .asp extension and hands the file to the ASP engine.
3. The engine runs the embedded script (classically VBScript or JScript).
4. Anything outside script tags is passed through as HTML; anything inside script tags is executed.
5. The finished HTML is returned to the browser.

The visitor never sees your source code, only the generated page. This is the same request/response model used by PHP, Ruby, Python, and Node.js today — ASP was simply Microsoft's early entry into that pattern.

What ASP is typically used for

• Form processing — reading submitted fields and responding with a confirmation, error, or redirect.
• Database access — querying a database (commonly Microsoft SQL Server or Access via ADO) and rendering the rows as HTML.
• Session and state management — remembering that a user is logged in across multiple page requests.
• Dynamic content assembly — building pages from reusable includes so a header or menu is written once.
• Simple server-side logic — calculations, validation, and conditional display that must not be trusted to the browser.

ASP vs ASP.NET

These are often confused, and the distinction matters when choosing a technology.

If you are starting a new project on the Microsoft stack, ASP.NET Core is the relevant choice. Classic ASP is mainly encountered when maintaining or migrating an existing site.

When to consider something else

Classic ASP is a reasonable fit only when you are already running Windows/IIS and either maintaining an existing ASP codebase or working within a host that supports it. For new development, the practical alternatives are:

• ASP.NET Core — if you want to stay in the Microsoft ecosystem with modern tooling.
• PHP — the most widely supported server-side language across cheap shared hosting.
• Node.js, Python (Django/Flask), or Ruby on Rails — if your team already works in those languages.

The deciding factors are almost always your existing hosting environment, your team's language skills, and whether you are extending an old site or building fresh.

A note on the hosting context

The choice of server-side technology is tied to the hosting plan you buy. A Windows/IIS host is required for ASP and ASP.NET; a Linux host will not run them. This is why the technology decision and the hosting decision are usually made together — see the related question on choosing a hosting plan for how those constraints interact.

In stainless steel fabrication, design means engineering the part so it can actually be made: setting dimensions, material grade, joint and weld details, finish and tolerances, then checking that the workshop can cut, form, weld and finish it as drawn. It is not graphic design or product styling. This stage matters whenever you need a bespoke stainless item — a frame, tank, duct, pipework run or enclosure — and it usually starts from your sketch, sample or drawing rather than a finished CAD model.

What the design stage covers

Design work in a fabrication shop turns an idea into instructions the workshop can follow. That normally includes:

• Geometry and dimensions — overall sizes, bend radii, hole positions, and how parts fit together.
• Material grade — which stainless grade suits the environment (for example a grade chosen for corrosion resistance or for weldability). The fabricator should confirm the grade rather than assume it.
• Joint and weld details — where seams run, whether welds are visible or dressed, and how access is provided for the welder.
• Finish — the surface treatment required, such as a brushed, polished or other finish, and which faces are cosmetic.
• Tolerances — how accurate the finished part must be, since tighter tolerances generally mean more work.

How design decisions affect manufacture and cost

Most cost and lead-time differences between two apparently similar parts come from design choices, not from the amount of steel:

A design that is easy to weld and finish is usually cheaper and faster than one that only looks simple on paper.

Typical design-to-manufacture workflow

1. Brief or sketch — you provide a drawing, sketch, photo or sample, plus what the part must do.
2. Design review — the fabricator checks feasibility, suggests changes, and confirms grade, finish and tolerances.
3. Agreed drawing — a dimensioned drawing or model is signed off before cutting starts.
4. Fabrication — cutting, forming, welding and finishing to the agreed drawing.
5. Inspection — the finished part is checked against the drawing and finish specification.

The design review step is where most problems are caught cheaply, before any material is cut.

Common design mistakes that cause delays

• Missing dimensions, or dimensions that do not add up.
• No material grade specified, or a grade that is hard to weld or form.
• Finish left undefined, so the workshop guesses.
• No tolerance stated, leading to disagreement at inspection.
• No allowance for weld distortion on large or thin panels.
• Cosmetic faces not marked, so they get scratched during handling.

Questions to ask a fabricator at the design stage

• Which grade do you recommend for this environment, and why?
• Can this be made as drawn, or would a small change reduce cost or lead time?
• Which faces are cosmetic, and how will you protect them?
• What tolerance can you hold, and how will it be checked?
• Will welds be visible, dressed or hidden?
• What do you need from me before you can quote and start?

Getting clear answers to these before fabrication begins is the practical way to avoid rework and unexpected cost.