buserror

A LOT of features have disappeared on BMWs in the last few months. I looked into trading in my X5 (2019) for a X5 45e (plug in hybrid) but it was missing quite a few bits that came as standard before. Like, fog lights. Or the heated/cooled cup holders, wifi hotspot and several other features.

Strangely (ahem) the prices haven't gone down!

Hate to tell you, but I've been using sid for well over 20 years, and it is usually more 'stable' than most distro out there.

New one as of this morning is to kill STOP processes it doesn't like. I have no idea why, or how to revent it. All I did was update my 'sid' debian and here goes

I've used Berkeley DB for decades, in many projects, many time having to have a yelling match with other people who wanted to use one of the large spaghetti plate "database".. this was before the "noSQL" trend, and even after. How many projects /need/ network access etc, in a LOT of cases you just want a file backed, very quick library and that does the job.

For more complicated setups, sqlite also works wonder.

I don't know what the rage is all about with Eclise really. I'm a hard code dev for 30+ years, kernel, embedded, I do a lot of C, last time I wrote some java was in 1995 to give it a spin, none since.... ... And I use Eclipse CDT as my primary "IDE" all day. It's stable, it's as quick as the other JS monsters out there, and one thing it has is that the Indexer is unique -- the Eclipse Indexer will index /anything/ -- even enormous codebase. And it's not "ctags" dump indexing, it's full C preprocessor expanded macros.

And really, if you use the "Makefile" projects, it's just an IDE. And it's better than everything I tried (as of last year) -- most IDEs out there can't even parse "Make" output correctly to parse the error messages!

especially since the english pronunciation, as listened by a french speaking person, means literally "hit with fat", bringing to mind someone fishing off a creature by slapping it with a large piece of pork belly :-)

I love that "coup de grace" is listed in the examples, as it's actually... French!

Reminds me of the famous (fictional?) quote of Bush president saying "There is no french word for entrepreneur !" :-)

Exactly what I thought when my scripts started spewing that annoying error. Even busybox has a 'which' implementation applet which (aha) is a debian based one.

I use a similar approach in libmish [0], ie I "reserve" the bottom 2 rows, and output the scrolling text in the top parts. Pretty straightforward.

[0]: https://github.com/buserror/libmish

Errr, I switched from Apple (II, and mac) after 20+ years of being a professional developer to -- Linux/embedded. To be fair, I was also a UNIX developer all that time, starting with Minix all the way back then, to Pr1meOS, HP/UX, SunOS, Solaris and blah blah. The fact I had that UNIX background is what saved me. I was really highly technical and very highly rated Mac dev until about 2006 when I realised this was a lost cause. I would not stand developing for the apple business these days -- these days, I can use my "embedded" skills on linux (or bare metal) and "be the tree that stands out from the forest" -- these days on Apple-land you are just chowder.

Mind you, I might have audio working on my linux workstation, but I can't seem to get the mouse wheel doing the right thing. That's the price to pay, and I might grumble about it (a lot) but it's better than having half the available API your app used to use just diseapear into thin air.

Why I don't understand is, why is nobody talking about Crystel? She sold something she didn't own betraying the trust of everyone, and yet, nobody mentions her. She went to hols and xmas parties, she was "elected" by peers and then she picked the worst person even and SOLD HIM SOMETHING SHE DIDN'T OWN.

possibly because the israelis already have all the imagery they would want anyway, and the blurring is only a problem for people who don't?

When I was about 17, I worked with a chartered surveyor (aka géomètre) on digitizing the whole path from Lille to Paris (france) and use the "computer" to split the polygons that were digitized by a team of people using "cadastres" (official, high definition paper maps).

The polygons were entered by a team of people, from the map into a small serial-to-file program, and that file was then fed to a Hypercard stack that did the polygon intersection...

...To was to be the path of the Eurostar Lille<->Paris. The land in the middle was expropriated, sometime leaving landowner with bit of land they could not reach as the next "bridge" back to it was 20 miles away!

Anyway, I used hypercard back then for a multitude of reasons at the time. It had "plugins" to read/write stuff, it had pretty good interface, it allowed code to very easily detect errors in the digitizer input, and allowed a very, very rough preview of what the "cut" would look like.

