ivan/site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add 2024

Browse Source
This commit is contained in:
Rawley
2024-01-03 19:32:39 -06:00
parent eaaf1cf431
commit 4204132308
2 changed files with 61 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

59
2024.html Normal file
View File

@@ -0,0 +1,59 @@
<!DOCTYPE html>
<html>
<head>
<title>2024</title>
<meta name="description" value="Plans for 2024">
</head>
<body style="margin: 0; padding: 0; background-color: rgb(254, 249, 232)">
<div style="margin: 48px; width: 580px;">
<a href="/">&lt;&lt; back</a>
<h1>2024</h1>
<p>
2023 was a good year, but now it's 2024. Here's some of my technical plans for 2024.
</p>
<p>
<b>NOTE</b>: These are in no particular order.
</p>
<h2>Technology I plan to use in 2024</h2>
<ul>
<li>C++23</li>
<li>Perl 5.38 (Corrina!)</li>
<li>Raku</li>
<li>OCaml</li>
<li>Go</li>
<li>HTMX</li>
<li>Mojolicious</li>
<li>PostgreSQL</li>
<li>Memcached</li>
</ul>
<h2>Technology I want to learn more about in 2024</h2>
<ul>
<li>C++23</li>
<li>Lua</li>
<li>FreeBSD</li>
<li>Caddy</li>
</ul>
<h2>Technology I might learn in 2024</h2>
<ul>
<li>Common Lisp</li>
<li>Elixir</li>
<li>DragonflyBSD</li>
<li>FirebirdSQL</li>
<li>Nim</li>
</ul>
<h2>Technology I won't learn in 2024</h2>
<p>
It's not that I hate the following, it's just that they don't really interest me,
or the people behind them do not seem to value people using them (ala Rust).
</p>
<ul>
<li>Rust</li>
<li>Next.JS</li>
<li>Zig</li>
<li>Kubernetes</li>
<li>Terraform</li>
</ul>
<p>Have a safe an fun 2024.</p>
</div>
</body>
</html>

4
jpa-hibernate-stupid-performance.html
View File

@@ -50,8 +50,8 @@ public interface ARepository extends JpaRepository<A, UUID>, JpaSpecificationExe
</pre>
<p>
After applying these, the query time went down from 15 minutes to ... *drum-roll* ... 3 seconds. So please, for the love of all that is computationally efficient, force your JPA
to use <pre><code>OUTER JOIN</code></pre>, or even roll your own SQL, ORM's really are one of the biggest trade-offs, and they really can bite you. This is why tend to
stay in the <pre><code>DBI</code></pre> universe when I write Perl. It's funny shocking Ruby on Rails and Java developers with my ~15ms queries :D
to use <code>OUTER JOIN</code>, or even roll your own SQL, ORM's really are one of the biggest trade-offs, and they really can bite you. This is why tend to
stay in the <code>DBI</code> universe when I write Perl. It's funny shocking Ruby on Rails and Java developers with my ~15ms queries :D
</p>
<br>
<br>