Lexing separately is cleaner in that the lexer's only job is to produce tokens and then the parser's only job is to consume tokens and produce e.g. an AST. It also means that you can use that token stream for other things that don't require a full parse (e.g. for syntax highlighting). The disadvantage is that you're often doubling the allocations and increasing the memory footprint. I alternate between separate lexer, combined recursive descent parser and generated PEG parsers depending on what is more important: speed + maintainability, speed of execution or speed of development
That’s a level of confidence, preparation and forward thinking that would be uncharacteristic. The reality is that everyone else is cutting staff so it’s become expected. And because it’s expected and happening throughout the industry it’s a lot easier to do a layoff or two now than it was a year ago
It’s not because it’s “expected” in the abstract. It’s because everyone is competing for money with the US Treasury, and the rates on those Treasury bills are looking better than they have in a long long while.
Did you have a growth business that’s going to be 50% bigger in 10 years? A few years ago that would sound not-amazing but reasonable. Today that’s nothing. You can get that kind of returns from bonds with like zero risk.
Firms therefore prioritize savings like they haven’t done in years.
Yep. And those of us who listened to the experts and took steps to understand the issue and act upon our findings were largely ridiculed and harassed endlessly as "tree hugging hippies" or "paranoid tin-foil hatted doomers" and shunned by pretty much everyone else around us until many of us (like myself) have simply given up. Why the hell should I care about literally anything if that caring only utterly destroys any chance at a remotely enjoyable life? I don't want to live the rest of my life learning to hate every single human I meet simply because they're human (monster). I'd rather just accept we're all doomed because most of us are ignorant, greedy, hateful, and stupid, and depressing though that may be, it's less depressing than speaking about things I know to be true and instantly being shunned for it by almost everyone. The alternative (one I've seriously considered) is for me to sneak off to the woods somewhere and build a cabin and defend it to the death.
Your biggest adversary, one that's cast a dark shadow over your country and it's allies, one that's consumed trillions of dollars of defence spending over the last 75 years, is now being ground down and exhausted with approximately zero of your countrymen's lives at risk and all for a mere few billion dollars. You're getting a bargain.
The USSR was a major adversary for roughly 45 years, 1946 to 1991. The US provided them major economic aid in WWII which they leveraged into a massive expansion and had minimal interaction before the war.
Russia is a politically distinct fragment of that empire, just like Ukraine.
There's many benefits in having a state machine configuration that can be serialized, especially if you can store that config in a database and load it at runtime. And actually xstate does allow you to pass the functions directly if you want to
Yes it allows strings or references to the function. My issue is that since the former is allowed, either people start using that method, or you have to start a “debate” within your team about patterns to avoid.
The serializability of your state itself has nothing to do with how events are bound to callback functions. If you serialize a string name of a function and not the source code of that function this buys you nothing. The source code itself is all text, so its serializable no matter whether the code is suitable for being statically analyzed
it's like a much more structured, and observable version of redux. observable in the sense that not only can you tell what has happened, you can also tell (and visualise) what can happen next
