The Puget Sound ferries often have a partially-done jigsaw puzzle on one of the tables. You can't finish it in 30m, so people come and do their part and move on. Eventually someone will put in the last piece, I guess, I've never seen it happen.
I love those. I have finished one (well it was missing a couple of pieces), between West-Seattle and Vashon, and what was better was that I contributed to the puzzle earlier on the way from Vashon.
My last visit to Seattle was in 1998 so I can't confirm this firsthand, but I would bet that when someone finishes the jigsaw, ferry staff bring out a new one.
Usually somebody just scrambles it again, but they are regularly rotated. I don’t have a precise measure, but I would guess every couple of weeks or so.
Let’s be realistic. I love long distance train journeys, but mainly for recreation. Being on a train for 3-5 days is pretty exhausting no matter how comfortable. I’ve done the 30 day Amtrak pass before and it was fantastic but I wouldn’t be looking forward to that if it was a work trip where I want to fly in and then get back to my family as fast as possible. There’s no way that can compare to a 5-6 hour flight+2 hours at the airport.
Amtrak is decent on very specific routes and still an absolute joke to anyone who has used trains in Europe, Japan, Taiwan, etc, and no personal experience but I'd imagine China too. My friend takes the Amtrak route up and down the Pacific coast precisely because she's stuck on a train for days and can't be disturbed while doing boring paperwork as an anti-procrastination strategy. Although the observation cars do have great views.
People who have used trains in Japan or Taiwan - islands have never used a train that is anything like Amtrak does and so have no comparison. Even in Europe long distance cross border rail is in most cases pretty bad as well.
However if you only compare the shorter distance rail in those places to what the US has some of the other trains are actually pretty good. Even then though Chicago's trains are a better comparison than anything Amtrak offers
I mean what do you consider long-distance? Inter-railing is a time honoured tradition for European Youth, and many of my generation alone would be very familiar with economy sleepers from e.g. Krakow to Prague or Budapest.
The ICE trains in particular are magnificent, and a worthy alternative to air travel.
Yes people do it all the time in Europe. It mostly works. However if you follow the space at all you will see a lot of stories about things going wrong - far more than there should be. Amtrak is mostly fine in the US, but there are still far more problems than there should be.
I mean, maybe you had a different experience. In my experience in the northeast , the internet service is about as reliable and consistent as the trains themselves (ie not consistent, garbage fire)
I was rather disappointed by the internet connection on the Cascades line (going Seattle --> Portland and back). As far as I could tell, they use T-Mobile for backhaul. Who are headquartered in Seattle. Yet the connection barely seemed to work for about half of the journey
boo, it's in the middle of no where along part of the route. Tmobile coverage is mainly in urban areas and along free ways no matter what slingblade tells you on the tv commercial. I don't know if you'd get any coverage on parts of that route other than wired.
Just like how sometimes when you're flying over the rockies or into canada you just don't get internets. There's still middles of no where out there. Often not very far from the freeway.
This wouldn’t bother me as much but it’s really like 5-7 days depending on freight use of the lines and they can’t tell you ahead of time what it’s going to be somehow?
Calories isn't everything, there is a lot more focus these days on how different foods affect metabolic hormones affecting satiety, blood sugar, etc. On those metrics, fat alone (which account for most of the calories in peanuts) is very satiating and does not trigger a later blood sugar drop (which causes cravings). That's why people on a diet drink 'bulletproof coffee' (coffee with butter in it), because it is extremely filling while not making you hungry later.
I loved the tactile feel of 3.5" floppies (especially coming from the - actually floppy - 5.25"s). Great choice. In particular, the spring-loaded metal shield was very satisfying to play with, unfortunately those are missing on the disks in the picture (apart from one, which seems to not have the closing spring)! Possibly a casualty to the three year old user.
That's how I read this too. The publisher invested a non-trivial amount of work and was left with nothing, for no better reason than the author changed their mind. From the tone of the post, the author seems to not realize or care.
The publisher changed their mind, too. I don’t think the author was pointing fingers, just sharing information that his readers might enjoy or find useful.
That was a lot of words to get to the point that Fleming probably misremembered the sequence of events when he retold the story 15 years later. He even mentioned this possibility at the time. Interesting article but not much of a mystery.
Seems like you would at the very least need a fairly thick application layer on top of Postgres to make it look and act like a messaging system. At that point, seems like you have just built another messaging system.
Unless you're a five man shop where everybody just agrees to use that one table, make sure to manage transactions right, cron job retention, YOLO clustering, etc. etc.
Performance is probably last on the list of reasons to choose Kafka over Postgres.
There's a lot of logic involved client side regarding managing read cursors and marking events as processed consumer side. Possibly also client side error queues and so on.
I truly miss a good standard client side library following the Kafka-in-SQL philosophy. I started on in my previous job and we used it internally but it never got good enough that it would be widely used elsewhere, and now I work somewhere else...
(PS: Talking about the pub/sub Kafka-like usecase, not the work queue FOR UPDATE usecase)
Ugh, I've had the exact same problem in a Java project, which meant I had to go through thousands and thousands of lines of code and make sure that all 'toLowerCase()' on enum names included Locale.ENGLISH as parameter.
As the article demonstrates, the error manifests in a completely inscrutable way. But once I saw the bug from a couple of users with Turkish sounding names, I zeroed in on it. And cursed a few times under my breath whoever messed up that character table so bad.
They do. But a generic warning about locale-dependence doesn't really tell you that ASCII-strings will be broken.
For nearly every purpose ASCII is the same in every locale. If you have a string that is guaranteed to be ASCII (like an enum constant is in most code styles), it's easy to think "not a problem here" and move on.
Unchecked exceptions are more like a shutdown event, which can be intercepted at any point along the call stack, which is useful and not like a return type.
Debugging. It's one of the most useful tools for narrowing down where an error is coming from and by far the biggest negative of Rust's Result-type error handling in my experience (panics can of course give a callstack but because of the value-based error being most commonly used this often is far away from the actual error).
(it is in principle possible to construct such a stack, potentially with more context, with a Result type, but I don't know of any way to do so that doesn't sacrifice a lot of performance because you're doing all the book-keeping even on caught errors where you don't use that information)
The instrumentation and observability are more heavyweight than the overhead of unwinding the stack which is already keeping track of the most important information (in most mainstream langauges, at least. And even if you don't have a contiguous stack there's usually still the same information around at the point an error is created, assuming that you have something like functions that are returning into other functions. Exceptions, as a model, basically allow the code that raises an error to determine where the error is going to be caught without unwinding and removing the information that lets you track from the top level to where the error was raised). It is still tradeoff, of course (returning errors is more expensive than success), but it's one in a much better place in practice than other options (as obvious by the fact that errors-as-values implementations rarely keep this information around, especially not by default)
reply