dvratil

I don't think this has anything to do with modern trends - := is a formal way of writing assignment (the widely used = is actually an equality sign), and has already been present in Pascal for decades (and other languages as well).

We bought a breath monitor which is a desk/plate (about 20x50cm) with a small device attached via a long cable. You put the desk under the mattress and hang the device somewhere on the crib. When it's on and the kid would stop breathing, the device starts beeping really loud.

It already triggered a few times for us, luckily in all cases it was because we carried the baby from the crib a forgot the turn off the breath detector :-D

My dad (who's an architect but learned a little bit of programming on the university in the 80s programming on punch-cards) wrote a few simple QBasic programs with basic math and English vocabulary excercises for me when I started primary school. When I was 13 or so I found them again and ask my dad to explain it to me how it works. He did not remember much, but he showed me a few commands he remembered and that's when my world turned up-side down. I learned everything else myself from the built-in documentation (although I did not understand big portion of what the docs said) and spent almost all my time at the computer, writing stupid small programs in QBasic. The ultimate program I wrote was a silly Windows 95 clone with the Start menu, calculator and clock programs built in. At some point the code was too big that it wasn't possible to run it, because there wasn't enough memory left after QBasic loaded the source code. Worth saying that the computer had 4MB RAM, though, so it was probably just a few thousand LoCs.

From QBasic I went to Delphi, did a detour to PHP/HTML during high school and ended up at C++ some 14 years ago. Today I'm a SSE and I still love programming and everything about computers. Seeing this post (and all the cool stories in the comments) brough a big nostalgia hit - all those hours spent in front of my dad's Compaq Contura just writing one QBasic program after another (and playing Commander Keen, of course!)...there's a big box of flopp disks at my parent's house, I suddenly feel a big urge to go buy a floppy drive and see if any of my masterpieces have survived...

I suppose the title means that they have the source code physically, just no one can understand it, because the author had to remove all comments and shorten all variable names to one character so that the code would fit into the RAM.

Indeed things have improved massively in the past years. I think LVFS played a big role in that.

Reminds me when about ten years ago, working in an all-Linux company there was an issue with some Lenovo docking stations. I don't recall anymore what the issue was exactly, just that something wouldn't work properly when you plugged in a laptop with Linux. The problem was solved by a firmware upgrade, but upgrading the docking station firmware was possible only from Windows. So there was this one poor person in IT who had to install Windows on a spare laptop and then everyone would bring their docking station to them to upgrade the firmware...

The reason simply is that when no type is specified, `dig` performs a lookup for an A record (i.e. IPv4 address). When you manually specify AAAA, it does AAAA lookup, which returns IPv6 address. (details in `man dig`)

Does anyone else feel way too entertained by reading all this stuff about fb being down, all services relying on fb being down, and many services not relying on fb being down but being down due to being DDoS'ed by users trying to find out why fb is down?

It's DNS over HTTPS. It relies on the same system as plain DNS, so DoH won't really help in this case...

1) It can have new features - the are some upstreamed from KDE, and it's just about users coming with new proposals - nobody cames, no new features. Easy. 2) Why would you change something that needs no changing? 3) Lot of efort goes to QML, yes. Why not? 4) Maybe. Nothing prevents you from writing QWidget equivalent of the "cool" QML widget and upstreaming it.

Obsolete stuff is unmaintained. You can rest assured that QWidgets will be maintained and bugs will be fixed.

You can't add API into Qt 4, there are new additions only in Qt 5 and as someone already explained, a lot of stuff from KDE widgets is being upstreamed to Qt 5. New widgets and API are being added. There are no or just little changes simply for one reason: why change something that works? To change stuff just for the sake of change is not a justification and it would only make it more difficult for devs to port their apps from Qt 4 to Qt 5.