Is it just me, or has DDG been having trouble often lately? Or is it just a combination with some outage + degradation of search results lately that makes me g! regularly these days? Didn't use to need that.
My mom grew up in South Africa, '40s and '50s, she always made us wash our lips after eating mango to avoid a rash. Only later did I discover I didn't need to, I always assumed the rash-causing compound has been bred out of modern mangos.
Funny, I started typing a comment here, about the author not getting the Ruby side of things right, that actually the difference would rather be that Ruby uses a special language construct and Python just normal methods and conventions. But just skimming through the previous comments it seems that Python also has these a `yield` keyword that would be more idiomatic to use.
I think we're dealing with someone who had limited experience with both Python and Ruby. This article is somehow getting more attention then it merits.
It's hard to compare as the business model has changed, I believe that nowadays it's basically impossible for a library to get an individual subscription to a individual journal: subscriptions are bundled and (online) subscriptions are sold institution wide with contracts running in the millions. That's very different from what Kunth is describing, where individual libraries choosing what subscriptions they need (eg we need the JoA in our (physical) collection so we buy a subscription to that).
I was fortunate enough to get one of the last physical reward checks which was accompanied by a printout of my e-mail, written on in pencil.
Fortunately, it survived a house flood which destroyed the book it was in, so now the envelope it's in is prominently displayed on a rack in my living room and would be one of the things I'd grab in the event of a fire.
Every so often, when a co-worker knows who Knuth is I bring it in to a workplace to show off.
Extremely envious of this! I don't own a copy of Art of Computer Programming, so I did spend a not-insignificant amount of reading through some of Knuth's other writings trying to find mistakes that no one else has found, and I came up empty handed. There might be mistakes ripe for the picking in there, but I'm afraid I'm not quite smart enough to find them.
Still, a guy can dream. If I ever pick up Art of Computer Programming I might give it a go again.
I once emailed Dijkstra. I was 14, it was the mid 90s, and I had just connected to the real internet a few months ago. I had just come across his name as a prominent computer scientist. I wanted to be one just like him, so I asked him what I should do.
He replied. it was 3 full paragraphs. He told me to study algorithms and to learn python.
I have a blog post by Norvig where he gently chides me for wasting enormous amounts of CPU trying to find a counterexample to the Beale Conjecture.
Not exactly frameable, and not exactly something to be proud of, but I got a chuckle nonetheless.
I agree, if you think of just a few big OSS project, like Linux, Postgres, Sqlite, nginx or apache web server, run as proprietary companies each of those would easily be worth way more then $177M (for reference, nginx was sold for $670M in 2019).
This is a webserver that can run various web applications for you. In a typical setup you'd run a web/http server (nginx or Apache etc) to handle the 'slow' connections to the client and a separate app server (say, an express application, or Django or Rails etc) that is completely separate from the webserver. The web server acts as a reverse proxy, sending the request on to the app server. The response from the app server is then passed to the webserver, which sends it back tot he client. So a request would this path: client -> web server -> app server -> web server -> client.
This is done because web servers are optimised to handle (many) requests from clients (including things like TLS termination, optimised handling of static files, orchestrate to which backend service to send a request and much more), while application servers are optimised to run the application code.
In this model, the web and app servers run separately, for example in separate containers and they have to talk to each other so you have to somehow connect them (often this is done through a network socket).
So what Nginx Unit does is combining the two: it can do the standard web server stuff (not everything a normal nginx can do, but often that's not needed anyway), but also run your application for you, which could, depending on your setup, make your life a bit easier, as now you don't have to tie the two together.
Why would that be misleading? This seems to be just an attempt to better understand (some of the / potential) causes that unknown condition. Perhaps it doesn't help to diagnose it, as there might not be any direct evidence left in the body to point at the original cause, but in the longer term it certainly helps if you know where to look.
It's just that if CFS doesn't point to something real, then that non-real, non-specific thing, having an origin doesn't really make sense.
But if it is actually real (and specific), as indicated by another commenter, the origin seems fine. Still seems like there's mixed views in medical community though.
reply