I don't think introducing the BEAM is the hard part, I think it's all about the language barrier.
577 karma · joined September 11, 2018
I don't think introducing the BEAM is the hard part, I think it's all about the language barrier.
But, obviously, like 99% of people, the parent poster lacks the willpower to do that. wink wink
My team and I are kind of trying to break this up, since we suffer from this a lot.
So I moved towards descriptive variable and function names, but those could lie as well.
So I'm thinking, how could we ensure truthful intentions at all?
And I think only a combination of small pull requests, good variable and function names and a thorough review can save us here.
But I don't know, I'm just a junior developer.
The author presents valid and sensible issues with the state of theming on the GNOME platform. And the overarching topic is essentially User Experience.
Even the slightest change in color can introduce friction between UI elements. Or to be more extreme, if a theme turns your entire app into a white blurry mess, you would get mad at the application, and not the theme. Although many of the same design principles are used in the making of either a chair or a graphical user interface, they are definitely not the same in any regard.
On the topic of icons: just like language, they evolve over time. On top of that, icons can have different meaning depending on your background. Icons can be combined to form a composite icon, and now imagine one of those icons is not displayed as you intended it to be. The entire meaning can change because the design intentions are lost.
On the topic of branding: it's not about your desktop being a billboard. It's about being able to recognize the brand across different operating systems, and it's also - more or less - the only thing about the product that is not designed for the purpose of user experience (but in a sense, they still are). And let's be honest: most apps we use in our day to day life have very tame brands and adhere to certain standards. That is because the apps we use are usually good, and we throw the bad, obnoxious ones away really quickly.
All in all, the author presents valid concerns, especially if you don't project them on how you prefer your UI, but rather, how potential Linux / GNOME users could have additional difficulties because of theming issues.
Discords architecture is one where an entire guild stays on one machine. And the sorted set is part of a guild as well.
So, there is no need to persist it, since it is ephemeral in nature.
Edit: perhaps to expand on this a bit more, keep in mind that discord is not a cloud native application. They have a few strong server nodes and a Cassandra cluster (at this point I am curious if they switched to scylladb) that handle all or at least most of their client facing features.
Since they do not need to scale services, the servers they have are stateful. Hence, if the guild server crashes, so will the data structure, since the data structure is of no use if the server crashes and would need to be rebuilt from scratch either way.
(Disclaimer: I am not an insider, just an Elixir fanboy)
Also, imagine blind people coding. I imagine they have a completely different stance on how code should be formatted.
I write some garbage-formatted code, press ctrl-s, and the code is formatted automatically.
Even on a single-dev project, I would take a config and just put it there for the convenience it provides me.
If I ever were to code python again, I would probably also use black.
(To anyone who's wondered as well)
Shame on me.
Our frontend client basically reads any stream it needs. And the main problem is, if you have to handle 40+ streams (and that is not even 30% of what's to come), it gets more and more difficult to provide a good user experience.
Thankfully, after much discussion we agreed to do it better... Soon ish.
At least that's what's holding me back.
I would not accept shit from people just because they have some authority in some place.
At least not in the sense that someone would "naturally" rather grab things with their hands rather than their feet.
This is why to me neither ctrl-f nor PgDn are natural, and anyone can choose one or the other. Ultimately they were both created by someone who saw the need to have a shortcut to move one entire page down.
Listening to this along with the clicking sounds of my coworker's keyboards makes me feel like I am in a rainy forest.
So, in my head, millions feels closer to billions than billions does. It's weird.
But at least I would not constantly call out the people I sold it to, as if my words had any meaning at that point.
Also, it's frustrating to me, to see how it's seemingly impossible to care about the users AND have enough users bringing in revenue at the same time so that you are never in a position where big companies try to blackmail you with sweetsane amounts of money into giving them access to data.
Edit: After reading the responses, I must correct myself. The turmoil within the human soul is much more nuanced, rendering "stop flame, whin0r" an inadequate response. The only thing I know is that I'd probably have done the same, as I reckon most would have.
I just feel like I've been lied to in University. Java was presented as the silver bullet in University. "It runs anywhere and models the real world". "In Java, you can't compare apples and oranges!". Turns out you can, if someone implements an AppleOrangeComparator. Great.
I'm just venting at this point, don't mind me.