Russia will not take any single oblast.
In fact, it has retreated from two oblasts in the past 6 months.
And now retreating from part of Belgorod.
Good luck contradicting reality, bro.
Yep, with closed-source financial applications such issues are a common thing, just on a smaller scale so they do not meet the news.
Many of contemporary financials are also still being worked on the mainframes, utilizing the technology stack of 80s, and there are many differences between vendor implementations in the space.
While there are many argues about usability of crypto for payments today, crypto standards do exist in form of RFCs that are open source, produced by community, and are enforced world wide by application developers.
Very progressive step forward IMO as compared to software side of traditional finance today.
Sorry but this is such a bad take. Many of the bigger banks and financial institutions have very mature and well architected tech stacks, as do many newer fintechs. They have the funding to hire some of the best engineers, and they do. Being open has advantages, yes, but it's not inherently better.
There have been plenty of bugs and vulnerabilities in blockchain technologies over the years.
The mature and well architected tech stacks in traditional finance come from the economy of the scale, from where also comes funding as you metioned. Crypto currently has the blockspace problem which prevents from scalability. So, while there are some well performing companies in crypto (dozens of them), there are much more companies in traditional finance, just because of scale.
The problem of blockspace have been solved in smaller networks with use of sharding, and will be rolled out to bigger networks in form of upgrades. If the world does not see regulation uproar banning crypto everywhere in coming years, crypto will endure true economies of scale. Think every PoS app, every B2B payment gateway, every web application in the wild accepting both Visa and crypto based payments, with crypto fee -- and price -- being less. I don't see how traditional finance can withstand this challenge. IMO this is also like BBS forums vs. Web technologies in 90s. I say it as someone who worked on parsing and producing Mastercard related file formats, and also worked on enterprise crypto applications. While I agree right now the crypto is laughable from many aspects, so it was the web in it's early years.
Yes, crypto is definitely not the solution to this. This was a transient problem, that was resolved within the week. Everyone got paid back. An issue with the EVM overcharging people is irreversible. Those funds would be lost for good. At least with trad-fi, you can click a few buttons and revert payments.
> Certain digital assets, including BTC, ETH, LTC, and at least two fiat-backed stablecoins,
tether (“USDT”) and the Binance USD (“BUSD”), as well as other virtual currencies as alleged
herein, are “commodities,” as defined under Section 1a(9) of the Act, 7 U.S.C. § 1a(9).
This is interesting, it appears ETH was named a commodity in some US federal legal document. Interesting to see how this will play out in court. Should this override SEC statements about ETH being a security ?
IMO this is more a case of who you ask and what their current goal is.
CFTC regulates commodities, so of course they will say things they want to regulate are commodities. OTOH SEC regulates securities, so they will say things are securities.
See also the way any kind of fraud can become "securities fraud" if you have investors. Basically, if your business involves defrauding customers, that is likely going to negatively impact stock price when it comes out, and if you lied and told shareholders you were not defrauding customers, you are also defrauding shareholders thus securities fraud thus SEC jurisdiction.
Ukraine banned yandex in 2017 for mass data harvesting of Ukrainians, probably that's the main reason why gp did not find it in Ukrainian Bing. It's still possible and perfectly legal to access yandex or other data harvesting engines/disinfo websites over VPN or Tor, so the ban main objective is to protect non-tech-savvy users from the interference of hostile foreign criminals.
Not sure why the downvotes, as, yes, Yandex along with several other russian internet service companies is blocked in Ukraine and it is almost certainly why it is not being set as default, because doing so would straight up break search altogether.
Arkady Volozh is only one of co-founders of Yandex, one who survived.
It is interesting that another co-founder, Ilya Segalovich, was not only
involved in development of Yandex, but was also taking part in public activity,
such as combating electoral fraud, supporting children adoption laws reform,
attending opposition rallies. He passed away in July 2013.
I had participated in migrating around 100 fairly complicated pipelines from Airflow to Dagster over six months in 2021. We used k8s launcher, so this feedback does not apply to other launchers e.g. Celery.
Key takeaways roughly those:
- Dagster's integration with k8s really shines as compared to Airflow, it is also based on extendable Python code so it is easy to add custom features to the k8s launcher if needed.
- It is super easy to scale UI/server component horizontally, and since DAGs were running as pods in k8s, there was no problem scaling those as well. For scheduling component it is more complicated, e.g. builtin scheduling primitives like sensors are not easily integrated with state-of-art message queue systems. We ended up writing custom scheduling component that was reading messages from Kafka and creating DAG runs via networked API. It was like 500 lines of Python including tests, and worked rock-solid.
- networked API is GraphQL while Airflow is REST, both are really straightforward, however in Dagster it felt better designed, maybe due to tighter governance of Dagster's authors over the design.
- DAG definition Python API, e.g. solid/pipeline, or op/graph in a newer Dagster API, is somewhat complicated as compared to Airflow's operators, however it is easy to build custom DSL on top of that. One would need custom DSL for complicated logic in Airflow as well, and in case of Dagster it felt easier to generate its primitives, than doing never ending operators combinations in case of Airflow.
- Unit and integration testing are much easier in Dagster, the authors put testing as a first-class citizen, so mocks are supported everywhere, and the code tested with local runner is guaranteed to execute in the same way on k8s launcher. We never had any problems with test environment drift.
The biggest caveat was full change of internal APIs in 0.13, which forced the team to execute a fairly complicated refactor, due to deprecation of the features we were depending on e.g. execution modes. Had we spent more time on Elementl slack, it would be easier to put less dependencies on those features ^__^
I don't agree with the posting. In my opinion, UML had rebirth in 2010s with the growth of popularity of PlantUML. See that PlantUML is referenced already in this thread, and to positive sentiments already expressed, I can add the notion that PlantUML fits much better, than most of earlier UML related software, for the purpose of network modelling. While original UML standard was not specifically designed for representing networks, PlantUML has network diagram type built-in. And extensibility of PlantUML allows to cover many use-cases beyond that. I imagine that with a certain amount of tenacity applied, it would be possible to create PlantUML library for "masala diagrams" as well.
Also, "agile" shops usually love that tool, since it requires minimal learning curve for any person on a team to start producing nice-looking diagrams.
In Europe, there are not much cities that were designed for automobiles. Most down town designs predate automobiles by several centuries. That is why traffic congestion, and related externalities, are very significant problem for Europe, much more than for US. During several last years, there had emerged a movement when large cities introduce anti-car rules, effectively banning traffic in the most affected areas.
