HN user

nequo

5,037 karma
Posts249
Comments1,166
View on HN
people.redhat.com 1y ago

SELinux Coloring Book (2020) [pdf]

nequo
1pts0
cglab.ca 1y ago

Pre-Pooping Your Pants with Rust (2015)

nequo
1pts0
www.yodaiken.com 1y ago

Undefined behavior in C is a reading error (2021)

nequo
25pts67
github.com 1y ago

Wayland Maker – A Wayland Compositor Inspired by Window Maker

nequo
2pts0
matklad.github.io 1y ago

Rust's Ugly Syntax (2023)

nequo
161pts165
www.youtube.com 1y ago

New innovations in credit cards (1985) [video]

nequo
1pts0
www.youtube.com 1y ago

Gem versus Windows – Battle of the GUIs (1986) [video]

nequo
3pts1
www.courtlistener.com 1y ago

Anoke v. Twitter, Inc.: Rule 7.1. Corporate Disclosure Statement

nequo
1pts0
wiki.mozilla.org 1y ago

Firefox about config privacy tweeks

nequo
1pts1
www.youtube.com 1y ago

Tony Hawk's Pro Strcpy [video]

nequo
2pts0
www.theguardian.com 1y ago

Amazon says US labor watchdog that filed labor charges violates constitution

nequo
4pts0
community.intel.com 1y ago

Microcode (0x129) Update for Intel Core 13th and 14th Gen Desktop Processors

nequo
2pts1
lwn.net 1y ago

Mel Chua RIP

nequo
8pts1
discourse.haskell.org 1y ago

Ideas for Master's Thesis

nequo
2pts0
www.theguardian.com 1y ago

Rupert Murdoch in secret legal battle with children over media empire

nequo
12pts5
github.com 2y ago

Sandboxed kernel mode WebAssembly runtime (2020)

nequo
2pts0
www.microsoft.com 2y ago

The Functional Essence of Imperative Binary Search Trees

nequo
1pts0
terbium.io 2y ago

Comparing Rust's Traits and Haskell's Typeclasses (2021)

nequo
4pts0
steveklabnik.com 2y ago

Is WebAssembly the Return of Java Applets and Flash? (2018)

nequo
6pts2
archive.fosdem.org 2y ago

Parsing POSIX [S]hell (2018) [video]

nequo
2pts0
filtra.io 2y ago

Rust Jobs Report: June 2024

nequo
1pts0
stevana.github.io 2y ago

The sad state of property-based testing libraries

nequo
208pts121
github.com 2y ago

Comparing the C FFI overhead in various programming languages (2021)

nequo
5pts2
lean-lang.org 2y ago

Lean 4.9.0

nequo
1pts0
www2.lib.uchicago.edu 2y ago

OCaml for the Skeptical (2006)

nequo
4pts0
book.realworldhaskell.org 2y ago

Real World Haskell (2008)

nequo
2pts0
steveklabnik.com 2y ago

Why is Clojure so stable? (2018)

nequo
2pts0
lean-lang.org 2y ago

`do' Unchained (2022) [pdf]

nequo
1pts0
arxiv.org 2y ago

Denotational Semantics and a Fast Interpreter for jq (2023)

nequo
4pts0
www.youtube.com 2y ago

APL Demonstration (1975) [video]

nequo
85pts36

the developer who should know the application better than the systems administrator

On the other hand, the administrator knows their system better than the developer. There could be certain network connections or file paths that you want to block on one system but not on another.

If you include boost (which, admittedly, is a heavy dependency, but still a single one)

Then in principle, we could curate a set of useful Rust crates, treat the set as a single dependency, and be on the same page as C++ with Boost.

I don't think that you violated any guidelines. I think that the downvotes for your parent comment are only an expression of disagreement with what you propose. If I can suggest, don't take it personally.

Turning `'` into `lifetime` would make Rust code that needs explicit lifetimes extremely verbose. That would make code harder to keep on the same line, for no added benefit in expressiveness.

Allowing both `'` and `lifetime` in the syntax would make the language more confusing to anyone who is learning it, and it opens up unproductive debates about syntax in code bases if two authors have conflicting preferences.

The problem is that neither Linus nor the other prominent maintainers will live forever. C was the right choice in 1991 but today the landscape is different enough that its shortcomings, for the younger generations, are painful to ignore.

So saying yes to Rust, or to some other language that is not filled with foot guns and could also work in the kernel space, is not only a matter of kindness but a matter of long-term strategy for the kernel.

Thank you, I’ve been looking for an explanation of this. So Mono is useful to Wine because its users care more about licensing and running legacy software: Mono is free software and an acceptable runtime for pre-.NET 5.0 stuff.

This is irrelevant to the example cited by Hopper. If you have a large log, you don't have time to breed a larger ox. You need to solve the problem with the oxen you have.

This wiki page raises some good points, for example, the stateful nature of some of the APIs:

  Instead of returning a data structure of the match results (eg from a call to match-string), the match results are mutated in global memory and accessed in separate function calls. This is both less functional in style and more error prone. For example, if save-match-data is not used appropriately, then library functions can trample on the match data which a higher level function is in the middle of using.
But in some other parts it reads like two or more personalities stuck in the same body shouting at each other using the same mouth:
  EmacsLisp Isn't Scheme

  This, from my highly unscientific sample, is far and away the most popular reason EmacsLisp sucks. Well, that’s good to know. EmacsLisp is also not Perl, or COBOL, or IBM 1130 assembler, or a bicycle, or an orange. Thanks for the help!

It is true that macOS is a bad example here because it is not using a Linux kernel.

But Apple also names operating systems that use the same kernel different "OSes": iOS and iPadOS share a kernel with macOS, and for all I can tell, so do watchOS and tvOS.

An operating system consists of both a kernel and a userland. The Linux kernel by itself does not make an OS. I think this makes it legitimate to call CentOS, NixOS, SerpentOS, iOS, watchOS, etc., OSes.

The burnout that you’re pointing out is a sign that it is work. People who play video games competitively often go through burnout:

https://www.cbsnews.com/news/esports-burnout-in-video-gaming...

So I think about it as this: if I regularly feel pressure to complete tasks that I don’t want to, then it is work. This covers activities that one is not paid to do and that others may call hobbies. For example, training for a marathon as an amateur.

A constant in a codebase is not “uttered somehow at some point.” It is a fixture for everyone to see until it is changed by another commit.

I’m not offended. It is unprofessional. Talking about sex at a workplace that is not about sex is going to be offputting to many people who are not there to have sex.