ginsider_oaks
ginsider_oaks on Hacker News
> "review the image for [...] blatant indicator of plagiarism"
There's a program for that on your computer, it's called 'true'.
more like suing the driver because the (self-driving) car hit a human.
> Programs must be written for people to read, and only incidentally for machines to execute.
from the preface of SICP.
would it be better if they didn't skip the hard part? (i.e. if they re-designed it from first principles)
does something being hard to do make it more virtuous?
would it be better if they didn't have fun coding it?
is something worse if it was fun to make?
or even better:
:'<,'>s/^/> /
if you use ublock origin you should be OK, it warns you when you try to access lubuntu.net
I remember someone making a card game GALGA [1] in Haskell and compiling a high-level "rules" DSL to a low-level "animation" DSL and "primitive" DSL for handling animations and state changes respectively.
[1] https://roganmurley.com/2021/12/11/free-monads.html
funnily my friend just discovered that you can split it into thirds a few day ago and now does it whenever he eats a banana
list languages and array languages are quite different.
in LISP, the lists are heterogeneous i.e. each element can contain different types, which is also how you can e.g. make a tree out of lists in LISP.
typically in array languages all elements are the same, and you use operations that apply to the whole array e.g. one operation for summing the array rather than a loop.
> Most of them shouldn't have a right to vote in the first place [in my opinion].
> > These are simply more opinions [...]
> > > No, not opinions. Demonstrable facts.
you're going to have to explain this one to me
The point is that the first list is a series of (flawed) reasons that the author, and probably many others, have been discouraged from blogging.
And even if you know they're flawed, it can still get in your head and discourage you, so the author provides a different list of reasons to still blog in spite of that. It's not meant as proving/disproving any of the points, but simply as motivation to keep going.
Lojban[1] is a constructed language which is (or tries to be) syntactically unambiguous. Of course even fewer people speak Lojban than Esperanto, but there's still a sizable community.
[1]: https://mw.lojban.org/papri/Lojban
just give me the NSA putting backdoors in my chips rather than this two-faced nonsense.
They're not conflating.
mgaunard says:
> The alternative that the parent said was making all of your state be a union
> with some kind of error, and making sure all accesses handle the fact the
> variable might be in a erroneous state.
This is exactly what `Result` is in Rust. While I haven't used Rust, it seems
that panics are generally discouraged and only used as a last resort whereas
exceptions are more commonly used in C++ and Java.
What is stopping someone from publishing SNKRX to a site like itch.io and
selling it for 1€ instead? And if nothing is stopping it, why hasn't someone
done it yet (that I know of).
I'd like to present a counterexample: SNKRX[1]. It costs 3€ and is under the MIT
license, you can find it on github[2].
It sold >100,000 units[3], and AFAIK no one's massively undercut the author. I
guess he's kind of undercutting himself by making it available on github, but I
bet most people would rather pay 3€ and have nice steam features than download
and compile a game off a site they likely don't know.
And yes, I do realize he's still the copyright holder for SNKRX, but he's not
really enforcing it with a permissive license like MIT.
[1]: https://store.steampowered.com/app/915310/SNKRX/
[2]: https://github.com/a327ex/SNKRX
[3]: https://www.a327ex.com/posts/2022/
Are noise and procedurally generated textures mutually exclusive?
The Wikipedia article for gradient noise[1] says:
> Gradient noise is a type of noise commonly used as a
> procedural texture primitive in computer graphics.
[1]: https://en.wikipedia.org/wiki/Gradient_noise
it sounds like the danish word for carrot: "gulerod" which translates to "yellow root".
the actual copying isn't a problem, it's distribution. if i buy access to a PDF i'm not going to get in trouble for duplicating the file unless i send it to someone else.
when someone uploads their copyrighted text to a web page they are distributing it to whoever visits that page. the browser is just the medium.
Wow, I do something similar, however it is much more limited in scope (and all on pen & paper for now). I also share the author's last name.
is any rust code some way immune to unsafe blocks?