1,565 karma · joined April 15, 2016
We also took insane child mortality numbers and all kinds of defects for granted.
Our mothers still consumed food that has a tendency to contain/grow listeria. Then it was found in several cases where the reason for the death of the child was not known.
Now pregnant women (at least in Europe) are strongly advised to avoid products from raw milk and uncooked meat (hams and salami.
Things change, and not without a reason.
The argument from the less concerned was something along: Better safe then sorry, no one can say what larger amounts of estrogen will do to a boy well below 1.
The amount of oat you have to feed a cow to get a single litre is not even close to the literal handful you need for an oat-based milk - let alone the time and how of work that went into caring for the cows, handling the mess, etc.
It should not even be close. We simply industrialized the whole diary thing, and consider it essential.
And I say this as someone who cannot live without cheese. It should just be way more expensive and reflect the cost it has on the environment/society.
Here we buy litres or half, and we adore milk, mostly 3.5%. The non-diary alternatives are not even allowed to be called milk (they are now drinks).
The wikipedia link above has 2009 as the earliest date.
In Austria you would find random scenic train rides on TV whenever you would switch on the TV in the middle of the night at least from 2002 onward, if not earlier... And I don't think this started in Austria.
Several repairs on iPhones and other Apple hardware are exactly that: not authorized by Apple, unless done by Apple itself.
Autonomous lawn mowers are everywhere in my neighborhood, albeit being quite expensive. Some even have two for front and back.
Unless you have a very big yard or a very small yard it is quite literally "the thing to have" right now.
This is a huge market in central Europe.
2. Accept the fact that you will always have a shallower knowledge than people that focus on specific things. Be humble, there will always be someone smarter in the room with knowledge on his favorite topic that you will not be able to match unless you dive way deeper than you are currently willing to go.
3. Realize that your drive for knowledge and understanding is actually a natural thing - I would argue that this is the case for most people, and while some have found ways to satisfy this "need" with random redirection activities (mostly "entertainment" and shopping), some have found "their thing" and are investing their energy into a specific thing - which sometimes is utterly useless (as in "useful for the greater good, humanity, or for someone") , sometimes can be turned into something useful for oneself or for others (e.g. "money in the bank").
4. As soon as you make your hobby your job, it is no longer a hobby, it is now your job. And for most people that means they no longer enjoy it nearly the same way they did before. A envy the few lucky ones where this is not true. You now need a new hobby.
5. Don't forget to enjoy life. If you found something that makes you happy, that is purely awesome! But also realize that you will have to do things that at the same time (1.) keep you from doing what you love, but (2.) also enable you to do what you love. Some people call it their "job". You need money and time, your family needs money and time, your hobby needs money and time. Find a way to sustain all that, so you can do and enjoy the things that make you happy.
Soon you would only want to play on closed/invite-only servers, since the guys that "wanted to be nasty" didn't go into their own little corners, but were glad to spoil it for everyone else. And even then the cheaters invested a lot of time and effort to sneak into closed circles to ... I don't know, simply cheat?
Guys just randomly using your key (at a point were Half-Life was really cheap and easy to come by) were also a constant annoyance.
So Valve had to do something, and this was the Steam client, cheat detection, and a constant cat and mouse game to save the experience for players and assets/investments for the developers and in effect their "platform".
Never underestimate the desire of idiots to ruin it for everyone else.
Before that, MoBo manufacturers even made extensive use of additional chips for networking, USB, mora SATA ports, RAID and what not, which could make the whole system more complicated/fragile (all the additional drivers!).
I nowadays try to avoid that and aim for boards close to "reference" (whatever the chipset offers out of the box).
Or am I just thinking about an entirely different thing...?
It really does not fit the narrative of what AMD did with Zen so far, that's for sure.
This would have been my main reason to build an AMD system, although I was easy to win, I always built AMD systems IIRC... And I ended up postponing it again and again, since I don't game and the reasonable (budget) options were always lagging behind regarding technology/efficiency - most of all, my Phenom (actually a rebranded Athlon with 2/6 cores disabled) was still doing OK. Now there will be AM5... Didn't follow the news, is it supposed to live as long as AM4?
Would it even pay off for AMD to repeat that effort?
Skoda at least (I expect all of the newer VWs, Audis, Seats, ...) use the built in mobile uplink to gather massive amounts of data about usage, e.g. how often the car is "pushed hard", or driven dangerously. Nobody knows exactly how they will use that, maybe to limit guarantees? - but if the cars is yours and yours only, this shouldn't matter, right? It shouldn't happen in the first place. Well, not anymore I guess.
The manufacturers will not limit these possibilities to a certain drive-train technology - why should they? It is also not limited to "newer companies", all of them will do it. Further, if the customer likes these models, the manufacturers (and increasingly more of them) will expand their offering.
Heck, the majority of cars on the street where I live are not legally owned anyway, they are all leased and people like that a lot.
The manufacturer could make a cost/benefit-analysis, concluding that building a machine that lasts approx. these 1000 runs but no longer, and paying for recycling afterwards is cheaper than building something that lasts and is recyclable.
Also, replacing it every ~200 cycles with just another cheaply built throwaway-machine could also become a viable business model. Why should the manufacturer care, if it becomes cheaper?
You could also make the manufacturer pay for recycling anyway - which is the case in the EU for several device classes IIRC, no need for a rental model to establish that. For some devices this means that the manufacturer has to take it back when you are done with it. The problem of course is that this is directly paid for by the customer - and by itself does not change anything.
But my argument is that it wouldn't for the rental model either.
Being able to carry it home, will give you our your conspirators more than enough time.
An acquaintance of mine had his new and shiny bike stolen in front of his flat on a busy street over night. Well secured with awesome locks to the communal bike rack.
The thief simply cut through the rack pipe, and took bike and lock as is. Battery-powered heavy duty tools that are now easy to come by will get you anything left on the street - no matter how well secured...
The best deterrent I found? No air in the tires. Bike will remain there for weeks.
Had a loved bike stolen from me on the bus stop since I had no time to lock it. My brother found it in the schoolyard on his way to work with empty tires (tube lost air very slowly).
I used the RT_PREEMPT patches in 2012/13, so my insight is most certainly rusty, dated and might even be wrong here or there. But still:
First of all, RT_PREEMPT is about realtime as in "hard realtime" for control systems. This has nothing to do with "small latency" (the cycle time could be minutes), but with deadline guarantees, allowing control loops over (realtime) network protocols, etc.
Then, almost all important additions of the RT_PREEMPT patches were mainlined one after the other. The last bits were never mainlined although essential for full preemptive kernel AFAIR, but:
Most "modern" (>15 years) OTS-platform (x86, x86-64) is increasingly unfit for realtime - no matter what kernel/OS you use, because your CPU is not in control. Beginning with DMA, later also "management engines", modern platforms might dethrone your CPU on the lowest ring entirely and for as long as they want, to serve a request/interrupt, e.g. fan control, while your CPU wakes up 500ms later realizing that it missed quite a few deadlines. (Fan control is a bad example, but DMA is not. Also Intel ME!) This makes almost all Linux PCs inherently unable to reliably keep these guarantees.
This puts the whole "hard realtime on Linux"-project in a pickle - since it requires full control over the platform. And most shops that go this route, will take the small additional step of using something well tested and with vendor support.
And the rest buys platform and OS with support from a trusted vendor.
I didn't say nuclear does generate CO2. I said it produces waste, and that I have a definition of renewable that does not include nuclear.
You first shifted the goalposts and said it is "green" (what is "green"?? who defines "green"?), citing sources. I discredited the sources, since it these are just announcements, made by (political) institutions, where politicians lobby for a re-labeling of certain energy sources, because it suits their agenda.
None of this makes nuclear "renewable" in my book.
IMO the world renewable implies something in the line of "self-regenerating"/"grows naturally"/"replenishes" and producing toxic waste in my world-view is orthogonal to that meaning.
And don't try to explain that nuclear waste is non-toxic, I think my interest in discussing this really ends there.
I won't adopt definitions forced by countries that also want natural gas plants to be categorized as "green" ("who cares what they emit?!")
Renewables fluctuate. Nuclear is not great at scaling, and most reactors cannot be shut down without taking weeks and months for safe re-starting.
Nuclear is good for base load. And countries that have a lot of (really expensive) nuclear to cover their base load, have zero incentive to invest into renewables, since its output would just become surplus.
For broad adoption of renewables, we need to accompany it with (hopefully clean) solutions that can buffer and restore surplus energy efficiently and most importantly scale up and down really fast, to smooth out the fluctuations. Keeping a constant 50 Hz is becoming increasingly difficult with renewables.
In the past Austria used to store (nightly) surpulus energy from german nuclear reactors and (more recent also renewables) and getting paid to do so, to feed it into the own network and also selling abroad during daytime. This was stopped because it was putting a lot of strain on the north-south bottlenecks in the German power network, aggravated by large wind farms in the north, that became capable of covering the whole German power use for short periods of time.
In the German speaking world everyone knows what a hp is (PS), how much his car has, his past cars had, in which configurations their car is available... although the kW is what is printed on the documents since ages now.
Nobody likes change. Some people still complain about the Euro, and that the DM was so much better... At least it is not called ECU.
Yeah, because what I want is to buy a watch if I want to pay with my phone. Great solution!
> Complain to your bank / switch to a better bank.
Ah, yes, the "Switch-banks-because-your-phone-is-broken"-Trick, didn't think of that!
> LineageOS shoves the commit log right in your face, you can have a pretty good idea when it's really important to update.
Yeah, but the CVEs and firmware bugs are not and will never be in the commit logs. And even if they are, when I install an update on my phone OTA, I obviously will not pull up the commit log! How much time do you think I have?!
That's what the "Security Level"-indicator in the device settings/info is for.
> Really? Performance and stability are typically the reasons to switch to custom.
Yes, really. My LineageOS was always crappy slow on my BQ Aquaris, for every version. The camera is simply unusable. Every update brings another random bug. Since a few weeks it will lose WiFi, needing manual intervention, sometimes just 3 seconds after connecting.
If you want a working device, and not tinker with it all the time, or risk being stranded without certain functionality, you are safer with a device with a decent stock from a manufacturer that updates it diligently.
Most of the time it is unusable and slow. It randomly crawls, i.e. opening a browser, an input field, or the GMail App will make the device halt for about 10s. It will never get the new Android. Camera was always crappy with LineageOS. WiFi is broken since a few weeks and will constantly just vanish, needing to connect manually.
I almost only ran Cyanogen or Lineage on my devices, if not stock. I tinkered a lot with my Cyanogen installs back in the days, trying to even the bumps and failings.
Any device that has a decent stock image will run better with stock than any LineageOS or CustomROM in my experience.
Most devices never get custom ROMs any longer than you would get regular updates anyway (since newer Android versions would not run on this chip).
Custom ROMs are a mess anyway:
- Untrusted sources
- Random annoying bugs (What, you need a camera?? Pff)
- Flaky "Android-Experience" (Yeah, you might be able to install Google Apps... after the 6th try)
- Device is "untrusted" - no Google Wallet or banking apps without yet another hack
- "Security Updates? You can get a full image every 2 weeks if you want that, but no idea what is included and what will break, sorry"
- Performance and stability of the device usually takes a big dive
Most importantly: You cannot build AOSP for a device, if there is no support from the firmware (Qualcomm), which is the main reason why there are no Android updates in the first place - at least that's the problem nowadays.
> Facebook ENABLED this coverup.
Wat? How is this not considered a conspiracy theory? 5 comments down an article that discusses fact checking...
Hm, maybe my sarcasm-meter is off by a notch again. dunno.
Research based on or involving code/models/algorithms should always be accompanied by a code drop. Nobody expects the code to be of good quality.
Everything else is not reproducible - and against the scientific codex (IMO).
I read so many papers that claim incredible results, and wondering how they implemented their models in this particular simulator (close to impossible with only what is out there), only to find that there is just nothing to be found, anywhere. No repo, no models, no patch. NIL.
Sending an E-Mail? No response.
Further, anyone could just claim anything this way. Why bother doing any real work?
What if there is a small error in the code?
Wouldn't it be better to know that? In a scientific sense, searching for "the truth"?
The goal is not to ostracize automatic updates, but to have faster fixes.
Or to separate security updates from feature updates, but I think this ship has long sailed for modern browsers.