jval43

I might be wrong but I remember that I couldn't extract some really old Stuffit archives using the current versions, but an old copy of 'stuffit520.611linux-i386' I tracked down could.

Does anyone know if that makes sense? Did the format ever change?

It's unclear from the question, but they were apparently looking for a very small number.

But is that connection timeout, or query timeout, or something else? If you have long-running complex data processing or ingestion jobs, query timeouts could well be measured in minutes or hours. So a small number doesn't make sense there, and the connection technically doesn't timeout.

For connection timeouts, if you run a connection pool then timeouts of a few seconds or more could be fine and be the difference between the system being completely down vs just slow in case the load / contention unexpectedly increases. Not great of course and it won't hold for long, but might help in some very specific bursty scenarios. If you are able to safely re-use the connections in the pool most of the time the timeout matters even less. Reusing connections is usually possible, but it depends on the database and what errors require establishing a new DB connection.

And of course with a pool you actually have 2 'connection timeouts': one for establishing a new connection to the DB and a second one for acquiring a connection from the pool. The second one is usually most relevant for an application, but both matter.

But even without a pool a higher number (say a few minutes) could possibly make sense given a specific scenario. A database with a connection limit is equivalent to decrementing a semaphore (acquiring a lock), and there are cases where you'd want to wait for just a bit longer to acquire that lock instead of just timing out. A slightly longer timeout won't hurt if e.g. you implement a retry mechanism anyways instead of aborting.

Not saying long timeouts are a sign of great engineering, but context matters a lot for these sorts of questions.

It's even worse for playlists that change (daily mixes, made for you, or curated playlists).

When updating them, Spotify will first delete all old songs and then try to download the new ones. If a lot has changed and you're on a spotty Wifi connection this effectively deletes everything. Happened to me several times while on vacation.

There is the solution of enabling offline-mode before leaving for vacation, but as you mention it's very easy to accidentally disable it and once it's disabled all your playlists are toast.

I've dealt with this on Windows and Linux, and on Linux it was even worse. There I usually had to turn it off altogether.

It was never an issue on Macs for me though, even before "retina" resolution was a thing. Which by the way turned out to be a genius way to solve the issue, even though people didn't realize at the time.

However, I also remember that many people just didn't notice or didn't care. Completely fuzzy display and they just thought that was how it was supposed to be. In the XP era, people would just set the screen resolution lower to something like 800x600 to trade subpixel fuzziness for regular fuzziness.

VGA cables and later cheap VGA-DVI adapters didn't help either. You got VGA fuzz plus subpixel fuzz, total mess. Fun fact: Just last year I sat down at a shared desk at work and noticed a slight fuzziness, and after some investigation saw there was a USB-C dock -> VGA out -> HDMI adapter horror-show going on. Nobody noticed!

I went looking and it was indeed Chrome that could do it. See screenshot from 2009 here: https://superuser.com/a/42499

Google removed the feature intentionally in 2013: https://bugs.chromium.org/p/chromium/issues/detail?id=297648

Apparently Opera supported it too at the time, and from the comments Safari as well.

Performance reasons seem to have killed it. I'd think that after 10 years now any modern computer would be able to handle it.

With all their employees and machine learning people Netflix couldn't find a single data scientist to present this in a nicer way?

All we get is an Excel sheet dump with a huge list, not even grouped by series? Not to mention regions, languages, genres, some graphs, etc.

I'm a bit surprised to be honest.

Didn't Chrome do this at the very beginning, when it was initially released? I faintly remember that being a feature.

Personally I would already be content if my browsers didn't forget their history all the time, both Firefox and Safari history is way too short-lived.

re: replies, check out hnreplies.com (no affiliation), it works quite well.

Agreed. If you don't test your script in other shells and on other platforms, why advertise compatibility. And not just the script, but also the programs called.

I got burned by supposedly "portable" scripts by the whole Ubuntu dash disaster, and again when I started using Mac OS X, and then again once I used Cygwin and msys2 on Windows.

I do keep portability in mind when writing shell scripts to ease porting later, but without testing there's really no way to be sure "/bin/sh" is right. And some of the Bash features such as arrays are legitimately useful.

For personal photos, integration with the iOS Photos library is something I'd like to see from more apps. RAW Power is pretty much the only raw editor that integrates well, without needing to copy files around and creating duplicates.

Ligatures are great if done right. E.g. the set in Fira Code gives me a 2 character wide ≠ instead of != so it retains the monospace widths.

Nitpick: "0f1012 vs 272928" doesn't actually mean anything. Any two shades of black or any color could result in these numbers depending on how the camera exposure is set and how the raw->jpeg conversion is done.

What's maybe also interesting is that the whole transition was very developer-driven, at least in my circle. It wasn't management deciding from the top.

Around me it was just everyone that wanted to use Git: potential hires, junior devs, senior devs, etc. Even the older devs with 20+ years of experience liked it well enough to not oppose the change.

And management was also happy because it didn't cost anything to run a Linux server with Git + GitWeb installed.

Yes I remember when I applied for my first internships, several companies highlighted that they "used version control". It was a feature back then!

Short answer: It was better than everything else, and the competition really sucked.

