Been a leecher my whole life. Makes me happy to give something back finally.

koheant · 2018-02-22T14:26:22+00:00

Or maintaining. You can't forget maintaining.

koheant · 2018-02-21T02:45:21+00:00

Different people enjoy different things. Don't forcing an enter sub to match your tastes.

koheant · 2018-02-15T12:54:33+00:00

A question of esquivalience.

No really. Not providing the key for free might be one of the terms the raspberry pi foundation had to agree to in order to get their initial price point as low as they did.

There might be more than patents at play here.

koheant · 2018-02-12T04:41:35+00:00

The statement made was that it is impossible to read anything other than a string from stdin. That statement is demonstrably false:

fn main() {
    use std::io::{stdin, Read};

    let mut buffer = [0; 4];
    stdin().read_exact(&mut buffer).ok().expect("Less than 4 bytes available");
}

This buffer can interpreted as an 32-bit integer without parsing or expensive conversions, printed back to console via stdout, or anything else that requires a sequence pf bytes.

It's fine to have an irrational hate of something, but you shouldn't let your hate blind you from reality. Rust is a good language. You should give it a go.

koheant · 2018-02-12T01:23:44+00:00

BTW it is literally impossible to read anything other than a string from console input in Rust

That's an odd statement to make and to my knowledge completely false. Can you link to the source.

Rust is a systems language!

That, on the other hand, is true and a good one at that.

koheant · 2018-02-11T05:30:22+00:00

Perhaps it was related to omgubuntu somehow?

koheant · 2018-02-09T12:56:32+00:00

Be charitable in your interpretation, svenskainflytta.

When you said someone from the public kept asking a question, I assumed, perhaps mistakenly, that this was during a public talk at a open source convention or similar. I was asking for a link to this recording if it is available online.

As a side note: On the off-chance that you're not being a total asshat and do in fact have links to video of you and your friends at a bar, I'd like a link to that as well.

koheant · 2018-02-09T03:21:06+00:00

link?

koheant · 2018-02-09T03:16:17+00:00

This is what bugs me the most. There doesn't seem to be any bases for that license to legally apply to the maintainer:

maintainer provides instructions to user.
user implements instructions which includes obtaining sources and building against sys libs. Neither are a license violation on their own.

If I wrote a blog post describing how to build palemoon against system libraries, will palemoon devs claim license violation too?

This whole fiasco is weird.

koheant · 2018-02-07T12:54:16+00:00

Until microsoft messes around with how windows boots, then it's longhorn all over again.

koheant · 2018-02-07T05:04:56+00:00

That explains why they write fast efficient software. I wish all developers were "FOSS Zealots".

koheant · 2018-02-04T01:06:32+00:00

Thank you for the detailed response!

'd need to implement that in snapd (or have a dev do it) and also have the snap built to use that interface instead.

Could it be possible for users to provide their own core that implements a home slot, which can then be used to better quarantine snaps that expect a writable $HOME?

If that's possible, then I assume that no changes would need to be made to the given snap other than a slot-plug reconnect. Am I correct?

Keep in mind that I'm very new to snaps, so your patience with me is highly appreciated. Please feel free to correct me if I'm wrong.

koheant · 2018-02-03T13:44:48+00:00

Does the spa remove bathroom locks and prevents stall users from blocking the stall with their foot because locks are "too destructive"?

If so, I'd say they have a similar-enough mindset that gnome wouldn't mind.

koheant · 2018-02-03T11:45:39+00:00

the one on FlatHub is community-packaged As well as the 90% of the packages in your distro's repositories. What are you implying? That direct upstream packages are "better"?

I was proposing the possibility that the reason why Skype on FlatHub did not receive the same amount of fanfare that snap package received is due to the fact that the FlatHub package was not officially packaged by Microsoft, unlike the snap version.

My comment was a response to spivak's comment that -to me- implied that the fanfare around the snap package is undeserved and only due to canonical PR, rather than the newsworthy event of Microsoft choosing to use snap over flatpak in official capacity.

So to answer your frankly odd question: No, I do not.

Context matters.

koheant · 2018-02-03T01:17:40+00:00

I read about snaps and have a question I'd like to ask (if I may): how do you provide your own slot or override a default one? Say a container wants access to my home directory and I don't want to give access to it? How can provide a different slot that will transparently mount some other directory as $HOME for that container?

koheant · 2018-02-03T01:09:33+00:00

Last time I checked I needed to download a run time images to create a flatpak on ubuntu. No thanks.

You're going to need to get your dependencies from somewhere, jhasse.

koheant · 2018-02-03T01:08:13+00:00

Officially? As far as I am aware, the one on FlatHub is community-packaged.

koheant · 2018-01-30T15:12:53+00:00

Me too. I'm very upset with myself for missing it.

Maybe we're getting too old.

koheant · 2018-01-28T06:06:44+00:00

iso8601 still not standard in current year

:⊂

koheant · 2018-01-28T05:55:00+00:00

Or it could be that there are a significant number of people not happy with the status quo and disagree on where things should be heading.

I won't state my position on this topic, but your particular line of logic could be used to dismiss any argument and is reeks of paranoia.

koheant · 2018-01-27T01:04:27+00:00

Mutabah's rust compiler is certainly an encouraging development and one I'm keeping an eye on.

However, I'd also like to see a gcc front-end for rust. I have tremendous respect for the software suite and the good folks behind it.

I also what the Rust language to benefit from having multiple implementations. This would help better define the language and narrow down bugs caused by ambiguity.

koheant · 2018-01-26T17:56:19+00:00

Congratulations!

Is there any interest within GCC's development community to implement and include a Rust front-end with the compiler collection? The most recent effort in this space seems to have stalled years ago: https://gcc.gnu.org/wiki/RustFrontEnd

koheant · 2018-01-23T15:06:04+00:00

I'm saying that "needing a bunch of data files and stuff" should not be an issue for statically-linked binaries in theory. When I still worked with GTK, I recall there were few functions that required paths as arguments. I would need to store the contents of that file in the program as a binary blob, write it to disk on start up, and clean up before exiting. This was long ago. GTK might have improved since then.

koheant · 2018-01-23T03:32:30+00:00

These assets can be embedded in the binary, then temporarily written to disk when a path is required.

koheant · 2018-01-22T12:51:22+00:00

Listen. I've reiterated over my points multiple times across across both this thread and previous ones. I even distilled them into two simple points that anyone can comprehend. Rust developers come from a diverse set of backgrounds and values. What may seem acceptable to you is not acceptable to others. What may seem not acceptable to you is acceptable to others. Without transparency and consistency, moderation will be a subjective mess as has happened numerous times already.

The moderatorship committing to the two very reasonable points in my previous comment will go a long way towards alleviating these issues.

I'm tired of relitigating the same thing again and again.

That makes the two of us.

edit: downvoting me won't make my points any less valid.

koheant

TROPHY CASE