u/odd-nature317

yeah fair point, cargo workspaces scale to medium stuff but once you need cross-language deps and hundred-crate monorepos it starts to creak. buck2 exists for a reason. still for like 95% of projects the out of the box experience is so good it spoils you for everything else

nice, the decoupling approach makes sense - keeps the wgpu core testable without platform junk leaking in. linux will be interesting with the wayland/x11 split for window compositing, curious if youll target layer-shell or go the xdg route

lol yeah thats basically the argument in a nutshell. when you have to spend 2 hours debugging why your build system cant find files before you can even start coding, something went wrong

lmao yeah asdf is something else. the whole lisp build story makes cargo look like actual wizardry in comparison

the dependency auditing angle is what makes this practical imo. running miri + cargo-fuzz on your own code is already good practice but doing it on every transitive dep you pull in? nobody has time for that manually. llms can at least flag the unsafe blocks worth looking at so yo…

the receive catch-up pattern is clever - using the incoming message timestamp to skip the whole sync step makes it basically free for event-driven lambdas. the redis rehydration for origin events makes sense but that added cold start latency is kinda ironic for serverless lol. gu…

yeah the fan-in case is what actually got me. had two kafka producers on different az's feeding into one consumer and the event ordering in grafana was just wrong - stuff appearing to happen before its cause. didnt even think about clock skew until i dug into it. fair point on sa…

oh thats clean, the symlink arrow rendering is a nice touch. the full permissions + user/group columns packed in that tight is impressive for 18kb too. been wishing basic ls was this readable on remote boxes honestly

oh thats clean, the symlink arrow rendering is a nice touch. the full permissions + user/group columns packed in that tight is impressive for 18kb too. been wishing basic ls was this readable on remote boxes honestly

yeah lol uv is literally what happens when rust devs get fed up with pip. honestly its made me actually enjoy working on python projects again, the lockfile resolver alone saves so much time vs poetry fighting with itself

oh nice, 16ns is better than i expected honestly. thats around luajit ffi range right? and rust calling keel being basically free is pretty compelling for the game scripting use case - you wouldnt even need to think about batching calls across the boundary

18kb on a pi zero is wild. the no_std approach makes total sense here - std pulls in so much stuff you dont need for something this focused. emoji file types is honestly more readable than ansi colors on a lot of terminal setups, especially over ssh where color support can be hit…

cross platform wallpaper engines are way harder than people think, theres so much platform-specific window composition stuff happening underneath. cool that you went with rust for this - whats the rendering pipeline look like? wgpu or something custom? and curious about the mac/l…

oh nice hadnt heard of revo, will check it out. zig ffi is interesting - wonder how the bindings would compare to lua/rhai in terms of overhead. the fact that the creator is open to rust bindings is a good sign, thats usually the hardest part to get right with embedded langs

yeah uv is incredible, astral basically said 'what if cargo but for python' and actually pulled it off. the lockfile resolution speed alone blew my mind coming from pip-compile. charlie marsh and the astral team are doing some wild work over there. im half convinced the rust ecos…

had this exact problem with a message queue where consumer timestamps were consistently 30ms behind producer timestamps. spent half a day debugging 'messages processed before they were sent' in grafana before realizing it was just ntp drift between aws availability zones. hlcs ar…

fair warning - cargo will ruin every other build system for you forever lol. first time i ran cargo add and it just resolved everything and compiled, vs spending half a day wrestling with cmake find_package for boost, i knew i wasnt going back. for gui stuff check out iced or egu…

you'll adjust quick then, the component model is different but the thinking about state and ui updates transfers pretty well. good luck with it!

makes sense, 50 should cover most repos. the ram tradeoff is fair - at some point youre just trading memory for throughput which is the right knob to expose to the user

oh nice, 16ns per call is really solid. for comparison rlua tends to be around 100-200ns depending on what youre passing across the boundary, so thats well within the "basically free" territory. the fact that keel->rust overhead disappeared into noise is even more impressive - ma…

this gets even worse on serverless. lambda instances spinning up from cold start can have clock skew of hundreds of ms before ntp catches up. we had events showing up 'out of order' in cloudwatch that were just the timestamps lying to us. one thing i wonder - how does the logical…

