Rearrange and edit
This commit is contained in:
@@ -31,7 +31,7 @@ information.
|
||||
|
||||
# Stands
|
||||
|
||||
There were many stands run by all the FOSS projects we know and love. The
|
||||
There were stands run by all the FOSS projects we know and love. The
|
||||
stands were an odd experience compared to a "normal" conference.
|
||||
|
||||
Generally at conferences you have a few big corporations and a bunch of smaller
|
||||
@@ -66,18 +66,6 @@ and available to view on [the FOSDEM site](https://fosdem.org/2019/).
|
||||
Here's a sample of those I attended. I recommend you follow the links and check
|
||||
out the videos yourself if you find them interesting.
|
||||
|
||||
## [Java 4..12, Kotlin, Code Coverage and their best friend — bytecode: scandals, intrigues, investigations](https://fosdem.org/2019/schedule/event/kotlin_code_coverage_bytecode/) --- Evgeny Mandrikov
|
||||
|
||||
A talk I really enjoyed that I selected largely at random. Evgeny Mandrikov,
|
||||
works on [JaCoCo](https://www.jacoco.org/jacoco/). They build code coverage
|
||||
information by looking inside Java class files which allows them to work with
|
||||
multiple JVM languages. Unfortunately, it turns out that `javac` outputs code
|
||||
that... isn't quite what you'd expect. It can also be extremely different for
|
||||
the same code depending on the target JVM version. The talk had a series of
|
||||
interesting examples of compiler output bytecode demonstrating these issues and
|
||||
proving that when you're reverse engineering, sometimes you just have to make a
|
||||
guess.
|
||||
|
||||
## [What's new in PostgreSQL 11](https://fosdem.org/2019/schedule/event/whats_new_in_postgresql_11/) --- Magnus Hagander
|
||||
|
||||
My colleague Magnus presented what's new and magical in PostgreSQL 11. Some of the ones that interested me were:
|
||||
@@ -92,6 +80,18 @@ And of course general improvements in performance, with better use of parallelis
|
||||
|
||||
If you're a PostgreSQL user I'd suggest checking the talk out yourself to get all the details.
|
||||
|
||||
## [Java 4..12, Kotlin, Code Coverage and their best friend — bytecode: scandals, intrigues, investigations](https://fosdem.org/2019/schedule/event/kotlin_code_coverage_bytecode/) --- Evgeny Mandrikov
|
||||
|
||||
A talk I really enjoyed that I selected largely at random. Evgeny Mandrikov
|
||||
works on [JaCoCo](https://www.jacoco.org/jacoco/). They build code coverage
|
||||
information by looking inside Java class files which allows them to work with
|
||||
multiple JVM languages. Unfortunately, it turns out that `javac` outputs code
|
||||
that... isn't quite what you'd expect. It can also be extremely different for
|
||||
the same code depending on the target JVM version. The talk had a series of
|
||||
interesting examples of compiler output bytecode demonstrating these issues and
|
||||
proving that when you're reverse engineering, sometimes you just have to make a
|
||||
guess.
|
||||
|
||||
## [Netflix and FreeBSD](https://fosdem.org/2019/schedule/event/netflix_freebsd/) --- Jonathan Looney
|
||||
|
||||
This was a slightly disappointing talk. I was hoping for some information about
|
||||
|
||||
Reference in New Issue
Block a user