mfranc42

For C++ projects I use a language server to jump around within Emacs. For a Linux kernel which is my day job, I just use git grep, since I couldn't make the language server work across multiple architectures at the same time and plain old C is simple enough for that. I have never used auto completion, so perhaps I don't know what I am missing. At least to me, coming up with an idea how to do stuff is more time-consuming than writing it down in an editor.

I'm missing s390x.

But there is a global timeline. The age of the universe itself. It happened when the universe was roughly 300M years younger. Somebody might say the universe was created a year ago if they traveled through it extremely close to the speed of light. But we know how fast we travel by measuring redshift/blueshift of the cosmic microwave background and it's definitely far from any relativistic speed. There must be some effect of gravity, but that is also within a rounding error. So, I'd say we are much closer to the "truth" than somebody who travels through the universe a few percent of the speed of light or "lives" right next to the supermassive black hole. Whether something we will never see exists or happens is a philosophical question akin to "if a tree falls in the forest..."

That looks like a misspelling of "Immortel" to me

Well, if you never compare A to B, you won't believe it for sure. :-/

That angle of view corresponds to a lens with 588mm focal length on a full frame camera (horizontally), and 392mm (vertically). Funny that astronomers and photographers mean very different things by saying wide angle. ;-)

I don't remember using PGO like ever. And even if you do use it, isn't it like breaking compilation into two phases that are themselves deterministic?

It is pretty useful picture in my eyes, because that's what I've been observing since like forever. Non-deterministic compiler would be pretty hard to test or reason about.

It might be a banal observation, but an important one if you want to contrast a compiler with something like an OS kernel or most modern programming projects that interact heavily with outside world. When you throw hardware, network traffic, or users into the mix, it gets crazy.

He probably meant that a compiler is a pure function for a given source file and a set of flags. Of course, if you change a compiler or flags, you can get something radically different, but you shouldn't get something radically different because it's Tuesday, midnight, your username starts with n, you have more than 3 hard drives, or because it reads some bytes from /dev/urandom.

It's bit of a stretch, sure, but I don't expect my performance problems to go away by recompiling stuff over and over again without changing either the code or flags and expecting the optimizer to make a better decision next time. It doesn't work that way.

Yes. Namespaces good. Escape sequences good. Terse syntax good. As long as it's not rare and obscure good. :-)

Well, they are closely related. Which is unfortunate for C++ because it can never free itself from all the C legacy basement.

GNOME doesn't certainly offer that. Maybe, it's just me. But I was unable to handle more than 3 windows at the time. Escaped to sway to solve it.

It seems to me that it's comparing apples and oranges. I use Instagram because everybody else uses Instagram. I use Flickr, because I'm into photography and I don't mean Iphone or Android photography. I mean photography in general.

Instagram is a mobile app. End of story. There is some web/desktop whatever, but it's a joke. I do most of the image manipulation on my laptop/desktop, so I want something that works there. I want to share a full sized result, not a 1080px preview. Mobile app is a welcomed bonus.

Instagram is not a site for photographers. It's an image centric social network. Photographers can use it to reach wider audience, but besides that it has zero features geared towards photography as such. It works for exactly 3 (yes, three!) image sizes and doesn't even show EXIF data.

Yes. People keep repeating this and while it is a real problem for some designs, most professional cameras allow to bypass it with a remote trigger, often an official one.

Besides people were doing long exposure since like forever with great success. If the sensor overheating was a problem, it would make sense to introduce a hard limit and some cameras have them, but from my experience the likely reasons for the prevalent 30s are: 1/ most people don't do several minute exposures 2/ they need to sell remote triggers to somebody.

30s limit was there even during nineties when you could do hours on film without overheating anything.

I understand the business decisions. But, what you are suggesting is already kinda happening with mobile phones. They have shitty sensors, but software ecosystem that can thrive around it. My guess the next big thing will be a professional camera with android and third party software running on it, doing all sorts of cool stuff.

First, I'm not complaining about 5Dm2. I use magic lantern on it and I'm happy with it. It does what I want. I'm just sad that unpaid enthusiast must provide functionality that should be there in the first place. Also, I recently bought Panasonic Lumix S1 and as you can imagine, there's not magic lantern for it.

Second, an hour was just an example. Most of my exposures are not longer than 4 or 8 minutes.

Third, I'm happy that you are fine with external controllers. But I'm not. I find them crude and unnecessary. I'm doing a lot of HDRs and I don't understand why I cannot simply preprogram my camera with sequence of shots and execute it without any gadgets and limitations. Say, there's this nonsensical limit for 1 minute or 30 seconds everyone seems to defend for some strange reason, (is there some sort of Stockholm syndrome at work?), at least the manufacturer could provide a better bracketing setting to compensate for it. It's not like it's rocket science. An intern could write the firmware in a few days. I cannot even patch the camera without voiding the warranty. I know they are always workarounds, but why make things complicated, when they could be simple.

I have done 30 minutes exposures with digital (5D mark II and magic lantern) with very little noise, so I doubt sensor heat is the problem. Try to bump ISO and you got so much more noise.

I often need it for HDRs at night. I know I can do like wayloads of high iso noisy short exposures and average them in post, but it's clunky and even harder to set up automatically. I would prefer something user friendly. When I'm shooting at night, it's often cold and even not so safe. Fiddling with apps and cable releases is not something I'd like to do.

I know that the hardware is capable of it, but they just have to sell you that cable release or what not in order to unlock the capability, which is what I'm not happy about.

I have Lumix S1. It has gazillion of features, but, for example, the exposure duration is limited to 1 minute. :-(

It's all fancy shit. But guess what. My 35mm camera from eighties has command back with intervalometer. I can say stuff like in 10 minutes do an hour long exposure directly on the camera. The fact that I cannot do it on modern camera without cables or mobile phones is a travesty.