You should be commended for an honest question, but why the hell are you home schooling your kid if you have no idea what you're doing? That's child abuse.
Uber isn't exactly cheap, just cheaper than taxis, which are super-expensive. Kitchen work generally requires some kind of training, often some kind of licensing or certification, and is rarely the cheapest type of labor.
Anyway, the main issue here is population density, not labor availability. If there tens or hundreds of thousands of people working and living in a quarter mile radius and average foot traffic was in hundreds or thousands per hour rather than dozens or less it would likely be easy to sell $4 bowls and make a profit - most of the US is vastly less dense and walkable than that though, even in cities.
But I wonder if that characterization is actually flattering for Prolog? I can't think of any situation, skill, technology, paradigm, or production process for which "doing it right the first time" beats iterative refinement.
Like Lisp and Smalltalk, Prolog was used primarily in the 1980s, so it was run on Unix workstations and also, to some extent, on PCs. (There were even efforts to create hardware designed to run Prolog a la Lisp machines.)
And, like Lisp and Smalltalk, Prolog can be very nice for iterative development/rapid prototyping (where the prototypes might be good enough to put into production).
The people who dealt with Prolog on punchcards were the academics who created and/or refined it in its early days. [0]
I mean there are nearly two full decades between the appearance of Prolog(1972) and PC revolution late 1980s and early 1990s.
>>The people who dealt with Prolog on punchcards were the academics who created and/or refined it in its early days. [0]
That's like a decade of work. Thats hardly early 'days'.
Also the programming culture in the PC days and before that is totally different. Heck even the editors from that era(eg vi), are designed for an entirely different workflow. That is, lots of planning, and correctness before you decided to input the code into the computer.
>>"doing it right the first time" beats iterative refinement.
Its not iterative refinement which is bad. Its just that when you use a keyboard a thinking device, there is a tendency to assume the first trivially working solution to be completely true.
This is doesn't happen with pen and paper as it slows you down. You get mental space to think through a lot of things, exceptions etc etc. Until even with iterative refinement you are likely to build something that is correct compared to just committing the first typed function to the repo.
> the stated power capacity of wind generation is a theoretical maximum, and the actual capacity will be much lower in practice.
Capacity is constant. You're talking about capacity factor, i.e., average utilization. Numbers from 2018 for Danish offshore wind farms show capacity factors approaching 50%. These brand-new turbines mounted on 150 meters+ towers in the middle of the North Sea will absofuckinglutely beat that.
That's more of a damning indictment of the American education system than praise of immigration. I'm not a fan of autarky in general but it seems reasonable that a country should be self-sufficient in smart people.
Its not intended as praise, but a reality-check on the status quo.
Our leadership in science and tech has always been linked inextricably with sourcing talent from everywhere. You can look at immigrant Nobels, patents, enrollment in doctoral programs, representation in executive teams in tech companies, % of American unicorns founded by immigrants -- it will point to the same conclusion.
Whether or not we should be self-sufficient is another matter, but we aren't even close, not in the highest echelons of STEM.
I'm curious though, what country would serve as evidence that sourcing talent domestically alone can propel a nation to global leadership in these fields?
Back then the C implementation of the (i.e., "one") micro benchmark beat the Rust implementation. I could squeeze out more performance by precisely controlling the loop unrolling. Nowadays, I don't really care and operate under the assumption that "Python is faster than $X and if it is not, it is still fast enough!"
You're tall so you can't sit upright? :P Do you need to lean backwards when you work too? I think you are wrong and a lot of people are not fine with it. I don't need a closeup view of someone's bald spot while trying to eat shitty airplane food.
reply