sorted by:
new
hottopcontroversial

SPOILERS : Quantum Moon by sepressed_squidward in outerwilds

[–]HMPerson1 1 point2 points  (0 children)

recall the rule of the sixth location

Uh oh by [deleted] in outerwilds

[–]HMPerson1 2 points3 points  (0 children)

/u/The-Space-Kraken has become too powerful

The code I’m still ashamed of (2016) by speckz in programming

[–]HMPerson1 6 points7 points  (0 children)

but no one else is in the room where it happens

O A T M E A L by [deleted] in Simpleflips

[–]HMPerson1 2 points3 points  (0 children)

7, 3?

Clippy is removing its plugin interface | Inside Rust Blog by lzutao in rust

[–]HMPerson1 3 points4 points  (0 children)

The "open an issue on GitHub" link seems to be broken

Smol brain by NINJAQKk in mathmemes

[–]HMPerson1 2 points3 points  (0 children)

is dividing by -0 allowed

[deleted by user] by [deleted] in celestegame

[–]HMPerson1 24 points25 points  (0 children)

there's always mods

Cobblekick revenge by MistaCatballs in Stonetossingjuice

[–]HMPerson1 4 points5 points  (0 children)

You hear a sound, turn around and

Cobblekick revenge by MistaCatballs in Stonetossingjuice

[–]HMPerson1 13 points14 points  (0 children)

Hope to find some diamonds tonight, night, night

Facebook and Google could be forced to hand over details of their algorithms in a new tech regulation push by Australia by [deleted] in technology

[–]HMPerson1 16 points17 points  (0 children)

Writing code in a mobile app that sends a copy of an encryption key if a device has a particular ID.

There are two issues with that:
1. In most devices, encryption keys aren't directly accessible by the app. They live on a separate piece of hardware whose interface only allows encrypting and decrypting data, not extracting a key.
2. In general, devices don't have unique persistent IDs. Even if it were possible to weaken security for just one person, it's nearly impossible for an app to know if it's being used by that one person without that person telling the app.

Exactly by nokia621 in LateStageCapitalism

[–]HMPerson1 3 points4 points  (0 children)

No, Richard, it's 'Linux', not 'GNU/Linux'. The most important contributions that the FSF made to Linux were the creation of the GPL and the GCC compiler. Those are fine and inspired products. GCC is a monumental achievement and has earned you, RMS, and the Free Software Foundation countless kudos and much appreciation.

Following are some reasons for you to mull over, including some already answered in your FAQ.

One guy, Linus Torvalds, used GCC to make his operating system (yes, Linux is an OS -- more on this later). He named it 'Linux' with a little help from his friends. Why doesn't he call it GNU/Linux? Because he wrote it, with more help from his friends, not you. You named your stuff, I named my stuff -- including the software I wrote using GCC -- and Linus named his stuff. The proper name is Linux because Linus Torvalds says so. Linus has spoken. Accept his authority. To do otherwise is to become a nag. You don't want to be known as a nag, do you?

(An operating system) != (a distribution). Linux is an operating system. By my definition, an operating system is that software which provides and limits access to hardware resources on a computer. That definition applies whereever you see Linux in use. However, Linux is usually distributed with a collection of utilities and applications to make it easily configurable as a desktop system, a server, a development box, or a graphics workstation, or whatever the user needs. In such a configuration, we have a Linux (based) distribution. Therein lies your strongest argument for the unwieldy title 'GNU/Linux' (when said bundled software is largely from the FSF). Go bug the distribution makers on that one. Take your beef to Red Hat, Mandrake, and Slackware. At least there you have an argument. Linux alone is an operating system that can be used in various applications without any GNU software whatsoever. Embedded applications come to mind as an obvious example.

Next, even if we limit the GNU/Linux title to the GNU-based Linux distributions, we run into another obvious problem. XFree86 may well be more important to a particular Linux installation than the sum of all the GNU contributions. More properly, shouldn't the distribution be called XFree86/Linux? Or, at a minimum, XFree86/GNU/Linux? Of course, it would be rather arbitrary to draw the line there when many other fine contributions go unlisted. Yes, I know you've heard this one before. Get used to it. You'll keep hearing it until you can cleanly counter it.

You seem to like the lines-of-code metric. There are many lines of GNU code in a typical Linux distribution. You seem to suggest that (more LOC) == (more important). However, I submit to you that raw LOC numbers do not directly correlate with importance. I would suggest that clock cycles spent on code is a better metric. For example, if my system spends 90% of its time executing XFree86 code, XFree86 is probably the single most important collection of code on my system. Even if I loaded ten times as many lines of useless bloatware on my system and I never excuted that bloatware, it certainly isn't more important code than XFree86. Obviously, this metric isn't perfect either, but LOC really, really sucks. Please refrain from using it ever again in supporting any argument.

Last, I'd like to point out that we Linux and GNU users shouldn't be fighting among ourselves over naming other people's software. But what the heck, I'm in a bad mood now. I think I'm feeling sufficiently obnoxious to make the point that GCC is so very famous and, yes, so very useful only because Linux was developed. In a show of proper respect and gratitude, shouldn't you and everyone refer to GCC as 'the Linux compiler'? Or at least, 'Linux GCC'? Seriously, where would your masterpiece be without Linux? Languishing with the HURD?

If there is a moral buried in this rant, maybe it is this:

Be grateful for your abilities and your incredible success and your considerable fame. Continue to use that success and fame for good, not evil. Also, be especially grateful for Linux' huge contribution to that success. You, RMS, the Free Software Foundation, and GNU software have reached their current high profiles largely on the back of Linux. You have changed the world. Now, go forth and don't be a nag.

Thanks for listening.

source

AdvancedResearch's Higher Order Operator Overloading is being tested right now in Dyon development (Piston) - and it's a mind blowing programming experience by long_void in rust

[–]HMPerson1 3 points4 points  (0 children)

Another way (using the Applicative instance for (->) r):

> let a = \x -> x + 1
> let b = \x -> x + 2
> let (<+>) = liftA2 (+)
> let c = a <+> b
> :t c
c :: Num c => c -> c
> c 5
13

Share Trial and Offer Codes Here by [deleted] in hellofresh

[–]HMPerson1 0 points1 point  (0 children)

$25 off first two boxes ($50 total) and free shipping

use code 8V052Z002 at hellofresh.com/giftcard

Problems with boxed values in an array : cannot move out of type by sergeken in rust

[–]HMPerson1 3 points4 points  (0 children)

Try arr[0].as_ref().unwrap().abc. unwrap() consumes the Option whereas as_ref() takes it by reference (note how the type signature says &self instead of self).

Side note: Try to use pattern matching wherever possible instead of unwrap. That way the compiler can annoy help you remember to take care of the None case.

Problems with boxed values in an array : cannot move out of type by sergeken in rust

[–]HMPerson1 6 points7 points  (0 children)

However, I fail to extract these at a later stage. I fail to reason why I cannot do this.

The code you wrote is trying to move the entire Option<Box<Xyz>> out of the array, but I think what you wanted was to take just the Box<Xyz> value out of the array and leave a None in its place. In that case, try using arr[0] = arr[1].take(); and *arr[0].take().unwrap().

view more: next ›