I did quite a few cool projects in my career, but every time I drive at 300km/h on the eurostar to paris, I take a little extra pride into thinking I "did" that :-)

You heart might survive, but your joints probably won't. The stress you put on them when running/sporting when young will come back to haunt you later on!

Don't ask me how I know :-)

I've got at least a dozen soviet film cameras; Zorki 1s (one of my favourite), Zorki 3's (and the "crown" of the collection, the 3c). I've got a Zorki 1 that is /at least/ as smooth as my Leica IIIc, it is incredibly smooth. These are easy to fix, easy to maintain and with a bit of care (and understanding how to use the TINY rangefinder) you can make fantastic images.

One camera the article doesn't mention is the Iskra. It's a "folding" 6x6 medium format camera that is probably the best I've seen in terms of quality. Problem is, finding a good one is tough, as it was very complex (it was a copy of Agfa Isolette) -- very often the cameras are completely worn out due to use over so many years. If you find one that works, you are SUPER lucky. I bought 5 to get 2 working, but it's worth the money, the lens is spectacular, and being medium format, a scan of that will compare to even modern cameras.

Another camera that is not mentioned is the more modern "panoramic" camera Horizont that use a rotating shutter to give you a fantastic panoramic view with correct verticals! This one is a marvel really, I made fantastic pictures with mine.

There is a lot of fun to be had with these cameras; there are also dozens and dozens of lens that are worth playing with!

This is very cool! Do you know how old is the data, generally?

It's still used in England -- my accountant (old school) writes to me as "Mr M xxx, Esq" -- and I'm not a lawyer. It is supposed to be a form of politeness when mentioning someone else's name.

I have not done a comparison, but RDP is mostly pixel based from what I understand, while x2go is "protocol" based (and therefore limited to xorg/x11), so it's a LOT quicker than say, VNC (even with compression) -- for example, if you drag a window around, it's perfectly "instant" -- there is no lag.

I can develop using geany/vscode/eclipse remotely over a reasonably good DSL/fibre connection and quite frankly, there is zero difference with being "local" to the workstation. Don't even need a LAN.

Only thing which obviously doesn't work as good is web browsing/video etc as that is inherently a lot more pixel pushing.

I use x2go all the time, I have one single big workstation, and the laptops and the "thin" machine in my lab are tethered to it all the time, even when outside, via wireguard.

I'm not surprised a raspi can do that, as I've used an antique thinkpad x201 for doing it for many many years now!

Clickspring is actually manufacturing porn. Nothing else, it's just overload! Everything is perfect, shinny, well lubricated. Just amazing. I'm glad he's back at making videos too, I had withdrawal! :-)

You don't risk "overexposing" (as the article says) anything with film/paper; basically you reach the "reciprocity failure" where the rule of exposure fails, and you can pretty much ignore the exposure time /completely/ at that point. Double it? fine. 4 times? still fine :-)

I've done many 30 minutes+ exposures on both pinhole and large format cameras. On the later, it captures an insane amount of tonalities from what you are imaging, almost like "HDR" but well, with just a piece of carboard for shutter and a watch to time how long your patience lasts :-)

I know... but it's not the same as hearing the screams of despair as your arch-tank-enemy gets destroyed by your cleverly laid mine from across the office floor! :-)

I bought a Mac Plus recently, and one of the new things I installed on it's MASSIVE 20 megabytes hard drive was Bolo. And then I proceeded to waste a good hour playing it all sadly by myself without the Localtalk network that used to be full of games, back in the day. sniffle

I used to use linux's list.h quite a bit, that is the "good taste" implementation, where the head is the same as the elements. My only problem with that implementation is the fact it is non-typed. Heads are generic, and the code using them has to use container_of() macros to recover the containing type.

I've since discovered bsd/queue.h [0], which is very similar in purpose, but is not "good taste" (which I don't mind at all) on the other hand it is type safe, has quite a few variants for single and double lists, and oh also, it's not GPL.

[0]: https://github.com/freebsd/freebsd/blob/master/sys/sys/queue...

