The source content for blog.juliobiason.me
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.

158 lines
8.0 KiB

<!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:&#x2F;&#x2F;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="&#x2F;">English</a></li>
<li class="sidebar-nav-item"><a href="&#x2F;pt">Português</a></li>
<li class="sidebar-nav-item"><a href="&#x2F;tags">Tags (EN)</a></li>
<li class="sidebar-nav-item"><a href="&#x2F;pt&#x2F;tags">Tags (PT)</a></li>
</ul>
</div>
</div>
<div class="content container">
<div class="post">
<h1 class="post-title">Commented Links for 2020-08-02</h1>
<span class="post-date">
2020-08-02
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
<a href="https://blog.juliobiason.me/tags/async/">#async</a>
<a href="https://blog.juliobiason.me/tags/ios/">#ios</a>
<a href="https://blog.juliobiason.me/tags/ios-14/">#ios 14</a>
<a href="https://blog.juliobiason.me/tags/facebook/">#facebook</a>
<a href="https://blog.juliobiason.me/tags/emacs/">#emacs</a>
<a href="https://blog.juliobiason.me/tags/telegram/">#telegram</a>
<a href="https://blog.juliobiason.me/tags/go/">#go</a>
<a href="https://blog.juliobiason.me/tags/copyleft/">#copyleft</a>
<a href="https://blog.juliobiason.me/tags/copyright/">#copyright</a>
<a href="https://blog.juliobiason.me/tags/patents/">#patents</a>
<a href="https://blog.juliobiason.me/tags/google/">#google</a>
<a href="https://blog.juliobiason.me/tags/algorithm/">#algorithm</a>
<a href="https://blog.juliobiason.me/tags/small-teams/">#small teams</a>
</span>
<p>Async/Await Fails, Facebook Complains About iOS 14, Telegram on Emacs, Go is
Google Language, Copyleft is Copyright, Google Blaiming &quot;The Algorithm&quot; Again,
Many Teams Fragmentations.</p>
<span id="continue-reading"></span><h2 id="beware-of-async-await"><a href="https://www.brandonsmith.ninja/blog/async-await">Beware of Async/Await</a></h2>
<p>Not much as &quot;careful with async/await&quot;, but &quot;don't use async/await in the
wrong way&quot;. And since async/await is in all the rage these days, in every
language, the same problem can happen in any of them.</p>
<h2 id="facebook-says-apple-s-ios-14-changes-could-hurt-its-ad-targeting"><a href="https://www.cnbc.com/2020/07/30/facebook-says-apples-ios-14-changes-could-hurt-its-ad-targeting.html">Facebook says Apple’s iOS 14 changes could hurt its ad targeting</a></h2>
<p>You know Apple may be doing something right for a change when Facebook says a
change will hurt them.</p>
<h2 id="telega-el-gnu-emacs-telegram-client-unofficial"><a href="https://github.com/zevlg/telega.el">telega.el: GNU Emacs telegram client (unofficial)</a></h2>
<p>Emacs kitchen sink just gets bigger.</p>
<h2 id="pkg-go-dev-is-more-concerned-with-google-s-interests-than-good-engineering"><a href="https://drewdevault.com/2020/08/01/pkg-go-dev-sucks.html">pkg.go.dev is more concerned with Google's interests than good engineering</a></h2>
<p>Again, I disagree with Drew in a lot of points, but I have to give it to him
when he gets the point right.</p>
<p>One of the points of Git is its decentalization. Surely the <em>de facto</em> use of
Git these days is not decentalized, but sadly centralized. And Google should
know better, as they had their own Git repository (GoogleCode, anyone) and
they just... fucked it up. And now, because they fucked it up, it seems they
want to just screw it further, so people don't realized how they fucked it up.</p>
<p>And, again, Go is Google language. It's not yours and they are not interested
in helping you there.</p>
<h2 id="open-usage-commons-a-warning"><a href="https://forum.palemoon.org/viewtopic.php?f=65&amp;t=24914">Open Usage Commons: a warning</a></h2>
<p>Let's ignore the &quot;world is ending&quot; tone of the post here, and let's focus
on what's here:</p>
<ol>
<li>To help you trademark your open source project, you give up all your
patents and such to the Open Usage Commons.</li>
<li>Let me repeat that: You <em>give up</em> all your <em>patents</em> to <em>someone else</em>.</li>
</ol>
<p>Copyleft works 'cause, in the very deep, it is a copyright law; you can sue
anyone that tries to steal your patents and trademarked content if, say, they
tried to take your trademark away, or used their position to overtake as the
&quot;the one who knows it&quot; from you.</p>
<p>One thing that remind me in the very start of the post is that GNU Foundation
does the same thing: If you want to make your application a GNU application,
you have to give your patents and trademarks to the GNU Foundation. While it
may appear the same, they are completely different:</p>
<p>If you want to release anything under any GPL (GPL, LGPL or AGPL), your
<em>don't</em> give anything to the GNU Foundation; it is still yours. If you want to
make your application a GNU application, the GNU Foundation still have to
accept it.</p>
<p>Trademark and copyright is <em>very</em> important to open source projects. Don't
give them up.</p>
<h2 id="google-blames-algorithm-for-adding-porn-titles-to-train-station-search-results"><a href="https://grahamcluley.com/google-porn-titles-train-station-search-results/">Google blames algorithm for adding porn titles to train station search results</a></h2>
<p>Once again, the mythical &quot;the algorithm did it!&quot; excuse. It's not &quot;sorry, we
did mess up with the training data&quot;, it's &quot;the algorithm&quot;.</p>
<p>Google idea of &quot;organizing the worlds data&quot; seems far and far away when they
don't even try to understand the data themselves.</p>
<h2 id="independence-autonomy-and-too-many-small-teams"><a href="https://kislayverma.com/organizations/independence-autonomy-and-too-many-small-teams/">Independence, autonomy, and too many small teams</a></h2>
<p>I've seen this: Because people buy the &quot;communication grows exponentially&quot; and
should make smaller teams -- which is correct. But they make &quot;smaller teams&quot;
and not &quot;smaller problems that can be dealt by smaller teams&quot;. And that's when
things fall apart.</p>
<p>Honestly, to me, this feels a lot like failing to have a proper architect,
someone who can see the big picture and think on ways to make all the pieces
come together.</p>
</div>
</div>
</body>
</html>