HackerTrans
TopNewTrendsCommentsPastAskShowJobs

willx86

no profile record

Submissions

Searching for a Well Designed API

1 points·by willx86·4 bulan yang lalu·5 comments

Tree CLI's plain text secrets

w.willx86.com
1 points·by willx86·6 bulan yang lalu·0 comments

comments

willx86
·12 hari yang lalu·discuss
I converted with claude Use my repo for lsp.nix as neovims new v10 has a new way of configuring lsp's as lspconfig is depreciated, so I used the new lsp configuration method but went doc hunting to find out I need lspconfig for proper completions! ( I'll give it a push now to ensure it's my latest version)
willx86
·12 hari yang lalu·discuss
I eventually gave up using mason and lsp servers and used nixvim

https://github.com/will-x86/nixos-dotfiles

( ./home/base/nixvim)
willx86
·bulan lalu·discuss
..... I like my auto generated username it's a funny one
willx86
·bulan lalu·discuss
Used it today, I like it so far

One small thing I have now got 30 more red dots as during my gym session I regulary change the music by opening my phone :)
willx86
·2 bulan yang lalu·discuss
Seems like you want a custom cartridge

They exist, e.g. https://www.coolspotgaming.co.uk/products/custom-game-boy-ad... ( I haven't used this service )

This seems like a good mid point between a $500 cartridge and having no friction between games
willx86
·3 bulan yang lalu·discuss
Docs are 404 and terms send me to pricing...?
willx86
·3 bulan yang lalu·discuss
Fascinating

Are you not wasting 8 bits using a Qn.m of 8.8? If you values are only 0-1?
willx86
·4 bulan yang lalu·discuss
https://blog.cloudflare.com/ai-labyrinth/

A bit like this? ( iocaine is newer)
willx86
·4 bulan yang lalu·discuss
If engines are hard to build, why not build a car 3x the size of a normal one, well you can but due to things like aerodynamics, etc etc you'll never match the speed or fuel economy of cars.

Same with chips, efficiency, speed, etc all depend on good design, and cutting edge factors, if the main reason your chip isn't faster is because of the distance between your L1 cache and your core is far, then having a bigger node process but bigger chip won't make it quicker.
willx86
·4 bulan yang lalu·discuss
https://st.suckless.org/
willx86
·4 bulan yang lalu·discuss
+1 I love the parental controls I can limit social media to only a few hours a day ( only on my phone profile) And it has good Tailscale integration!
willx86
·4 bulan yang lalu·discuss
Love it!
willx86
·4 bulan yang lalu·discuss
Very interesting thank you :)
willx86
·4 bulan yang lalu·discuss
Thank you!
willx86
·4 bulan yang lalu·discuss
This is primarily to try and learn from, I should've made this a bit clearer.
willx86
·4 bulan yang lalu·discuss
As someone who has only used zig a little

I've has more core dumps/seg faults than any other language I've ever used.

Skill issue? Yes, 100℅, it's definitely due to my lack of skill in the language

The only time I've ever made a rust program seg fault is when using nightly macros/"features" and being on stable, leading to rustc crashing with a nice error and then I change to nightly

and that was caught at compile time...

Skill is a huge factor in safety

"70% of vulns are..." Yes, production code written at huge companies by experts... If experts are making those mistakes, that says a lot about it IMO

That being said, I'm not a "one language for all", they have their place, embedded rust is hilarious as it's essentially a requirement to have unsafe blocks in your initialisation

Anyway rant over
willx86
·4 bulan yang lalu·discuss
Personally I've spent a lot of time coding in go relative to my total time programming

An introduction into topics that are a bit deeper than typical are very interesting to me

It may not make me an expert in the topic reading this, but it at least gives me some new information and if I'd like to know more, I know what to look for.

Before this article if I wanted to know more my searches would be "How does Go memory management work"

Maybe I'm in a minority as this being not trivial information to me though
willx86
·5 bulan yang lalu·discuss
Pretty cool

Short thing, when I built something similar using chromedp I had to scroll on some pages to properly render all of them, due to lazy rendering on some websites ( also some pages had infinite scroll so had to break after a certain amount scrolled)

Might be worth adding it as an option ( unless it is already)

Nice project
willx86
·5 bulan yang lalu·discuss
Another thing maybe

Using context here would be great so jobs can be cancelled instead of timeout
willx86
·5 bulan yang lalu·discuss
Looks pretty cool I've wanted something similar many times

Quick question, why this style?

opts := toil.Options{}. WithWorkers(4). // Use 4 workers (default: number of CPU cores) StopOnError(true)

Most golang uses: toil.Options{Workers: 4} etc etc?

Bar that I look forward to using it!