-
Notifications
You must be signed in to change notification settings - Fork 2
/
index.html
246 lines (233 loc) · 11.7 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
<!DOCTYPE html>
<html lang="en-US" dir="ltr">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Berlin.JS JSConf.eu 2019 Special</title>
<link rel="stylesheet" type="text/css" href="style.css" media="screen" />
</head>
<body class="sans-serif bg-js-yellow">
<nav class="pa4 flex flex-column">
<h1 class="ttu mv0 pl2">
<span class="headline">
berlin.js
</span>
</h1>
<h2>JSConf EU 2019 special</h2>
<h3 class="f2 f1-ns b ttu mt0 pt5">
Thursday May 30th
<br class="dn db-l" />
6pm at
<a href="https://goo.gl/maps/u6k4zWKcw5y" class="black link underline">co.up</a>
</h3>
</nav>
<main class="ph4">
<section class="mt4 mt5-ns">
<div class="mw9 center cf">
<section class="fn fl-l w-100 w-40-l pr4-l">
<h2 class="f3 f1-ns lh-title fw9 mb3 mt0 pt3 bw2">
Wait, what's this?
</h2>
</section>
<section class="lh-copy f5 f4-ns fl mt0-l measure">
Welcome to our <a href="http://2019.jsconf.eu">JSConf EU</a> special, a special occasion
for the Berlin JavaScript community to mix and mingle with people coming to JSConf EU
2019 from all over the world. We will have talks and plenty of space to meet new people.
See you there?
</section>
</div>
</section>
<section class="pt4 pt5-ns">
<div class="mw9 center">
<h2 class="f3 f2-ns ttu b ma0 bb bw2">
Featuring amazing speakers...
</h2>
<section class="lh-copy">
<div class="cf">
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Aaron Turner
</h2>
<h3 class="f4 f3-ns fw6 mb0">
WebAssembly for Javascript Developers
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
This talk covers the learnings and experiences of developing
<a class="black link underline" href="https://wasmboy.app">WasmBoy</a>. A Game Boy
Emulation Library for running Game Boy ROMs in both NodeJS and browsers, written
in
<a
class="black link underline"
href="https://github.com/AssemblyScript/assemblyscript"
>AssemblyScript</a
>.
</p>
</article>
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Bryan Hughes
</h2>
<h3 class="f4 f3-ns fw6 mb0">
The Node.js Event Loop: Not So Single Threaded
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
You've probably heard, and possibly lamented, that Node.js is single threaded.
It's true that all JavaScript executed by Node.js is run in a single thread. This
means each JavScript file you write, module you require, and even Node.js itself,
all contend for processing time. But JavaScript isn't the only code in Node.js.
There's also a lot of C++, most important of which is the event loop. One of the
event loops responsibilities is to manage a set of threads called the thread pool.
As it turns out, most C++ code in Node.js is multithreaded! Come learn how the
event loop works in detail, how it affects the performance of your app, and how
you can use this knowledge to your advantage!
</p>
</article>
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Kate Beard
</h2>
<h3 class="f4 f3-ns fw6 mb0">
Architect Your Culture Like You Architect Your Code
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
At a coding bootcamp, you have 3 months to go from zero to dev. Without feeling
empowered by a culture of psychological safety to ask all the questions, make
mistakes, and sometimes fail hard, you would never learn what you needed in the
time given. Imagine if all of the spaces we inhabit as coders throughout our
careers - the communities we're part of, the companies we work at, the teams we’re
on - offered this environment? How much more would we learn and contribute? This
talk offers insight from my time at Founders & Coders: how we achieved this
culture; what we did right and wrong; how you can translate our cohort's
experiences into actions; and how deliberately building a culture of psychological
safety can improve the communities, teams, and companies you’re a part of.
</p>
</article>
</div>
</section>
</div>
</section>
<section class="pt4 pt5-ns">
<div class="mw9 center">
<h2 class="f3 f2-ns ttu b ma0 bb bw2">
... and then some ⚡️
</h2>
<section class="lh-copy">
<div class="cf">
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Nico König
</h2>
<h3 class="f4 f3-ns fw6 mb0">
CSS speed dating for JavaScript people
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
A lot of people dislike CSS for no reason, either one did not take the time to
learn the fundamentals as they did with JavaScript, or sometimes one just don't
know about specific superpowers of CSS. Let's take 10 minutes to quickly go
through crucial CSS fundamentals and dive into some nifty techniques for your next
front-end adventures.
</p>
</article>
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Glen Maddern
</h2>
<h3 class="f4 f3-ns fw6 mb0">
Frontend Application Bundles, the Docker of Frontend
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
Frontend apps are on the cusp of a revolution—React is about to launch a streaming
server renderer that massively improves performance on both low-end and high-end
devices. It's a new dawn for performance & accessibility, but raises another
question? How should we host the server component? Can we do that without vendor
lock-in? Enter FABs (Frontend Application Bundles), a portable, compact,
immutable, server-side JS format that lets you deploy anything from static sites
or Next.js to full custom server-rendered React apps anywhere that can run JS,
like Cloudflare Workers, Lambda@Edge, Now, etc. Finally, we can have a toolchain
that supports the full breadth of frontend projects & server environments, without
locking everything to a single host. My talk aims to draw parallels between the
server world of a decade ago & the frontend world of today. In the past, companies
like AWS & Heroku were innovating & offering exciting new products, but users had
to make a choice of which one to use and lock-in their development to target that
platform. Today, it's exciting offerings from platforms like Now and Netlify, but
all their innovation is locked down inside their ecosystem. Docker changed that in
a profound way, and FABs are poised to do the same thing. So this talk is a
prediction of the future—that with React's new streaming renderer, a lot more
companies will be looking to add a server-side component, and a standard,
interoperable bundle format like FABs makes that much more accessible.
</p>
</article>
<article class="pv2 fl w-100 w-third-l pr4-l">
<h2 class="f4 f3-ns fw6 mb0">
Alejandro Oviedo
</h2>
<h3 class="f4 f3-ns fw6 mb0">
You Don't Know Your Dependencies
</h3>
<p class="f5 f4-ns measure lh-copy mt0">
If you’re building applications chances are your dependency tree is in the order
of hundreds. That can easily scale up to at least a thousand for large
applications (like popular OS projects Ghost or Keystone). Join me in my hindered
journey to address a big elephant in the room: managing dependencies. Updating a
dependency or following common practices shouldn’t have to be a mysterious thing.
What’s the right thing to do in your package.json? Exact versions? Using a caret?
What’s the reason behind lockfiles? What type of tooling is out there? I’ll
present answers from my research to these common questions.
</p>
</article>
</div>
</section>
</div>
</section>
<section class="mt4 mt5-ns">
<div class="mw9 center cf">
<section class="fn fl-l w-100 w-40-l pr4-l">
<h2 class="f3 f1-ns lh-title fw9 mb3 mt0 pt3 bt bw2">
We care about human beings
</h2>
</section>
<section class="lh-copy f5 f4-ns fl mt0-l measure">
Our goal is to have an awesome, inclusive and safe community meetup where people meet,
hang out together, chat, listen to talks, exchange ideas and make new friends.
<strong>
Any harmful or discriminating behaviour will not be tolerated and results in the
offending person being expelled from the meetup.
</strong>
For details on what kinds of behaviour are not tolerated and consequences for violating
these rules, we refer to the
<a href="http://rubyberlin.github.io/code-of-conduct" class="black link underline"
>Berlin Code of Conduct.</a
>
</section>
</div>
</section>
<section class="mt4 mt5-ns">
<div class="mw9 center">
<h2 class="f3 f1-ns lh-title fw9 mb3 mt0 pv3 bt bb bw2">
Kindly sponsored by
<a href="http://co-up.de/" class="black link underline"> co.up community space</a>
</h2>
</div>
</section>
</main>
<footer class="pa4 pv5-l cf">
<div class="f5 lh-copy fl w-100">
<div class="fl-ns w-100 w-20-l pr3-m pr4-l underline">
<a href="http://twitter.com/berlinjs" class="black link dim b">
We're on Twitter
</a>
</div>
<div class="fl-ns w-100 w-20-l pr3-m pr4-l underline">
<a href="http://www.meetup.com/Berlin-JS/" class="black link dim b">
And on Meetup
</a>
</div>
<div class="fl-ns w-100 w-20-l pr3-m pr4-l underline">
<a href="https://berlinjs-slack.herokuapp.com/" class="black link dim b">
We also have a Slack
</a>
</div>
</div>
</footer>
</body>
</html>