What packaging types are there for Rust? Isn’t everything just source-based through cargo?
I make things: electronics and software and music and stories and all sorts of other things.
What packaging types are there for Rust? Isn’t everything just source-based through cargo?
Rust and Haskell (I think Haskell counts)
I find Rust crates generally have pretty good docs. Docs.rs is a major time saver
More like gaming executives
You can build with mingw64 built with msvc and use more or less the same Makefile. As for Xcode… well, there’s not really a good reason to support Mac. On principle I wouldn’t even try
How the heck does a Makefile not scale??? That’s all it does!
Life is and will always be better writing your own Makefiles. It’s literally so easy. I do not get the distaste. Cmake is arcane magic. Bazel is practically written in runes. Makefile is a just a glorified build script, but where you don’t have to use a bunch of if statements to avoid building everything each time.
It’s a bit more than iced as they’ve created a library on top of it, esp for the theming they desire
Build a project. Learn how to do each step by searching the internet. It’s quite literally that easy.
Nvidia and Wayland is still BORKED
Nope
Nextcloud Server
I can only get it to work via snap and on Ubuntu. I’ve tried Ubuntu, Debian, Arch, Fedora, and NixOS for distro and both manual and snap. It doesn’t even have a flatpak.
People use IPv6?
I still don’t know anything about it
a = [ Haskell
, is
, the
, GOAT ]
Brave
I used to use Duck Duck Go, but it’s supposedly not as private as it claims to be, and my understanding is Brave is a bit better there.
I don’t use the Brave browser tho, just the search engine
I’m a relatively new hire and we just hired another person 2 weeks ago
It’s effort to switch, and we don’t benefit from having separate copies of the repo bc we’re so small. No one steps on eachother’s toes, so distributed version control isn’t necessary.
Now, the fact that most devs know git and SVN is dead is not lost on our CTO, but putting the effort to switch over doesn’t provide direct value to the customer, so I have to make the case that switching to git would do enough from a productivity and maintenance standard to effect customers.
Yes. We use SVN. I hate it. I’m trying to build a case to switch to git. We’re a small team, but a growing team
Epiphany is a neat little project, but my understanding is it has performance issues bc it can’t use the GPU or something, like YouTube videos load slow.
I agree. We’ve let the standards for what is good drop.
I think it’s mainly because the “just works” mentality has become infectious among engineers. It’s one thing when just starting out, but as you learn more and gain experience you should care more.
People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.
I think the second, slightly less strong reason is because many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway. Another skill I see less and less amongst my brethren.
This response needs more up votes