wkrp

In my (minor) experience Timescale works fine. The developer experience is good and it is very convenient to be able to JOIN against your hypertables. My only real complaints are operational (no logical replication, normal postgres update complaints), but man Clickhouse is really slick. I wrote some small reviews of the two in my submission history if you want a bit more detail.

Really it would be more like Nebulex/Cachex which provide a really nice caching interface across ETS (what Mnesia is built off of) or other data stores.

To be fair, there is more than just print debugging. You have access to tools like red(x)bug https://github.com/nietaki/rexbug, the Elixir-LS project has Debug Adapter Protocol support. And in my opinion, the REPL (and decent software architecture) makes it easy to investigate your code by just running the functions as needed (even if your live production system if you want).

Modern tactics are to use every radar around via datalink (AWACS, Ground Station, stealthy drones flying ahead). The onboard radar is last resort, but still very capable.

I agree with you. The good news is that it looks like some of the alternate clients are focusing on it. https://commet.chat/ has voice channels (video rooms but default to camera off), and cinny's element call support PR defaults to camera off in video rooms as well iirc.

There are tools such as deploy-rs, colmena, and morph that let you deploy nixOs configs using nix. I can't speak to how good they are personally, I use ansible to push my nix configs.

Thanks!

I wrote a blog post about my experience using Clickhouse on a side project. You normally see discussions of Clickhouse involving large data sets and complex problems. I previously used Timescale to store the same data, so this also covers a comparison of the development experience between the two.

I was a little unclear, I think Timescale performs quite well. Just that in my (very limited) experience, Clickhouse performs better on the same data.

I actually have a blogpost on my experience with it here: https://www.wkrp.xyz/a-small-time-review-of-timescaledb/ that goes into a bit more detail as to my use case and issues I experienced. I'm actually half-way through writing the follow up using Clickhouse.

As detailed in the blog post, my data is all MMO video game stats such as item drops. With Timescale, I was able to join an "items" table with information such as the item name and image url in the same query as the "item_drops" table. This way the data includes everything needed for presentation. To accomplish the same in clickhouse, I create an "items" table and an "items_dict" dictionary (https://clickhouse.com/docs/sql-reference/dictionaries) that contains the same data. The Clickhouse query then JOINs the item_dict against item_drops to achieve the same thing.

If you know the shape of your data, you can probably whip up some quick scripts for generating fake versions and inserting into Timescale to get a feel for storage and query performance.

I was using Timescale for a small project of mine and eventually switched to Clickhouse. While there was a 2-4x disk space reduction, the major benefits have operational (updates & backups). The documentation is much better since Timescale's mixes their cloud product documentation in, really muddying the water.

Despite that, man it is really nice to be able to join your non-timeseries data in your queries (perhaps the fdw will allow this for clickhouse? I need to look into that). If you don't have to deal with the operations side too much and performance isn't a problem, Timescale is really nice.

Lix is a fork of nix-the-language and nix-the-program. In doing so, they forked the det-sys installer to install Lix instead of Nix.

/messages might be a legacy endpoint compared to a newer /sync. I know Matrix has been working hard on their sliding sync api.

I don't have any examples from my code, so the best I can do is the relevant documentation.

Its all done using phx-hook https://hexdocs.pm/phoenix_live_view/js-interop.html#client-... . While the documentation makes it look a bit more fancy, it is just a JS object with mounted() function. I set up my columnDefs and gridOptions in that function, and add the handleEvent() callbacks that are where I get data from the elixir side using send_update/3. Ag-grids vanilla JS documentation has been very helpful for how to use it without the benefit of react/vue,

LiveView is so nice for full stack development, it's a wonderful palette cleanser after a day of enterprise programming.

I can attest to its JS interoperability. I have a project that streams data realtime into a liveview page that uses a combination of ag-grid, maplibre-gl, vega+lite, and Google's model-viewer all at once. All it takes is a little bit of JS plumbing to handle create and updates.

That's something ghost.org does by default. I unknowingly ran into the same issue for my blog.

Well for one, the Army would have to start worrying about bases with full landing strips, pilot training, the bureaucracy and command structure that would be required to run the squadrons. They would need mechanics that know how to repair them, people that know how to arm and refuel them.

You end up doing a good amount of work just to try and protect a very expensive plane from Air Force politics. Ideally, the Air Force would just settle on an inexpensive prop plane that could perform the same missions as the A-10 at much less of the cost.

I'm not knowledgeable on how effective a helicopter is for CAS.

You've just complicated your logistics and added a whole bunch of personnel requirements for the Army to have any significant amount of planes for use in combat. Not to mention, the Army has helicopters to perform this exact same function already.

I think he means that if you dont have a VR ready graphics card, that costs another $200.

I'm also a mostly backend dev (C#) and Vue didn't take too long to get started. Outside of getting node/yarn set up on my machine, I was able to create a project and start fiddling with Vue pretty quickly.

I found https://www.taniarascia.com/getting-started-with-vue/ as a better initial starting point compared to the Vue website.

I've been using Vue for the past few weeks on a for-fun project and have been loving it once I grasped the basic concepts.

You are not paid a salary while in a military academy, you are given a stipend from which they deduct food, board, and other costs.

It is a stipend, and stipends are allowed by the NCAA. The handbook in your link calls it a stipend. Since there is a hard cap on how much cash you can actually take from your "pay", I would call it a stipend.

I know for the Naval Academy, you don't get the salary. Even if you were previous enlisted you are no longer paid your salary, though I believe the 4 years in the academy count towards retirement.

That already happens now. See Ole Miss: https://www.sbnation.com/college-football/2017/2/23/14704892...