Sunday morning. Dayton, Tennessee. This was the town in which the famous Scopes trial (Darrow vs. Bryan) was held
#Dayton #Tennessee #Scopes #Darrow #Bryan #Gothic #undefined #photography #DorotheaLange
Sunday morning. Dayton, Tennessee. This was the town in which the famous Scopes trial (Darrow vs. Bryan) was held
#Dayton #Tennessee #Scopes #Darrow #Bryan #Gothic #undefined #photography #DorotheaLange
Встречаем yx_scope: DI-фреймворк для работы со скоупами в открытом доступе
Для больших проектов не всегда хватает одного модуля: иногда надо пошарить какие‑нибудь классы или UI‑элементы. Так со временем проект дробится на много мелких модулей, которые так или иначе связаны разного рода зависимостями. И если за этим не следить, то рано или поздно структура проекта может стать запутанной. Наша команда разрабатывает приложение Яндекс Про, которым пользуются водители и курьеры. Из‑за многомодульности разные команды использовали разные подходы к связыванию зависимостей — в основном это getIt , injectable и riverpod . Но у всех решений были свои недостатки. К тому же то, что в одном проекте используется несколько подходов, сильно усложняло взаимодействие команд. Сложности подтолкнули нас к поиску собственного решения, которое удовлетворяло бы всем нашим требованиям. И теперь мы готовы поделиться им с комьюнити: наше решение — это группа библиотек yx_scope . Расскажу, зачем нужны скоупы и как они работают, в чём преимущества нашего фреймворка и как его использовать.
📅 Melden Sie sich jetzt noch an!
➡️ „Treibhausgas-Bilanzierung entlang der Lieferkette (Scope 3)."
#Workshop in #Berlin am 11.06.2024.
➡️ Anmeldung, Agenda und weitere Informationen: https://allianz-entwicklung-klima.de/termine/praesenz-workshop-treibhausgas-bilanzierung-entlang-der-lieferkette-scope-3/
#einewelteinklima #treibhausgasbilanzierung #lieferkette #scope3 #scopes #wirteileneinziel
noticed on ubuntu 24.04 that libtinfo5 is no longer a package (you have to manually install a dpkg), but the LLVM 13 binary distro that we still use in scopes depends on it, so i took that as a sign that our dependency is rapidly getting very very old.
therefore, i finally ported our #scopes backend from LLVM 13 to LLVM 17, and even though they completely removed typed pointers, the port only ended up taking me 3 hours (but I felt *very* lost in the beginning).
the f"..." string formatting prefix in #scopes
none of these do produce any intermediate string objects. it's all streamed.
i wonder how far i can drive this. like, could we fit an entire ascii flex layouter in there? ;-)
thinking about a short hand for the `mutable` qualifier in #scopes. the shortest synonym of mutable is "fluid", and "~" is an associated iconographic character. which readily makes this operation available:
some nice operations that can be performed on the exp2-heap i'm working on. efficiently base any pointer, find its size, offset it safely. the pointers require no extra tags and can be passed to C as-is. (in fact, when overriding the system malloc, all C libraries will produce these pointers)
as an important bonus, there's an extra bitmap segment that runs parallel to the pool at ratio 1:64 which is used to mark memory locations that are themselves addresses.
added three new features to #scopes core:
1. the parser recognizes and expands prefixed symbolic literals
2. the `c` string literal prefix now also supports symbols
3. the `c` prefix expands multi-character sequences up to 8 bytes (in LE) for easier definition of RIFF codes
(i wrote this in our discord)
like rust, #scopes defines itself as a systems programming language, it just feels more entitled to unconstrained expression; systems programmers are far too ready to stunt their vocabulary and lock their jail cell from the inside, but then complain about feeling burned out later. i have been there in my 30s, and so i see that as flagrant disregard for one's needs. program performance is no altar at which to sacrifice your ability to concisely express your ideas.
alright. i built a simple toy serializer for #scopes that just uses the existing print module to dump serialized values to the console.
already it can do many of the standard types, and even handle shared references.
but i will have to write a default binary serializer/deserializer next to know if the interface makes sense.
rewrote the #scopes tokenizer in scopes as a collector. now it's possible to color-code scopes sources when streaming them from a file to the terminal.
wrote a small tokenizer with collectors in #scopes https://gist.github.com/paniq/ff7c84972a3fa9a862cc1ab12f92b035
i'm porting the TLSF allocator from C to #scopes. it's a pleasure, the code is very well written and documented.
@kim_harding What definitions are being used - territorial, production, consumption? Journalists need #CarbonLiteracy #EmissionsOwnership #Scopes
💭 Was sind eigentlich #Scopes? Und welche Rolle spielen sie bei der Berechnung der unternehmensbezogenen Treibhausgasemissionen?
Unternehmen emittieren Treibhausgase. Nicht alle Emissionen sind aber auf den ersten Blick erkennbar. Um unternehmensbezogene THG-Emissionen zu berechnen, werden diese in drei Geltungsbereiche (=Scopes) geordnet und berechnet.
➡️ Mehr zu Scope 1, 2 und 3: https://allianz-entwicklung-klima.de/toolbox/was-sind-scopes-geltungsbereiche-bei-der-berechnung-der-unternehmensbezogenen-treibhausgasemissionen/
🔎 Zum Scopes-Factsheet: https://allianz-entwicklung-klima.de/wp-content/uploads/2023/07/Factsheet_Scopes.pdf
I have a recent LLM guess the language of snippets written in #scopes, and it thinks it's a dialect of Rust. that's not too far away, actually.