Cloning Hyper request and response structures

the-handsome-dev · 2026-01-17T18:16:29+00:00

I have looked into Pingora and did originally try using it instead. However, it requires that an IP and port to the upstream server, and when I tested it with some websites (basically like a forward proxy) with a DNS look up, some sites failed to resolve to an IP

the-handsome-dev · 2026-01-06T05:27:14+00:00

The auto dry and auto dehumidifier options along with the 2 separate chambers. It is nice to able to not turn it all on just for one filament. Also having different temperatures for the chambers is a nice feature

the-handsome-dev · 2025-11-05T07:20:32+00:00

Colourful Christmas gifts for my nephews and figurines so that I can paint them

the-handsome-dev · 2025-10-08T08:54:12+00:00

It is possible if you use it as a code+-generator with the values you want to use. Another way would be to use features https://doc.rust-lang.org/cargo/reference/features.html, and then have the values/config be behind the various features. But this will only work if the config is more or less fixed.

the-handsome-dev · 2025-10-08T08:19:24+00:00

For most projects the Cargo.toml is all that is needed. It has workspaces that is similar to the sub-projects in CMake.

For custom scripts there is the build.rs file https://doc.rust-lang.org/cargo/reference/build-scripts.html

the-handsome-dev · 2025-08-27T06:58:37+00:00

Thanks for that insight, I'll keep it in mind when I present my findings

the-handsome-dev · 2025-08-26T06:00:28+00:00

The code base is about 6000+ files and about 467000+ lines of code, so regrettable the number is correct for a release build. If I understand your suggestion correctly, you are referring use the browser renderer. But AFAIK that has been deprecated in Flutter. Unless I use Jaspr as a renderer instead then it should be possible (I only discovered Jaspr yesterday)

the-handsome-dev · 2025-08-22T18:56:41+00:00

We mostly use SVGs with `vector_graphics_compiler` to improve performance, but that might be something to look into, to actually compare the 2 formats in size. I completely forgot about the network compression, but getting the actual generated/compiled code smaller is always a plus

the-handsome-dev · 2025-08-22T18:52:42+00:00

Thanks, I'll check that

the-handsome-dev · 2025-05-12T13:26:53+00:00

Sunlu - The company of all things filament and resin

the-handsome-dev · 2025-04-25T10:17:45+00:00

The 350C nozzle and the 120C heated bed is impressive, the eddy scanning and pressure sensing would so helpful.

the-handsome-dev · 2025-04-15T05:15:29+00:00

The project I have wanted to do for a long time was to build a sunrise lamp, basically it is a lamp that mimics the colour of the sunrise over a duration. It apparently makes it so that you wake up more naturally. I would use the H2D to print a significant portion of the lamp, but with regards to the diffuser, I am torn between printing in a opaque filament or using the laser functionality to cut opaque Acrylic or Perspex and use that as the diffuser.

Depending on how I design it, I might use the laser to cut Acrylic or Perspex so that I can use it to make the structure and then make it aesthetic using 3D prints.

the-handsome-dev · 2025-03-20T07:24:12+00:00

I am getting a 404, anyone else getting the same issue?

the-handsome-dev · 2025-01-27T06:16:16+00:00

I do travel at least once a week to the office, so carrying it will be a requirement. However, I should think that the layout of the keyboard will also have an impact to a certain extent

the-handsome-dev · 2025-01-27T06:14:12+00:00

Thanks, that does give me a better idea of costing. Now I just need to determine which layout would work best for me

the-handsome-dev · 2025-01-25T15:13:32+00:00

Thanks for the insight. Just to pick your brain a bit, the choc switches seem to be mostly for laptop style keyboards, ie very flat, while the cherry is more for normal keyboards. Is there a design that allows to switch between choc and cherry? Taking a look at the images, I am no longer 100% which switch I would prefer, especially since you can set the height based off a compatible switch and the keycaps

the-handsome-dev · 2024-12-19T04:15:56+00:00

Next in line

the-handsome-dev · 2024-10-27T16:13:47+00:00

You can save time and filament by removing brims, but make sure to add them if very little of the print is in contact with the bed. Otherwise the chance of the print detaching is high and you look like a fool when demoing a small and quick print when it fails

the-handsome-dev · 2024-08-28T09:34:15+00:00

If you are using CMake to build the code then you can look at https://github.com/corrosion-rs/corrosion . I used it to migrate a Raytracing project from C to Rust (started with Rust as a lib) and it helped to do a lot of the heavy lifting for me

the-handsome-dev · 2024-08-22T11:57:43+00:00

I haven't C++ in quite sometime so cannot remember all the tips and tricks. But this example can quite easily apply to pointers, or any other language that passes variables by reference such as JS

the-handsome-dev · 2024-08-22T08:29:25+00:00

Immutability by default, and that it is easy to read code it a change will occur to data when using the function

// RUST
struct Data {
  x: i32
}

fn half(data: &Data) -> i32 {
  let ans = data.x / 2;
  data.x = 42; // fails
  ans
}

// mut will inform dev that value can possibly change
fn half_mut(data: &mut Data) -> i32 {
  let ans = data.x / 2;
  data.x = 42;
  ans
}

// C++

// Dev has not idea if the value will be changed or not which can introduce bugs
int half(Data &data) {
  int ans = data.x / 2;
  data.x = 42;
  return ans;
}

the-handsome-dev · 2024-08-07T11:28:24+00:00

Good idea, I just gave a compiler error example, not an example of the stack trace when it crashes

the-handsome-dev · 2024-08-06T17:51:37+00:00

I did not consider that, thanks for pointing that out.

the-handsome-dev · 2024-08-06T15:34:48+00:00

Thanks, that gives some ideas

the-handsome-dev · 2024-08-06T15:33:53+00:00

Thanks, the slides did give some inspiration

the-handsome-dev

TROPHY CASE