PageSourceSearch

https://www.hibnet.org/

html hibnet.org collected 2026-10-06 18:00:20 UTC 10,093 bytes, 180 lines download raw bytes

1<!DOCTYPE html>
2<html lang="en">
3<head>
4<meta charset="utf-8">
5<meta name="description" content="I don't talk much, I don't think less.">
6<meta name="viewport" content="width=device-width, initial-scale=1">
7<title>hibNet</title>
8<link href="assets/css/all-nocdn.css" rel="stylesheet" type="text/css">
9<meta name="theme-color" content="#5670d4">
10<meta name="generator" content="Nikola (getnikola.com)">
11<link rel="alternate" type="application/rss+xml" title="RSS" hreflang="en" href="rss.xml">
12<link rel="canonical" href="http://www.hibnet.org/">
13<!--[if lt IE 9]>
13<script src="assets/js/html5.js"></script>
13<![endif]--><link rel="prefetch" href="blog/experimenting-around-react-scalability/" type="text/html">
14</head>
15<body>
16<a href="#content" class="sr-only sr-only-focusable">Skip to main content</a>
17
18<div class="pagewrap">
19<div id="header" class="clearfix">
20    <div id="nav">
21        <ul id="main-menu-links" class="links clearfix">
22<li class="active">
23<a href=".">Blog <span class="sr-only">(active)</span></a>
24                </li>
25<li>
26<a href="http://www.scoop.it/t/fun-for-geeks">Fun <span class="glyphicon glyphicon-new-window" aria-hidden="true"></span></a>
27                </li>
28<li>
29<a href="attic/">Attic</a>
30                </li>
31<li>
32<a href="about/">About Me</a>
33
34            
35        </li>
36</ul>
37</div>
38    <div id="logo">
39        <a href="."><img src="images/me/1.png"></a>
40        <span class="slogan">I don't talk much, I don't think less.</span>
41    </div>
42</div>
43
44<div class="container" id="content" role="main">
45    <div class="body-content">
46        <!--Body content-->
47        <div class="row">
48            
49            
50
51    
52
53
54    
55<div class="postindex">
56    <article class="h-entry post-text" itemscope="itemscope" itemtype="http://schema.org/Article"><header><h1 class="p-name entry-title"><a href="blog/experimenting-around-react-scalability/" class="u-url">Experimenting around React's scalability</a></h1>
57        <div class="metadata">
58            <p class="byline author vcard"><span class="byline-name fn" itemprop="author">
59                Nicolas Lalevée
60            </span></p>
61            <p class="dateline">
62            <a href="blog/experimenting-around-react-scalability/" rel="bookmark">
63            <time class="published dt-published" datetime="2018-01-12T09:30:57+02:00" itemprop="datePublished" title="2018-01-12 09:30">2018-01-12 09:30</time></a>
64            </p>
65        </div>
66    </header><div class="p-summary entry-summary">
67    <div>
68<div class="paragraph"><p>Writing backend code has always been my preference because it allows more structured code, since backend often means Java in my industry, the web. On the other hand frontend coding has always been a pain because of the mess. Javascript may be the culprit, but probably more because it allows to be messy more than being messy itself. Then one day I tested Angular (the v1) and I had the wow effect: first time I felt like an engineer writing Javascript code. Then appeared React: awesome, about same idea but just a library not a full framework. Our team at <
68a href="http://www.scoop.it/">Scoop.it</a> adopted it and embraced it.</p></div>
69<div class="paragraph"><p>We embraced it so much that we felt the pain in writing big React pages. Raw React doesn’t scale well. People already faced this scalability issue. They came with the idea of Flux (thank you people at Facebook to have shared it with us).</p></div>
70<div class="paragraph"><p>While reading about Flux I started designing a way of managing the state. Later some smart guys of our team dived and fell in love of Redux, an open source implementation of Flux. I learned from them and I made improvement to my design. Here is the story.</p></div>
71<p class="more"><a href="blog/experimenting-around-react-scalability/">Read more…</a></p>
72</div>
73    </div>
74    </article><article class="h-entry post-text" itemscope="itemscope" itemtype="http://schema.org/Article"><header><h1 class="p-name entry-title"><a href="blog/parallel-universe/" class="u-url">Parallel Universe</a></h1>
75        <div class="metadata">
76            <p class="byline author vcard"><span class="byline-name fn" itemprop="author">
77                Nicolas Lalevée
78            </span></p>
79            <p class="dateline">
80            <a href="blog/parallel-universe/" rel="bookmark">
81            <time class="published dt-published" datetime="2013-10-04T16:30:57+02:00" itemprop="datePublished" title="2013-10-04 16:30">2013-10-04 16:30</time></a>
82            </p>
83        </div>
84    </header><div class="p-summary entry-summary">
85    <div>
86<div class="paragraph"><p>Lately I saw a lot of excitement around writing asynchronous code, non blocking, lock free, etc… This is good as we are moving towards more parallelized/concurrent softwares and libraries. There are nice performance improvements ahead. But I fear that we are going into having code hard to understand and therefore to debug.</p></div>
87<p class="more"><a href="blog/parallel-universe/">Read more…</a></p>
88</div>
89    </div>
90    </article><article class="h-entry post-text" itemscope="itemscope" itemtype="http://schema.org/Article"><header><h1 class="p-name entry-title"><a href="blog/tweaking-search/" class="u-url">Tweaking the search</a></h1>
91        <div class="metadata">
92            <p class="byline author vcard"><span class="byline-name fn" itemprop="author">
93                Nicolas Lalevée
94            </span></p>
95            <p class="dateline">
96            <a href="blog/tweaking-search/" rel="bookmark">
97            <time class="published dt-published" datetime="2013-09-13T14:43:13+02:00" itemprop="datePublished" title="2013-09-13 14:43">2013-09-13 14:43</time></a>
98            </p>
99        </div>
100    </header><div class="p-summary entry-summary">
101    <div>
102<div class="paragraph"><p><a href="blog/you-know-for-search">Setting up a search engine</a> in one thing, but to make it actually work, in the human sense, is another story. Having a search which basically does a grep on all your content is the bare minimum you can do, but what makes Google awesome is that when you search something, you find <em>quickly</em> <em>good</em> content. When you search something, you should find <em>good</em> results, and the good results <em>first</em>. Here some of the things we did to make the Scoop.it search looks good.</p></div>
103<p class="more"><a href="blog/tweaking-search/">Read more…</a></p>
104</div>
105    </div>
106    </article><article class="h-entry post-text" itemscope="itemscope" itemtype="http://schema.org/Article"><header><h1 class="p-name entry-title"><a href="blog/you-know-for-search/" class="u-url">You know, for search</a></h1>
107        <div class="metadata">
108            <p class="byline author vcard"><span class="byline-name fn" itemprop="author">
109                Nicolas Lalevée
110            </span></p>
111            <p class="dateline">
112            <a href="blog/you-know-for-search/" rel="bookmark">
113            <time class="published dt-published" datetime="2013-07-13T16:27:56+02:00" itemprop="datePublished" title="2013-07-13 16:27">2013-07-13 16:27</time></a>
114            </p>
115        </div>
116    </header><div class="p-summary entry-summary">
117    <div>
118<div class="paragraph"><p>As soon as you start having a good amount of data, browsing them is not anymore a solution and you need a search engine. It happened to us some time ago at <a href="http://www.scoop.it">Scoop.it</a>. We are pretty happy with what we put in place almost 2 years ago. Let’s revisit the story.</p></div>
119<p class="more"><a href="blog/you-know-for-search/">Read more…</a></p>
120</div>
121    </div>
122    </article><article class="h-entry post-text" itemscope="itemscope" itemtype="http://schema.org/Article"><header><h1 class="p-name entry-title"><a href="blog/its-time-share/" class="u-url">It's time to share</a></h1>
123        <div class="metadata">
124            <p class="byline author vcard"><span class="byline-name fn" itemprop="author">
125                Nicolas Lalevée
126            </span></p>
127            <p class="dateline">
128            <a href="blog/its-time-share/" rel="bookmark">
129            <time class="published dt-published" datetime="2013-06-24T
12908:27:22+02:00" itemprop="datePublished" title="2013-06-24 08:27">2013-06-24 08:27</time></a>
130            </p>
131        </div>
132    </header><div class="p-summary entry-summary">
133    <div>
134<div class="paragraph"><p>Now that have learned and practiced software engineering a good amount of time, I think I can share back some of my experiences and discuss with you about some hopfully interesting ideas.</p></div>
135<p class="more"><a href="blog/its-time-share/">Read more…</a></p>
136</div>
137    </div>
138    </article>
139</div>
140
141
142
143    
144
145
146
147
148
149        </div>
150        <!--End of body content-->
151
152        <footer id="footer">
153            Contents © 2026 <a href="mailto:[email protected]">Nicolas Lalevée</a> - Built with <a href="https://getnikola.com" rel="nofollow">Nikola</a> - Delivered by <a href="https://www.netlify.com/">netlify</a> <hr>
154<a rel="license" href="https://creativecommons.org/licenses/by-nc-sa/4.0/">
155    <img alt="Creative Commons License BY-NC-SA" style="border-width:0; margin-bottom:12px;" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png"></a>
156
157            
158        </footer>
159</div>
160</div>
161
162
163            
163<script src="assets/js/all-nocdn.js"></script>
163<script>$('a.image-reference:not(.islink) img:not(.islink)').parent().colorbox({rel:"gal",maxWidth:"100%",maxHeight:"100%",scalePhotos:true});</script>
163<!-- fancy dates -->
163<script>
164    moment.locale("en");
165    fancydates(0, "YYYY-MM-DD HH:mm");
166    </script>
166<!-- end fancy dates -->
167</div>
168
169<script>
vendor: 345 bytes, lines 169-175
169
170  (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
171  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
172  m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
173  })(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
174
175  ga('create', '
175UA-41053753-1
vendor: 39 bytes, lines 175-177
175', 'auto');
176  ga('send', 'pageview');
177
178</script>
178
179</body>
180</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.