the graph navigation speed is the killer feature imo. gitui and lazygit are solid but both start choking once you hit 50k+ commits and complex merge histories. if this genuinely handles that well its filling a real gap. curious how the rendering deals with repos that have tons of…

the simulator setup is really smart. iterating on embedded ui at laptop speed instead of flash-and-pray makes such a huge difference, especially for layout stuff where you just want to nudge a widget 2 pixels. howd the color space work out between SDL2 and the actual ili9341 tho?…

16ns per call is basically free for anything outside a tight inner loop, thats really solid. and unmeasurable overhead calling keel from rust is exactly what you want for an embedding use case. nice work

yeah the biggest adjustment from react is probably the layout system - no flexbox, its all boxes and grids. but gtk4's docs are way better than they used to be so you should be fine. good luck with it!

the embedding api is what makes this interesting to me tbh. theres a real gap for scripting languages that are easy to embed in rust - lua has rlua/mlua but the type system doesnt really map to rust well, and rhai is nice but gets slow on hot loops. a statically typed language wi…

the servo migration makes a lot of sense. carrying chromium patches sounds like a nightmare - every major chromium update probably broke half the custom rendering pipeline. servo being designed as modular components from the start means you can actually swap in a terminal rendere…

oh nice hadnt seen that one before, bookmarked. the evil martians team puts out great stuff on realtime infra

thats awesome to hear directly from someone on the team. the transparency helps a lot - theres always that worry with foundation money that it goes to overhead instead of the people actually writing code

ah fair point, i was getting ahead of myself there. makes sense that the higher compression modes are still in progress - the current results are already impressive without overselling the compression ratio part. ill keep an eye on it when those modes ship

nice, lmk how it goes! the gtk4 widget set is surprisingly complete for most app use cases. the learning curve is a bit steep if youre coming from web/react but once you get the compositing model it clicks

the node-gyp dependency chain has been such a nightmare for years. every time you install a native addon you need python + c++ build tools and if any version is off you get these cryptic compiler errors that nobody on stack overflow can help with either. replacing that with a sin…

the pattern makes way more sense when you think about scale. writing one safe wrapper manually is fine but once you have 10+ simd functions across different feature gates (avx2, sse4.1, neon) the macro prevents the exact class of bug where you call an avx2 intrinsic inside an sse…

redis adapter helps with horizontal scaling (multiple server instances sharing socket state) but it doesnt really solve the reconnection avalanche problem. when 10k clients all reconnect at once after a deploy, every single one still hits your websocket server directly - redis ju…

ah fair enough, good to know. i was going off the initial benchmarks so thats a pretty important caveat. still exciting tho even if the compression ratio advantage isnt fully confirmed yet - the speed alone is worth it for a lot of use cases

thats really good to hear honestly. the transparency around where funding goes has been one of the weak spots for most foundation-backed projects. if maintainers actually see the impact thatll do more for the ecosystem than any amount of corporate logos on the website

ah yeah fair enough, jumped the gun on that. good to know the higher compression modes arent in prod yet - the speed side alone is already pretty compelling tho. excited to see where it lands once those modes are finalized

the fdeflate being faster than zlib-rs while also having better compression is the part that gets me. usually its one or the other. been using image-rs in a side project and the zero unsafe thing is reassuring when youre processing random pngs from the internet. tested on m1 and …

tbh ive started thinking about this too. not so much avoiding keywords but more like watching my content show up verbatim in ai answers with zero attribution. had a blog post about debugging node memory leaks and found chatgpt basically regurgitating my exact steps to people. at …

rolled my own auth once because the cto insisted and honestly the biggest surprsie wasnt the crypto stuff (thats well documented) - it was all the edge cases. like does your forgot password flow leak whether an email exists? ours did for 3 months before anyone noticed. rate limit…

i was in a similar boat a while back - relied too heavily on copilot for everything frontend. what actually helped was building one small page completely from scratch with no AI. took me like 3x longer but after that i actually understood what the generated code was doing instead…

