Feels like an article wrote from somebody who knows a lot about the FFT for people who already knows a lot about the FFT.
All mathematic exposition feels that way.
Readit Newsdkjaudyeqooe commented on Discrete Fourier Transform nima101.github.io/dft... · Posted by u/pykello
Somewhat off topic rant, but am I the only one who find mathematical notation unnecessarily obtuse?
The bit that gets me is defining degree as n-1. For someone without a mathematical background, it takes a bit of pondering to figure out that you have to define n as one more than the actual degree, the opposite of what seems natrual. My mind at least just wants to think about n as the degree, and use n+1 as the last index. To me it seems aggressively unintuitive.
I guess you want to align the coefficient numbers but would it be a sin to define another index c = n-1 for that purpose?
But I'm a mathematical lightweight and maybe mathematical thinking is all about this. Perhaps some greater talent can correct my thinking.
So much negativity.
I’m just excited that our industry is lead by optimists and our culture enables our corporations to invest huge sums into taking us forward technologically.
Meta could have just done a stock buyback but instead they made a computer that can talk, see, solve problems and paint virtual things into the real world in front of your eyes!
I commend them on attempting a live demo.
All you're doing here is associating your hopes and dreams with grifters and charlatans.
They should be mocked and called out, it might leave room for actual innovators who aren't glossy incompetents and bullshitters.
Deleted Comment
dkjaudyeqooe commented on Hacking Coroutines into C wiomoc.de/misc/posts/hack... · Posted by u/jmillikin
My favorite trick in C is a light-weight Protothreads implemented in-place without dependencies. Looks something like this for a hypothetical blinky coroutine:
typedef struct blinky_state {
size_t pc;
uint64_t timer;
... variables that need to live across YIELDs ...
} blinky_state_t;
blinky_state_t blinky_state;
#define YIELD() s->pc = __LINE__; return; case __LINE__:;
void blinky(void) {
blinky_state_t *s = &blinky_state;
uint64_t now = get_ticks();
switch(s->pc) {
while(true) {
turn_on_LED();
s->timer = now;
while( now - s->timer < 1000 ) { YIELD(); }
turn_off_LED();
s->timer = now;
while( now - s->timer < 1000 ) { YIELD(); }
}
}
}
#undef YIELD
Your company is probably using hardware containing code I've written like this.
What's especially nice that I miss in other languages with async/await is ability to mix declarative and procedural code. Code you write before the switch(s->pc) statement gets run on every call to the function. Can put code you want to be declarative, like updating "now" in the code above, or if I have streaming code it's a great place to copy data.
A cleaner, faster way to implement this sort of thing is to use the "labels as values" extension if using GCC or Clang []. It avoids the switch statement and associated comparisons. Particularly useful if you're yielding inside nested loops (which IMHO is one of the most useful applications of coroutines) or switch statements.
dkjaudyeqooe commented on Bulgaria to join euro area on 1 January 2026 ecb.europa.eu//press/pr/d... · Posted by u/toomuchtodo
Also the experience of Greece not too far back and the austerity imposed by Germany is not quite forgotten. Varoufakis[1] can attest to its severity. The Greeks voted against it but Germany imposed its will.
[1]https://jacobin.com/2025/07/yanis-varoufakis-on-the-legacy-o...
This is nonsense. Not mentioned is that Greece has borrowed excessively and had defaulted on its loans. A bailout was organized by the EU and IMF with terms that Greece had every opportunity to reject. No one forced anything on Greece. The referendum was not binding and political theater for the government of the time.
That Greece accepted the terms reflected the reality that the alternative was much worse and would have caused great suffering for Greeks.
Deleted Comment
>Airlines are an abusive oligopoly there
>Average fares are skewed by low cost carriers entering the market.
The large carriers, created through mergers that should never have been allowed, have the most popular routes locked up through ownership of landing/takeoff slots and similar. On those routes, fares have substantially increased due to a lack of competition.
The low cost carriers business model is to fly new routes (to secondary airports if required) at low prices, often creating new demand (Breeze is a classic example of this).
The math is very straight forward if you consider what each group is doing in the market.
The airline industry is famously unprofitable; it is commonly said that on net, the sum total of airlines have made $0 over the course of their history. It is true that there are periods where they do make a profit, but these periods are offset by times when they make massive losses (such as during COVID, after the Great Recession, and after 9/11).
Globally, big airlines seem to be doing fine:
https://www.aerotime.aero/articles/most-profitable-airlines
I think there are lots of airlines that are propped up by governments that lose money leading to the meme you're quoting. Many industries were affected by the events you quoted, those sorts of things aren't specific to airlines.