HNHacker News
TopNewBestAskShowJobs

Xylakant

13,469 karma · joined June 3, 2011

submissionscomments
Xylakant··on 4k tons of potatoes to be given away for free in Berlin
The neighbors snow response contractor had an electric brush on a broom handle, that looked pretty nifty and took like 15 minutes for the whole front to be spotless clean. Then they added a bit of grit, done. The contractor for our block didn’t even show up. Not sure allowing salt would have changed anything.
Xylakant··on Verizon outages reported across U.S.
The great thing is that with all of the encrypted/signed DNS thingys, you now have not one, but multiple options to combine “invalid certificate” and DNS in one outage. You no longer need to choose!
Xylakant··on 4k tons of potatoes to be given away for free in Berlin
The problem is not salting or not - the problem is that the house owners are liable for cleaning the sidewalk and they all outsourced it to the same companies. And the companies unsurprisingly all fail to deliver on their obligations because they take on way more customers they could possibly handle. The result is as expected - nothing gets done. A shovel and broom, maybe some grit would have been enough.

But there’s no shred of enforcement and instead of calling for enforcement, politicians now call for relaxing the rules on salting.

Xylakant··on No, it's not a battleship
A modern continuation of the Swedish Wasa class?
Xylakant··on The state of the kernel Rust experiment
> Saying these features could appear everywhere is no difference from "unsafe" possibly appearing everywhere in Rust.

That's not true in practice: Unsafe code is clearly delineated and can be 100% correctly identified. In C, usage of dangerous features can occur at any point and is much harder to clearly separate.

Xylakant··on The state of the kernel Rust experiment
> It’s mostly C and C++ developers trying to build a new option for solving their same problems.

I've observed that a lot of the folks I used to meet at ruby conferences have moved to Rust. No idea what led to this, but maybe it's just folks that were generally curious about new programming languages that moved to ruby when it became better known and that the same interest led to adopting Rust.

Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
Oh, I agree that illegal stuff happens in the EU aplenty. The question was whether this is illegal and it almost certainly is. Job postings from recruiters - while morally reprehensible - may just skirt the law, but straight up using applications for profile building, marketing and other purposes almost certainly isn’t permitted
Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
Any model that charges for self-hosted runner is going to feel unfair to someone. Per seat pricing is better for small orgs with a lot of CI minutes, per-run pricing would be good for orgs with few, long runs, per minute pricing is nicer for orgs with many small runs.

In my observation the critisicm was strongly dominated by outrage over the actual fact.

