You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
187 lines
11 KiB
187 lines
11 KiB
11 months ago
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
|
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||
|
|
|
||
|
|
<!-- Enable responsiveness on mobile devices-->
|
||
|
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape-->
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover">
|
||
|
|
|
||
|
|
<title>Julio Biason .Me 4.3</title>
|
||
|
|
|
||
|
|
<!-- CSS -->
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css">
|
||
|
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class=" ">
|
||
|
|
|
||
|
|
<div class="sidebar">
|
||
|
|
<div class="container sidebar-sticky">
|
||
|
|
<div class="sidebar-about">
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a>
|
||
|
|
|
||
|
|
<p class="lead">Old school dev living in a 2.0 dev world</p>
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<ul class="sidebar-nav">
|
||
|
|
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/">English</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li>
|
||
|
|
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="content container">
|
||
|
|
|
||
|
|
<div class="post">
|
||
|
|
<h1 class="post-title">Links for 2020-03-04</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-03-04
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/privacy/">#privacy</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/capacitors/">#capacitors</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/biowaste/">#biowaste</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/ibm/">#ibm</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/clang/">#clang</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/microservices/">#microservices</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/material-design/">#material design</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/ultra-rich/">#ultra-rich</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/meritocracy/">#meritocracy</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/rust/">#rust</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/github-actions/">#github actions</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/disability/">#disability</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/the-witcher/">#the witcher</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>Interesting links for 2020-03-04.</p>
|
||
|
|
<span id="continue-reading"></span><h1 id="leaked-document-shows-how-big-companies-buy-credit-card-data-on-millions-of-americans"><a href="https://www.vice.com/en_us/article/jged4x/envestnet-yodlee-credit-card-bank-data-not-anonymous">Leaked Document Shows How Big Companies Buy Credit Card Data on Millions of Americans</a></h1>
|
||
|
|
<p>Alright, this is stupid: "We removed the user information and put an unique ID
|
||
|
|
in place" is completely bullshit. I know it, you know it, but it seems it is
|
||
|
|
the general way of selling user information around.</p>
|
||
|
|
<p>Even if someone removes the unique ID but keep other information, things are
|
||
|
|
still traceable: For example, how many people do you think are white, male,
|
||
|
|
above 40, not married, living in a specific suburb (I won't even claim the
|
||
|
|
street itself) that bought some product? I bet you could pretty much find me
|
||
|
|
with just that, 'cause that description would fit 0.00001% of the city
|
||
|
|
population, anyway.</p>
|
||
|
|
<p>Maybe we need to rethink this "sell information" thing, since privacy is long
|
||
|
|
gone. We need laws that, if you want to sell collected information, you need
|
||
|
|
to put one single vector per information. That means that, if you want to sell
|
||
|
|
that information, you need to have one dataset for skin color, which says a
|
||
|
|
white person bought some product; another dataset for sex, which says a male
|
||
|
|
bought some product; and so on. No unique IDs.</p>
|
||
|
|
<p>It's not perfect, but I believe that would get more traction than simply say
|
||
|
|
"don't capture any data", 'cause, seriously, it is not working.</p>
|
||
|
|
<h1 id="aerogel-from-fruit-biowaste-produces-ultracapacitors-with-high-energy-density-and-stability"><a href="https://www.sciencedirect.com/science/article/pii/S2352152X19309077">Aerogel from fruit biowaste produces ultracapacitors with high energy density and stability</a></h1>
|
||
|
|
<p>Hey, that's cool that we are finding ways to recycle stuff like biowaste for
|
||
|
|
something like capacitors, but I have to wonder if that, in our current world,
|
||
|
|
that means people will produce durian and jackfruit just to let it rot to
|
||
|
|
create biowaste for the capacitors, instead of something simple, like feed
|
||
|
|
people.</p>
|
||
|
|
<h1 id="ibm-to-transition-their-z-os-power-aix-compilers-to-being-llvm-clang-based"><a href="https://www.phoronix.com/scan.php?page=news_item&px=IBM-Will-Use-LLVM-Clang-Stack">IBM To Transition Their z/OS, POWER + AIX Compilers To Being LLVM/Clang-Based</a></h1>
|
||
|
|
<p>I have to wonder if the move is something like this: IBM bought RedHat; RedHat
|
||
|
|
sells Linux solutions; IBM stronghold are the mainframes, which are dying; by
|
||
|
|
changing the base system from their compiler to Clang, they are also saying
|
||
|
|
"hey, people who build stuff for our platforms, you should use Clang now!",
|
||
|
|
which would make transition those codebases to Linux a bit simpler.</p>
|
||
|
|
<p>But yeah, just wondering if that makes sense.</p>
|
||
|
|
<p>(Also, Clang <em>Fortran</em>?)</p>
|
||
|
|
<h1 id="microservices-combinatorial-explosion-of-versions"><a href="https://worklifenotes.com/2020/03/04/microservices-combinatorial-explosion-of-versions/">Microservices – Combinatorial Explosion of Versions</a></h1>
|
||
|
|
<p>I have a strong problem with this post: Basically, the problem it points
|
||
|
|
happens if you keep two different versions of the <em>same microservice</em> running.</p>
|
||
|
|
<p>That's not how you should build your fleet -- even if it is possible and not
|
||
|
|
that hard.</p>
|
||
|
|
<p>One point of upgrading a microservice is keeping backwards compatibility with
|
||
|
|
their inputs; if you deploy a new version what receives a complete different
|
||
|
|
input, you can either add both input interfaces in the new service or just add
|
||
|
|
a brand new microservice that just converts the old input to the new one --
|
||
|
|
which increases the fleet, but it's not that a big point.</p>
|
||
|
|
<p>One thing to keep in mind with this upgrade policy is that you <em>need to
|
||
|
|
monitor the inputs</em>. Once the old input version is not being send anywhere
|
||
|
|
else, you can remove the input/disable the microservice -- with the second
|
||
|
|
option being less intrusive, as you won't need to redeploy the updated
|
||
|
|
microservice with the old input support.</p>
|
||
|
|
<h1 id="stop-using-material-design-text-fields"><a href="https://www.matsuko.ca/blog/stop-using-material-design-text-fields/">Stop using Material Design text fields!</a></h1>
|
||
|
|
<p>Or you could, for instance, to drop Material Design completely.</p>
|
||
|
|
<p>Yes, I'm not a fan of Material Design. I'm not UX expert, but I feel that it
|
||
|
|
fails in a lot of places -- not only text fields.</p>
|
||
|
|
<h1 id="the-self-attribution-fallacy"><a href="https://www.monbiot.com/2011/11/07/the-self-attribution-fallacy/">The Self-Attribution Fallacy</a></h1>
|
||
|
|
<p>"Intelligence? Talent? No, the ultra-rich got to where they are through luck
|
||
|
|
and brutality."</p>
|
||
|
|
<p>"If wealth was the inevitable result of hard work and enterprise, every woman
|
||
|
|
in Africa would be a millionaire."</p>
|
||
|
|
<p>I keep saying this around, and one thing that resonates with what I say would
|
||
|
|
be: It's not that the ultra-rich are brutal, brutality is what made them rich.</p>
|
||
|
|
<h1 id="void-terminal-based-personal-organizer"><a href="https://github.com/void-rs/void">Void: terminal-based personal organizer</a></h1>
|
||
|
|
<p>Not sure if it falls into any of my workflows, but HOLY COW, graphs in the
|
||
|
|
console?</p>
|
||
|
|
<h1 id="building-rust-for-multiple-platforms-using-github-actions"><a href="https://medium.com/@jondot/building-rust-on-multiple-platforms-using-github-6f3e6f8b8458">Building Rust for Multiple Platforms Using Github Actions</a></h1>
|
||
|
|
<p>While focused on Rust, because the focus are the Github Actions, one could
|
||
|
|
"easily" port for other languages (for different levels of "easy").</p>
|
||
|
|
<h1 id="web-crawler-in-rust"><a href="https://rolisz.ro/2020/03/01/web-crawler-in-rust/">Web crawler in Rust</a></h1>
|
||
|
|
<p>"How to Draw an Owl", but for Rust crawler. :)</p>
|
||
|
|
<p>I got most of the stuff, but I guess anyone learning Rust would suddenly see
|
||
|
|
the later listing and think "This is nuts!"</p>
|
||
|
|
<h1 id="the-cost-of-indirection"><a href="https://www.joshmcguigan.com/blog/cost-of-indirection-rust/">The Cost of Indirection</a></h1>
|
||
|
|
<p>"How a newbie, a seasoned and a veteran Rust coder solve this problem", but...
|
||
|
|
for Rust.</p>
|
||
|
|
<p>I'm not that interested in the times, but in the different implementations of
|
||
|
|
the same thing in the same language. May be interesting 'cause some
|
||
|
|
implementations may make more sense than other to some people.</p>
|
||
|
|
<h1 id="toss-a-coin-to-your-bitcher"><a href="https://uncannymagazine.com/article/toss-a-coin-to-your-bitcher/">Toss a Coin to Your Bitcher</a></h1>
|
||
|
|
<p>A disabled person commenting on the way "The Witcher" series deal with
|
||
|
|
disabled people, in this case, Yennefer. Honestly, even when I watched, I
|
||
|
|
couldn't see Yennefer as disabled, 'cause... well, one 'cause although I think
|
||
|
|
about my own disability (glasses), I don't see that much different than any
|
||
|
|
other "normal" person (although I still think Gordon Freeman is the <em>only</em>
|
||
|
|
short-sighted "hero" I ever saw), and I know what happens with Yennefer in the
|
||
|
|
future (thanks for the games).</p>
|
||
|
|
<p>Still, it's eye-opening to see this kind of post to get a view of how disabled
|
||
|
|
people see disabled characters.</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|