Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F

FizzyOrange

@ FizzyOrange @programming.dev

Posts
2
Comments
1234
Joined
3 yr. ago

  • VLC Literally Reaches for the Moon to Mark its 20-Year Anniversary

    Jump

  • Yeah definitely Blender. It's not that hard to write a media player (hence why there are others like MPC). It's also not that hard to write a Unix kernel (hence why there are others like *BSD). A 3D modeller as complex as Blender though? I can easily imagine a world where it didn't exist and we were all stuck with Povray or whatever.

    Kind of like the situation with CAD. (Though the FreeCAD 1.0 release seems to be finally vaguely usable based on my brief play with it so that might have changed.)

  • 12 years of incubating Wayland color management

    Jump

  • Can't downvoted truth.

  • 12 years of incubating Wayland color management

    Jump

  • What are the issues?

  • Finding coding gigs nowadays

    Jump

  • Not sure about freelance, but for a salary in my experience, answer some recruiter spam on LinkedIn. I always thought they'd be crap since they are spammy... But after using some I've totally changed my mind. At least in my industry (silicon verification):

    • Companies use them.
    • You get a foot in the door & can bypass all the HR crap.
    • They know all of the relevant companies. I learnt about my current company from the recruiter.
    • They give you some hints about the interview process.
    • They do all of the chasing up for you.

    Also, they get a big payoff if you get a job, so their interests are more or less aligned with yours. The only slight difference is that they just want you to get any job, so they might push you to a job you don't really want. But it's minor.

    Basically you get a lot of benefits for using them and you aren't paying the cost - the company is. They won't pay that cost to you if you don't use a recruiter and save them cash, so there's no real reason not to use a recruiter.

    It may be very different for less niche sectors; I don't know.

  • Years In The Making, Intel Timed I/O "TIO" Looks To Finally Land In Linux 6.15

    Jump

  • Yeah that makes sense.

  • Years In The Making, Intel Timed I/O "TIO" Looks To Finally Land In Linux 6.15

    Jump

  • Facebook and Google are the customers that use this feature.

    Apparently. Does anyone know what they use it for?

  • State of Rust survey 2024: most Rust developers worry about the future of the language

    Jump

  • There's no reason for any developers to participate in such surveys, it's nothing to do with experience. I do though because I am nice.

  • Are there any non-unixlike Linux-based OSes other than Android?

    Jump

  • You won't really find anything since the kernel dictates a huge amount about how the OS behaves. If you look at the differences of Linux to other OSes, most of them are in the kernel.

    Android is still very Unix-like in its userspace. I think probably the biggest thing you can change is to ditch the archaic /bin, /usr, etc. filesystem. Android and NixOS both sort of do that.

  • How to minimize pain of Windows in work environment?

    Jump

  • Programming on Windows can be totally fine, if you're working with a language that cares about Windows support. E.g. in my experience:

    • Good: Rust, Go, C#, Java, Deno, Dart
    • Okish: Python, C++, Node
    • Bad: Perl, OCaml

    If it's in the "bad" category I would recommend installing WSL and using VSCode's remote feature that lets you have a Windows copy of VSCode connect to WSL.

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • And why are you imagining things would go down like that

    Because I am familiar with human behaviour.

    Rust is disabled by default

    I'm not too familiar with Linux's CI system but I assume they at least test that it compiles, even if it is disabled by default.

  • Linus sets his foot down, against the gatekeeping attempts in the kernel

    Jump

  • If the Rust guy hadn't made a fuss? Absolutely.

  • Linus sets his foot down, against the gatekeeping attempts in the kernel

    Jump

  • so the social media publicity was required to resolve this issue?

    Certainly seems that way unfortunately.

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • or the kernel releases with broken Rust

    This is what I don't believe. I think what will actually happen (or could at least), is:

    C dev that refuses the learn Rust: "Hi, here's a change to the DMA API."

    Linus: "Can you fix the Rust code before I merge this?"

    C dev: "Ok, Rust devs it's your job - can you fix it?"

    Rust devs: ""

    C dev: "Hello? Where are you?"

    ...

    C dev: "Can we just merge it now?"

    Linus: "No we need to fix the Rust."

    Again, to be 100% clear, I think that this shouldn't block Rust. We should just expect the C devs to learn a bit of Rust (seriously if they're writing Linux DMA systems they are easily bright enough to do it). But pretending that they won't have to to keep them happy seems disingenuous.

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • To be clear I fully support Rust in Linux. I just think it's going to rapidly be impractical to work on Linux without learning Rust.

    The solution isn't to pretend that isn't the case; it's to learn Rust!

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • I do understand that that's what they claim. I just don't believe them. Because it requires either

    1. magical Rust maintainers who are always on call to help, or
    2. people to be on with the Rust code breaking all the time.

    Neither seems likely.

  • Get Ready For KiCAD 9!

    Jump

  • I don’t agree that dragging keeping wires is sane behavior.

    Well... I'm afraid you're wrong about that. It's the behaviour almost all users expect, it's the most useful behaviour, and it's the behaviour of virtually all software that has wire-like interfaces.

    Can you imagine if all the nodes in Blender disconnected every time you moved them? Ridiculous.

  • To people making shitty guides/tutorials.

    Jump

  • Linus responds to Hellwig - "the pull request you objected to DID NOT TOUCH THE DMA LAYER AT ALL... if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG."

    Jump

  • I don't know I think the argument about forcing maintainers to learn Rust is probably true - sure the Rust code might not touch the DMA code, but Linux doesn't have stable APIs so in theory you're supposed to be able to change an API as long as you fix all the drivers that use it.

    That now involves fixing Rust drivers, so you're going to need to know Rust.

    However I don't think that's a good reason not to do it. In my opinion Linus should just be honest and say that the Rust experiment has been successful, Rust is going to be part of the kernel moving forwards, and you will probably have to get off your arse and learn it.

    All this "you won't have to learn Rust" talk is thin reassurance to keep people happy. I don't think anyone really believes it.

    Reminds me of when WASM was introduced and everyone was saying "the goal isn't to replace JavaScript" to keep the JavaScript folk happy, despite everyone knowing that that was exactly the goal.

  • Announcing Rust 1.85.0 and Rust 2024 | Rust Blog

    Jump

  • So glad they made the sane move and fixed std::env::home_dir(). The previous situation of having it deprecated due to fairly insignificant reasons, while recommending an abandoned crate instead was just silly.