Brand New in Beta --
Build scalable, resilient, and efficient network-intensive applications with Erlang and Elixir — the perfect fit. The BEAM’s actor model perfectly mirrors the way nodes operate in a network.
https://t.co/e4kP8a2JE3
@whatyouhide#myelixirstatus#Beam #elixirlang #elixir #erlang #YourElixirSource
I always learn something new by reading the commits from my team at @dashbit / @livebookdev .
Use:
$ mix xref graph --format stats --label compile-connected
... to discover improvement opportunities to reduce compilation cycles.
https://t.co/afGPJFg7VW
#MyElixirStatus
💡 @lawik, Founder of Underjord is joining us at Code BEAM Europe 2024 to present his talk 'The Nerves Community Fleet' that's packed full of expect practical demos which will (hopefully) blow the lid off of what you thought Nerves can do for you. 💥
➡️ https://t.co/VWJj6lLRVA
🚀 Exciting news for all functional programming enthusiasts! Join us for our third meetup of the year on September 12th. Whether you’re a seasoned pro or just curious about functional programming, this event is for you!
With an incredible trio of speakers, make sure you don't miss out and secure your seat, today: https://t.co/Ys91qRMh8g
📅 Date: 12 September
🕕 Time: 6 pm
📍 Location: Erlang Solutions office - Karmelicka 7/ Kraków
#elixir #erlang #meetup #myelixirstatus #functionalprogramming
When you build open-source the opportunity for awesome collaboration between companies it's just there
Awesome work from @samwillis from @ElectricSQL and @ggrdson from @supabase
If you support me or any other artist/creator via @Apple’s @Patreon iOS app - be sure to switch to the web for payments.
From November Apple will be pocketing 30% of all creator income paid via iOS.
This is terrible news for those surviving on small donations.
Shame on Apple.
Hey! Hey you!
Do you work on an @elixirphoenix app?
Submit it to BuiltWithPhoenix.com to help people convince their bosses that Real, Important Companies are using this stuff. 😄
#MyElixirStatus
🙌Welcome to another #GettingToKnowUs edition!
🎙This time we got to meet @adolfont the creator and co-host of the @elixiremfoco, and one of the chairs of the Education, Training, & Adoption Working Group of the Foundation.
✨Check out a sneak peek of the interview!
📱Read the interview: https://t.co/Get2kts87x
🎥Full interview on our channel: https://t.co/5JQ54Ds4vL
#WeBeamTogether #Erlang #MyElixirStatus
SQL books won’t teach you this.
Natural Keys vs. Autoincrement IDs vs. Public IDs. (or maybe all together)
Natural Keys
Natural keys carry intrinsic meaning because they are part of the domain.
They are directly related to the data, making them intuitive and easy to understand. Examples include email addresses or employee IDs.
The problem is that they are usually not good for performance, but they can also be a security risk if you expose them.
Autoincrement IDs
Autoincrement IDs automatically generate unique integers to identify rows within a table.
They are often used as primary keys.
Simple integers are fast for the database to index and query. They provide optimal performance.
However, they are vulnerable to enumeration attacks since predicting the next or previous record is easy.
Public IDs (UUIDs)
UUIDs (Universally Unique Identifiers) are 128-bit identifiers used to uniquely identify information without relying on a centralized authority.
They are difficult to guess, making them suitable for public exposure in APIs.
The problem is they are larger and more complex than integers. This can impact performance, particularly in indexing and storage.
Finding the Sweet Spot: A Mixed Approach
Combining different types of keys can offer a balanced solution:
• InternalID: Used for internal operations and relationships between tables.
• PublicID: Used in API responses and endpoints to securely reference user records.
• Email (Natural Key): Used to ensure unique identification of users within the business logic.
The mixed approach keeps your system fast, secure, and easy to understand.
Thoughts?
Ok I know it's bragging but I have to 😆 It's so great to hear from @josevalim itself.
If you're interested what this is about, then you can look here https://t.co/659THWRk36
Why GDPR-compliant analytics is better than Google Analytics:
1. JS weighs 100 times less.
2. Not blocked by browsers, so you have complete data.
3. You don’t need a GDPR popup
4. You have uniform data across all users, not just those who clicked "Yes" in the GDPR popup
Elixir community, i need some help for https://t.co/OxOEm5x0vd please!
What tech are people using with Phoenix!
Reply like so:
```
name: "Nerves",
url: "https://t.co/7IQS0RQNyx"
logo_url: "https://t.co/RNZahphFUN"
```
#MyElixirStatus@elixirlang@elixirphoenix
@th3mus1cman I have been through too many economic crashes in my country and people that have their home paid always navigate these hard times easily, without struggling to have money after paying the bills.
So, I would pay the Mortgage without blinking.
When making Flint, my schema validation library built on Ecto, one of the primary use cases I had in mind was @thmsmlr's Instructor library.
I've used it a ton, but the boilerplate needed with even simple validations would become tedious. So this is my solution
#MyElixirStatus
📢 Do you know that the BEAM is known to scale well in performance and design❓
🛠The BEAM is the Erlang VM created in the 80s by Ericsson to automate telecom switches. Used now by Elixir and Gleam programming languages
#BEAMDYK#Programming#Developers#MyElixirStatus#Erlang
🚀DYK 8 - Scalability - A Tour of the BEAM (Elixir, Gleam, Erlang) on Fault-Tolerance, Concurrency, Parallelism, Distribution and Scalability
Do you know that the BEAM is known to scale well in performance and design?
🧵 1/13
#MyElixirStatus#BEAMDYK#Elixir#Erlang#GelamLang