CameronDev

joined 2 years ago
MODERATOR OF
[–] CameronDev@programming.dev 1 points 7 hours ago

I was clearly joking. Also, OP doesn't identify as a femboy either.

[–] CameronDev@programming.dev 3 points 3 days ago (1 children)

Your iPhone was designed for Bluetooth, on laptops and desktops its an after thought.

[–] CameronDev@programming.dev 2 points 3 days ago

Some of the cheap USB hardware are unofficial clones, which get disabled by the official drivers. The clones sometimes work in Linux, but not reliably. It can be really hit and miss.

[–] CameronDev@programming.dev 7 points 3 days ago (5 children)

To be fair, Bluetooth sucks on Windows desktops as well. The hardware is just garbage a lot of the time

[–] CameronDev@programming.dev 6 points 3 days ago

Gleam is very similar syntactically. Never used it, so can't say anything more about it.

 

Hi All. This might not be for everyone, and is very rough around the edges, but I have written a tool to more easily test how custom addressable RGB effects work.

Simply copy the code portion of the lamba into a text file, and then build and run, and it will output on your terminal how the effect will look.

It is very rough, you need a C compiler, and a RGB/TrueColor capable terminal.

If it works for you, let me know, if it doesn't, also let me know.

https://github.com/cameroncros/ESPHome-ARGB-Tester

[–] CameronDev@programming.dev 4 points 4 days ago

Lol, if only I had known about this a year ago, that's exactly what I wanted/needed.

I guess I could change the topic name to "Rewrite of dtach in Rust" :/

[–] CameronDev@programming.dev 2 points 4 days ago

Yup, good catch, rushed it out on the train. Will fix

[–] CameronDev@programming.dev 30 points 4 days ago (3 children)

The funniest part is I think of myself as femboy or trans

My friend, you tried your hardest to deny your truth, and your subconscious still leaked through :D

[–] CameronDev@programming.dev 2 points 4 days ago

Well, your point stands regarding alacritty_terminal, but right now, it actually works just fine for that test case:

I suspect once I stop directing the raw input/output to the shell, it might become more important.

[–] CameronDev@programming.dev 4 points 4 days ago (1 children)

The name of the branch is probably misleading, its not gonna be better than screen, it was meant to be better than my first attempt.

This is likely to never have any real use outside of my own personal usage.

[–] CameronDev@programming.dev 7 points 5 days ago (2 children)

Yeah, its a bit of a mess, it does so much. The thing I wanted was just the persistent sessions, so probably not gonna go further than that. Of course, the code exists, and someone else is welcome to take it and run with it (I'll give it a permissive licence eventually).

 

I dunno if this is appropriate for this community, so mods, please delete if not.

I have been writing a screen clone in rust.

https://github.com/cameroncros/PoorMansScreen/tree/better_screen (The main branch is how I currently use it, not at all screen-like, the better_screen branch is much closer to a screen replacement.)

It all currently works fine, albeit quite simple, and I suspect not following best practices. Please talk shit about my code so I can fix that :D

For my next stage of development, I would like to use some combo of vt100 and ratatui to wrap the shell in a border, or add a menu bar at the top or bottom to make it clear when the user is inside a "screen". Does anyone have any thoughts on how to go about doing that? I am very unskilled at ratatui.

4
Visualisation Megathread (programming.dev)
submitted 1 month ago* (last edited 1 month ago) by CameronDev@programming.dev to c/advent_of_code@programming.dev
 

Visualizations are hard, and take time, so here is a thread to highlight the visualizations that we have found/created.

Please feel free to post your visualisations!

1
Final Leaderboard (programming.dev)
submitted 1 month ago* (last edited 1 month ago) by CameronDev@programming.dev to c/advent_of_code@programming.dev
 

Those of you running behind, keep at it, but this is the leaderboard as it stands at the end of 2024.

Happy new year!

 

A lot lower success rate than I suspected, I guess a lot of the scoreboard times were probably legit?

80
Preliminary Leaderboard (programming.dev)
submitted 1 month ago* (last edited 1 month ago) by CameronDev@programming.dev to c/advent_of_code@programming.dev
 

Well, that was a month. Congrats everyone who has reached the end, and thanks to everyone who has contributed solutions and advice.

Sometime in January I will create a megathread for visualizations. If anyone has any other ideas, happy to hear them, otherwise, take a well earned 11 month rest until next year :D

 

Day 25: Code Chronicle

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

 

I am wondering if manual inspection is the way to go for pt2? Seems almost achievable with some formatting. Anyone been down this road?

13
submitted 2 months ago* (last edited 2 months ago) by CameronDev@programming.dev to c/advent_of_code@programming.dev
 

Day 24: Crossed Wires

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

 

Day 23: LAN Party

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

 

Day 22: Monkey Market

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

 

Day 21: Keypad Conundrum

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

view more: next ›