dkryptr

Joined 6 years ago

Karma

Submissions

Member since

Apr 27

Recent submissions

Even if you have the full menu on your phone, you still have to zoom into the menu to read it and pan the view. I don't see how that's any different from scrolling through a categorized menu in a website on your phone.

Comment · 3 years ago

To be fair, that's not a very formal resignation. He just... quit.

Comment · 3 years ago

Agreed. When I first considered porting small APIs over to Rust, Rocket appeared to be the most popular besides Actix. Axum hadn't even came out (it came out a month later and we ended up using it even though it was in its infancy). It's pretty unfortunate because Rocket could be amazing but the lack of updates killed it. See you guys in 5 years when v0.6 comes out.

Comment · 3 years ago

I feel kind of bad saying this, but too little too late in my opinion.

Comment · 3 years ago

https://linear.app is nice. I haven't used it with a large group but for some personal projects and it works nicely.

Comment · 4 years ago

> Except that I read that it's great for writing, but a nightmare for reading.

This is true at first. I can see it being pretty daunting to come into an existing project and trying to understand the styling of components. Starting from scratch and easing it into an existing project is much easier imo. That's what I did for a personal website. Now that I understand it and have converted the entire website to Tailwind, I don't want to switch to anything else going forward.

Here's a Prettier plugin that sort the classes to keep everything consistent across components: https://github.com/tailwindlabs/prettier-plugin-tailwindcss

Tailwind combined with classnames (https://github.com/JedWatson/classnames) makes it really easy to have conditional styling based on component state.

Comment · 4 years ago

I started with the book to learn the fundamentals. I didn't get very far before I decided to rewrite an existing API I had in Python into Rust.

It definitely took some time and learning but now I have 6 Rust API microservices, a few scheduled/queue-reading services, and a shared library for common models/utils/providers.

Comment · 4 years ago

This is the way. (my setup is 1:1 it sounds like)

Comment · 4 years ago

That's essentially the selling point behind Zicam and other homeopathic drugs.

Comment · 4 years ago

Traefik is great, but their documentation is awful IMO. I moved to Caddy which I prefer currently.

Comment · 4 years ago

Just a heads up that the privacy policy and terms and conditions pages are not showing up. The page loads, but there's no text where it looks like there should be.

https://www.airsoftbazaar.com/help/terms-and-conditions https://www.airsoftbazaar.com/help/privacy-policy

Comment · 4 years ago

TIL. Thank you!

Comment · 4 years ago

100% agree. I'm actually surprised AWS hasn't built in a Chaos Monkey into their APIs/console so people can test their resiliency regularly if an AZ goes down.

edit: of course, AWS does have this: AWS Fault Injection Simulator

Comment · 4 years ago

I work on a large Next.js project that has at least 100 custom made components all using Tailwind CSS. It is, without a doubt, the best way to iterate and make changes. I will never go back to manual stylesheets. Having a separate CSS stylesheet feels like context switching and breaks the flow of development in my opinion.

Comment · 5 years ago

I've developed multiple microservices in Rust (using axum[0]) and cargo-watch[1] has really come in handy. I usually only have to wait ~5 seconds for my changes to re-compile and the server to spin up.

I can't really speak for massive projects, but in my experience after the first build the compile times aren't too bad. Only the changed code re-compiles.

Another commenter mentioned they can code for hours without needing to re-compile and I've found that to be true also. I use rust-analyzer[2] in VSCode and I can usually get a lot done without needing to manually test every change. I guess it depends on if I'm writing logic heavy code or writing code-architecture (custom traits, implementations, and whatnot)

[0] - https://github.com/tokio-rs/axum [1] - https://github.com/watchexec/cargo-watch [2] - https://github.com/rust-analyzer/rust-analyzer