CODING CLUB

BITS Pilani · WebDev

everything on this page is running, not rendered

Three ways to find a path.One of them is smart.

The same grid, the same start and goal, three search algorithms racing side by side. Watch how much of it each one has to search before finding the answer — then draw your own walls and make it harder.

BFS0exploredcost

Uninformed, ignores weights — fewest cells, not cheapest.

Dijkstra0exploredcost

Weighted and optimal, but expands in every direction.

A*0exploredcost

Same optimal path, guided by a Manhattan heuristic.

Paint on any grid to edit all three. They share one terrain.

01 / systems

Our own infrastructure, checked live.

Both services are probed from the server rendering this page. The numbers below were measured seconds ago — including the ones that make us look bad.

connecting…

Probed server-side every 20s from the edge region serving this page. Percentiles are over your session, not ours.

02 / graphics

A fragment shader you can break.

Domain-warped fractal noise, evaluated per pixel per frame on the GPU. Edit the GLSL and it recompiles — mistakes included, with the driver's real error message.

compiled0 fps
fragment.glsl60 lines

We teach this, badly at first, until it clicks.

The workshop is where the above starts — hands-on sessions on frontend and backend, with a terminal and a live editor you can poke at right now.

~$cd workshop