> In 2024, everyone looking for a code editor knows how to extract a tar.gz right?
I'll raise my hand and say I still get the `tar` terminal command options confused and have to pause and figure out the file format I'm dealing with and the options. So, no, I usually don't know, and have to look it up in the manpage/help. "Was it -xvfz for this one? Shit I just did this recently..."
I helped write what might be a similar API gateway prototype in rails (made a DB query and decorated downstream requests with auth/role/etc headers). You might have threadpool/process/concurrency tuning to do. Even then, I don't think rails is a good solution for what is essentially an HTTP proxy, and I would've pushed for a different tool if time wasn't an issue. Rails was fast to build, I'll give it that. We ended up getting downstream service to $1M ARR so rails wins out against my "let me write it in XYZ language/framework" again somehow.
Came to upvote this. I think that github component in particular worked really well for me on a recent experiment. Server-rendered HTML can use custom components in our fancy world today! It's a feel-good place to be compared to just a decade ago imo.
I'll throw out the the GTFS transit standard involves publishing zipped CSVs representing your DB tables regularly. There are nice things about it and downsides IMO. This is how google map's transit directions function -- they rely on agencies to publish their schedules regularly in zipped CSVs I think.
One downside is that dev experience is pretty bad in my opinion. It took me years of fiddling in my free time to realize that if you happen to try to use the CSVs near a schedule change, you don't know what data you're missing, or that you're missing data, until you go to use it. My local agency doesn't publish historical CSVs so if you just missed that old CSV and need it, you're relying on the community to have a copy somewhere. Similarly, if a schedule change just happened but you failed to download the CSV, you don't know until you go to match up IDs in the APIs.
I still have my OG backlit kindle. It's showing its age with a tiny tear that lets backlight through, but I'm still pushing through books on it. I'd be curious how these newer E-ink displays have improved, wonder what the refresh rate (hz?) is on them.
just in case I confused: i'm not sure mold helps with the size of that directory :D. I was commenting on how big my rust repo is really, just saying that mold seems to help big builds like mine
This linker noticeably improves rust development happiness on an exploratory, chunky repo of mine that is trying to be a big ole web monolith (uses SeaORM and axum/tokio). You don't want to know the size of my `target` directory, but incremental builds are snappier!
Looks slick for how quickly it was built. I was surprised by the download size and RAM footprint, but... if it was easy to do cross-platform, I'm thinking this is still ahead of electron on footprint? Or at least competitive. Interesting!
same. Back in ~2009 I had the pleasure/horror of debugging/fixing "TCL drivers" for a piece of Java software that aimed to integrate with various pieces of hardware. I'll never risk putting anyone else through a similar torture if I can help it. ...then again I've left a trail of Ruby/Rails behind me that might get the same job done :)
Takes me back to my BF1942 days, careening around maps in planes and tanks. I was dirt poor. I usually had to get a ride to the video rental store to rent console games. I'm thankful to have kept busy thanks to these groups. It kepted me interested in computers and exposed (a little) to software dev. ...and awesome music! Man, the music...
Here here. I backed Onivim hoping it was going to shine a light in the darkness, and it seemed promising, but ultimately was abandoned? I think, unsure.
I remember reading about PropelAuth somewhere and thinking that Rust might slow down development -- something I wanted to be proven wrong about since I've been learning rust off and on, and like some things about it. It seems it's ending up up a mixed bag, and the negatives in the bag are still light enough that you're carrying it forward. Thank you for this blog post!
I feel this pretty hard, but left the small-turned-big company within the last year.
So I thrashed around in your latter section for a few years. Luckily the old organization gave me space to work on what I choose, if I could come up with impactful things. But turns out those things are usually visible by leadership, not the dev with his head buried in guts of the company.
Jury's still out on the new company but the difference in impact was visible from Day -1 (I was given access to datadog and spotted some random, high-throughput DB path that needed an index).
I have this same experience. I put ubuntu LTS on a family member's computer back in 2011, made sure the browser icons were big and front/center, and the support nags stopped. They said they loved whatever I did. I think there is some security-by-obscurity in there too, where all the insane spam/fraud/virus stuff couldn't even work on ubuntu if she ended up clicking on one. Nowadays I take it with a grain of salt: The support nags might have also stopped because other family got scared I would wipe their computer and put this new thing on there they were scared of having to learn.
It's hard to infer from some quick documentation-reading whether kubernetes is required to enjoy a lot of the described benefits. Feels like a big first step: "Adopt kubernetes." Having been at a medium-sized org leaning into kubernetes, I can see the draw of a system like this, especially for non-IC roles.
I'll take a devil's advocate bite and offer: Onboarding. It's easier to get junior and mid-level devs started on a repo/project if they don't have to understand 100% of the full, entire stack. Maybe I'll bathe the babies in early ignorance to hook them and help them grow.
That said, if they stay in baby form and never grow...
"My only gripe is filling in card details, there is never a floating icon to click to do it automatically, you need to go to the menu bar and select the card."
At one point I became convinced that this is actually a security feature. If I recall, an article demonstrated tricking users into entering their master password using those "in-browser" decorations. I could write some html/js to build your password manager icon/etc and trick you into thinking I'm your password manager? I now accept it as a necessary UX chore to leave the browser page, but would be interested in being wrong.
At first bluff, I'd expect a ton of example and implementation code to be open-sourced. I still don't know what nightmare code is crawling CSV/ZIP (forget which) files daily doing ACH transfers, but afaik that's still how electronic banking is done? Would love to learn I'm outdated there.