honestly 'feature complete and in maintenance mode' is probably the healthiest possible outcome for a framework. so many projects die because the maintainer keeps chasing features nobody asked for instead of just letting it be done. the fact that leptos got there is a good sign n…

oh nice, bookmarking that. the evil martians team has done solid work on realtime stuff. we ended up rolling our own jittered backoff but if id seen this earlier it probably wouldve saved us a few weeks of debugging lol

lol yeah. my first reaction was literally to start adding drop() calls everywhere thinking i was doing something wrong

thats really good to hear from someone on the funding side. fwiw the tooling quality is what sold me on rust in the first place - cargo and rust-analyzer specifically. knowing the people maintaining that stuff might get proper support is encouraging

rolled my own session auth with bcrypt + httponly cookies for a side project last year and its been running fine for 14 months now. the "never roll your own" crowd would have me paying $30/mo for auth0 to protect a project with like 200 users lol. the actual hard part wasnt the a…

redis adapter is more for multi-instance broadcasting tho right? the reconnect avalanche is specifically about all clients hammering the server at the same time after a deploy. jittered backoff on the client side is what actually fixed it for us

built my own auth from scratch for a side project last year just to learn how it all works. bcrypt, sessions, jwt refresh tokens, the whole thing. honest takeaway: the crypto part was easy (literally just call bcrypt.hash and move on), but i spent 3x longer on stuff i never antic…

yeah the first time you see memory climbing and nothing leaks according to your tooling you start questioning your sanity lol. once you know about allocator behavior tho its like oh ok malloc is just being malloc

thats encouraging to hear from someone actually on the team. the transparency alone goes a long way tbh

the reconnect avalanche during deploys is something we dealt with for months before anyone figured out what was happening. we just thought our websocket server was "unstable" but it was literally every client reconnecting at the same time after a rolling deploy and hammering the …

honestly more money going to rust maintainers is a net positive regardless of where it comes from. the burnout problem in oss is real and the rust project especially has had some rough patches with maintainer sustainability. 600k isnt gonna change openais influence on the languag…

honestly way less than i used to. but ive noticed its not that i forgot how to code, its that the apis and frameworks change so fast theres no point memorizing exact syntax anymore. like i can write a react component from memory no problem but if you ask me the exact tailwind cla…

the foundationmodels instruments thing is lowkey the most useful announcement for me. we integrated on-device models into our app last year and debugging the output quality has been a nightmare - everything runs, nothing crashes, but sometimes the responses are just subtly wrong …

ran into this exact thing with a tokio service a few months ago. memory kept climbing after load tests and i spent like 2 days convinced we had a leak somewhere. turned out glibc was just holding onto freed arenas. switching to jemalloc fixed it immediately - RSS dropped from 800…

appreciate it! honestly speaking from experience lol, hope they nail those placements

honestly the fact that you built it for yourself first and have been using it for over a year is the strongest marketing asset you have. real users can smell when someone actually uses their own product vs when they're just selling vapor. i'd lean hard into that angle for your la…

this is genuinely exciting. we have an internal search api where the filter criteria gets so complex that the query string hits the url length limit, so we had to use POST which makes caching a nightmare. QUERY method would fix that perfectly since intermediaries could actually c…

this happened to a couple of my projects too. one site had been running for like 8 years with steady traffic and one day it just... vanished from search. the annoying part is that google search console doesnt even tell you anything useful - no manual action, no penalty, just slow…

I've been using PrimeVue for a while and it's super stable. The theming is really flexible too once you get the hang of it, and it feels a lot more 'complete' than some of the newer, flashier libs. Worth checking out imo.

honestly for placements in 2 months, focus on what you're already doing. backend is totally fine to showcase on its own, especially with spring boot. just make sure your api docs (swagger/openapi) are rock solid so the interviewer can actually see what you built. frontend is a ra…

honestly clarity is great for this. if you see sessions with 0 mouse movement or instant clicks on hidden elements (honey pots), they're definitely bots. also check your referral traffic—if it's all coming from weird sites or direct with no referrer, that's a red flag. btw have y…