Xylakant··on Are Apple gift cards safe to redeem?
Your iphone is tied to the old apple account and you can't untie it if you can't access the old account. (You can go through support with proof of purchase, but that requires you have proof of purchase at hand etc.)
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
That is good to remember - I'll keep that in mind if I ever want to hire in [Germany, Japan] without spelling this out for some reason.
Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
Yes, gitlab does still have free self-hosted runners. OTOH, github has a free organisation plan and gitlab doesn't. So yes, strictly speaking self-hosted runners are free, but you're paying for the dev-seats.
Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
Self-hosting all of your CI is yet another tradeoff. The software comes for free (if you're using Free Software, that is), but you now have operational overhead. I'm not saying it's an unreasonable move, but it's also not a free swap
Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
> I’d be more willing to pay if GH Actions wasn’t so flakey and frustrating (for hosted or self-hosted runners, I use both).

This is indeed a reason I do consider leaving GHA. The underinvestment into this part of the product shows. But they also did announce quite some investment into new and (for us relevant) features alongside the pricing change, so I'll have a look at how this changes with some sorely needed work on the product.

Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
How do you pay? Because the basic organization plan is free and gives access to GHA and includes 2000 free minutes.

If you upgrade the plan, you get more minutes for free - which can be consumed by the cost for free runners. They haven't specified at which rate a self-hosted runner consumes the free minutes, but at least for us, the change will largely consume free minutes.

> You might as well say that we should be paying per PR and Issue because, well, that part can’t just be free, you know?

You're misrepresenting what I said. I said, I'm fine with this for these reasons. It's a statement about me, not about what you should do nor what you should consider fine.

I pay (quite a bit) for GH because I do receive a service that's worth it, at least for now. And I'd rather see that GHA is something that makes them money than become something that is second-rate and lingers, just as it did before they made this announcement.

Xylakant··on GitHub postponing the announced billing change for self-hosted GitHub Actions
Fun thing is that almost every other CI as a service provider charges you in some shape or form for self hosted runners. CircleCI limits the number of self-hosted Job Running in parallel based on your plan and charges a fixed base fee per seat.

So moving away from GHA will not make self-hosted runners free, they’ll move into a different pricing structure that may or may not be beneficial.

And I think charging for self-hosted runners is actually fine. They’re not free for the provider either - log aggregation, caching of artifacts, runner scheduling, implementing the runner software etc are non-trivial problems for any larger CI system.

So I’m actually fine with the proposed change since it also gives me the power as a customer to say “hey, I’m paying for this, fix it.”

Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
But that would filter for German applicants. Who else would have a fax?
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
I believe you have entered a race to the bottom and while I understand why, I'm pretty certain you can't win this way.

You are effectively filtering out the remaining companies that do care from the pool that you're talking to.

Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
The box would need to be off by default and clearly state the purpose. It would at least be possible to verify it exists and no example has been shown.
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
That’s a great idea if you’re hiring locally but we do hire international remote and I suspect no one will snail-mail me an application from the Americas or South Africa to Germany.
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
It certainly would be illegal in Europe under the GDPR - data collected for one purpose (handling of applications) cannot be used for another without explicit, informed consent.
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
I can tell you that our HR takes the time to write proper responses to every application, but we straight up delete AI written applications. I honor the effort put into any application, but if people haven’t spent the time, then why should we?
Xylakant··on 'Ghost jobs' are on the rise – and so are calls to ban them
When we post a job ad on LinkedIn, I already get 30 spam answers in the first few minutes, people that have obviously spent not a single second reading the requirements. And you want to further automate this? I’ll just ask my people person to automate the response.

We really try to spend the time to answer every application, but since AI generated applications have become a thing, we have decided to not answer those. Why should I spent time if you haven’t spent the time?

Xylakant··on A giant ball will help this man survive a year on an iceberg
Yes, sure. But even that wouldn’t work - those people still need to have advanced warning and be close to a capsule. But if you’re close to a capsule, then you’re likely close to home and you can just build a flood safe room in your house.
Xylakant··on A giant ball will help this man survive a year on an iceberg
I’m amazed by the idea that providing escape capsules would have saved many lives. The Christmas tsunami caused about 230 000 fatalities in a densely populated area. People didn’t even get to higher ground. Where are you going to store the hundreds of thousands capsules that you’d need to even make a dent in that number. And how will people get into those capsules within minutes of the warning?
Xylakant··on Go is portable, until it isn't
If you need glibc for any kind of reason, that approach is still used. But that won’t save you if no glibc is available. And since the folks here want to produce a musl build anyways for alpine, the easier approach is to just go for musl all the way.
Xylakant··on Rust in the kernel is no longer experimental
Let's take a simple example to illustrate how unsafe {} cuts down the review effort for many operations. Take a static mutable global variable (a global counter for example). Reading a static is safe, mutating it (increasing the counter) is not - it requires an unsafe {} block.

If you need to check which places mutate this global static you only need to check the unsafe parts of the code - you know that no other part of your code could mutate it, the compiler won't let you. If you have a bug that is related to mutating this static, then it might manifest anywhere in your code. But you know for certain that the root cause must be in one of your unsafe blocks - even if you don't know which one.

Good programming practice will cut down that effort even more by dictating that unsafe access should be grouped in modules. For example when binding to a C module (unsafe) you'd usally generate an unsafe wrapper with bindgen and then write a safe wrapper on top of that. Any access that tries to go around the safe wrapper would be frowned upon and likely fail review.

And again, the compiler will help you there: Any access that tries to bypass the safe api would need to be unsafe {} again and automatically receive extra scrutiny in a review, making it less likely to slip through.

Compare that to a C codebase where anything goes. A static might be mutated anywhere in your codebase, even through a pointer to it - meaning you can't even reliably grep for it. It may slip through review unnoticed because no attention is drawn to it and cause bugs that are hard to trace and reason about.

If you're writing embedded code, similar considerations apply - access to registers etc. require unsafe {}. But because access is unsafe {}, it's usually gated behind a safe api that is the boundary of the low-level code and the higher buisness logic. Unsurprisingly, these are critical parts of the code - hence they receive extra scrutiny and in our project, we allocate substantial review capacity on those. And the compiler will enforce that no safe code can circumvent the access layer.

The number you're tagging as unrealistic figure is the result of dedicated and careful design of language and compiler features to achieve exactly this outcome. It's not a random fluke, very clever people did sit down and thought about how to achieve this.

Xylakant··on Rust in the kernel is no longer experimental
But you know that it's one of them. That cuts 96% of their codebase out, even assuming you have no idea which one it could be.
Xylakant··on Rust in the kernel is no longer experimental
That's the other interesting observation you can draw from that report. The numbers contained in the first parts about review times, rollback rates, etc. are broken down by change size. And the gap widens for larger changes. This indicates that Rusts language features support reasoning about complex changesets.

It's not obviously clear to me which features are the relevant ones, but my general observation is that lifetimes, unsafe blocks, the borrow checker allow people to reason about code in smaller chunks. For example knowing that there's only one place where a variable may be mutated supports understanding that at the same time, no other code location may change it.

Xylakant··on Rust in the kernel is no longer experimental
Thanks for the correction.
Xylakant··on Rust in the kernel is no longer experimental
1 memory safety vulnerability, that's a pretty important distinction.

Yes, I believe that at least the order of magnitude is correct because 4 800 000 of those lines are guaranteed to not have any by virtue of the compiler enforcing memory safety.

So it's 1 per 200 000, which is 1-2 orders of magnitude worse, but still pretty darn good. Given that not all unsafe code actually has potential for memory safety issues and that the compiler still will enforce a pretty wide set of rules, I consider this to be achievable.

This is clearly a competent team that's writing important and challenging low-level software. They published the numbers voluntarily and are staking their reputation on these reports. From personal observation of the Rust projects we work on, the results track with the trend.

There's no reason for me to disbelieve the numbers put forward in the report.

← PreviousPage 3 of 34Next →