After having been paid for a few months to do upstreaming, I know very well that nobody close to the linux kernels is doing any 'coding' anymore.

it's seems to be more of an excercise into pleasing the priesthood to their, current, very important way/shape/form "canon" of what IS right at the moment than actually get any 'coding' done. And given the time it takes, i wonder if ANY of the top level maintainers actually program anymore, and are just "patch gateways".

And yes, there is a massive caste of priesthood of the patch series, discussing and making decisions on stuff they often borderline understand, and on criteria that are in fact quite far from the "it make sense" line of thinking.

I know, I've spend months re-writing drivers which were perfectly fine, neat, written with the upmost care of "upstreaming" as our team could figure out, to have to rewrite them completely and entirelly in the whim of someone halfway across the world, who didn't couldn't possibly have known what we were working on (as we were the designers, mostly) but who decided that version of the "canon" was not matching ours.

It's a stupid waste of time, money, brain cells, and the result is actually lesser than the original code.

For no good reason as the canon will change next year anyway.

For many years, I thought that the Linux kernel ecosystem was pretty much self-sufficient, but it's grown way too big, to the level of MASSIVE bloatware level nowadays. Massive corps have dozens of guys working on it, and many of them are also 'maintainers' -- full time; threading patches, some of them with conflicts of interest, or lack of understanding, or both, or just having been left behind a while back while still being innundated with patches.

I think it's doomed, in that form anyway.

How funny, I use tcc /all the time/ and I was just tinkering with one 'script' [0] the other day. Basically more often than not for me it's easier/quicker to write stuff in C than fighting with another script language that will break next time I want to use that 'script'. C works.

of course I could compile it, but really, it doesn't have to, and to develop/try that sort of small C tools, tcc is just unbeatable.

[0]: https://gist.github.com/buserror/227a7e64c92acece821ec8ee587...

I use that fact quite a bit when training my labrador; when in the woods, if she ranges too far, I'll just stop and stay completely motionless. She'll fail to see me at about 15-20 meters from me, especially if I'm against a tree or something. Even if I'm not obscured at all.

Soon tho, her nose will pick me and I can then see her eyes 'click' on me eventually. I use that trick to keep her "worried" she'll lose me, so she keeps checking on me at shorter intervals and control her urge to follow a yummy smell.

The interesting thing is that on the other hand, she has no problem tracking a moving object in flight at 100m, like a pigeon. Once I was shooting clay pigeons, and missed one overhead, and a few minutes later she came back all happy with my unbroken clay target, she had tracked it, marked it, and retreived it!

I think that it's a long article to just say that a 1) good 2) big screen, or two, or 3 is a good idea. The bigerrer, the beterrer.

I wrote a lot of code on Mac classic format (512x342) using Monaco 9 -- it was great; next step was 640x480, and 800x600, and then (for a rather long time) 1024x768.

It was still perfectly fine, as (at the time) Apple screens were some of the best, nice crisp, clear with good contrast. I didn't feel particularly handicapped because of the screen real estate, you just adapt to what you have.

Now my main machine is Linux with 2*32" 4K screen side-by-side, and about 60cm from me. I use Liberation Mono 17pt as a terminal font, and 9pt is just microscopic on the screen.

And guess what? I still wish I had a bit more screen space sometime! :-)

One thing I always tell more junior developers who ask me about what the most valuable piece of information about programming in my whole career is: Get a good SCREEN, get a good KEYBOARD, and get a good CHAIR, the rest are just details.

Oh, also, make sure the screen(s) are perpendicular to any window, and watch that posture!

</walks off waving is cane in the air> :-)

I use 232" 4K monitors side by side; Before that I had 230" 1920x1200 (not 1080p!) side by side too; to me it's sufficiently "a wall" that I put them about 80cm from me, each angled a bit inward.

Quite frankly anything bigger and you get a kink in your neck by having to move your head so much!

I have a Zeiss 6x9cm film camera from 1936 that works wonder still. For tech gizmos, I have a HP 16C (the programmer's one) from 1864 that I still use most days! (I bought a second one about 15 years ago, as I grew terrified it would break down)