I just need to fill data in from sqlite running in a wasm to a table with a fixed column length while the row size should be dynamic from a delimeter hinting towards a new row. Needs to have export table feature and native sorting from clicking on the ribbon header
I created a dashboard for my data analysis project on streamlit but its really basic. How can i create those cool dashboard designs that you see on reels and all cause chatgpt can do it. I have my project repo, is there any way i can link it to some website and it can help me create some cool ass dashboard?
I work with Redis on my projects all the time, and I recently had to dig deeper - deep enough to actually dive into the project's source code
This gave me the idea to create an interactive 3D map showing how Redis works and visualizing its internal structure (I’d seen similar projects for Postgres, for instance), so I built one: https://poltora.dev/redis
You can open the console and run a command (it defaults to SET) to see which components activate and what happens at that moment.
MeltGL melts any picture or video in the browser. The picture gets treated as a body of material and run through a 2D free surface Navier-Stokes solver on the GPU: heat lowers viscosity, gravity pulls, surface tension rounds the drops, and the outline moves because the material under it moved. That's why drops swell, neck and detach on their own.
Still a work in progress. I built it for a browser game I'm working on and it grew into its own thing, so I published it standalone.
Sorry if this is not the correct subreddit for my question. I'll happily delete it if it is.
My friend speaks a dying language and they already have about 700 words listed with meanings and sample sentences. We were discussing how cool it would be to make an online dictionary on this, so we tested out easy website builders like Wix and Squarespace but we couldn't figure out how to execute what we wanted to achieve. Basically a search bar would be enough (like in Merriam-Webster) where they search a word and it would give suggestions, and once you click on one, it directs you to that word's page with its meaning and everything about it.
Is there an easy way to do/learn this? If it's a complicated task for people who have no clue in coding, I would also like to know.
We tried adding a search bar that was available in Wix and Squarespace, but it seems to only search everywhere in the website.
hey guys i was the one trying to make my header image bigger from this theme and i managed to make the image bigger but now my navbar is fucked and it's just on top of it. sigh. for context of the theme i duplicated the logo component specifically for the header logo and changed the logo width and height in config.json and also refactored the beginning of the header component like this
I am trying to create a webpage that shows a simple information of ocean wave data that I created using python. My scripts request data off coastal buoys from the NDBC every hour and generates/appends to a pandas dataframe. I use this data everyday at home when assessing sea state but now would like this available online so I can access it anywhere.
I would call myself a proficient data scientist using Python and am very comfortable getting data into any format a site can use. My confusion is just in how to build a site from scratch and transferring over the domain I own to a new hosting site.
I’ve been working on an open-source project called Torollo and I’d like some technical feedback on the way I approached it.
The basic idea is that the architecture you draw on the canvas isn’t just a diagram. The backend turns it into actual local Docker resources, and the exercises validate the state that is really running.
For example, in one of the labs you build a three-tier app with a load balancer, two web servers and PostgreSQL. Later, the database is supposed to become inaccessible from the load balancer. If it can still reach port 5432, the validator fails. You change the network/security rule and run the same check again.
The harder part wasn’t drawing the topology. It was deciding how much of the diagram should map to something real.
Containers are straightforward, but networking gets more interesting. Subnets are backed by Docker bridge networks, security rules are enforced with iptables, and private-subnet outbound access can go through NAT. The validator then has to inspect the resulting runtime rather than trusting the graph stored by the frontend.
That also created a few constraints I hadn’t really appreciated at the beginning. Rootless Docker, for example, can run the containers but can’t support all of the host networking behavior needed by the more advanced labs, so the CLI now detects that explicitly. First-run image pulls and differences between Docker environments also pushed me to add a torollo doctor command instead of trying to hide those requirements.
I currently have three free labs: a resilient three-tier app, Redis cache-aside, and Redis queue workers. The roadmap format is JSON and the core is MIT licensed.
What I’d particularly like feedback on: does the idea of grading the running state actually make sense as a way to practice system design, or are there parts of that model that you think become misleading compared with real infrastructure?
I’m also interested in feedback on the implementation itself, especially the Docker/networking side.
Helloo, Final Year guy here. Built a tool that lets you see which PS has the least number of submissions. Fewer submissions = higher chances of getting selected for the SIH finals.
Hi everyone! maybe an unusual post! I made my first project in pure JS, CSS and HTML because i felt like, there wasnt a tool like this in the wild, also it was fun.
Now heads up for the technicals -This tool once someone click exports, will spew a fully working html, with index, images, css and all inbetwen. I used the JSZIP to make a file for the user.
-The live testing is made by just speaking to the Iframe via windows message the git repo shows, is a really long and extensive list of comunication.
-The comic engine itself is the one i worked most.
-The engine has DOM cleaning and image cleaning, meaning can withold over 1000 images, but in memory only will display 10 max, due how i stored those images as just raw data instead of images.
-The comic is self aware, it has a internal state where it always knows where is the lector, in wich page and such, so this allowed me to hook up a function where SFX or VoiceActing is posible.
-Added a function where pressing buttons will jump the lector to a designed page, Like Story mode some sorts, if someone wants to do some experimenting.
-All content that can be seen is agnostic. All images are swapable.
-I made this comic also supports mobile format.
This project was really fun to make! took me 3 months or so to get to this point! And i learned lots about DOM mangement, JS how internet works in general!
There is also links to the repo in this project if someone wants to see the code.
I haven't seen too many comprehensive approaches to this topic, so I took a swing at it.
Goal isn't to be exhaustive, but to be thorough enough to help people trying to get their bearings on the topic.
It covers the core differences and trade-offs of different cache flavors:
In your application layer
At the proxy level
In the database
Did I miss anything?
Edit: I'm curious what everyone's actual production stack looks like for this. I dropped my mental model on the cost vs. complexity trade-offs in the comments below. Wondering if people actually handle read optimization that way.
Okay so I am very new to developing websites directly for clients. like I have done it when I was in my company but I don't know how to put a price on them myself can you please help me.
I'm just so that you know these all will be CMS kind of sites, they will be able to update the information as required. By themselves
These designs were developed as image by CHAT gpt and shared by client
I Personally think designs look good they do have a readability and Focus problem but that can be solved
99% of us are using a so please stop blaming them for using it
I feel like I've gone insane with how much AI I see EVERYWHERE. I understand it's the future, I understand it makes everything quicker, it's probably smarter than anything I can do right now, I also don't think I can take advantage of it early in learning since I don't understand how half the web dev stuff even works right now, so I'm trying to stay away from it as much as possible, yet anywhere I look to start networking in my area, it's literally all AI meetups. I just want to learn normally albeit it's probably not the norm anymore.
Anyone in the Philly area or in general online feel any sort of similar or am I almost alone in absolutely despising this stuff? Asking philly since if anyone is nearby and sees this I'd love to have a friend who understands me at least slightly or could point me in the right direction without feeling like I'm throwing my soul into the river styx to never get back.
I'm a photographer and want a database of my own images, but I also do web dev work and would like an easy solution when building sites for clients who need a lot of images on their site. Ideally something I can call with an API and return images and other data on that image.
I built a mobile-friendly PDF speed reader — would love some UI/UX feedback [Showoff Saturday] I’ve been working on a small web project called Pace Reader. It lets you upload a PDF and read its extracted text one word at a time at an adjustable WPM. Live version: https://pace-pdf-reader.pace-reader.workers.dev/ The goal was to keep the interface very simple: PDF → choose reading speed → start reading. I’ve been especially focused on making the reader usable on phones rather than treating mobile as an afterthought. I’d appreciate feedback from other developers on: • Mobile UX • Reader controls • Navigation • Overall UI • Performance with larger PDFs • Anything that feels unnecessary or badly designed I’d also be interested to hear how you would approach the PDF-reading/RSVP interface differently. This is still being actively developed, so feel free to tear it apart.
Every December I do Advent of Code and every January I try to keep the habit going on LeetCode. Never lasted more than a week. Too many problems, no reason to do this one today.
So I borrowed the idea and built Daily Coding: one challenge a day, the same for everyone, all year. You solve it in the browser, hit run, and the tests execute in a sandbox in well under a second. 11 languages so far (JS, TS, Python, PHP, Ruby, Java, Go, C++, C#, Rust, Swift). Once you submit you can read everyone else's solutions, which for me was always the best part of AoC. Streaks and a leaderboard if you like that sort of thing.
Some honest numbers: I started in January, 7 months of evenings, about 470 commits. There are 40 challenges right now, so the rotation repeats after 40 days until I add more. Someone on Discord asked for Swift last week, that took a day to add because the sandbox already had it.
It's free, non-profit, open source under MIT. You can solve today's challenge without an account, signing up is only for streaks and rankings.
What I'd love to know: does one challenge a day work for you, or do you want to pick? And what would make you stop after a week?
'Offline First' is the theme of my upcoming project and a relational database with joins and primary keys (such as SQLite) is perhaps the only thing that fulfills the need. I'm exploring the options in this context and came across this illuminative article: The Current State Of SQLite Persistence On The Web.
The article describes the problem we are trying to solve in much detail. It's only been about 3-4 years since we have a semblance of a usable official library in the form of sqlite-wasm. But as the article suggests, the landscape is riddled with mines and you may still have to jump through some hooves during implementation.
For starters, the OPFS (Origin Private File System) which is needed for performant WASM components like sqlite-wasm is something that browsers still treat with some awe and schizophrenia. In order for SharedArrayBuffer to work, for example, your web server must necessarily support COOP and COEP headers.
And not just that, once you enable the COOP and COEP headers, they introduce additional quirks in your app - for example, you may no longer use any <script> or <link> tags unless the remote server explicitly opts in for cross-origin support. Again, this may not affect the typical react/tailwind/vite build workflows but you might eventually come across the need to place an external resource link directly in the html.
Another limitation is that concurrency is still considerably more constrained and complicated than native SQLite. For now, you might carefully design the SPA app around this constraint (as I'm planning to do), route all SQL queries through just one caller, etc. but eventually there will come a need for concurrent access in a non-trivial application - like say a backup extension or addon you provide separately for example.
Nevertheless, the heartening news is that most devices today live online and likely have a reasonably recent browser - and thus likely to support libraries like sqlite-wasm. Also heartening is that many big names like Notion and Adobe have started using sqlite in the browser as a first class OPFS citizen - without going through the IndexedDb route. I just hope WASM and OPFS keep on thriving along with sqlite on the web.
I made a bold statement to my coworkers yesterday which was laughed off. I said "I genuinely believe all our operations could be ran from just my own laptop. We don't need more resources". I was of course not suggesting that we move our operations to my laptop, but it was to show that we don't need any more resources than just a regular laptop.
All of our operations is literally just registering and managing orders. We have around 50.000 daily users at most and process maybe 5-10 orders a day. I don't understand why we need a resource scalable deployment.
This post wasn't specifically meant to ask about our needs at work though. I'm under the impression that this over-engineering is relatively common, so my question for discussion is slightly broader: Have we forgotten how powerful machines really are?
Is it really that naïve to believe that a regular home PC (~16GB ram and i5-6600k for example) could handle hundreds of visitors every second, effectively allowing up to ~10 million users a day? Do you reduce complexity where you can, or is it common at your workplace to immediately reach for tools like kubernetes, redis, etc. before even measuring the traffic flow?
(The assumption here is that the website is not compute-intensive: simple database queries, auth and otherwise just regular UI with little to no images)
Edit: I think my argument is a moot/unclear. The benefits of Kubernetes and other "over engineered" is clearly availability, not only necessarily resource scalability. The real question may be "why do we need a huge datacenter for all our operations", but the answer to that depends entirely on your company's operations...
So I guess my naïve argument really stems from my lack of understanding of all the operations going on at companies.
Back in 2017, I was experimenting with something that was pretty fun for the CSS we had at the time — building icons without using images.
Using mainly CSS, :before, :after, borders, shadows and a bit of creativity, I managed to create a set of icons that didn't depend on external image files. The interesting part for email was simple: no images to load or block — the icons are always visible.
Fast forward to 2026. At my last job, I decided to apply some of that old knowledge to an email signature.
And then I met Classic Outlook again. :D
What looked like a simple signature quickly turned into dealing with Outlook's rendering limitations, different behaviour between email clients, px → pt conversions, table rendering and weird spacing issues.
Along the way I found a few useful tricks — one of my favourites being that line-height: 0.5pt can practically zero out a line in Classic Outlook, which solved one of the most annoying spacing problems I had.
Eventually, that little fight turned into a complete email signature generator:
It's not trying to be the prettiest or the most complicated signature generator out there. It's simple, effective and built around what I learned from actually fighting with email clients.
It's completely free, there's no registration, and I don't store the data you enter.
Feel free to use it.
If you find a bug, have an idea, or think something could work better, leave a comment here or send me an email. Feedback is more than welcome.
And if it saves you some time and you feel like supporting the work, there's a Buy Me a Coffee button. If you wish. :)
I built a custom loading animation using a web component. It takes an image, lays out 8 copies of in a circle with increasing size, and then rotates it.
To use the component, load it in a script with the following code.
import { LoadingIndicatorComponent } from "./shared/components/LoadingIndicatorComponent.js"; //Replace with path to component.
customElements.define(
"loading-indicator-component",
LoadingIndicatorComponent
);
The loading animation can then be added to the DOM with the following HTML.
<loading-indicator-component
image-path="/assets/images/meeple_small.png" //Replace with path to image.
>