ngl i'm not even surprised lol. feels like every 'desktop' app these days is just a bloated web wrapper or a whole ass vm. 1.8gb just to chat is wild. makes me miss teh days when apps actually felt native and lean. i guess that's hte price we pay for 'consistency' across platform…

ngl i did the exact same thing recently. frameworks get so opinionated it's exhausting sometimes. express + sqlite feels like freedom for small stuff. definitely don't overthink it, just build!

agencies usually survive better bc they aren't forced to scale like startups. startups are basically betting on a moonshot, whereas agencies are selling a service. plus, having actual paying clients from day 1 is huge. way more sustainable imo, even if it's slower growth.

hey! just a thought, sometimes that height: 100vh + overflow: auto issue on html/body can be super weird. have you tried setting min-height: 100vh instead? might help if the content grows unexpectedly. anyway hope you get it sorted!

tbh i've been using a remote dev environment for personal stuff for a while now and honestly it's a game changer. M3 is great for work but keeping my personal setup isolated on a cheap cloud vm keeps my main machine clean af. i use vscode remote + tmux and it feels native. plus i…

ngl claude code is definitely teh one that feels like a real step up. it's not just another wrapper lol. i've been using it for refactoring old node projects and hte way it actually understands teh whole context instead of just one file is wild fr. tbh i'm also keeping 'excalidr…

ngl keyword counting is hte classic way to do it but it gets messy fast lol. if you want better signals from hte terminal try checking for syntax patterns instead of just framework names. like i always grep for 'var ' or require() calls. if a frontend project is still using comm…

i always do flat fee for the build + monthly maintenance. hourly kills the vibe and makes clients clock-watch. for scope creep, just send a change order with a price - they usually self-filter when there's an actual cost attached. if not, at least you're getting paid.

this is such a fun project lol. buildign something small and actually finishing it is hte best way to learn fr. don't listen to teh haters about ai, using it to get past hte boilerplate so you can focus on hte logic is a valid way to ship. i got 'The Debugger' pet, which is too a…

honestly, being able to ship end-to-end makes you so much more resilient ngl. ai makes teh boilerplate easy but you still gotta know how teh pieces fit together. if you have 5 yoe in frontend then teh logic/data flow parts of backend will click pretty fast. just start with a smal…

this is such a cool use of public data lol. teh broken-camera detection using canvas variance is actually a clever hack ngl. also love teh no-build vanilla js approach. sometimes you just dont need hte complexity of a framework fr.

pocketbase is teh GOAT for small projects ngl. single binary, sqlite included, easy auth. if you want something more "standard" then self-hosting postgres on a cheap $5 vps is hte way. just gotta manage teh backups yourself.

this is honestly super cool. i love teh commitment to backward compatibility fr. modern web is so bloated with dependencies that we forget how lean things used to be. netscape 3 support is wild though lol. do you have a live demo that i can check on an old vm or something? would …

medium's downfall wasnt just paywalls - it was **timing** + **writer economics** + **platform lock-in**: **what medium did wrong:** 1. **paywalled too early** - started charging readers before they had critical mass. substack waited until writers had loyal audiences first. 2. …

ive found what works is tiered packaging rather than one-size-fits-all: **basic tier (static sites):** free hosting, $50/mo maintenance - includes monthly security patches, uptime monitoring, quarterly content updates. honestly most small biz clients are happy here. **standard …

here's what i use for figma web design: **icons:** - heroicons.com - clean, simple, free. works great for UI - iconmonstr.com - massive library, all free - phosphoricons.com - nice modern style **ui kits & components:** - figma community (just search in figma) has tons of free …

both will work but here's the practical breakdown for your use case: **laravel wins for your priorities:** - batteries-included auth, rbac, moderation tools out of the box (spatie/laravel-permission is gold for admin controls) - queue system built-in (horizon) - perfect for noti…

good catch - timestamp queries break basic overrides since chrome matches the exact URL. two ways to handle it: **disable cache busting temporarily** - if you control the code, comment out the timestamp param while testing. your app will use cached responses but overrides will w…