Long answer: A big factor was that new devs already knew Git because it had taken off spectacularly in the open source world. In only a few years SVN was legacy and everyone switched to Git (and Github) for open source.

Windows shops that had been using SVN had a very natural transition to Git, with lots of tooling and experience available.

But there were indeed a lot of Windows shops that used other, mostly commercial and centralized version control systems before. While they might have had some advantages over CVS and SVN or when used for enterprise, those advantages disappeared when compared to the new distributed version control systems like Mercurial and Git.

Even though Git is not exactly easy to learn, it was still vastly better than the old version control systems. In many ways the old systems just really sucked in comparison.

As for Git Bash: You could always install Git through Cygwin, but I don't remember Windows people using the command line much. There were many Git GUI applications for Windows, and IDEs provided integrations as well. E.g. Eclipse came with a completely commandline-free Git client and integrated UI that worked flawlessly on Windows.

As for Mercurial vs Git: it wasn't completely clear from the start that Git would "win", as they are very similar. I think network effects, Github, and the Linux kernel halo effect are mostly responsible for the difference in use.

Pretty cool to finally get the 3D motion capture data from the pods. Accuracy for running distance was always excellent even for older Stryds, so the motion data should hopefully be good.

As I understand it they seem to require two units for Footpath, i.e. growth by having existing customers buy a second one. But maybe I'm reading it wrong, as I don't see a reason why that feature wouldn't work with just a single unit.

More akin to the perpetual motion people.

Don't forget "server" licensing, which is by CPU core. And who knows if they mean virtual or physical ones.

Never. You can pry my passwords from my cold, dead hands.

Even worse, on the Apple Watch you cannot input text at all in one of these languages, as you cannot (!) turn autocorrect off on the watch.

They managed to fit a full QWERTY keyboard on the screen yet made it completely useless.

Isn't wind created by temperature and pressure differentials between regions? How much is due to earth's rotation?

Awesome. I would be curious to see what the difference is between monsooned malabar and some more regularly stored beans.

It is an affront though, a butchering of the language and just generally disrespectful. The distinction is an integral part of the German language and it's wholly inappropriate for a telco provider to address someone like this.

Same goes with names: missing accents, umlauts, special characters, wrong ordering, wrong titles/gender etc. is aggravating. And customers do complain.

German companies often spend a non-trivial amount on software engineering time and data cleanup to get these things right. And the French take it even more seriously.

Non-native speakers may not understand it, but that's no excuse and you will alienate people and customers. Even younger generations notice.

And just fyi I'm a millennial and per "Du" with everyone I know. Not my telco provider though.

Apple only truly started competing against Garmin recently. Improved running metrics, low power mode, better battery (Ultra) etc only showed up recently while Garmin and others had them for years. Even GPS wasn't on the first iteration.

Now do iOS. Content-aware fill still fails with OOM on iPad Pro, yet works fine on older Macs with less processing power.

The Canon R5 has no lag at all. The EVF (a 1600x1200 120Hz OLED display with 100% coverage) feels as fast as an optical viewfinder, and the R5 can shoot 20fps with full autofocus tracking and without blacking out the viewfinder. Shutter lag is actually less than on DSLRs as there's no mirror to flip and electronics have gotten way faster in the last 10 years.

The newer ones like the Canon R3 are even faster and the Sony A1 can do 240fps in the EVF.

Another perk of EVFs: they're much brighter indoors as they simulate the actual exposure.

No, you are both correct. You are talking about the SSPL, the parent poster you are replying to is talking about the Elastic License which does in fact prevent you from modifying the code and running it in production:

See 2.2 Restrictions: https://github.com/elastic/elasticsearch/blob/master/license...

With the dual-licensing you have a choice of Elastic license or SSPL, but they both have terms you might not like. And if you use the binaries you automatically use the free as in beer Elastic license.

>* I can long press on notifications and directly block it forever or finely tune the App sending it what it is allowed to send etc.*

Apple improved that on iOS, see the screenshots here: https://support.apple.com/en-us/HT201925

Also, I just aggressively remove apps that try to show spam notifications.

Here's my solution to these issues:

1. I am "that guy", but who cares? It's like a carpenter bringing his own tools. I bought a second one after 1 year of lugging it around, because it's worth it to me.

2. Use/buy US QWERTY on everything, with US-International dead keys. I've been typing German (QWERTZ) this way for >10 years now, and it makes some programming tasks/tools easier to use.

3. Alternatively get a set of blank keycaps for your keyboard. This is actually a key ;-) feature of mechanical keyboards, you can get keycaps in all shapes and sizes and even custom printed ones. I use blanks or US QWERTY.

4. Keep a second (regular) keyboard plugged in case a coworker comes around. This is easy, as there is usually one on the desk already.

5. Borrow keyboards from friends for 2 weeks and try them out full-time. Some that I've tried were downright painful. I know it's hard to return stuff in Europe but if you can, try to.

6. Although expensive I think it's a good investment, especially if may prevent health issues in the future. Some employers may even pay for it, or offer an alternative.

So basically what Gerrit offers as the "cherry-pick" submit type? You work on the master branch, then push commits as changesets to Gerrit. After review they are cherry-picked by the system onto the target (master) branch, in whatever order they happened to be reviewed. Or am I missing something?