Argorak
Joined 16 years ago
Karma
6,244
Submissions
1,541
Member since
Sep 16
Recent submissions
Comment · 5 months ago
I mean, all customers got a mid-long email, this does not sound like anyone buries anything.
Comment · 2 years ago
Unless something has drastically changed, PyCon covers itself and earns the PSF quite some money on top. Here are numbers from 2020:
https://thefortunate.blog/diversification-is-the-future-for-...
> Out of USD4.5MM of revenue for the PSF in 2019, around 63% of it came from PyCon. USD1.9MM was the costs of having PyCon, which means that for every dollar spent on PyCon, the PSF gets back 1.50 dollars.
https://pyfound.blogspot.com/2020/03/psfs-projected-2020-fin...
Obviously, the revenue has sharply dropped for a time because of COVID, but I'd be surprised if PyCon is run at a loss nowadays.
So you can assume none of your sponsorship money goes to running PyCon.
Comment · 2 years ago
It is and there's the variant where you go bottoms first which is called... "Arschbombe" - "Ass-Bomb".
Comment · 3 years ago
There's an ongoing discussion about potential adoption into upstream, though.
The thing here is: it would be harmful if we, Ferrous Systems, claimed or even be confused with a more general Rust spec. That's a) the privilege of the Rust project and b) problematic if consumers were to understand it that way.
Comment · 3 years ago
Yes, and this does indeed happen. Turns out publishing such a thing makes people get in touch.
Comment · 3 years ago
He, thanks! Weird how that happened though, as the post _was_ edited by an English speaking person living in Germany :).
Comment · 3 years ago
We're being asked about these regularly, but e.g. bluetooth certification is still too prohibitive to just do without a customer.
However, I'm also frustrated with "everything is customer funded", so we're looking at ways to make this things happen.
Sorry to be vague.
Comment · 3 years ago
That matches our experience. They were super pragmatic. Also, their feedback was tough, but always technically grounded and from the perspective of "is the user always well informed?".
Comment · 3 years ago
Yes, we built bindings for LynxOS 178 a while ago and demonstrated Rust on QNX at embedded world.
https://www.lynx.com/press-releases/rust-compiler-support https://ferrous-systems.com/blog/how-we-built-our-embedded-w...
Porting Rust to RTOSes is reasonably easy.
Comment · 3 years ago
It's certainly an unusual pricing style, but people grok it and appreciate it. Also, note that this is for the "quality managed" version - additional support and documents that I sign off for safety (so enter a liability) are more expensive.
But on the other side, there's so many that would buy if it were more accessible.
Comment · 3 years ago
(disclaimer: also a co-founder of Ferrous Systems)
The ISO 26262 is certainly an effective standard. The boxes to tick are of the kind "do you have your requirements written down?" ("will someone later know what this thing does?").
So, we do have to tick boxes, but we're free to pick on how to tick boxes :). What TÜV now certified is that our box-ticking process is fine.
I have absolutely no problem with framing this as box-ticking in some way, but that box-ticking has _meaning_. However, on an existing tool, that means you write the spec (spec.ferrocene.dev) and check if everything has a test implemented. Yep, that's an amount of pretty dumb and repetitive work. And pretty often, on widely-used software, for the happy path, you'll find that it's rather bug-free. So, yes, you tick the box, but you now know that this is in order.
In other cases and on less popular platforms, we frequently find issues like e.g. changes in code size between versions (which could hint to a bug). And it's not just super-niche targets, the last version had a size regression on certain arm targets.
Details on some of the fixes over the last years can be found here: https://ferrous-systems.com/blog/how-ferrocene-improves-rust.... We find a lot of things in corners and better ways to improve the Rust compiler.
As we're a downstream to Rust, we're actually incentivised to push changes upstream with preference, so yes, we contribute to the general quality of the Rust compiler (also of older versions) and with that to bug-free-ness of the resulting software.
So, we're over here, ticking boxes, informing parties when one box doesn't tick.
Comment · 3 years ago
Yep, it's only the target files for lynxos178.
Comment · 3 years ago
We got hit by this: https://www.cloudflarestatus.com/incidents/t53r6tfsg1sj
Cloudflare served private preview URLs through the deployed website.
Honestly, doing ops for over 10 years, i didn't have this in my cards ;).
Comment · 3 years ago
Footer: © Amazon Web Services EMEA SARL (Niederlassung Deutschland)
This is probably the AWS lead initiative to place their preferred people into a council they see being formed anyways.