FizzyOrange

joined 1 year ago
[–] FizzyOrange@programming.dev 1 points 2 days ago

Difficult pronunciation and it also sounds like a lame "cool" name that a super nerd would think of.

[–] FizzyOrange@programming.dev 7 points 4 days ago

Dunno why you're being downvoted. It's very obviously deliberately chosen to make 12 year olds giggle.

[–] FizzyOrange@programming.dev 6 points 4 days ago

Krita is quite far ahead of GIMP at this point. I'm not a pro Photoshop user but if you are and you're looking at alternatives, that's the place to look.

[–] FizzyOrange@programming.dev 1 points 5 days ago

I think there are some crates that wrap the unsafe code for you, e.g. https://github.com/rodrimati1992/abi_stable_crates/ (I haven't ever tried it).

[–] FizzyOrange@programming.dev 0 points 5 days ago

He is. By using statically linked binaries.

Technically this is conflating two things: bundling dependencies and static/dynamic linking. But since you have to bundle your dependencies to use static linking, and there's little point dynamic linking if you bundle your dependencies... most of the time they are synonymous.

Exceptions are things like plugins, but that's pretty rare.

[–] FizzyOrange@programming.dev 7 points 6 days ago (1 children)

I don't know why you're being downvoted. It literally starts with the word OPINION in bold red caps.

[–] FizzyOrange@programming.dev 27 points 6 days ago

asking the maintainers to lock down APIs which the C devs purposefully leave malleable, in part, to avoid binary blob drivers being feasible.

No, they were asking them to define the semantics of the filesystem APIs. Those semantics are not encoded in the C API but the Rust devs wanted to encode them in the Rust API to avoid making mistakes.

The C devs didn't want to, not because of concerns about binary drivers, but because the semantics are already broken. Apparently different filesystem drivers assume different semantics for the same functions and it's a whole mess. They don't want to face up to this and certainly don't want anyone pointing it out, so clearly it must be the Rust devs' fault for wanting APIs to have consistent semantics.

The rest of your comment is nonsense.

[–] FizzyOrange@programming.dev 3 points 1 week ago

Any from reputable manufacturers?

[–] FizzyOrange@programming.dev 3 points 1 week ago (8 children)

Even that's ok. I couldn't find anything at all when I looked about a year ago. Only one model that the Thread people were still recommending despite it being discontinued.

I had another look and still couldn't find anything vendor neutral and cheap. Can you post some links?

[–] FizzyOrange@programming.dev 3 points 1 week ago

Freeing home energy gear from vendor lock-in. Matter 1.4 adds some big, expensive gear to its list of device types and control powers, and not a moment too soon. Solar inverters and arrays, battery storage systems, heat pumps, and water heaters join the list.

Yeah I seriously doubt solar inverter providers will sign up to this. Here's what QCells said when I asked them about an API:

I’m sure it is possible and we’re in discussions with some providers over opening up to their requirements, but it’s not something we’d offer to individuals unfortunately.

They view control of their "virtual power plants" as a commercial asset and they don't want to give it away for free.

Don't buy a QCells solar inverter btw. I should have done more research! I believe GivEnergy are less stuck in the 80s but don't quote me on that.

[–] FizzyOrange@programming.dev 7 points 1 week ago (10 children)

Ugh, I was working on a DIY smart lock. "I'll use Matter!" I naively thought.

Ok you need a border router for Thread support. No problem, I'll buy one. Should be cheap right since an ESP32 can handle it. Nope! You pretty much can't buy a standalone border router. All the articles are "don't worry, you might have one already if you have a Nest Hub or a Home Hub or...". Well I don't have one.

Pretty lame. I guarantee if they make a vendor neutral border router dongle you can just plug into your router's ethernet port and sell it at cost price (like £5) they'll see triple the uptake.

[–] FizzyOrange@programming.dev 7 points 1 week ago

PDF writing isn't too bad IMO, since you don't need to understand the whole spec. I've written a PDF writer for maps from scratch and it was fairly easy and not too much code.

PDF reading though... Yeah I'm happy to leave that to people with more time and use their libraries.

A modern format would be nice, but I don't think it would be anywhere near nice enough to give up how universal PDF is.

 

Does anyone know of a website that will show you a graph of open/closed issues and PRs for a GitHub repo? This seems like such an obvious basic feature but GitHub only has a useless "insights" page which doesn't really show you anything.

view more: next ›