The government is subsidizing kpop companies somewhat via funding for arts and entertainment (as essentially all governments in a position to invest in soft power do, of course).
I'm not aware of any military backing, though. Kpop stars occasionally perform at army concerts - South Korea is a country with mandatory service for all young men, so as you can imagine these are popular -, and while I assume these are paying gigs it's also infrequent enough that I doubt you can call it backing.
World cup 1958, Brazil National team coach explains a very convoluted and intricate tactical play for a goal in their match against Russia (then Soviet Union).
A very famous player - Garrincha, arguably one of the greatest players of early football/soccer - listened to his explanation and asked
"That's very cool and all, Mr. Feola. But have you checked with the Russians?"
(In English I think 'did the Russians agree' may sound more idiomatic)
It means that this is a decision Ukraine can't make all by themselves. It depends on what will happen to them as much as it depends on what they will decide.
It also doesn't fit very well, because it's more intended to be used about cartoonish plans that expect other people to behave exactly as the plan predicts. I dunno why the GP got to it.
This is an expression from the cold war, and roughly means "have you reached an agreement with your foe?" in a context that the foe is involved in the "solution" you're proposing. Something like that.
I love those RFC documents. I am currently working with CCSDS documents and they are total trash comparing to RFC. For example when I read documents about how TCP works or TLS works I see that it has been written by professionals with experience and vision. And CCSDS documents have been written by bureaucrats who have never written a line of code in their lives.
I am curious how the company behind Flox intends to make money, I hope they intend to make money on consulting or operate non-profit sponsored by some institutions.
Hey from Berlin! I'm Ron one of the founders at Flox and also board member of the NixOS Foundation. Just noticed folks are talking here and that's super exciting! We are all in the midst of the yearly NixCon so apologies if I'm slow to respond or my answers are a bit shorter. Definitely happy to dig deeper!
I saw your question and actually wanted to share the response I shared a few months ago, happy to unpack or talk about any of it as well.
This is from our original 1.0 announcement here (https://news.ycombinator.com/item?id=39692801) -> bringing forward what you saw today for free and open source, was a major part of why I started Flox, with much more to come into it. What we released today will be free forever (both the open source client and the FloxHub services for sharing environments). We plan on expanding the offering to include a more robust private software catalogs that layers on top of the OOTB Flox Catalog that ships with Flox. If you are interested in publishing your output or need revised versions of open source packages in Flox then it'll be very easy to have your own catalog to compliment the always-free Flox Catalog that Flox ships with today. Beyond that, we are focused on a number of services that help bring Nix's build to the enterprise. Over time we intend to sell a solution to enterprises - through subscriptions and services - so they can more effectively manage expansive and fragmented software supply chains. As part of developing custom tooling for enterprises, we think it's reasonable for them to participate in funding for that work.
From what I gather it's exactly this in reverse: they already were a consulting company providing development environment to teams as part of their package, and Flox is an internal tool they open-sourced. (interpreted from what I read on their about page: https://flox.dev/about/)
I have the same experience, I like splitting my embedded C microcontroller peripheral drivers into 3 layers:
- header files with registers addresses and bitmasks
- asynchronous layer that starts transactions or checks transaction state or register interrupt handler called when transaction changes states
- top, RTOS primitives powered, blocking layer which encapsulates synchronization problems and for example for UART offers super handy API like this:
status uart_init(int id, int baudrate)
status uart_write(int id, uint8_t* data, int data_len, int timeout_ms)
status uart_read(int id, uint8_t* buf, int buf_len, int timeout_ms, int timeout_char_ms)
Top, blocking API usually covers 95% use cases where business logic code just want to send and receive something and not reinvent the synchronization hell
reply