I have an old printer, maybe 15 years old or so. Linux still prints and Windows doesn't!
Readit Newspbohun commented on Microsoft purges Win11 printer drivers, devices on borrowed time tomshardware.com/peripher... · Posted by u/rolph
There also is an unofficial mirror which has updates.
I'm not. I'm learning a little bit each day, making my brain better and myself more productive as I go.
pbohun commented on Hate is a strong word, but I don't like Windows 11 blog.urara.pl/hate-is-a-s... · Posted by u/todsacerdoti
It feels like everything is falling apart and getting worse. Yet somehow people are racing to produce AI slop faster. If software eventually collapses under its own weight, things might be so borked we have to bootstrap everything from scratch, staring with assembly.
I liked the path windows was going in late 2010s. WSL, power toys, many great utils, great performance.
But it has since then stalled and got increasingly worse. Especially with this AI shoving everywhere, not even mentioning getting ads at some point in notifications and start menu.
I'm not particularly in love with MacOS either (but have no realistic alternative on my MacBooks).
I'm more and more inclined of switching my desktop (my main working machine) to Omarchy, two coworkers in my team use it and love it and seems the sweet spot for what I need as a dev without the annoyance of Windows or the god awful macos.
It sounds weird to say, but Steve Ballmer was probably the best CEO of Microsoft.
pbohun commented on A million ways to die from a data race in Go gaultier.github.io/blog/a... · Posted by u/ingve
Meaning similar to Erlang style message passing?
Not quite. Erlang uses the Actor model which delivers messages asynchronously to named processes. In Go, messages are passed between goroutines via channels, which provide a synchronization mechanism (when un-buffered). The ability to synchronize allow one to setup a "rhythm" to computation that the Actor model is explicitly not designed to do. Also, note that a process must know its consumer in the Actor model, but goroutines do not need to know their consumer in the CSP model. Channels can even be passed around to other goroutines!
Each have their own pros and cons. You can see some of the legends who invented different methods of concurrency here: https://www.youtube.com/watch?v=37wFVVVZlVU
There's also a nice talk Rob Pike gave that illustrated some very useful concurrency patterns that can be built using the CSP model: https://www.youtube.com/watch?v=f6kdp27TYZs
pbohun commented on A million ways to die from a data race in Go gaultier.github.io/blog/a... · Posted by u/ingve
> people insist on using the dangerous way and then blame it on the language
Can you blame them when the dangerous way uses 0 syntax while the safe way uses non-0 syntax? I think it's fine to criticize unsafe defaults, though of course it would not be fair to treat it like it's the only option
They're not using the dangerous way because of syntax, they're using it because they think they're "optimizing" their code. They should write correct code first, measure, and then optimize if necessary.
pbohun commented on A million ways to die from a data race in Go gaultier.github.io/blog/a... · Posted by u/ingve
The first Go proverb Rob Pike listed in his talk "Go Proverbs" was, "Don't communicate by sharing memory, share memory by communicating."
Go was designed from the beginning to use Tony Hoare's idea of communicating sequential processes for designing concurrent programs.
However, like any professional tool, Go allows you to do the dangerous thing when you absolutely need to, but it's disappointing when people insist on using the dangerous way and then blame it on the language.
pbohun commented on APT Rust requirement raises questions lwn.net/SubscriberLink/10... · Posted by u/todsacerdoti
Interesting how instead of embracing Rust as a required toolchain for APT, the conversation quickly devolved into
"why don't we just build a tool that can translate memory-safe Rust code into memory-unsafe C code? Then we don't have to do anything."
This feels like swimming upstream just for spite.
That's not what the comment said. It said, "How about a Rust to C converter?..." The idea was that using a converter could eliminate the problem of not having a rust compiler for certain platforms.
pbohun commented on Programming with Less Than Nothing joshmoody.org/blog/progra... · Posted by u/signa11
Haha! You know, I think this is a perfect illustration between something being mathematically beautiful verses pragmatically beautiful. The beauty of one often looks ugly by the standards of the other.