niemeyer

6 ms·

1.
by niemeyer 3y ago
> Either take my code without a contract or live with the bugs The less simplistic view of the situation is that major maintainers (corporate or otherwise) pay the price of keeping the project up for the long run, under the defined licen
2.
by niemeyer 3y ago
I'm sad to see Stephane leaving, but it's lost in me how his departure towards doing whatever else he wants to do suddenly transforms into LXD not being open?
3.
by niemeyer 3y ago
It was always pretty clear that something would have to get adjusted the day Stephane left the company, because it's a major project for Canonical and Stephane preferred to run some of the infrastructure himself. From his own comments
4.
by niemeyer 6y ago
I don't know who you talked to, but I can tell the story is richer and more interesting than that. Saying that snaps have performance issues is similar to saying that containers have performance issues. They do affect performance becau
5.
by niemeyer 6y ago
That's exactly it. I work at Canonical and was part of the internal conversation around this subject. We constantly walk that fine line where we want to encourage open source work and communities around it to flourish, while at the sam
6.
by niemeyer 6y ago
> It is a pretty nifty idea but like all things made by Canonical it is basically digitized garbage. > At least those are not made by people with a disdain for error checking. Every single time there's a topic about Ubuntu or Can
7.
by niemeyer 8y ago
If it makes you happy, yes, I see it. But that doesn't make things better for anyone. We've had more interesting discussions around this issue where people could actually present good arguments towards more control, and some of th
8.
by niemeyer 8y ago
Indeed the size calculation is incorrect. It's likely looking at the unpacked size, but snaps are never unpacked, which ironically is a difference missed by itself. These are the actual sizes for these snaps: $ snap info vlc | grep
9.
by niemeyer 8y ago
Yes, the article indeed is on the low end. It focuses mainly on the package sizes, and gets it very wrong as mentioned in other comments.
10.
by niemeyer 8y ago
Yes, the size is wrong. It's looking at the unpacked size, but the snaps are never unpackaged. Here are the actual sizes for the mentioned snaps: $ snap info vlc | grep stable: stable: 3.0.4 (555) 204M
11.
by niemeyer 8y ago
There's a long thread with in depth discussion about this: https://forum.snapcraft.io/t/disabling-automatic-refresh-for... For those that understandably won't want to go through it all, the short version is t
12.
by niemeyer 8y ago
There are self-hosted proxies, and there are publicly hosted stores, but all stores are part of the exact same hierarchy and share some of their knowledge. That's mainly a consequence of implementing the intended user experience as ori
13.
by niemeyer 8y ago
> I'm assuming with "LSM stacking" that you mean The term "LSM stacking" is public. Search for it and you'll get good material. > Are you going to convince Red Hat to That's not how things work. Cano
14.
by niemeyer 8y ago
I don't think that was ever true? Docs: https://docs.snapcraft.io/build-snaps/electron Example: snap info electron-quick-start
15.
by niemeyer 8y ago
> I don't think it's the majority _per se_ (since Ubuntu Core can't run those), but most of the popular ones likely do. No, that's also incorrect if you slice it by popularity. We don't have a public chart easily
16.
by niemeyer 8y ago
> Snaps rely heavily on Ubuntu's specific flavor of AppArmor to be able to offer full confinement, The AppArmor patches have been largely upstreamed by Canonical, and improvements continue to float upstream constantly. So claiming i
17.
by niemeyer 8y ago
No, not really. Files at ~/.* were never readable or writable for strict snaps, even when they were granted the "home" interface, precisely for that sort of reason. The file permissions and ownership are also strictly checked
18.
by niemeyer 8y ago
I work for Canonical on snapd, so can provide some background here. You're probably describing Ubuntu Core instead of classic Ubuntu. The UX there is oriented for devices, and it was cooked to avoid default passwords in an environment
19.
by niemeyer 10y ago
Such competing efforts are actually a form of non-voluntary collaboration. rpm and deb (and apt, yum, synaptic, ...) have significantly evolved together along the years, looking at each other. This happens all the time, and is happening aga
20.
by niemeyer 10y ago
Yes, people are using in production. Last community meeting we had some folks reported a large server deployment in the UK (in the order of thousands of servers) that was being partly transitioned to snaps. I think that's the biggest u
21.
by niemeyer 10y ago
We have a sprint next week to discuss some of that. The recent focus around snaps has been on the feature set leading to Ubuntu Core 16, which is itself in freeze at this point. The features are mostly general, though, and have been landing
22.
by niemeyer 10y ago
Interview processes aren't about ensuring 100% of the good candidates get hired, but rather about trying to ensure that the candidate finally selected is good. Being several times on the hiring end of that conversation, there's a
23.
by niemeyer 10y ago
If you log into one of their shared hosts you'll see custom kernel, custom packages, etc.
24.
Snappy Interfaces(blog.labix.org)
2 points by niemeyer 10y ago|0 comments
25.
by niemeyer 10y ago
Indeed, or any other case where the application is granted permission to do something sensitive (camera?) and abuses that trust. Even in those cases, though, it is an improvement to know the access exists, and to have control over it. Some
26.
by niemeyer 12y ago
There are further details about how it works in this blog post: http://blog.labix.org/2012/08/22/multi-doc-transactions-for-... While it does work, it's still a workaround for the lack of first-class tra
27.
by niemeyer 12y ago
The transaction does span across hosts with the linked package.
28.
by niemeyer 12y ago
There are many different aspects to shared object support, there is support to some of these aspects today (you can link against shared libraries, for example), and there are on going conversations about supporting other models. This is a r
29.
by niemeyer 12y ago
Where's the data showing bananas are more heavily treated than any other fruit? Here is some actual data from 2009, with analysis for Brazil by a proper agency (ANVISA's PARA, Project for Analysis of Agrotoxic Residue in Food): h
30.
by niemeyer 12y ago
The rule was never entirely clear, but there was definitely support towards allowing Go pointers to be visible in C code, as long as they were held referenced inside Go code somewhere. See this thread, for example: https://code.g

More ›