<FromGitter>
<j8r> Whitelisting might maybe be offending , but I never understood how master or slave is. The computers are our slaves, and that's great x)
<FromGitter>
<j8r> whitelisting and blacklisting are offending, ok. Is greylisting offending too?
<raz>
just stop thinking about it and be offended already!
<FromGitter>
<j8r> That's right, be offended, then eventually think after :)
<FromGitter>
<ImAHopelessDev_gitlab> I use the master terminology for my game server architecture. Master Server, then the instance servers (game servers). For the database, I've come across master and slave words, but it's slave to the master (the database, not a human being)
<FromGitter>
<ImAHopelessDev_gitlab> In that PR, `whitelisting` is still a far more concise word. `Filtering` is ambiguous, because what are you filtering? Is it good? Bad? What kind of filtering?
<FromGitter>
<ImAHopelessDev_gitlab> `whitelisting` is concise, because it's literally the accepted ips (good ones)
<FromGitter>
<wontruefree> I would have left it the way it was
<FromGitter>
<ImAHopelessDev_gitlab> since I've got a job IRL, I'm not going to spend too much time on that thread. i'm pretty time-starved so I need to focus. I do believe crystal is still in good hands however, just please don't go too overboard with this is all i ask
<FromGitter>
<wontruefree> agreed
<FromGitter>
<j8r> nice @ImAHopelessDev_gitlab, what is it about?
<FromGitter>
<j8r> nice @ImAHopelessDev_gitlab, what is it about?
<FromGitter>
<ImAHopelessDev_gitlab> what is, my job? lol
<FromGitter>
<asterite> this was just one word in one PR. That's all it took to make the project a bit more inclusive. And if that didn't have any effect or benefit, well, it doesn't matter because it was so simple to change.
<FromGitter>
<asterite> it's interesting to see how that PR got so much reaction for something that really doesn't affect anyone in a bad way, but might affect some in a positive way
<raz>
i'd argue it already affected everyone in a bad way by taking time out of your day and by encouraging similar distractions in the future. but i think you handled it in the best way for the time being (a time in which even a polite "nope" could've raised twitter-hell).
<raz>
i think it got so much reaction because many people (at least myself) don't like this trend at all.
<FromGitter>
<j8r> Yeah agree, anyone can be offended for lots of things. Rubyist because Crystal does borrow everything, purists because there are aliases etc. Soon, every place where red is used for danger/bad things, rednecks will complain haha :)
<FromGitter>
<j8r> *does not borrow from Rubt I meant
Flipez has quit [Ping timeout: 256 seconds]
Flipez has joined #crystal-lang
Vexatos has quit [Quit: ZNC Quit]
Vexatos has joined #crystal-lang
sorcus has quit [Ping timeout: 272 seconds]
sorcus has joined #crystal-lang
alexherbo2 has joined #crystal-lang
<FromGitter>
<wontruefree> I didnt a reaction to the PR but now that I see the linked forum post I am going to have to go back and read it
alexherbo2 has quit [Ping timeout: 240 seconds]
<yxhuvud>
I think the new terminology is generally slightly clearer, but the difference is miniscule enough that I don't really care. *shrug*
<FromGitter>
<Blacksmoke16> Similar functionality will be coming to Athena as well for use on your actions, as well as a blog post showing how it can be used within your own project to support similar constructs
<FromGitter>
<Blacksmoke16> in a compile time type safe manor*
<FromGitter>
<Blacksmoke16> manner*
<raz>
looks useful. but can't wrap my head around when/how i would use it :D
<raz>
can it serialize any arbitrary object?
<raz>
or... maybe a question that makes more sense. what advantage does it give me over JSON::Serializable?
<FromGitter>
<Blacksmoke16> main example i always use is imagine a like `IgnoreOnCreate` and `IgnoreOnUpdate` annotation that you can use to not deserialize a property on `POST` and/or `PUT`, but allow it on `GET`
<FromGitter>
<Blacksmoke16> mainly just more flexible with some new unique features
<FromGitter>
<Blacksmoke16> like virtual properties, the exclusion strategies, and the constructors
<raz>
yea it looks like powerful stuff. i just still struggle to wrap my head around all those abstractions. DeserializationNavigatorInterface, PropertyMetadataBase, ObjectConstructorInterface
<raz>
each of your samples is so packed with them that i feel like i have to know athena before i can start learning athena :D
<FromGitter>
<Blacksmoke16> most of them you dont really need to worry about, probably could nodoc some of them...
<FromGitter>
<Blacksmoke16> as the navigators and visitors are kinda just an implementation detail
<raz>
yea well if i see them in the examples then i assume i should at least have an idea of what they do ;)
<raz>
(in order to make use of that stuff)
<FromGitter>
<Blacksmoke16> where do those first 2 show up in the docs?
<raz>
oh not there, was on your forum link
<FromGitter>
<Blacksmoke16> ahh right, thats prob why i didnt nodoc them
<FromGitter>
<Blacksmoke16> `PropertyMetadata` is a struct which contains metadata about a property :P
<FromGitter>
<Blacksmoke16> i.e. imagine we had reflection and you could get that data about an ivar
<FromGitter>
<Blacksmoke16> likes its name/type/annotations at runtime
<raz>
yup, i dunno if you can hide some of that from the user-facing code. it would def help approachability ;)
<FromGitter>
<Blacksmoke16> its kinda tricky, as you wont need it if you never need to create an exclusion strategy, but if you do then you need to know what methods you can all on the metadata obj
<raz>
then again, this serializer is prob something one would normally only reach after having learned the surrounding basics already
<FromGitter>
<Blacksmoke16> prob yea, its not something the average project would need id imagine
<raz>
yea
<FromGitter>
<Blacksmoke16> `*::Serializable` stuff has been getting better lately as well
jesfre has joined #crystal-lang
<oprypin>
i'm having a blast with {{read_file}} and makefiles
<oprypin>
embedding a shader's source code through ECR feels amazing as well