1,229 karma · joined June 23, 2012
Yes, in my opinion, but from Zig's success you can see some people are willing to trade safety for a simpler language. Different people have different values
Though to be fair you can also use zig in old C projects, moving things incrementally. I don't know how many projects do that Vs greenfield projects though
Following your example, it'd be like the author of a book buying the book they wrote from someone else. If the author chooses to pay someone else 1000$ for their book, they can, but they will be wasting money.
A company doing a stock buyback is trading off their own capital (they have to spend it, it's not an infinite money glitch where they buy it from themselves) to get back shares of the company itself at the then-market-price. The market chooses whether that's a good trade. It may not
I know that bash does this, and possibly other shells, but it doesn't work in general when you `execv` the file (or when using the subprocess API on python f.i). But cool trick anyway
Doesn't look like that's the case in OP's solution, where HTML tags are transformed into Lua tables. I guess then there's some code that turns the lua tables into the html text to be sent to the client
But now I see this website and it turns out that "Cleopatra" is consistently one of the most visited pages in the Spanish Wikipedia. Odd! I googled and it turns out that it's because it's one of the example queries in Google Assistant (source, in Spanish: https://www.elespanol.com/omicrono/software/20230118/cleopat... ). I must have tapped on it without realising. And like me, thousands of others, every day! Fascinating
This is one of the things that _are_ addressed by the project.
Regarding your broader point, I don't know if adding a new language would/will help emacs or not but it's _plausible_ something like that would work. The plugin ecosystem in the vim world became more vibrant once writing them in lua was an option.
Additionally, even if you insist that this reader monad is a "wrapper", your definition would also informally apply to things like `Applicative`, and not all applicatives are monads (some are).
Some monads are more easily understood as wrappers (`Maybe`, `List`, ...) and you can be very productive if you just stick to that level of understanding. But there's a deeper understanding that one can get.
[1] https://hackage.haskell.org/package/mtl-2.3.1/docs/src/Contr...
I wonder if Amazon would ever consider having completely independent implementations of the same software (made and maintained by different teams) running in each availability zone. This would reduce the correlation between AZs. Of course, this would be much more expensive, but perhaps worth it if availability was critical.
In fact, I vaguely recall that this was a common practice in the development of some kind of critical system (avionics?).
> We can see a correlation between GPU prices and the value of crypto currencies, but correlation does not mean causation. A causation is plausible in this case.
And then they go on to repeat a very reasonable argument, which I happen to believe to be true, but the kind of argument that everyone was already making before looking at any data.
The fact that the correlations do not hold as much for CPUs is good, but still not enough to stablish causation. As you said, there might be some confounding factors that affect crypto and GPUs but not CPUs.
I'm not blaming the author, because determining causation is hard, and checking there's correlation between two variables can still be interesting, but the article falls short of answering the question.
"Generally useful" is a vague concept. If you judge by number of job openings, you'll probably find JavaScript is more useful. There are probably metrics by which C is more useful.
"Being everywhere" is not necessarily a good measure of the upside one can get by learning it. For example, electronics are also everywhere (more so than C!) but software engineering is generally a better career (measured by income f.i)
There are a few languages where types only exist (for the most part, though with exceptions and hacks here and there) at compile-time, like Rust, C++ or even Haskell IIRC.