codeburst.io

Honestly, I had no idea that "monkey-patching" was a term, I thought it was something Op just made up :-).

I have just looked it up, and it indeed is a term [meaning something](https://en.wikipedia.org/wiki/Monkey_patch). Even meta-magic seem to be a term, but less defined seems like.

I don't think we need AST for monkey-patching, but it can be argued that each program can be converted to an AST. Anyway, less important.

The "monkey-patching" seem to basically mean anything that changes the runtime somehow. The example in Python on Wikipedia article just changes the value of a global variable. In Lisp we have many, many tools which can change code at runtime, I would even argue that Lisp is all about flexibility and "monkey-patching" since we already write AST and have the entire symbol table and the compiler available to us at runtime. Functions are just objects like any others and we can install any object in the function slot of an symbol, we can wrap it in our own function and install that one, everything is a list and dynamic in some way, so we can add slots to classes and structs if we want etc.

For meta-magic I found [this one article](https://betterprogramming.pub/the-magic-of-metaprogramming-732f0300a5c7) and [this one](https://codeburst.io/laziness-i-meta-programming-34ef4abdafc6) that seems to use the term in a sense as what we normally do with macros in Lisp or with templates in C++. The other one is a bit lengthy and I really didn't have patience nor time to…

I dunno. I'm a long time reddit user, but I'm done with it. It's really time to just dig into some self hosted shit with a reasonable ingress like Cloudfront or whatever works and just dump this crap. People still say "and my axe" on reddit. We don't need this siloed internet anymore. mTLS is SUPER easy to implement and in my opinion is the future of the internet. I've got some courseware as well as some simple VMs, containers, helm charts, juju charms and I've got a process for building custom distros with GPU support and clusters inside clusters that can federate with enterprise org level OIDC.

I'm a bit ahead of the curve I think? I don't know. All this talk about the big guys, we are at a tipping point. It's happening now. That's why they are trying to regulate AI IMO. They understand that we are moments away from being able to bridge all of our own resources in a way that isn't siloed.

We can host it all ourselves now. It's fine. The future is going to be weird... but really it's just getting the internet back that got hijacked from us 20ish years ago or whatever.

If you want to try yourself, since I can't recommend my gear because I have to finish the rest of the rollout, KubeSail doesn't get enough attention. Easy to set up on any computer you have laying around, but their gizmo is pretty cool too. I think their app store is neat and I could get my grandma hosting her own K8s cluster to the web with this tutorial.

https://codeburst.io/ddclient-c9a6ac1d8f81

Throw…

while most rdbms-based projects will continue using foreign key constraints (and all will be referentially cast in stone), and postgressives will enjoy 100000x query speedups by remembering to include your hornsnaggle_tree_index_lookup_speeder_upper index,

there is a certain fanatical mindset from the rdbms world that sounds a bit like:

never forget
always include jquery with every web app you make.
it's made by real profeshunalz who know more than you and lots of people already included it and you should simply just learn to accept that all front-end web problems have already all been solved by jqueremy and you should simply refactor it all in terms of jqueremy.
anything else is korrupshun.
In other words, always only ever consider the same tools and techniques. LOL

A mere search for other database types produces pages upon pages of "why sql is beating nosql" and all stack overflow answers always doom you to the 7th level of hell for anything but 3rd normalized form. hey let's all use lookup tables for many to many. it's a cult. it's nuts.
anyone who has spent any amount of time with database-backed applications is surely aware of the tradeoffs they are making when choosing non-relational databases of any kind.

The obsession with forcing every all all use cases into the rdbms mindset makes me say "well then, let's just flatten everything even further into mapped key-value a la ohm." in which one encodes the key with path info and the value with the value, etc.

if the…

So I've my self used Lombok but I've been using Kotlin lately. IMHO Kotlin if far far superior in terms of how it provides appropriate constructs that are patches to a stale language (hopefully new release cycle fixes it).

So far I've observed with libraries like Lombok there is a smaller community (compared to language community) that vets the idea; and the features are opinionated to that particular community. Which results into fragmentation; just as example https://immutables.github.io/ and https://github.com/google/auto are two libraries providing features like factories and immutable value classes. Then you get articles like https://codeburst.io/lombok-autovalue-and-immutables-or-how-to-write-less-and-better-code-returns-2b2e9273f877 for improving your code.

This in my opinion doesn't hurt as long as you are a small company. But when your code is going to be used across teams with different opinions, and language doesn't enforce a single way to define construct these kind of byte-code mangling ideas fall apart. I've personally people complain about Lombok and they hate it every bit. Doing these constructs at language level removes debate, and unifies how people in larger community. I hope newer versions of Java move fast enough to make something simple like `@Cleanup` a thing of past. I will highly encourage everyone to try Kotlin too; it's almost transparent drop-in with better syntax.

Sure, object-relational impedance mismatch is a problem, but if you're going to throw the baby out with the bathwater, you need to propose alternatives. Luckily for us, this is not the author's only post...

The author's followup article advocates instead for building your own in-process persistence system for each application, with no persistent data structure other than a (non-write-ahead) log, even for an application the size and scale of Stack Overflow itself: https://codeburst.io/doing-without-databases-in-the-21st-century-6e25cf495373

I post this only because "name 20 things wrong with this article" might be a good take-home exercise for a student, or as a weeding exercise for recruiting... except that, on the off chance the student/candidate were to fail at said exercise and buy into the content unironically, I would have caused irreparable and irresponsible harm to their learning process, their future businesses, and the safety of their customers' data.

Seriously, what we have here is a fundamental misunderstanding of ACID, of the very idea that a computer might crash at an arbitrary point in a program, of the general importance of distributed systems, of safe software deployment, of parallelism, and of the very idea that a schema might evolve over time. It saddens me to know that this type of advice exists and receives a platform.

Hello everyone!

Today, we are launching a major release of Reactivesearch (v2).

Key highlights:

- Compatible with any Elasticsearch index hosted anywhere.

- Comes with over 30 pre-built components which are common in building data-driven UIs.

- Can be extended to work with your own UI components. (Really handy if already have a designed component and want it to work with Elasticsearch).

- We also provide designer templates of all our components, which is helpful for creating pixel-perfect UIs.

- Consistent API for web and native mobile apps (Native version of the lib is in alpha today)

You can see a post for building an e-commerce UI using Reactivesearch - https://codeburst.io/how-to-build-an-e-commerce-search-ui-with-react-and-elasticsearch-a581c823b2c3.

A lot of sweat and love has gone into building this, would appreciate any helpful feedback, improvements we can make, or issues you may be seeing. :)