Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
I want to point out that his index finger is morphed in a weird mist from stiching images and that the anime eyes filter erased the top of his glasses' frame. The whole photo has an eerie feeling..
 
NoIdeaWhatImDoing said:
the chin is the typical Chinese filter chin, chinese people like them pointy. He's probably first generation Chink because that's not an Otaku thing, japs like rounder faces.
Click to expand...
Creative Username said:
there is so much filter going on in that image, that i'm pretty sure not a single pixel in it is anywhere close to where it originally was
those weirdly skewed fingers are because an impressive amount of jaw was transformed out of the way
Click to expand...
TalmudicKetamine said:
How far back does his hairline go?
Line A or Line B?
Click to expand...

There is a pinned post with video of him: https://x.com/saltyAom/status/1939479411201614075


It looks like he probably had (at least) his nose surgically altered. Back on the topic of open source, is this framework any good? (source: https://x.com/saltyAom/status/1984853194477093304)



https://elysiajs.com/ / https://github.com/elysiajs/elysia

I've somehow avoided most frontend work for the past decade and can't stand React, so some JS/Node people chime in.
 
Or what? You get arrested by the rust police? At any rate, these people sound extremely cool and stable and blindly doing all they tell you is probably a very good idea with virtually no downsides ever.

[Just mentally copy paste what I have written before about why fragmentation is actually good in this space]
 
Oh my fucking god it gets funnier. He got promoted to the "senior" "engineer" and announced his retarded plans to fuck up APT literally at the same day:

1000020071.png

Some people are not having it tho

I find this particular wording rather unpleasant and very unusual to
what I'm used to from Debian in the past. I have to admit that I'm a
bit disappointed that such a confrontational approach has been chosen.

Thanks,
Adrian
Click to expand...

(Someone pls archive, I'm phonefagging)
 
skunt said:

it's that time of the day again, a core system component is being rewritten to rust because [reasons]
Click to expand...
muh memory safety
Demonstrate where it's unsafe and fix it, or are you just going out on a hunch, cargo (heh) culting "safety"

The deb parsing part of apt is just 10k lines of old-ass cpp with no smart pointers and char * everywhere. Start with that, instead of forcing your dumbass rust shit
 
WielkiWapiesz2137 said:
I wonder how comparatively many memory bugs have been introduced by switching to rust instead of just sticking to C
Click to expand...
considering that the language formally proves the absence of memory bugs in properly written bugs, 0 in theory
in theory
in practice: very optimistic to assume that nobody who wrote any of the code your 920 dependency crates is a completely retarded niggermonkey who did something really stupid in an unsafe block
 
-fsanitize=address
There, now it's memory-safe. Just like Java, C#, Go, Ada, every dynamic language (other than Forth) ever, etc. Outside of obviously-marked danger zones like FFI, unsafe blocks, Unchecked_ anything in Ada, etc, these all formally prove the absence of memory bugs by turning them into bounds errors and null pointer exceptions. Aren't semantics convenient!

And no, there is absolutely zero chance that the performance hit from sanitizers would significantly slow down parsing of archives, unless they're implementing their own compression for some bizarre reason.

It wouldn't surprise me if insisting on writing the same program 3 times over ends up causing some bugs to be caught (and some to be introduced...), but they could pick pretty much any language for this and I would prefer it over Rust. Nothing needs dependency bloat and package churn quite like the system package manager.

It's important for the project as whole to be able to
move forward and rely on modern tools and technologies
and not be held back by trying to shoehorn modern software
on retro computing devices.
Click to expand...

Code: 
(define* (librsvg-for-system #:optional
                             (system (or (%current-target-system)
                                         (%current-system))))
  ;; Since librsvg 2.50 depends on Rust, and Rust is only correctly supported
  ;; on x86_64, aarch64 and riscv64 so far, use the ancient C version on other
  ;; platforms (FIXME).
  (if (supported-package? librsvg system)
      librsvg
      librsvg-2.40))

This is referenced in 101 places in guix.

Code: 
(define* (desktop-services-for-system #:optional
                                      (system (or (%current-target-system)
                                                  (%current-system))))
  ;; List of services typically useful for a "desktop" use case.

  ;; Since GDM depends on Rust and Rust is not available on all platforms,
  ;; use SDDM as the fall-back display manager.
  ;; TODO: Switch the condition to use (supported-package? "rust") and make
  ;; a news entry about the change.
  (cons* (if (string-prefix? "x86_64" system)
             (service gdm-service-type)
             (service sddm-service-type))
[...]

guix can't even have a default display manager, they have to set up fallbacks in case of rustardism.

I'm so sick of shitlang designers trying to offload their technical debt onto the ecosystem at large. Zig decides to drop support for bootstrapping, says "teehee I'm sure someone will come along and make their own bootstrapping implementation just like mrustc tries to cope with the shit sandwich Rust served everyone, don't worry guys". Gee, I wonder who has by far the most domain knowledge necessary for that kind of thing? Could it be you? You do realize that domain knowledge is 90% of the actual work, right? You could easily accomplish this yourself in 10% of the time it would take anyone else. Likewise, Rust devs insist that literally anybody except Rust devs has to fix their shitty platform support for them (and no it can't be gcc devs, they don't like them for some reason).

I've seen terrible package ecosystems elsewhere, I've seen smug preening weenies proclaiming that Their Language is the One True Language plenty of times before, I've even seen trannies being generally insufferable in plenty of other places. But this absurdly entitled attitude while simultaneously trying to push it into everything... is this what it was like to be into FLOSS at the height of the systemd debacle?
 
snotang said:
every dynamic language (other than Forth) ever
Click to expand...
some dynamic languages (scheme, common lisp) allow you to turn safety all the way down to 0 where you can do things like vector-set! off the end of a vector and fuck your shit up hard
most people do not use it for reasons that should be pretty obvious
snotang said:
guix can't even have a default display manager, they have to set up fallbacks in case of rustardism.
Click to expand...
at least they have started to support aarch64 and not just x86_64
it's massively fucked what's going on with these shitty nulangs, but eventually the gnu foot cheese warriors will sort everything out and you'll be able to use a rust compiler developed entirely by people who hate the way rustlets do everything, without even having to see cargo on your system
that's how c became a really good language btw: it was reimplemented several times by people with wildly different cultures and the shitty practices basically died out
snotang said:
I'm so sick of shitlang designers trying to offload their technical debt onto the ecosystem at large. Zig decides to drop support for bootstrapping, says "teehee I'm sure someone will come along and make their own bootstrapping implementation just like mrustc tries to cope with the shit sandwich Rust served everyone, don't worry guys". Gee, I wonder who has by far the most domain knowledge necessary for that kind of thing? Could it be you? You do realize that domain knowledge is 90% of the actual work, right? You could easily accomplish this yourself in 10% of the time it would take anyone else.
Click to expand...
they should also try not making ungodly complicated languages and instead making languages that are nice and simple
if the core of your language is more than about twice as complicated as c, you really fucked up bad
snotang said:
I've seen terrible package ecosystems elsewhere, I've seen smug preening weenies proclaiming that Their Language is the One True Language plenty of times before
Click to expand...
guix is the One True Terrible Package Ecosystem and guile is its One True Language obviously :smug:
 
Panzerfrau said:
Oh my fucking god it gets funnier. He got promoted to the "senior" "engineer" and announced his retarded plans to fuck up APT literally at the same day:

View attachment 8114352

Some people are not having it tho



(Someone pls archive, I'm phonefagging)
Click to expand...
Is "pull request: make project depend on rust for no reason at all" the new "pull request: add gay code of conduct"?
 
You must log in or register to reply here.
Back
Top Bottom