@veer66 @choe @densin ถ้าจะเอาเป็นจุดๆผมไม่ได้มองว่าง่ายกว่า แต่ถ้าจะทำอะไรแบบบูรณาการ เช่นมีปัญหา ต้อง debug / hot patch ด่วน ผมมองว่า Erlang เจ๋งครับ

git today: git ls-tree --full-tree -r --name-only HEAD

list all files in git directory in HEAD

stand อะไรใน JoJo ที่ทำงานแบบ async ได้

ตอบ: The World

Za Warudo "tokio" tomare

โคตร type signature วันนี้

Map<std::slice::Iter<'_, types::contract_event::ContractEvent>, std::result::Result<(std::string::String, std::string::String, std::string::String, u64), failure::Error>, [[email protected]/xxx/yyy.rs:53:9: 60:10]

1.1k toot already?
and I don't even come here weekly

fuck it's bigger than my entire OS


[email protected]:/ # pkg install rust
Updating local repository catalogue...
local repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 4 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
rust: 1.36.0_1
libssh2: 1.8.2,3
libgit2: 0.28.1
libedit: 3.1.20190324,1

Number of packages to be installed: 4

The process will require 696 MiB more space.

Are you telling me that Rust apps won’t even work with stable releases of the language? How is this acceptable?

error[E0554]: #![feature] may not be used on the stable release channel --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pear_codegen-0.1.2/src/lib.rs:1:1 | 1 | #![feature(crate_visibility_modifier)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error[E0554]: #![feature] may not be used on the stable release channel --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pear_codegen-0.1.2/src/lib.rs:2:1 | 2 | #![feature(proc_macro_diagnostic, proc_macro_span)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0554`. The following warnings were emitted during compilation: warning: Pear was unable to check rustc compatibility. warning: Build may fail due to incompatible rustc version.

oh wait I know how it's acceptable: NOBODY COMPILES RUST APPS, THEY DEPLOY WITH DOCKER

That's why nobody complains about this stuff. Building and packaging it is someone else's problem. Doesn't matter if it takes 128GB of RAM and 2 years of wall time, it's someone else's problem. You put on your DevOps shades and smash that docker deploy button and move on with your life ignoring that you have no idea how this software even works or if anyone will ever be able to build a new version

“Heh, well we solved the memory safety problems but you’ll never know which version of of the mime type library is actually in the fast path if there’s every a vulnerability”

Compiling mime_guess v2.0.0-alpha.6 Compiling mime_guess v1.8.7

“Base64 is so complicated we have made dozens of crates for it. Of course they’re not ABI compatible, so we need both.”

Compiling base64 v0.10.1 Compiling base64 v0.9.3

Why are there duplicate dependencies of different versions being compiled? How does that even work? Does Rust not have symbol collisions?

```
Compiling parking_lot_core v0.4.0
Compiling parking_lot_core v0.6.2
Compiling parking_lot v0.9.0
Compiling parking_lot_core v0.5.0
Compiling parking_lot v0.8.0
Compiling hyper v0.12.33
Compiling aho-corasick v0.7.4
Compiling buf_redux v0.8.2
Compiling twoway v0.1.8
Compiling generic-array v0.7.3
Compiling generic-array v0.12.3
Compiling url v1.7.2
Compiling url v2.0.0
Compiling mime v0.2.6
```

In case you’re wondering here’s the entire list of dependencies sorted so you can see the duplicates

https://pastebin.com/ZX9VNaB2

Now I’d like someone to explain why there’s openssl and rustls and nativetls and hyper-tls all in the same app toolchain. Is the community drunk? Can nobody decide on a canonical TLS library for this fancy new language? How many CVEs are lurking in this cesspool?

Compiling rand v0.4.6 Compiling rand v0.6.5 Compiling rand v0.7.0 Compiling rand_chacha v0.1.1 Compiling rand_chacha v0.2.1 Compiling rand_core v0.3.1 Compiling rand_core v0.4.0 Compiling rand_core v0.5.0

This is scary. Is something linking to an older random implementation that’s not so random?

Compiling sha-1 v0.3.4 Compiling sha-1 v0.8.1

Seems to be taking rust folks a while to figure out how to make a stable sha-1 implementation

holy shit. I did it. It actually works.

I have spun up a Pleroma instance on... my fucking Nintendo Switch. I don't think the Switch was ever intended to be a **webserver**, but hey, it's 2019 and there are lightbulbs with CPUs built into them soooo

It can be accessed at cursed.frinkel.tech. don't sign up if you want a reliable instance, since it'll probably be down 90% of the time, since I'd actually like to use my switch to do what it was intended to do and play games. :P
My Nintendo Switch displaying a…

(I joke, but it really annoys me how #Rust is still known as a blockchain language. We need some killer feature that spreads Rust farther.)

วันนี้เงียบๆ แหะ

เมื่อคืนนอนไม่หลับเลย เพราะตื่นมาตั้งทุ่มนึง เวลานอนเพี้ยนหมดละ

almost always come here - Fediverse, when I come to office early😅

Show more
Mastodon

mstdn.io is one of the instance in the fediverse. We're an open-minded generalistic instance. Learn more here!