@Edent My response is always. Okay, let me call you back and we can start this process. A scammer will insist they handle it for you. A bank may say they can handle it but will usually let you hang up and call back. Fraud departments don’t make commissions so there’s no reason for them to hold you on the line.
-This is so cool and helpful!
-I’m learning so quickly!
-I can share my progress with friends! 🥰
-I’m so obsessed with my streak haha!
-I want to punt this stupid owl into the centre of the sun
@girlonthenet@der_schrank I do well with gamification I found that pairing it with WaniKani (while there is some overlap) seems to be a comfortable balance between kanji and grammar. I’m only on section 2 lesson 14 right now though and level 4 in WaniKani 😅
@octorine@girlonthenet I got to Diamond League last week and came in last. Second to last was higher than any 1st place I’d encountered before that point. 1st place had over 20k xp 😅
@girlonthenet@der_schrank It is paid, but if you like it and have iPhone I recommend the free Tsurukame app. It hooks to the wanikani API and gives you a lot more information, dark mode, and just a better experience overall.
I'd like to find more YouTube channels about software development / engineering / etc but it's like 98% of the same white guy, screaming like a twitch streamer, making almost every video about "this is X killer" "why you should NEVER do that" or "your IDE is shit use X instead". Of course they talk like they are the thing and it's the only truth.
@alyx Code to the Moon, Code Aesthetic, Dreams of Code, ArjanCodes, Low Level Learning, Backend Banter, mCoding, Chris Biscardi, Jeremy Chone, Jon Gjengset, No Boilerplate, HyperNeutrino, and Logan Smith are a few of the ones I subscribe too. (Left the 5-6 “hype” devs I watch out of the list for you.)
I find it’s better to subscribe to a LOT of slow release channels. I get a consistent feed of good quality that way. 🙂
I looked at the #rust based, #Cosmic#desktop#environment, by #System76. This is branded "alpha" right now, but I'm flabbergasted by the users online, who think that "by summer" that thing will be ready for general use.
News flash, it won't.
It generally takes 2-3 years minimum after the official release for a brand new DE (with a brand new #API & libs) to become truly useful to most people. DEs aren't adopted unless matured. Hamper your expectations, lads.
The memory safety is really just circumstantial to most people that write Rust. The actual community hype revolves around just how easy it is to write scalable, maintainable, and performant software when compared to things like C.
It’s the main reason so many things are (so quickly) rewritten in Rust. The language makes it easy once you learn it.
What’s extra confusing about the #rustlang module system is the mod keyword doubles for creating and importing modules. So in one context it wraps stuff, and in another it's linking stuff.
Oh, and don't forget there are special file names and folders that do things without any use of stuff.
i hope #zig will be sustainable. i like its way more than #rust. and like in C or even RISC-V microarchitecture, but not so much in Rust and C++, the language definition is compact enough so that it just stick into your head. also, comptime is really cool invention in my opinion. #C#rustlang#riscv
@jarkko I feel like comptime is one of those things that’s convenient at first. But, then you build a function that’s restricted solely by compiler checks and doesn’t have a “proper” interface.
If anyone tries to develop on comptime you either have to document the requirements, let the users figure it out by compiler errors, or wrap it in interface functions. Plus any change can break code down the line.
It seems cool at first but, I like it less the more I look at it.
@jarkko Yeah it definitely has a lot of neat things (Super great for systems level stuff). I personally feel the ergonomics fall apart a bit in the module level scope of things. The FFI (especially with C) is definitely fantastic though.
I don’t have much direct experience with Zig except for friends that share their hype with me. So I can’t speak for it directly. Rust does provide a surprising amount of “experimental” and “nightly” features for memory though too.
ok look I know this is really stupid and pedantic, but come on, we’ve had 26 years to learn this
It's Wi-Fi
not Wifi or WiFi or wifi or wi fi
Wi-Fi. Hyphenated. Both words capitalized.
thank you for coming to my ted talk
(while you're here, “log in" is two words when being used as a verb… your login button or link should not say "login”, because the action they take is to "log in”)
@fil You can implement FromIterator<StartType> for Vec<EndType>
And then you can call:
x.into_iter().collect::<Vec<y>>()
Or
type Y = Vec<EndType>
.collect::<Y>()
The implementation in FromIterator will basically include that mapping but this can be quicker / more convenient if your calling it multiple places / exposing it to an end user.
Another cool tip.
Vec<Result<T,>> can be collected into Result<Vec<T,>>
Useful for collecting handles sometimes.
if you were sorting a parameter by ascending numeric value (in some sort of parameteric search engine) and the values included positive, negative, and ± values all together, where would you want the ± ones to be placed?
context is electronics stuff, where you're searching for a part that fits your required specs.
