This is somewhat tangential, but I'm feeling a bit ambivalent about all of the popular options for building RESTFul APIs lately. With every new entry in the ecosystem, the same libraries (authentication, migrations, logging, authorization) have to be re-implemented. In spite of all of this new stuff (Go, Node, and now Rust) I look around and don't really see how we've done any better than Rails in the past decade or so. Performance needs aside, I feel like we're just going around in circles since Rails.
Pretty much the same reason Wordpress marches on. The advantages of a "better" language are just not worth rebuilding the entire ecosystem around WP or Rails, both of which have massive leads and neither of which are standing still. RESTful APIs are pretty much a solved problem, the next language isn't going to get big by being a better Rails, it's going to get big by doing something new.
My disagreement with the fsf is pretty fundamental. I don’t see anything wrong, all things equal, with paying someone for software that is closed source provided there’s some way to ensure it’s not doing things wildly unexpected or malicious. Perhaps it’s impossible to verify such a thing without source code, but the core ethical claim seems off to me.
It's not about maliciousness it's about owning the machine. If you bought a radio in the 1950s, you could take it to bits and fix or upgrade it. You can't do that's with today's software.
It's not comfortable for companies but it is a simply better way of doing software development both ethically and in terms of quality.
This entire discussion is about laws regarding minimum wage, the act of literally making it illegal to hire for less than a certain wage. I’m not sure I see the confusion
> "The other way to frame minimum wage is that it makes it illegal to work unless you can produce $X value per hour."
Wages are a cost to a company. There are other costs to a company. Companies also return a profit to the owners. If a company's costs are too high, they my not return a profit; they may not be able to pay their creditors.
My dad ran his own very small business. I am familiar with a business not making a profit for a period of time. I am familiar with workers who are not profitable to employ.
It is a reduction to absurdity to state that minimum wage "makes it illegal to work unless you can produce $X value per hour."
There are interesting, non-absurd discussions about the effects of minimum wage, but this is not one of them.
So you're saying your Dad would be better off if he kept the $X then paying someone. That's what it means to produce value.
The number of employers seeking such an arrangement is so small it's irrelevant. In practice, not being able to pay people less that $15/hour means you won't hire people who bring less that $15/hour of value.
In this fictional scenario every single community member has become a racist but the government legislative and enforcement bodies are immune from this trend?
Making something illegal may feel good, but if 100% of the population (by the terms of your scenario) are against it, legislation is hardly going to move the needle.
I’ve tried a few Ubuntu distros as of late and truthfully they’ve all been pretty impressive. The last issue I really have is fractional scaling on a 4K.
I've seen these precluding secondary employment with competitive entities, but it seems there'd be little competition between Fred's and Alice's businesses (based on name alone).
Are compiler optimizations like summing a series done on an ad-hoc basis? Certainly the compiler couldn’t have discovered or inferred (not sure what term to use) that formula, no?
Ad-hoc basis. Usually comes out of studying the most common classes of computation and optimizing for it. For example, the "summing a series" probably falls out of loop optimizations: https://en.wikipedia.org/wiki/Loop_optimization
Those optimizations are happening on LLVM's end (though the higher-level language will have to expose sufficiently transparent abstractions to make these optimizations possible). I'd love to read a book on the optimization techniques that are implemented in LLVM/GCC to make transformations like this possible.