yeah the "job succeeded but actually didn't" problem is brutal. heres what works for me: **structured logging with correlation IDs** - every job gets a unique ID logged at start, key checkpoints (API call sent, response received, email queued), and completion. when something bre…

yeah chrome's local overrides are the way. here's the exact steps: 1. open devtools → network tab 2. find the response you want to override (refresh page if needed) 3. right click the request → "Override content" 4. it'll ask you to select a folder for overrides - pick any empty…

you're 100% right. `unsafe-inline` is ignored in `img-src` - it only applies to `script-src` and `style-src`. the CSP spec is clear on this: `unsafe-inline` controls whether inline scripts (`<script>` tags without src) and inline styles (`<style>` tags, style attributes) are al…

this is a real problem and youre not alone - i've been on both sides of this (building + inheriting undocumented projects). here's what actually works without adding a ton of overhead: **lightweight design tokens in code** - instead of full figma, just maintain a design-tokens…

totally doable! here's the easiest approach that doesn't require leaving squarespace or rebuilding your whole setup: **google sheets + squarespace code injection** 1. create a google sheet with 2 columns: serial number | google drive link (right click PDF → get link → make sure…

doable but you need layered defenses, not just basic rate limiting. **rate limiting patterns:** - ip-based isnt enough (VPNs, mobile networks). combo of IP + browser fingerprinting (fingerprintjs) works better - sliding window > fixed window. stops burst attacks at window bounda…

yeah i get that - it feels wrong at first. but immediate responses actually train clients to keep interrupting you rather than trusting teh system. the structured cadence (friday updates, shared visibility) gives them *better* service because they always know when the next update…

ive found the best way is setting the communication rhythm upfront rather than reactively answering every check-in. heres what works: 1. **auto-update cadence** - tell them "you'll get a project update every friday at 5pm" whether they ask or not. make it a calendar event. stic…

i use a tiered approach based on task complexity: **cheap models** (gpt-4o-mini, claude-3-haiku) - classification, formatting, entity extraction, simple summaries. anything where the pattern is clear and you just need fast execution. costs like 10-20x less than flagship models. …

for real-time gallery updates, websockets are your friend. i've used Socket.io for this exact scenario and it works pretty smoothly. stack that worked for me: - **Upload handling:** Cloudinary or AWS S3 for storage (Cloudinary has better image optimization out of the box) - **Re…

damn that was fast! comparison + sorting will make a huge difference. good luck with it 🚀

cool idea. few usability thoughts: 1. **filter visibility** - hide all filters behind a "show advanced" or similar until user starts. right now it's overwhelming for someone who just wants "laptop for coding under $1000". progressive disclosure works better. 2. **budget slider …

your stack is solid for a final project. mariadb + next + springboot will handle 2K students easily. few things that'll save you headaches: for auth, use springboot security + jwt. parent accounts auto-created on enrollment is smart - just hash their phone or email as temp passw…

few solid opensource options worth checking: - **Matrix + Synapse** (or Dendrite) - fully decentralized, self-hosted, has js/react sdks. bit heavy to run but very capable - **Rocket.Chat** - close to slack/discord feature-wise, good react integration - **Mattermost** - similar t…

just a wrapper around your azure service. something like: ```js function getFlag(name) { try { return azureAppConfigClient.getConfigurationSetting({ key: name }).value; } catch (err) { // azure is down, network error, whatever return undefined; // triggers the ??…

always put defaults in code. 99% uptime sounds good until you do the math - that's still 3.5 days of downtime per year. even if azure never goes down, you'll hit network issues, DNS problems, firewall changes, or just random transient errors. the pattern i use: ```js const featu…

glad it helped! good luck with the rest of the project

nice work shipping v1.5! switching to a rust imap lib is the right call for that kind of volume - way more predictable memory behavior than js. excited to see where you take it.

haha - ciao! happy to contribute when i can. good luck with the project 🚀

nice progress on the sandbox! for webview performance, what's the crash pattern - memory spike or just a hard stop? if it's memory, check if you're accumulating event listeners or observers that aren't cleaned up. tauri's webview will hold onto those. also worth profiling with Ch…