Comment UFOs (Score 3, Funny) 82
Literally.
Literally.
She fears that the introduction of 5G mobile networks will kill her
The sad irony is that the needless anxiety itself might actually have a detrimental effect on her health - which will undoubtedly be attributed to the EMF.
ActiveX? Visual Interdev?! Wow, that takes me back...
"It's 106 miles to Chicago, we've got a full tank of gas, half a pack of cigarettes, it's dark, and we're wearing sunglasses."
This article is from 2012. If you want up-to-date stats see LWN's regular reports, e.g. here is a recent one for 4.18:
https://lwn.net/Articles/76069...
(Though Red Hat is indeed still right up near the top.)
Yes, there will be lazy-ass bonespur children who just use this as an excuse to get out of a difficult assignment
But laziness is not why people feel reluctant to present, it's anxiety. A lot of people (myself very much included) just need that push to actually do the presentation, and then figure out that it's not quite as horrible an experience as anticipated; but if given the option we'd just as soon not do it in the first place. Of course everyone is different, but it seems to me this is not about recognising difference as much as it is about helping people to overcome their fears and gain skills that will be really beneficial to them in life.
Some of our most brilliant authors, scientists, mathematicians, etc were people who had crushing social anxiety and it would be a damn shame to penalize them so early in the game because of it.
Sure, but the best of those were the ones that didn't let their social anxiety get in the way of doing great things; in order to do that they had to figure out how to deal with it. Choosing to opt out doesn't seem like a real way of dealing with it to me.
I'd recommend watching this talk:
https://www.youtube.com/watch?...
or if you prefer, the excellent-as-usual LWN summary:
https://lwn.net/Articles/71231...
I don't like the language-specific package manager situation either, but the way these languages split things up does not lend itself well to the distro packaging model either unfortunately.
Then either there was something wrong with your printer or your guest is a complete moron.
Holding it wrong, obviously.
i undertake
i need kraut
rude intake
dunk tea ire
tuna reek id
take run die
Here's a segment from a TV show back in the 50s where he touches a little bit (in passing) on that, at least at that time:
What made you hate it specifically?
Similar story here, except now I use qmmp. It owes pretty much everything to WinAmp in terms of design, just as the ones you mention do.
However, OpenEmbedded has always been a nightmare. No matter how scrupulously I have followed instructions, I have never got anything of any complexity to actually build. It would take a long while to convince me that it was worth the time and effort that's been spent on it.
I'm sorry you've had that experience, but I can say that whilst we do indeed have a complex system, many, many other users by now have been able to use it successfully, from new users to small consultancies right up to large corporations. I'll also say that if the last time you tried it was more than a few years ago you were probably using something quite different from what we deliver today - it has certainly improved leaps and bounds since the handhelds.org days.
To do this efficiently, they encourage separating the distribution's own changes into a set of patch files that are applied on top of the upstream. But this does not scale well for device manufacturers, who generally have a lot of changes involved in supporting a particular hardware design, and quite frankly git is a much better tool for managing the patches than bitbake.
There's nothing that prevents you from pointing to a git repo in a bitbake recipe, in fact if it's more than a few patches, I would naturally encourage it - and it's pretty much assumed for kernel recipes.
You jest of course, but the sad thing is none of that stuff really matters in whether an app is successful or not - history has shown time and again that developers can write absolutely terrible code resulting in an app that's slow, crashes frequently and is painful usability wise, but despite all that if it does something useful or entertaining then users will still pay money for it. The basic idea is what counts.
You knew the job was dangerous when you took it, Fred. -- Superchicken
